Thinking About Implementing ITIL at Your MSP? Read This Before You Spend Another Hour or Dollar on It.
November 11, 2026

Thinking About Implementing ITIL at Your MSP? Read This Before You Spend Another Hour or Dollar on It.

You Don't Run an IT Department. You Run a Business That Sells IT. So Why Are You Using a Framework Built for the Other One?

If you're trying to decide whether your MSP should take on ITIL by yourselves, my answer for most small and mid-size shops is no, at least not as a full implementation. I

TIL is general guidance for IT service management, but it doesn't get into the stuff that eats an MSP owner's week, like pricing, standardizing across clients who all run different tools.

It also doesn’t make sure your techs hit their numbers. What works better is documenting your own systems, putting a standard and a metric on each one, and building all of it from what your clients value and who you are as a company. Borrow the good parts of ITIL where they fit.

I want you to swap in your own when you finish reading, because mine is made up. Say your MSP brings in $2 million a year. Divide that by 2,000 working hours and your time is worth $1,000 an hour.

Now think about last week. Say ten of your hours went to things somebody else on your team should have handled. A quote you priced yourself because nobody else was sure how. An escalation you jumped into. A question that only you knew the answer to. That's $10,000 a week of your time, about $520,000 a year, spent on work that isn't yours to do.

Nobody decided to spend it. It just happened, because the business only works when you're in the room.

What is ITIL, anyway?

ITIL started inside the UK government. The Central Computer and Telecommunications Agency put it together in the 1980s to bring some consistency to how government ran its IT, and the first set of books came out in 1989. It's been through a handful of rewrites since. ITIL 4 came out in 2019 and organizes everything into 34 practices (things like incident management, change enablement and service level management) along with seven guiding principles, including "start where you are" and "keep it simple and practical." ITIL 5 was announced in January 2026 and the Foundation certification followed in February, with the same 34 practices plus new guidance on AI governance and on managing products and services together.

 

If a client or an insurance questionnaire ever asks you about this, the thing to know is that ITIL is guidance and not a standard. Individuals can get ITIL certified, but a company can't. When an organization needs to prove it follows a service management standard, the one they usually mean is ISO/IEC 20000-1.

Should your MSP implement it yourselves?

It might not fit your organization very well. ITIL is broad on purpose, so it skips most of what you actually fight with: how to price and package against the cheaper guy down the street, how to standardize across a bunch of clients who all run different tools, what you should expect from a tech at 30, 60 and 90 days, how to explain a security finding so the prospect actually cares. It also assumes you have people to run all those practices, and a 10 to 40 person MSP usually doesn't have a process team sitting around. Whatever you take from it, you still have to translate into your own business, and the translating is where the hours go.

I've watched owners go down this road. Somebody rewrites the process docs, new words start showing up in meetings. Then Monday morning rolls around and it looks like the Monday before. Same questions on your phone, same escalations, same quote you end up pricing yourself.

When does it make sense?

A bigger MSP with somebody who owns process full time can get a lot out of it. If a client contract requires ITIL alignment or ISO/IEC 20000-1 certification, you do what the contract says. And if your customers are government or enterprise shops that live in ITIL language, speaking it helps. Even then I'd use it for what it's good at, like keeping incidents separate from problems and controlling change, and keep it inside your own way of working so you aren't rebuilding the company around it.

What would I do instead?

What we do at Built to Run starts from a different place. We look at your MSP as a set of systems: how a client gets onboarded, how a ticket gets handled, how an escalation moves, how a quote gets priced, how a new hire gets up to speed. For each one you set expectations, which just means writing down what good looks like, and then you manage to the systems instead of managing to a gut feeling or a checklist.

A system needs three things to deliver. A process that's written down, the people responsible for it, and the tools to do the job. Then there's the part most MSPs skip, which is a metric, and I'd argue it's the most important piece. The metric tells you how the system is really doing, it gives you a feedback loop so you can improve it, and it gives somebody a number to be accountable for. That somebody shouldn't be you.

 

None of this is a playbook we hand over, because nobody's off-the-shelf playbook can know how your MSP runs. The systems and the standards are yours.

