Managed IT services pricing is where most MSPs quietly bleed: a number copied from a competitor years ago, eroded by inflation, defended by nobody. Here are the models, the honest benchmark ranges, and the mechanics of setting — and raising — rates like a business rather than a favor.
1. The Four Pricing Models
| Model | How it works | Best fit | Watch out |
|---|---|---|---|
| Per-user | One rate per employee supported | The default for office-centric clients; scales with the number you can verify | Define what counts as a user (part-timers, contractors, shared logins) |
| Per-device | Rates per endpoint/server/network device | Device-heavy environments — clinics, shops, sites with kiosks | Sprawls in inventory arguments; needs a clean covered-environment list |
| Tiered | Good/better/best bundles on either base | Sales conversations — the three-tier proposal presentation | Tiers must differ honestly (coverage, security depth), not feature-stripping |
| Value / outcome | Priced against the risk or outcome carried | Compliance-heavy or high-stakes clients who buy certainty | Needs mature delivery data; hardest to defend without metrics |
Hybrids are normal — per-user base with per-server adders is probably the most common real-world structure. What matters is that the counting unit is written into the contract's covered-environment section with a true-up mechanism, so billing follows reality without a negotiation each time.
2. Benchmarks
Ranges, not gospel — geography, vertical, and stack depth move these numbers: full-stack per-user engagements mostly land at $100–$250/user/month. The bottom of the range is help desk + monitoring + patching with a basic security layer. The middle ($150–$200) adds a real security stack, backup with tested restores, and QBRs. The top carries compliance workloads (HIPAA, CMMC, FTC Safeguards), 24/7 coverage, or included vCIO strategy — see the vCIO services guide for how that layer gets packaged. Per-device engagements commonly run $30–$60 per workstation and $100–$400 per server, with network devices billed flat or bundled.
Benchmarks are a sanity check, not a strategy
3. Setting Your Price
Cost-up, in three steps. First, the fully loaded delivery cost per user: technician labor at realistic utilization (nobody bills 40 hours of a 40-hour week), the per-seat tool stack (RMM, EDR, backup, email security, documentation — it adds up to real money per user), and allocated overhead. Second, the margin the business needs to fund growth, on-call, and bad quarters — 50%+ gross margin on the retainer is the common health bar. Third, the market sanity check against the benchmarks above. If your cost-up number is above market, the answer is fixing delivery efficiency or moving upmarket — not pricing below cost and hoping volume fixes it.
Then present it as three tiers, anchored high, per the proposal template — the pricing conversation goes far better when the client is choosing between your options instead of judging your single number.
4. Raising Prices Without Churn
- Contract first. The annual adjustment clause (CPI or a stated cap) belongs in the MSA — a raise the contract already authorizes is an administration email, not a renegotiation.
- Evidence at the QBR. The metrics pack is why the raise lands: visible value makes price defensible; invisible value makes any price feel high.
- 60–90 days' notice, everyone on schedule. Client-by-client negotiation teaches clients that pushing back works; a uniform scheduled adjustment teaches them it's normal.
- Reprice the legacy accounts. Every MSP has clients on 2019 pricing. Grandfathering forever means your best-tenured clients are your least profitable — bring them to current rates over one or two cycles, with the option to trim scope instead.
5. Common Pricing Mistakes
- Copying a competitor's price without their cost structure — the classic route to profitable-looking, loss-making clients.
- All-you-can-eat language with no covered-environment definition, so scope grows while price doesn't.
- Discounting the retainer instead of removing scope — it reprices the same work and teaches the client the first number was padding.
- No annual adjustment clause, so every raise is a fresh negotiation you'll postpone for years.
- Pricing projects inside the retainer "to be nice" — out-of-scope work has a rate card for a reason.
Key Takeaways
Pick the counting unit that fits the client, price cost-up with a real margin, sanity-check against the $100–$250/user universe, present three honest tiers, and build the raise into the contract so value — shown quarterly at the QBR — keeps the price defensible. Pricing isn't a number; it's a system, and the contract, proposal, and QBR are its moving parts.