The Favor List Is Not a Business Model
A small IT business often starts with a simple promise: help people solve computer problems. That works until every request becomes a custom job, every quote starts from a blank page, and a five-minute favor turns into unpaid follow-up work.
An IT service catalog fixes that problem by naming the work you sell, defining the boundary of each service, and giving you a repeatable way to quote it. You do not need a corporate portal or a thick policy manual. You need a short list that makes common work easier to explain, deliver, track, and invoice.
Your IT Service Catalog Build Plan
- The Favor List Is Not a Business Model
- The Fast Answer: Start With Four Buckets
- Define the Work Before You Price It
- Build a Catalog You Can Quote From
- Add a Decline List Before Scope Creep Arrives
- A 90-Minute Catalog Setup Checklist
- Turn the Catalog Into a Repeatable Sales Tool
- Frequently Asked Questions
- References
The Fast Answer: Start With Four Buckets
- Best for: Solo IT consultants, freelance sysadmins, network installers, and micro-MSPs that handle a mix of support and project work.
- Main takeaway: Start with 12 to 20 clearly named services divided into four buckets: break/fix support, projects, recurring support, and add-ons.
- Time, cost, or effort: A first usable version can be built in about 90 minutes using a spreadsheet, a document, or the service-item area in your ERP.
- Biggest mistake to avoid: Listing vague services such as “computer support” without boundaries, assumptions, or a billing method.
- When not to use this: Do not publish a detailed public price list for work that still requires discovery, vendor coordination, or site-specific planning.
A service catalog is not the same thing as a giant menu. Its job is to reduce repeated decisions. The catalog should answer a few questions before the next call arrives: What is the service called? What problem does it solve? What is included? What is excluded? How is it billed? What information must the client provide first?
For a small IT provider, the simplest structure is usually four buckets.
| Catalog Bucket | Typical Examples | Best Billing Style | Main Boundary to Define |
|---|---|---|---|
| Break/fix support | Remote troubleshooting, printer setup, malware cleanup assessment, user account help | Hourly or minimum service block | When troubleshooting becomes a project |
| Projects | New computer setup, office Wi-Fi upgrade, email migration, workstation deployment | Fixed scope or phased quote | Deliverables, assumptions, and change requests |
| Recurring support | Monthly maintenance, patch review, backup review, monitoring, helpdesk access | Monthly agreement | Included hours, response targets, and exclusions |
| Add-ons | After-hours work, rush scheduling, hardware sourcing, travel outside normal area | Fixed add-on or hourly | Approval before work begins |
Define the Work Before You Price It
A useful catalog describes a client outcome with enough detail to support a quote.
Compare these entries:
| Weak Entry | Stronger Entry |
|---|---|
| Computer support | Remote workstation troubleshooting, up to 60 minutes, for one user and one device |
| Network setup | Small-office Wi-Fi assessment with coverage review, device count, and written next-step recommendations |
| Backup help | Quarterly backup restore check for one defined backup system, with a recorded result and follow-up actions |
The stronger entries remove ambiguity. The client can understand what they are buying, and you can recognize when the request has moved outside the original scope.
Use six fields for every catalog item
Create one row for each service and complete these fields:
- Service name: Use plain language that a client can repeat in an email.
- Client problem: State the situation that usually triggers the request.
- Included work: List the normal deliverables or time boundary.
- Excluded work: Name the most common extras that require approval.
- Billing method: Choose hourly, fixed-price, recurring, or discovery-first.
- Intake questions: Ask for the details needed before scheduling or quoting.
A catalog item called New Workstation Setup might include operating-system updates, standard application installation, printer connection, user profile setup, and a basic handoff. It might exclude data recovery, application licensing, line-of-business software troubleshooting, and after-hours migration. Those exclusions are not fine print. They are how a one-person shop protects the rest of the week.
Mini scenario: the “quick” new-PC request
A client buys three laptops and asks for “the usual setup.” Without a catalog, the job can quietly expand into password resets, old-device cleanup, email migration, printer troubleshooting, cloud-drive questions, and vendor calls.
With a catalog, the quote can separate the work:
- Three standard workstation setups
- One data-transfer add-on per device
- One line-of-business application review
- One optional after-hours scheduling add-on
The work did not become complicated because you used a catalog. The catalog revealed that the request was already more complicated than it sounded.
Build a Catalog You Can Quote From
Start with your last 10 to 20 completed jobs. Look for repeated work that consumes time, creates confusion, or appears on invoices under inconsistent names.
Build the first version in five steps
- Export or review recent invoices and tickets. Highlight recurring requests, repeated deliverables, and common extras.
- Group similar work. Separate support calls, projects, recurring services, and add-ons.
- Write one standard entry for each repeated task. Use the six fields above.
- Choose a billing method. Decide whether the entry is hourly, fixed-scope, recurring, or discovery-first.
- Test the list against three recent jobs. Check whether the catalog would have made the quote faster and the boundary clearer.
A spreadsheet is enough for the first version. Once the wording is stable, place the services in Odoo, ERPNext, or any other ERP that supports service items. ERPNext documents service items for service businesses, while Odoo supports service products and timesheet-based billing.
Match the catalog to the type of work
| Service Type | Use This When | Advantage | Tradeoff |
|---|---|---|---|
| Hourly support | The cause is uncertain and troubleshooting time varies | Easy to start without overpromising | Clients may want a spending limit |
| Fixed-scope project | Deliverables and assumptions are clear | Easier for the client to approve | Scope changes need a separate process |
| Recurring support plan | The client needs ongoing maintenance or response coverage | Creates predictable service expectations | The agreement must define limits |
| Paid discovery | The job is too unclear to quote responsibly | Produces a better project plan | Some prospects may resist paying before implementation |
Do not force every job into a fixed price. A catalog should reduce guesswork, not hide uncertainty. When the unknowns are large, sell a discovery step first.
Add a Decline List Before Scope Creep Arrives
A service catalog becomes more useful when it includes work you will not accept, work you will refer out, and work that requires a separate specialist.
The decline list is an internal tool. It prevents the stressful moment when a client asks for unfamiliar work and the answer becomes an automatic yes.
Common decline-list categories
- Work that requires licensing, certifications, or insurance you do not carry
- Unsupported legacy systems with no practical rollback path
- Data recovery jobs that should go to a specialist
- Projects with no written point of contact or approval process
- Rush work when the client will not approve an after-hours or expedited rate
- Requests that require access the client cannot document or authorize
A decline list shows where your responsibility begins and ends.
A 90-Minute Catalog Setup Checklist
Use this as a first-session SOP.
Minutes 0 to 20: collect the raw material
- Review your last 10 to 20 invoices, tickets, or service notes.
- Copy repeated jobs into a scratch list.
- Mark the jobs that produced confusion, unpaid follow-up, or repeat questions.
Minutes 20 to 45: create the first four buckets
- Move each repeated job into break/fix, projects, recurring support, or add-ons.
- Remove duplicate wording.
- Identify jobs that should become paid discovery rather than instant quotes.
Minutes 45 to 70: write the boundaries
- Add included work.
- Add excluded work.
- Choose the billing method.
- Add the intake questions needed before scheduling.
Minutes 70 to 90: test the catalog
- Rebuild three recent quotes using the new entries.
- Check whether the service names make sense to a nontechnical client.
- Add an internal decline list.
- Save version 1.0 and set a date to review it after the next five quotes.
Turn the Catalog Into a Repeatable Sales Tool
The catalog helps before a quote, during delivery, and after the job closes. It gives you a starting point, reveals extras that need approval, and creates consistent invoice wording.
This is where software can help, but software should follow the process. You can configure service items in Odoo, ERPNext, Zoho One, or any other ERP or service-management platform that fits your operation. The important step is defining the service first. A confusing catalog inside expensive software is still a confusing catalog.
Use this next-step framework
- If you quote from memory, build the spreadsheet version first.
- If your service wording changes on every invoice, standardize your top 12 entries.
- If every “small project” expands after approval, add exclusions and a change-request process.
- If clients repeatedly ask for the same maintenance work, turn that work into a recurring service option.
- If you cannot estimate the job responsibly, sell discovery before implementation.
The First Version Only Needs to Be Useful
Your first IT service catalog does not need 100 entries. Start with the work you already perform. Give each repeated job a clear name, a boundary, and a billing method, then review the catalog after five quotes. The goal is to turn familiar technical work into a process you can repeat, explain, and invoice.
Frequently Asked Questions
Q1. Does a small IT business need a formal service catalog?
A1. It does not need a large enterprise portal. It does need a consistent list of repeatable services with boundaries and billing methods. A spreadsheet or document is enough for the first version.
Q2. Should prices appear in the service catalog?
A2. Use pricing when the work is standardized. Keep discovery-first or custom-quote services flexible when the environment, device count, vendor involvement, or migration risk can change the effort.
Q3. Can the catalog be managed in Odoo?
A3. Yes. Odoo can support service products and time-based billing workflows. ERPNext or any other ERP with service items can also work. Define the services before configuring the software.
Q4. How often should the catalog be reviewed?
A4. Review the first version after five quotes. After the wording stabilizes, review it quarterly or whenever a repeated extra keeps appearing during delivery.
By: Marcus Irizarry
Why trust this: This post is written for solo IT operators and micro-MSPs, using a practical service-operations framework and current vendor documentation for service items and time-based billing.
Last updated: 2026-06-10
Disclosure: No paid placement influenced this post.
References
- Freshworks: Real-World Service Catalog Best Practices — Explains the service-catalog concept as a structured inventory of services that users can request.
- ERPNext Documentation: Item — Notes that service businesses can create an item for each service offered.
- Odoo Documentation: Track and Bill Time — Documents service products configured for timesheet-based billing.
0 Comments