Sample post — for illustration
Most mid-market companies read their managed-services invoice as a single number and move on. That number is the least useful thing on the page. The line items underneath it — and the ones that aren't there at all — are where the real story lives: what you're over-paying for, what you've quietly stopped using, and which risks your provider has decided are your problem rather than theirs.
We review a lot of these invoices. The pattern is consistent. The bill is designed to be paid, not understood. Here is what to look for the next time one lands in your inbox.
The bundle hides the math
A flat per-seat or per-device rate feels simple, and that simplicity is the point. It bundles high-margin, low-effort services (patching, monitoring) with the handful of things you actually escalate on, then averages the two into a price nobody questions. When you unbundle it, you often find you're paying enterprise rates for commodity tasks that could be automated or renegotiated.
Ask your provider for three things:
- A breakdown of active seats and devices versus what you are billed for — the gap is almost always in their favor.
- Ticket volume and resolution time by category, so you can see what you're truly buying.
- A list of tools and licenses passed through at markup, and the underlying vendor price.
An MSP invoice is a negotiating position, not a fact. The companies that treat it as fixed are the ones leaving the most money on the table.
What's missing matters more
The dangerous part of the invoice is the empty space. Backup testing, offboarding, security-incident response, and roadmap planning are frequently scoped out — not because they don't matter, but because they're labor your provider would rather bill separately or skip. When a board asks whether the business is covered, "we have an MSP" is not an answer. Knowing exactly which obligations sit inside the contract, and which have quietly fallen to you, is.
This is the work a fractional CIO does on day one: translate the invoice into a picture of coverage, cost, and risk that a non-technical leadership team can actually act on. Not to fire the provider — often the answer is to keep them and renegotiate from a position of understanding — but to make sure the relationship serves the business instead of the other way around.
You don't need to become a technologist to read your own invoice well. You need someone in the room who reads them for a living and answers to you, not to the vendor. That's the gap we fill — one relationship, on your side of the table.