The MSP Pricing Playbook for Owners Tired of Underpricing

Updated: May 2026

The quote is open on your screen. You're not sure of the number. You pull from the last deal, ask a peer in a Slack group, or round up and hope. Then year-end arrives and the P&L tells the story. Gross margin under 40%. Your best clients still on 2019 rates against a 2026 cost base. No clean answer when an account manager asks what to charge the next prospect.

This guide fixes that. Seven pricing models with ranges, a decision matrix that picks the model for each client, a five-step cost-build that prints a defensible floor price, a worked margin example on a 25-seat deal, and the operator framework behind a $2M-to-$20M MSP scale-up.

TL;DR: The 7 MSP Pricing Models in One Page

• Per-user. Flat fee per supported employee. Most popular model in 2026; around 22% of MSPs use it as the default.
• Per-device. Fee per supported endpoint. Fair when device counts vary widely between clients.
• Tiered or bundle (Bronze / Silver / Gold). Three pre-built packages clients self-select into.
• Flat-rate (all-you-can-eat). One monthly invoice, unlimited support inside agreed scope.
• À la carte. Pick-and-pay individual services. Useful as an upsell layer on top of a managed plan.
• Monitoring-only or break-fix hourly. The legacy model. Fading fast for new contracts.
• Value-based or outcome-based. Price tied to business outcomes (uptime, security posture). The emerging model for premium vCIO work.

One-sentence decision rule: if your average client has more than two devices per user and a heavy security stack, default to tiered per-user; everywhere else, default to plain per-user.

The 7 MSP Pricing Models

These are the canonical pricing structures in 2026 MSP land. Most operators run one as a default and a second as an upsell layer.

Per-User Pricing

What it is. A flat monthly fee per supported employee, regardless of how many devices that employee uses. The dominant model in 2026 - Kaseya's MSP Benchmark Survey placed it at roughly 22% of MSPs and rising every year since 2021.

Typical 2026 range. $70-$150 per user per month at 1-50 seats; $100-$250 per user per month at 75-150 seats; $200-$400+ in regulated verticals (healthcare, finance, defense) with full security and compliance bundled.

Best for. Knowledge-work clients where each employee has 2-4 devices (laptop, phone, tablet, occasional secondary monitor or remote setup) and the support volume scales with people, not endpoints.

Pros. Simple to quote. Maps to client headcount, which clients already track. Predictable for both sides. Aligns naturally with security tools that license per identity (Microsoft 365, EDR, identity-based MFA). Kyle Christensen, a former MSP owner who scaled his shop from $2M to $20M in roughly three years, puts the case more directly: business owners always know their headcount, but rarely know their device or server count. Asking "how many servers do you have?" risks making the prospect feel uninformed and erodes trust before a quote even lands. A human-friendly version - "$150 per user, you have 4 employees, that's $600 per month" - accelerates qualification and removes friction from the sales call.

Cons. Punishes you if a client has heavy device sprawl (warehouse workers with five ruggedized handhelds each, kiosks, IoT) without a per-device add-on.

Watch-outs. Define "user" tightly in the contract. Service accounts, shared logins, and contractors all become arguments at renewal otherwise.

Per-Device Pricing

What it is. A flat monthly fee per supported endpoint - workstation, server, network device, mobile.

Typical 2026 range. $50-$100 per workstation per month, $200-$500 per server per month, $25-$75 per networking device, $15-$40 per mobile. Bundled with patching, monitoring, and basic remediation.

Best for. Clients where device counts vary widely from employee counts - manufacturing, healthcare with shared workstations, retail with POS plus back-office gear.

Pros. Fair allocation when device density is uneven. Easy to baseline from the RMM inventory. Predictable when device count is stable.

Cons. Doesn't capture the labor cost of users who file five times more tickets than peers. BYOD blurs the count. Re-quoting hits every time a client adds or removes machines.

Watch-outs. Bring-your-own-device policies and remote workers buying their own gear distort the headcount. Specify covered device types upfront.

Tiered or Bundle Pricing

What it is. Three (sometimes four) pre-built service packages at different price points - the classic Bronze / Silver / Gold structure. Each tier adds services or shortens response times. Clients self-select based on budget and risk tolerance.

