MSP Pricing Math: How to Calculate Managed Services Pricing in 2026
Most MSP pricing advice starts in the wrong place.
It asks whether you should charge per user, per device, tiered, flat-rate, or all-inclusive. That matters, but it is not the math. A pricing model is just the wrapper. The real question is whether the number inside the wrapper covers the cost of delivering the work.
If you are searching for MSP pricing in 2026, the useful answer is not another list of models. The useful answer is a floor price.
Your floor price is the lowest monthly price you can charge before the agreement starts eating margin. It should be built from labor cost, tool cost, shared overhead, client complexity, and target gross margin. If that number is uncomfortable, good. It is probably closer to the truth than the peer average you copied three years ago.
Quick answer: how do you price managed services?
Price managed services by calculating the monthly cost to serve the client, then dividing that cost by one minus your target gross margin. If a client costs $5,000 per month to support and you need 50% gross margin, the monthly floor price is $10,000. Anything below that is a discount against your operating model.
Formula:
Managed services floor price = monthly cost to serve / (1 - target gross margin)
That one line is the difference between pricing by math and pricing by folklore.
Why MSP pricing models do not save you by themselves
Per-user pricing can be clean. Per-device pricing can be fair. Tiered pricing can make sales easier. Flat-rate pricing can make invoices simpler.
All of them can still lose money.
A per-user price fails when users have heavy support demand, messy device sprawl, or compliance work you never priced. A per-device price fails when the real work is identity, SaaS, security, and user support. A tiered package fails when the tier includes expensive services but the price was built from a competitor's website.
Scopable already has a deeper guide on per-user vs. per-device MSP pricing. The short version: choose the model that matches how the client consumes work. Then do the math underneath it.
NinjaOne's 2026 managed services pricing guide gets the foundation right: MSPs need to understand COGS, MRR, all-in seat price, and gross margin before they price. It also warns against relying too much on benchmarks because your costs and delivery model matter more than what another MSP charges.
That is the part many pricing articles skip.
The market price tells you what buyers might tolerate. Your floor price tells you whether the deal is worth winning.
The five numbers you need before quoting managed services
You do not need a perfect finance model to price better. You need five numbers that are close enough to expose the truth.
1. Burdened labor cost per hour
Do not use salary divided by 2,080 hours and call it done.
A technician's real cost includes payroll taxes, benefits, PTO, training, management time, tools used internally, and the fact that not every paid hour becomes useful client delivery. If a tech makes $80,000, the cost of an actual usable delivery hour is not $38.46. It is materially higher once burden and utilization are included.
Use your own payroll and utilization data. If you do not have clean utilization, start with a conservative estimate and tighten it over time.
The point is not precision theater. The point is to stop treating labor like it is free because nobody entered time.
2. Expected support load
For each client, estimate the monthly hours covered by the managed services agreement.
Include:
- Tickets
- Escalations
- Client meetings
- Internal coordination
- Documentation updates
- Vendor management
- Security review time
- Backup and alert response
- Agreement admin
This is where many MSPs underprice. They count tickets, but they miss the work around the tickets.
A client with ten tickets and four messy escalations can cost more than a client with thirty clean tickets. Support load is not just volume. It is complexity.
3. Tool cost per user, device, or client
List the tools included in the agreement. RMM, PSA, EDR, backup, email security, documentation, remote access, DNS filtering, MDR, SIEM, reporting, compliance tools, and anything else bundled into the monthly fee.
Then decide how each cost should be allocated.
Some tools are per endpoint. Some are per user. Some are per tenant. Some are fixed business costs that should be spread across clients.
Do not bury tool cost in overhead if the tool is required to deliver the service. That is service delivery cost.
4. Shared service overhead
Managed services consume shared resources. Dispatch, service management, QA, vendor renewals, internal automation, escalation planning, and client success all touch the agreement.
A small MSP often ignores this because the owner is absorbing the work. That does not make it free. It just means the owner is the margin buffer.
If you want pricing that survives hiring, delegation, and growth, shared service overhead has to be in the model.
5. Target gross margin
Gross margin is what remains after direct delivery costs. It is not net profit. It is the fuel that pays for sales, admin, leadership, product improvement, bad months, and actual profit.
ConnectWise Service Leadership's Q2 2024 report said average managed service gross margin rose to 46.2%, while 16% of MSPs still reported a loss. Its 2025 annual profitability report release said top-performing TSPs posted a fifth straight year above 19% adjusted EBITDA profitability in 2024.
The lesson is simple: average performance is not the target. It is a warning label.
A 50% gross margin target is often a practical floor for managed services. Many mature MSPs aim higher. The right number depends on your delivery model, overhead, risk, and growth plan.
The managed services floor-price formula
Once you have the five inputs, the formula is simple.
Monthly cost to serve = labor + tools + shared service overhead + risk buffer
Floor price = monthly cost to serve / (1 - target gross margin)
If target gross margin is 50%, divide cost by 0.50.
If target gross margin is 60%, divide cost by 0.40.
If target gross margin is 40%, divide cost by 0.60.
The higher the target margin, the more room the price has to cover the rest of the business.
This is the moment where pricing gets emotionally hard. You may discover that a client you thought should be $150 per seat is actually a $205 per seat client. Or that your $4,000 flat-rate agreement needs to be $6,800 to support the way the client behaves.
That does not mean the client is bad. It means the quote and the operating reality are out of sync.
A worked MSP pricing example for a 25-seat client
This example is illustrative. Do not copy the numbers. Copy the method.
Assume a 25-seat professional services client with a standard managed services package.
| Cost item | Monthly assumption | Monthly cost |
|---|---|---|
| Burdened labor | 18 covered hours at $62/hour | $1,116 |
| Tool stack | $32 per seat | $800 |
| Shared service overhead | $15 per seat | $375 |
| Complexity and risk buffer | $10 per seat | $250 |
| Total monthly cost to serve | $2,541 |
Cost per seat is $2,541 divided by 25, which equals $101.64.
Now apply target gross margin.
| Target gross margin | Formula | Floor price per month | Floor price per seat |
|---|---|---|---|
| 30% | $2,541 / 0.70 | $3,630 | $145.20 |
| 50% | $2,541 / 0.50 | $5,082 | $203.28 |
| 60% | $2,541 / 0.40 | $6,352.50 | $254.10 |
This is why peer averages are dangerous.
If you quote this client at $150 per seat, the monthly recurring revenue is $3,750. After $2,541 in direct cost, gross profit is $1,209. Gross margin is 32.2%.
That might feel fine until you remember gross margin still has to cover the rest of the company.
If you quote $205 per seat, monthly recurring revenue is $5,125. Gross profit is $2,584. Gross margin is 50.4%.
Same client. Same scope. Very different business.
The seven cost buckets MSPs forget
Most underpricing is not caused by one huge mistake. It is caused by small omissions that become normal.
1. PTO and non-delivery time
A paid hour is not the same as a usable delivery hour. PTO, training, internal meetings, admin, and context switching all reduce available capacity.
If your labor model assumes every paid hour is client-delivery time, your margin is fictional.
2. Escalation drag
Tier 1 ticket counts do not show the cost of senior people getting pulled into messy environments.
If one client constantly needs your best engineer, that cost belongs in their price.
3. Tool overlap
Many MSPs carry old tools because a subset of clients still needs them. That cost has to land somewhere.
If the tool exists because a client or service package requires it, include it in pricing.
4. After-hours exposure
Even if after-hours work is rare, the promise has a cost. On-call rotation, alert fatigue, response planning, and burnout risk all matter.
Do not include after-hours coverage in a package unless the price carries the risk.
5. Client complexity
Two 25-seat clients can cost completely different amounts.
One has clean identity, standard devices, modern network gear, and responsive decision makers. The other has legacy apps, shared logins, mystery vendors, compliance anxiety, and no documentation.
Those are not the same agreement.
6. Onboarding cleanup
If onboarding includes documentation repair, device cleanup, policy baseline work, backup fixes, and security remediation, decide whether it is a project fee or part of the monthly agreement.
Do not quietly finance onboarding with future margin unless you mean to.
For more on scope boundaries, read Scopable's guide to scoping an MSP project without bleeding margin.
7. Rework from vague quotes
Vague quotes create free work later.
If the agreement says "managed IT" but does not define exclusions, the client will assume more is included than you priced. That is not a sales problem. It is a pricing problem.
Scopable's guide to MSP quoting mistakes that hurt margins covers this pattern in more detail.
What healthy MSP unit economics look like in 2026
Use benchmarks as a reality check, not as your pricing engine.
ConnectWise Service Leadership's Q2 2024 data gives a useful reference point: average managed service gross margin was 46.2%, average adjusted EBITDA for MSPs worldwide was 14.1%, and 16% of MSPs reported a loss. That tells you the industry contains both healthy and unhealthy operators.
V2 Cloud's margin explainer makes a helpful distinction too: gross margin shows service delivery health, while net margin shows the full business after overhead. You need both.
For managed services, a practical target might look like this:
| Metric | Use it for | Practical target |
|---|---|---|
| Managed services gross margin | Service delivery health | 50%+ as a floor |
| Agreement-level effective hourly rate | Client profitability | Above burdened labor cost by a safe margin |
| Net margin | Full-company health | Enough to fund hiring, reinvestment, and profit |
| Revenue per user or endpoint | Packaging sanity check | Compare to your own cost model first |
| Project margin | Separate from recurring margin | Track outside the managed agreement |
The exact target is less important than the discipline. If you do not track it, you will argue from feelings.
How to handle clients below your new floor price
The worst move is to discover the math, panic, and send a vague price increase email.
Do not do that.
Start by segmenting clients into three groups.
Group 1: Healthy clients
These clients are above floor, aligned with scope, and reasonable to support. Keep them clean. Do not let old discounts creep back in. Review pricing at renewal and when scope changes.
Group 2: Fixable clients
These clients are below floor, but the gap has a clear cause.
Maybe the tool stack changed. Maybe the client added users. Maybe support demand increased. Maybe the agreement includes work that should be separate.
For these clients, bring options:
- Increase price to match the current scope
- Remove services from the managed agreement
- Move project work out of the monthly fee
- Change response commitments
- Clean up the environment to reduce support load
- Shift seasonal or uncertain seats to a different term model
Give the client a business choice, not a surprise.
Group 3: Structurally bad-fit clients
Some clients are underpriced because the relationship is not workable.
They ignore recommendations, fight scope, create constant exceptions, churn tickets, or need a level of service they will not pay for.
The price can go up. The behavior may not change.
For those clients, the answer may be a controlled offboarding plan or a narrower agreement with hard boundaries.
Where Scopable fits
Scopable exists because MSP pricing should not live in a spreadsheet that only one person understands.
The quote should carry the assumptions: users, devices, tool stack, labor estimate, exclusions, project work, renewal timing, margin target, and client-specific risk. When those assumptions are visible, the price is easier to defend and easier to adjust when the scope changes.
That is the connection between pricing and quoting. Pricing tells you what the agreement needs to cost. Quoting turns that math into something the client can approve.
If your current process separates discovery notes, labor estimates, margin checks, and proposal writing across five places, margin leakage is not surprising. The system is creating ambiguity.
Scopable helps MSPs turn discovery, scope, pricing logic, and client approvals into a cleaner quote workflow. It does not make hard pricing conversations disappear. It gives you better ground to stand on when you have them.
For adjacent thinking, see Scopable's guide to MSP pricing, quoting, and margin protection and the breakdown of MSP revenue leakage.
The pricing calculator your MSP actually needs
A useful managed services pricing calculator should not start with "market rate."
It should ask:
- How many users, devices, servers, and locations are in scope?
- Which tools are included?
- How many monthly support hours are expected?
- What is the burdened hourly cost of delivery?
- What shared overhead should be allocated?
- What complexity factors increase risk?
- What gross margin target is required?
- What work is excluded or priced separately?
Then it should show the floor price, the list price, and the margin impact of any discount.
That last part matters. A 10% discount is not a 10% haircut to profit. If the deal is already close to floor, it can erase most of the profit.
No public calculator asset is approved yet, so this article should not promise a download. If you want to see the pricing workflow in context, book a Scopable walkthrough instead.
Final rule: never quote below the floor by accident
Sometimes you will choose to price below floor.
You may do it for a strategic logo, a short-term bridge, a cleanup period, or a client you know will grow into the right scope. That is a business decision.
The problem is not choosing it. The problem is doing it without knowing.
MSP pricing in 2026 should be built from cost, scope, and margin. Not vibes. Not peer averages. Not the rate you inherited from 2019.
Your pricing model can be per user, per device, tiered, or flat-rate. Fine. Just make sure the number underneath it survives the work.
If you want to see how Scopable connects discovery, service scope, margin checks, and quote approval, join the Scopable early access list and ask for a walkthrough.
