What is a service catalog — and why your business already has one

What is a service catalog?

A service catalog is a structured, written list of the services a business provides, described from the customer's point of view. Not a marketing brochure and not a price list, though it overlaps with both — it's the operational answer to "what do you do, for whom, under what conditions?"

The term comes from ITIL, the service-management framework used by large IT organisations, but the idea is universal. A dental practice, a lettings agency and an MSP all have one, whether or not anyone has ever typed it out.

You already have one — it's just in people's heads

Ask three staff members what happens when a customer requests a refund and you'll get three procedures. Each one is a fragment of the real catalog, held in memory and applied inconsistently. That's fine at five requests a day and quietly ruinous at fifty.

The unwritten catalog fails in predictable ways: new staff take months to absorb it, answers vary by who picks up, and when the person who knows the awkward cases leaves, the knowledge leaves with them. Writing it down converts personal memory into a business asset.

What goes in a written catalog?

A useful catalog is more than a list of names. For each service it captures:

• What the service is and who it's for
• Availability — when and under what conditions it's offered
• Capacity — how much of it you can actually deliver
• Prices, where they're fixed enough to state
• The request types that surround it — bookings, changes, cancellations, complaints — ranked by how often they actually occur

Why did nobody write it down before?

Because historically the writing was an enterprise project. Platforms like ServiceNow, Jira Service Management and Freshservice all assume a catalog exists or can be built, and building one traditionally meant months of workshops, consultants and forms — a cost structure that only made sense for organisations with an IT department to run it.

Generation changes the economics. ReQuest DESK's AI Builder reads the documents you already have — price lists, service pages, procedure notes, old emails — or a plain-language description, and drafts the catalog for you: services, request types ranked by probability, and per-step autonomy settings you review before anything goes live. What took a quarter now takes days, often one working day, with no IT specialists and no enterprise contract.

The catalog is what the AI answers from

There's a second reason the catalog matters now: it's the foundation for trustworthy automation. ReQuest DESK grounds every answer only in your published catalog and knowledge base — nothing invented, nothing improvised, and coverage mapping shows you exactly which requests still lack a grounded answer.

That's the quiet reversal worth noticing. The service catalog used to be the paperwork you produced after adopting service management. Now it's the starting point — and if the framework behind it interests you, ITIL for small business covers how the rest of the discipline scales down just as well.