Typical 2026 range. Bronze $80-$120 per user; Silver $140-$200 per user; Gold $220-$350 per user. Top tier usually adds 24/7 coverage, security operations, vCIO time, and faster SLAs.

Best for. MSPs with a diverse client mix who want a single sales motion. Easy to upsell within the tier ladder.

Pros. Anchors price comparison. The Gold tier raises the perceived value of Silver, which most clients land on (the intended outcome). Sales conversations move from "how much" to "which level."

Cons. Tier design is hard to get right. Tiers too close together get clients to demand Gold at Silver price. Tiers too far apart leave gaps clients fall through.

Watch-outs. Review the tier definitions every 6-12 months. Tool-stack inflation will push your real cost into the next tier if you don't.

Flat-Rate (All-You-Can-Eat) Pricing

What it is. One monthly fee covers unlimited support inside an agreed scope. No per-incident charges, no hourly overage.

Typical 2026 range. $1,500-$15,000 per month flat for SMB clients, scaled by complexity and headcount band rather than line-itemed.

Best for. Mature MSPs with disciplined scope control and a strong tool stack. Often used as the headline plan with optional per-user or per-device variants underneath.

Pros. Simplest possible invoice. Clients love the predictability. Strong retention.

Cons. Heavy abuse risk when scope isn't bounded - one client's "unlimited" becomes the team's three biggest fires. Margin volatility is real if ticket volume spikes.

Watch-outs. Write scope as exclusions, not inclusions. List what's not covered (major migrations, after-hours projects, custom integrations) instead of trying to enumerate what is.

À La Carte Pricing

What it is. Individual services priced separately - help-desk per ticket, backup per terabyte, security stack per endpoint, vCIO hours.

Typical 2026 range. Highly variable. $25-$45 per help-desk ticket, $0.10-$0.30 per GB per month for backup, $5-$25 per endpoint per month for EDR.

Best for. As an add-on layer on top of a managed plan, not as the primary structure. Useful for project work, one-off needs, and clients who want to graduate to managed services from break-fix.

Pros. Easy for buyers to digest at first glance. Lets you sell into clients who balk at a full managed contract.

Cons. Quoting is constant. Invoices get long. Predictability is lower for both sides. Clients shop each line item against vendors.

Watch-outs. Don't let à la carte cannibalize your managed-plan upgrades. Price single items deliberately higher than the equivalent bundled cost.

Monitoring-Only and Break-Fix Hourly

What it is. The legacy model. Monitoring-only charges a small fee to alert on issues, no fix included. Break-fix charges hourly to resolve issues that pop up.

Typical 2026 range. $5-$15 per device per month for monitoring-only. $125-$250 per hour for break-fix labor, $250-$500 per hour for after-hours and emergency.

Best for. Project work, out-of-scope requests on a managed contract, and bridging clients onto managed services.

Pros. Low commitment. Useful for first-touch engagements and overflow work.

Cons. Punishes good preventative work - the better you keep a client running, the less you get paid. Margin is unpredictable. Revenue isn't recurring.

Watch-outs. Don't sign new clients onto a break-fix-only relationship in 2026. The economics don't work, and the model trains the client to call only when something explodes.

Value-Based or Outcome-Based Pricing

What it is. Pricing tied to business outcomes the MSP delivers - uptime percentages, security posture scores, ticket resolution targets, project completion - rather than per-seat or per-device counts.

Typical 2026 range. Custom. Often expressed as a base monthly retainer plus performance bonuses or penalties tied to SLAs. Annual contract values from $50k to $500k+ for mid-market vCIO engagements.

Best for. Premium vCIO and security-focused engagements with clients who measure IT in business terms (revenue uptime, breach cost avoidance, compliance audit pass rate).

Pros. Maps your fee to the value the client perceives. Defends against commodity comparison. Strong retention when outcomes are met.

Cons. Hard to measure. Requires a sophisticated client and an MSP with mature service-delivery data. Risk of penalty clauses if the SLA is poorly written.

Watch-outs. Define the outcomes specifically and tie them to data both sides can see. "We reduced ransomware risk" isn't an outcome; "MFA coverage at 100% of users, EDR alerts under 24-hour median resolution, zero successful phishing campaigns in Q1" is.

What Managed Services Cost in 2026

These are buyer-side numbers - the prices a client expects to see on a quote. MSPs setting their own price should benchmark here, then run the cost-build math in the next section to confirm they can deliver at this rate with a healthy margin.

