Pricing Your MSP: Service Tiers, Per-Device vs Per-User, and the MRR Model

Building a Tiered Service Catalog Instead of Custom-Quoting Every Client

Most established MSPs price in tiers — commonly labeled something like a basic, standard, and premium level — rather than custom-quoting every prospect from scratch, because tiers make the sales conversation faster and make your margin per tier predictable. A basic tier typically covers monitoring, patching, and helpdesk support during business hours; a mid tier adds faster response SLAs and more proactive management; a top tier adds the full security stack, strategic IT planning or virtual CIO involvement, and after-hours support. Define exactly what's included and excluded at each tier in writing before you sell your first client, since vague tier boundaries create scope disputes later — the same problem unscoped legal engagements create, just on the IT services side.

Per-Device, Per-User, or All-Inclusive: Match the Model to Your Client Base

Per-device pricing (a flat fee per managed endpoint) is simple to quote and predictable to deliver against, but can undercharge for clients with heavy multi-device users and overcharge for clients with shared or infrequently used devices. Per-user pricing (a flat fee per employee, covering all their devices) has become more common as remote and hybrid work increased the number of devices per employee, and it aligns your revenue with headcount growth at a client rather than device count specifically. All-inclusive or value-based pricing (a single negotiated fee covering the full relationship, less tied to a specific unit count) works best for larger or more complex clients where per-unit pricing undersells the actual scope of what you're managing. Most MSPs settle on per-user as a default with all-inclusive negotiated pricing for larger accounts, but the right choice depends on your specific client base's device-to-user ratio.

Pricing for Delivery Cost, Not Just What Competitors Charge

A common new-MSP mistake is pricing off a competitor's published or rumored rate without actually modeling your own delivery cost — your tooling license cost per client, your own time or a technician's time per client at the ticket volume you expect, and your target margin. Build the model bottom-up: total monthly tooling and overhead cost divided by target client count, plus per-client delivery time cost, plus your target margin, gives you a price floor specific to your business — not a market-average number that may not reflect your actual cost structure, especially at a lower client count where fixed tooling costs aren't yet spread across many clients.

Documenting Pricing and Scope in a Proposal Clients Can Actually Evaluate

Once you've settled on tiers and a pricing model, present it in a clear, professional proposal that lets a prospect compare tiers side by side — what's included, what's excluded, and what the SLA commitments are at each level. A proposal and e-signature tool like PandaDoc makes this presentable and genuinely trackable (you can see exactly when a prospect actually opens and reviews a proposal), which is useful sales data well beyond just the close itself. Whatever format you use, the goal is the same one covered in the MSA guide: a scope precise enough that neither you nor the client is guessing about what's included once the engagement starts.

Handling the Break-Fix Competitor Objection

New MSPs selling managed services against an incumbent break-fix or hourly IT provider frequently hit a specific objection: 'why would I pay a flat monthly fee when I only call my current guy when something breaks?' The honest answer is that managed pricing trades a client's unpredictable, reactive cost for a predictable one that also includes proactive monitoring and patching that reduces how often something actually breaks — but that argument only lands if you can point to something concrete, like the specific incident-frequency reduction proactive monitoring tends to produce, described in terms the prospect can verify rather than a vague promise. Be honest that managed pricing costs more in months where nothing goes wrong — the value is the reduced frequency and severity of the months where something does. A short, specific example from a past client's actual incident history lands better with a skeptical prospect than a purely abstract argument about the value of being proactive.

Common MSP Pricing Mistakes

The most frequent mistake is pricing too low to win early clients, which locks in a client base that's expensive to migrate to sustainable pricing later without churn. The second is a tier structure with unclear boundaries, creating scope disputes when a client assumes something is included that's actually a tier above what they're paying for. The third is pricing purely off competitor rates without modeling your own delivery cost, which can look competitive on a proposal while quietly losing money per client once your actual time and tooling cost is accounted for.

Take this further

RECOMMENDED TOOLS

Affiliate links: some links below are affiliate links. If you sign up through one, we may earn a commission, at no extra cost to you. How this works

FREQUENTLY ASKED QUESTIONS