If you’ve been paying an MSP invoice long enough to get bored with it, go read last month’s in detail. Not the total — the line items. You’ll probably find at least two things that made sense on day one but don’t now, and one thing that was never really justified. Managed IT services cost is rarely dishonest. It’s just sticky, and most MSPs count on that stickiness.
Here are six categories of line items that quietly inflate your bill by 20 to 40 percent over time, and how to push back on each without torching the relationship.
1. Onboarding and “setup” fees that linger
Onboarding fees are legitimate when there’s real work being done — documenting your environment, standing up tooling, migrating users to a new monitoring agent. The problem is when they show up on the recurring invoice past month three, or when the scope of what’s being “set up” balloons quarter over quarter.
How to push back: ask for a dated onboarding plan with a hard end date. Any work after that date gets quoted as a project, not billed as setup. If the provider resists, they’re anchoring a permanent revenue stream, not doing real onboarding.
2. Per-user vs. per-endpoint ambiguity
Most MSPs price on users or endpoints, not both. Read which one you agreed to. Then count.
Common gap: you’re priced per endpoint, but your MSP has been adding every printer, every shared terminal, every conference-room computer as a billable endpoint. Or you’re priced per user, but a departed employee’s account is still active and billable two months later. One client audit I ran found 18 percent of invoiced seats were “ghosts” — departed employees, test accounts, and unused service accounts.
How to push back: reconcile the active user list against the invoice quarterly. Ask for automatic deactivation within a set SLA (seven days is reasonable). Get credit for ghosts.
3. Tool markups
Your MSP is almost certainly reselling software — endpoint protection, email security, backup, MFA, password management — at a markup. Some markup is reasonable (they negotiate volume discounts, handle provisioning, absorb licensing risk). Markup of 2x or more is not.
How to push back: ask for the pass-through cost on every bundled tool, then compare to the public list price. You don’t need to know every internal number — just ask “what’s the street price on this tool?” A trustworthy provider will answer. An evasive one will suddenly need to “check with accounting.”
Alternative: negotiate a bring-your-own-license clause for specific tools. Many MSPs will allow it once you ask. The savings typically pay for the conversation.
4. Project minimums and change orders
The contract says new projects are quoted separately. The quotes start looking suspiciously similar — always rounded to 40 or 80 hours regardless of the actual work. Change orders get issued for what feels like incidental scope. Over a year, project spend is often 30 to 50 percent of the MSP relationship’s total cost, and a lot of that is shape-shifting.
How to push back: ask for itemized project estimates with tasks and hours, not round numbers. Set a policy internally that any change order over a small threshold requires a written scope memo before approval. And benchmark a big project — a migration, a firewall replacement — against an outside quote once a year. You’ll either validate your MSP’s pricing or find out something important.
5. After-hours and emergency tiers
Many MSP contracts include “business hours” support in the monthly fee and bill separately for after-hours. Fine in principle, frustrating in practice, because what counts as “business hours” gets narrower and narrower if nobody pays attention. A 7 p.m. call on a Thursday shouldn’t always be billed as emergency.
How to push back: define business hours in writing. Specify what qualifies as an emergency. Cap billable emergency events per month, or negotiate an all-inclusive 24×7 tier if you truly need it. And watch the invoice — emergency hours have a way of appearing for issues that were self-resolved or that took fifteen minutes.
6. Auto-renewal and CPI escalators
This one compounds silently. A typical MSP contract auto-renews for another 24 or 36 months if you don’t cancel within a narrow window, often 90 days before expiration. Inside many of those renewals is a CPI escalator — 3 percent, 5 percent, sometimes uncapped. Across a five-year relationship, that adds 15 to 25 percent to your bill without anyone negotiating anything.
How to push back: put the renewal window in your calendar the day you sign. Negotiate a cap on CPI escalators (2 to 3 percent is reasonable). At renewal, treat it like a new negotiation — get competitive quotes, push for better terms, and don’t assume inertia.
The posture to bring
None of this is adversarial. A good MSP relationship is long-term and collaborative, but it’s still a commercial contract. The providers who handle these conversations well won’t flinch when you ask. They’ll walk you through their margins, explain their costs, and work with you to tune the scope. The ones who do flinch are telling you what you need to know.
Your managed IT services cost should feel proportionate to the value you’re getting. If the line items above inflate it beyond that, the problem isn’t that the provider is overcharging — it’s that nobody has been asking. Start asking.