Per-user pricing, by company size, in the US in 2026:

Per-device pricing, by device type:

Tiered bundle pricing in typical bands: Bronze around $80-$120 per user covering patching, monitoring, basic help desk, and business-hours coverage; Silver around $140-$200 per user adding EDR, basic backup, faster SLAs, and a monthly review; Gold around $220-$350 per user adding 24/7 coverage, vCIO time, and advanced security operations.

What's usually included at the per-user rate: help-desk tickets, RMM and patching, baseline anti-virus or EDR, Microsoft 365 admin, basic backup, business-hours coverage.

What's typically priced as an add-on: cybersecurity bundles beyond baseline EDR (SOC, SIEM, vulnerability management), backup tiers (immutable, ransomware-resistant), compliance audits (HIPAA, PCI, CMMC), hardware procurement, on-site visits, after-hours work, and projects (migrations, deployments, custom integrations).

Premium verticals (healthcare, finance, defense, legal) trend $40-$100 per user per month above the standard bands because of the compliance stack pass-through and the tighter SLA expectations.

6 Factors That Should Drive Your Pricing

Pricing isn't a market lookup. It's a function of your costs, your scope, and how the business is positioned. Six inputs matter.

Fully-Loaded Operating Cost Per Seat

The number every MSP should know cold. Sum your monthly tool-stack cost per seat (RMM, PSA, M365, EDR, backup, documentation tool, password manager, miscellaneous integrations) plus your loaded engineer cost per seat (engineer fully-burdened salary divided by realistic seats supported per tech). For a tightly run SMB-focused MSP, fully-loaded cost runs $40-$70 per seat. For a heavier security-stack shop, $80-$120. Anything above $120 means either the stack has bloat or the team is carrying too few seats per tech. A periodic MSP stack audit is the fastest way to catch creeping per-seat cost before it eats your margin quietly.

Service Scope and Ticket Volume

Tickets per user per month is the silent driver of MSP margin. A clean knowledge base, mature onboarding, and disciplined scope control put this at 0.5-0.8 tickets per user per month. A reactive shop with poor docs and weak scope discipline runs 1.5-2.5. The difference between those two operating points is the gap between profitable per-user pricing and bleeding margin on the same rate.

Market Positioning (Commodity vs Premium)

A commodity-positioned MSP competes on price and lives in the $70-$120 per user band. A premium-positioned MSP - vCIO-led, security-deep, vertical-specialist - clears $200-$400 per user. The positioning shows up everywhere: the website, the sales deck, the kind of client meetings booked, the case studies published. Pricing follows positioning; raise positioning and the price follows.

Kyle Christensen calls verticalization the single fastest growth accelerator he saw on his own scale-up. Walking into a dental office saying "all we do is dental" lands harder than any generic IT pitch - it lets the MSP speak the prospect's language, build trust faster, and command higher prices. He pointed to a small-town Alberta MSP that grew to $22M and 95 employees on deep community and vertical focus alone. Narrow the addressable market on purpose: a focused pool of around 1,800 dental offices in a metro is easier to win than 90,000 generic small businesses.

Client Industry and Compliance Load

Healthcare adds HIPAA. Finance adds PCI, SOX, and GLBA. Defense contractors add CMMC. Each compliance regime adds tooling, audit work, and documentation overhead. Charge for it explicitly. Industry-specific MSPs price 20-40% above their generalist peers because the compliance scope is real work and clients know it.

Kyle Christensen's caveat for early-stage MSPs: avoid heavily regulated verticals like defense contractors (CMMC) until you have the R&D budget and liability tolerance to handle them. Dental (HIPAA is reasonably tractable with a Business Associate Agreement), construction, and CPAs are friendlier first verticals. The compliance premium is real money, but only if you can deliver the operational layer without putting the whole business at risk on a single audit.

Geography and Local Labor Cost

A New York or Bay Area MSP carrying senior engineer salaries at $140k+ can't price the same as a Midwest MSP with the same role at $85k. Local labor cost feeds directly into the loaded-engineer line of the cost-build. Remote-first MSPs blur this somewhat but rarely fully - clients still expect business hours in their time zone.

Cybersecurity Stack Pass-Through