What you measure changes with the client, too. Say one client is a fifteen-person firm with compliance obligations, so what matters is security, documentation and how fast you can show your work to an auditor. Another is a manufacturer with a plant floor, so it's uptime and how quickly you respond when a line goes down. Same MSP, different systems to watch, different numbers.

I start with clients and culture in making decisions because implementing a standard with no reason behind it feels like a rule somebody made up. And people treat it that way.

When it traces back to something a client cares about and to what your company stands for, your team gets it. If your clients value being kept in the loop, your communication standard says when and how. If ownership is one of your values, every metric has a named owner. Techs make better calls because they can see why the standard exists, you hire for the same values you wrote down, and your prospects can see what you do and why, which is more than the cheap quote down the street gives them.

The metrics do the improving after that. You look at a handful on a schedule, pick the one biggest gap and fix it this month. Your techs flag where a standard doesn't fit a client, and what they learn goes back into the system. You write a process down after it's proven on real tickets, not before. And you don't have to stop everything to do any of it. We build it a piece at a time, starting with the system that hurts the most.

If you're thinking you already have ITIL, keep it. Your team's knowledge of incidents, problems and change still pays off, and this is how the rest of the business gets to the same standard. If you're thinking you're too small, small is where it matters most because the owner is carrying everything. No time, I get it, nobody has any, which is why we do it a piece at a time and finish the first one before you lose momentum. And if you're worried your team won't follow it, they will once what good looks like is written down, every system has an owner and they can see their own number every week.

You can keep running the business out of your head, and a year from now you'll be answering the same questions and paying the same $10,000 a week, or whatever your real number turns out to be. Or you can pick the one system that hurts the most and start seeing it clearly.

Sign up at www.builttorunmsp.com and find out how.

 

Frequently Asked Questions

Should an MSP implement ITIL on its own?

For most small and mid-size MSPs, a full ITIL implementation costs more than it returns. ITIL is general guidance for IT service management, so it leaves MSP-specific questions like pricing, standardizing across clients and holding technicians to numbers for you to work out, and it assumes a team to run all of its practices.

When does ITIL make sense for an MSP?

It can make sense for larger MSPs with someone who owns process full time, for MSPs whose clients or contracts require ITIL alignment or ISO/IEC 20000-1 certification, and for those serving government or enterprise customers who run on ITIL. In those cases, use it for incident, problem and change management inside your own way of working.

Can an MSP be ITIL certified?

No. Individuals can earn ITIL certifications, but organizations can't be ITIL certified, and ITIL is best-practice guidance and not an industry standard. Organizations that need to prove their service management typically certify against ISO/IEC 20000-1.

What is an easier way for an MSP to document its standard path?

Start from what your clients value and who you are as a company, then list your key systems and write down what good looks like for each. Make sure each one has a process, people and tools, and give each one a metric and an owner. Standardize the 80 percent of needs clients share, treat the rest as defined exceptions, and review on a schedule.

What does each system in an MSP need in order to work?

A written process, people responsible for it and tools to do the work. It also needs a metric, which shows how the system is performing, feeds a feedback loop for improvement and gives its owner something to be accountable for.

How do you hold an MSP team accountable to metrics?

Give every system a metric with a named owner who isn't the MSP owner, let each technician see their own numbers every week, write down role expectations at 30, 60 and 90 days, and manage to the number when someone misses it instead of lowering it.

About the author
Bruce McCully

Bruce McCully

Bruce McCully built his first company, an MSP, from zero to $8.5 million in recurring revenue. A significant part of that came from cybersecurity incident response. Going into hospitals at 2am and recovering them from ransomware attacks. He didn't learn what happens when a business is unprepared by reading a case study. He was in the room when it happened. Then he founded Galactic Advisors. He scaled it to eight figures in recurring revenue, then stepped down as CEO to focus on MSP Advancement full time. Not because he lost interest. Because the systems he built meant the company no longer needed him to operate it day to day. He remains Chairman of the Board and majority owner. And now he's doing the only thing he wanted to do all along: helping MSPs level up.