ITIL for small business: what actually matters (and what to skip)

Why does ITIL feel like it was written for someone else?

Because it was. ITIL grew up inside large IT departments, and the packaging shows: certification tracks, change advisory boards, process owners for the process owners. Enterprise platforms built around it carry the same weight — long implementations, specialist admins, pricing that assumes a department will use it.

But the packaging is not the point. Strip it back and ITIL is simply a written-down answer to one question: when someone asks us for something, what happens next? Small businesses need that answer more than enterprises do, because there is no slack to absorb the misses.

The five ideas worth stealing

You do not need the whole framework. You need the handful of ideas that stop requests falling through gaps. In our experience they are:

• A service catalog — a plain list of what you actually offer, so requests land against something defined. If you have never written one, start with what a service catalog is.
• Request types — the recurring asks under each service, so 'can you…' emails stop being one-offs and start being routed work.
• An owner for every request — one name, not a shared inbox. No request should exist without someone accountable for it.
• Committed response and resolution times — a promise you state up front, then measure yourself against.
• A consistent resolution flow — the same steps every time, so quality does not depend on who picked it up.

What can you safely skip?

Skip the certifications — nobody's dental practice runs better because someone passed a foundation exam. Skip the committees and the months of process-design workshops. Skip anything whose purpose is coordinating between departments you do not have.

The test is simple: does this help the next request get answered faster, by the right person, in a consistent way? If not, it is enterprise scar tissue, and you are allowed to leave it behind.

The consultant used to be the entry fee. Not any more.

The honest reason small businesses skipped ITIL was never laziness — it was the cost of translation. Turning 'here is roughly what we do' into a structured catalog with request types and resolution steps used to take a consultant weeks.

That translation step is now the part AI does well. ReQuest DESK's builder reads your existing documents — or a plain-language description of the business — and generates the catalog, the likely request types ranked by probability, and a resolution flow for each. You review and adjust rather than author from scratch; you can see how the process works end to end.

Each generated request type also carries the discipline pieces: an owner, a committed resolution time, and an eight-phase resolution chain that runs the same way every time. You get the substance of ITIL without adopting its ceremony — typically live in days, not quarters.

Start smaller than feels respectable

Pick your ten most common requests and define only those: what the request is, who owns it, how fast you commit to resolving it, and the steps in between. That single page beats an unread framework binder.

Then let the definitions grow from evidence. Watch which requests arrive that you have not defined, and add types as the pattern proves itself — the discipline is in giving every request an owner and a deadline, not in how much process you wrote on day one.