Cybersecurity tool costs have risen faster than help-desk labor for three years running. EDR licenses, SOC services, vulnerability management, identity governance, and DNS-layer security stack up to $25-$50 per seat in 2026 for a serious security posture. MSPs that don't pass this through eat margin every quarter. The cleanest approach: a security-tier add-on that's a transparent pass-through plus a management fee. For an honest look at where stack cost adds up, the RMM tools comparison guide shows where the pricing pressure really comes from inside an MSP stack.

How to Choose the Right Pricing Model

A quick decision framework. Map your average client to the right column and pick the row that matches.

A few quick rules. If average devices-per-user is above two and counts vary widely between clients, default to per-device or a hybrid per-user-plus-per-device. If you bundle a heavy security stack, default to tiered per-user with a security tier add-on. If clients ask "what's included?" three meetings in a row, your pricing is too à la carte and the bundle needs a rewrite. And if clients ask "can we just pay hourly?" the brand is being positioned as commodity - fix the positioning before answering the rate question.

How to Set Your Price (Cost-Build Walkthrough)

The five-step cost-build that gives you a defensible floor price. Everything above the floor is margin and positioning.

1. Tool-stack cost per seat. Add monthly cost per supported seat for RMM, PSA, M365 management, EDR, backup, documentation, password vault, MFA, DNS security, anti-spam, and miscellaneous tooling. Realistic 2026 range: $25-$60 per seat for SMB tooling, $50-$100 for security-heavy stacks.
2. Loaded labor cost per seat. Take fully-burdened engineer cost (salary + benefits + payroll tax + tools + training) and divide by realistic seats supported per tech (typically 75-150 seats per L1, fewer for L2/L3). A $110k loaded engineer supporting 100 seats costs $1,100 per seat per year, or about $92 per seat per month.
3. Overhead allocation per seat. Office, software not tied to delivery, admin, owner salary, marketing, sales commissions. Divide annual overhead by total supported seats. Realistic range: $20-$40 per seat per month at a small MSP, lower as seat count grows.
4. Target gross margin. Healthy managed-services gross margin is 50-60% on recurring revenue. Top-quartile MSPs clear 60% (Service Leadership annual benchmark). Pick a target, then back into price.
5. Floor price formula. Floor price = (tool cost + labor cost + overhead) ÷ (1 - target margin). Example: $50 tool + $90 labor + $30 overhead = $170 fully-loaded. At 55% target margin, floor price = $170 ÷ (1 - 0.55) = $378 per seat per month. That's the floor. List price sits above the floor; discount band is anything between list and floor.

Worked example: 25-seat client priced three ways. Same scope (help desk, RMM, M365 management, basic EDR, backup, business-hours coverage), $170 per seat fully-loaded cost, $4,250 all-in monthly. At $200 per seat per-user, revenue is $5,000 with $750 gross profit at 15% margin - too thin. At $250 per seat Silver tier, revenue rises to $6,250 at 32% margin - closer but still below target. At $300 per seat Silver plus a $40 per seat security tier add-on, revenue lands at $8,500 with $4,250 gross profit at exactly 50% margin. Same delivery cost, but the structure hits the target. The obvious lever: the security stack pass-through is the line that quietly bleeds margin when it isn't priced explicitly.

For brand-new MSPs without an existing customer base, Kyle Christensen recommends a different starting point: a minimally viable product (a retainer or block-hour agreement, a basic RMM-plus-EDR stack) priced 25-30% below the nearest competitor for the first 10-20 deals. The goal at that stage is repetitive sales motion and customer feedback, not margin protection. Pricing confidence comes after the market tells you what your service is worth. Once revenue is stable, switch to the cost-build above and reset the price floor.

One useful sanity check: a $250k owner salary needs roughly $1.25M+ in recurring revenue at a healthy gross margin. Set a milestone (e.g., $500k by year one) and work backwards into the required deal volume at your chosen price point - the math tells you fast whether the pricing model clears the lifestyle target.

If running the cost-build by hand on every prospect is painful, the MSP margin calculator does the full math live against your real stack and prints the floor price for each pricing model.

2026 MSP Pricing Trends

Four shifts are reshaping MSP pricing this year.

AI help desk and per-user economics. AI-assisted ticket triage, draft replies, and similar-ticket suggestions are cutting average handle time 20-30% on routine work. The leading MSPs are routing 30-40% of Tier-1 volume through self-service or AI deflection. That changes the labor side of the cost-build: a $90-per-seat labor cost can drop to $60-$70 without sacrificing service quality. The shift is also pushing more MSPs toward AI-native all-in-one platforms like OpenFrame that ship the help-desk, PSA, RMM, and automation in one app instead of stitching together four vendors at four invoices each.

Cybersecurity-loaded bundles and the MSSP premium. Clients increasingly expect EDR, SOC services, vulnerability management, and security awareness training in the base bundle. MSPs that deliver this credibly are pricing closer to MSSP rates ($150-$300 per user) and moving up-market. MSPs that pass through tools but don't deliver the operational layer get squeezed between rising license costs and clients who think "EDR is standard now."

Co-managed IT for mid-market. Mid-market clients with an in-house IT team but no security depth are the fastest-growing co-managed segment. Pricing is usually a base retainer ($3,000-$10,000 per month) plus per-incident or per-project hours. The economics are strong because the client provides the day-to-day Tier-1 and the MSP layers in Tier-2/3 and security.

Transparent pricing as a sales differentiator. A small but visible set of MSPs publish their tier pricing publicly. The trade-off is real (commodity risk vs trust signal), but for SMB-focused MSPs that compete on responsiveness rather than custom scope, public pricing shortens sales cycles and pre-qualifies leads. Worth A/B testing against the current quote-on-call motion.

7 Common MSP Pricing Mistakes

1. Inheriting legacy client rates instead of resetting. Clients signed in 2018 at $85 per user are paying 2018 rates against a 2026 cost base. Reset at the contract anniversary or accept eroding margin.
2. Pricing on cost, not value. Cost-plus only sets the floor. Value-based pricing finds the ceiling. Skipping step two leaves 20-40% of potential revenue on the table at every renewal.
3. Discounting upfront without measurable scope. "First three months at 30% off" without explicit scope guards trains the client to expect the discounted rate forever. Tie any discount to a deliverable (onboarding, migration) that has a fixed end date.
4. Forgetting tool-stack inflation pass-through. EDR, M365, backup, and identity tools raised list prices in 2024 and 2025. If a contract doesn't include an annual CPI-plus-tool-cost adjustment clause, the MSP is absorbing the difference. Insert one at next renewal.
5. Letting projects bleed into the managed contract. "Quick migration help" becomes 40 hours of unbilled work. Define what's a project (any scope, time, or outcome outside the routine), quote it separately, and invoice it separately.
6. One price for all client sizes. A 10-seat client costs nearly as much to support as a 25-seat client (the per-account overhead is similar). Price the small clients higher per seat, or set a minimum monthly fee. Avoiding this trap is one of the cleanest ways to cut wasted IT spend on the MSP side.
7. Never raising prices. Year-over-year inflation alone justifies a 3-5% bump. Add value-delivery improvements, security stack additions, or new tools and the bump can land at 8-12% without pushback. Never raising trains the client to expect static pricing forever.

How to Raise Prices Without Losing Clients

Price increases on existing MSP clients don't have to mean churn. The pattern that works has three parts.

Announce 60-90 days ahead. Long-tenured clients hate surprises. Send a written notice that names the new rate, the effective date, and the reason. The notice itself should be short. The conversation that follows can be longer.

Anchor to value delivered, not cost increases. "We're raising prices because Microsoft raised theirs" is a weak position. "Over the past year we resolved 1,247 tickets, blocked 38 phishing attempts, completed three migrations, and prevented two ransomware incidents from spreading" is a strong position. Show the receipts.

Pair the increase with a measurable scope upgrade. A pure rate bump is hard to defend. A rate bump paired with added EDR, 24/7 coverage, a security awareness training program, or a vCIO quarterly review reframes the conversation from "you cost more" to "you get more." Pick one upgrade per increase cycle.

The middle 70% of clients accept the increase without pushback if the announcement is professional, the value story is honest, and the scope upgrade is real. The 15% who push back usually negotiate to a slightly smaller bump rather than walking. The 15% who walk were going to walk anyway - the price was just the trigger.

Frequently Asked Questions

What is the best MSP pricing model?
There isn't one universal answer. Per-user pricing is the most common in 2026 - around 22% of MSPs use it as the default. The right model depends on your average devices-per-user, the depth of your security stack, your target margin, and the kind of clients you sell to. Most mature MSPs run a primary model (usually per-user or tiered) and a secondary à la carte layer for projects.

How much does an MSP charge per user per month?
US MSPs typically charge $70-$150 per user per month for businesses with 1-50 employees and $100-$250 per user per month at around 100 employees. Premium verticals (healthcare, finance, defense) trend $40-$100 above the standard band because of the compliance and security stack. Co-managed IT for mid-market often falls below these ranges since the client provides Tier-1 support.

How much does an MSP charge per device per month?
Per-device pricing in 2026 runs $50-$100 per workstation, $200-$500+ per server, $25-$75 per networking device, and $15-$40 per mobile device. The bundle usually includes patching, monitoring, anti-virus or EDR, and basic remediation. Specialty devices (POS, kiosks, ruggedized handhelds) often carry custom pricing because the support model is different.

What is tiered MSP pricing?
Tiered pricing offers three pre-built service packages at three price points, usually called Bronze, Silver, and Gold. Each tier adds services or tightens SLAs. Clients self-select based on budget and risk tolerance. The model anchors price comparison and makes the sales conversation about which level rather than how much. Most clients land on the middle tier, which is the intended design.

What's the difference between per-user and per-device MSP pricing?
Per-user charges a flat fee per supported employee regardless of how many devices they use. Per-device charges per supported endpoint regardless of who uses it. Per-user is simpler when employees have multiple devices. Per-device is fairer when device counts vary widely between clients (manufacturing, retail, healthcare with shared workstations). Some MSPs hybrid both: per-user as the base, per-device for clients with unusual device sprawl.

What gross margin should an MSP target?
Healthy managed-services gross margin is 50-60% on recurring revenue. The top quartile of MSPs clears 60% (Service Leadership annual benchmark). Tool-stack pass-through and labor utilization are the two biggest levers. MSPs running below 40% gross margin on recurring services are almost always under-priced, over-staffed for their seat count, or carrying tool-stack bloat.

What is value-based MSP pricing?
Value-based pricing ties the MSP fee to business outcomes the client cares about: uptime percentages, security posture scores, ticket resolution targets, project delivery. It usually shows up as a base monthly retainer plus performance bonuses or penalties tied to SLAs. The model fits premium vCIO engagements where the client measures IT in business terms (revenue uptime, breach cost avoidance, compliance audit pass rate) rather than per-seat headcount.

How do I calculate my MSP price floor?
Add monthly tool-stack cost per seat, loaded labor cost per seat (engineer cost divided by seats supported per tech), and overhead allocation per seat. That's fully-loaded cost. Divide by (1 minus your target gross margin). At a $170 fully-loaded cost and 55% target margin, the floor is $378 per seat per month. Anything below that floor loses money on the contract; anything above is margin and positioning.

Set the Price, Then Hold It

Pricing isn't a one-time exercise. It's a quarterly habit: review the cost-build, check tool-stack inflation, audit ticket volume per user, raise rates with the contract anniversaries, and pair every increase with measurable value. The MSPs clearing 60% gross margin in 2026 aren't doing anything exotic - they're doing the basics on a 90-day cycle while the rest of the field does them once a year, or never. Kyle Christensen's benchmark for product-market fit in MSP land was 1.5-2% net revenue churn at 40%+ year-over-year growth. If churn runs higher than that, the issue is usually scope mismatch or value perception, not the headline rate.

Run the cost-build against your stack with the MSP margin calculator. If the floor price it spits out is more than 15% above your current rate, you have a pricing problem hiding in the P&L.

Keywords: msp pricing, msp pricing models, msp pricing model, managed services pricing models, managed service provider pricing, managed service provider pricing models, how to price managed services, how to price msp services, msp pricing guide, average msp pricing, msp models, msp pricing calculator, msp pricing spreadsheet, msp pricing template, msp per user pricing, msp per device pricing, msp pricing strategies, msp pricing examples, msp pricing structure, transparent msp pricing, msp pricing negotiation, managed it services cost, how much does managed it services cost, cost of managed it services, msp cybersecurity pricing, msp backup pricing, msp rmm pricing, cloud msp pricing, msp pricing 2026, msp pricing per user per month