How to Raise MSP Prices Without Losing Clients

Most MSP owners know some of their prices are too low and still put the increase off, because they fear the phone call. The advice online is mostly vendor and consultant opinion, and none of it tells you how many clients actually leave. This guide does not pretend otherwise. It gives you the arithmetic that shows how much churn an increase can absorb, a way to decide which clients go first, and a sequence you can run in one quarter.

How many clients can you lose before a price rise stops paying?

Fewer than most owners fear when margins are healthy, and more than they fear when margins are thin. A price rise of i on a service with gross margin m stays profitable until you lose i / (i + m) of your seats. At a 5% rise and a 40% gross margin, that is about 11% of seats.

The formula comes from comparing gross profit before and after. If today's price is c, your direct cost per seat is v and the new price is p, you keep today's gross profit while you retain at least (c - v) / (p - v) of your seats. Rewritten with percentages, the share you can lose is the rise divided by the rise plus your gross margin. The table applies it.

Illustrative arithmetic: the share of seats you can lose before gross profit falls below today's. The margins are example values, not market data. Find your own gross margin by client, not for the company as a whole.

Two limits. The table ignores what it costs to replace a lost client, and it ignores any effect on other clients. Treat it as a floor for the decision, not a forecast. The pricing calculator runs the same maths on your own cost per user, and how to price MSP services shows how to build that cost.

Why are price rises harder to avoid in 2026?

Costs are rising faster than the contracts that pay for them. In Kaseya's 2026 survey, 30% of MSPs said rising labour, tool and infrastructure costs directly constrained growth, and the report describes pricing power as limited. ScalePad's 2026 survey lists rising labour costs and vendor pricing among the top growth challenges.

10%

Kaseya, 2026 State of the MSP Report, 2026Vendor surveyn=1,061Verified 2026-10-11

30%

Kaseya, 2026 State of the MSP Report, 2026Vendor surveyn=1,061Verified 2026-10-11

ScalePad's list also shows why owners hesitate. Clients push back as well, so the squeeze runs in both directions.

Source: ScalePad, 2026 MSP Trends Report, Chapter 5 (ScalePad is a software vendor). Kaseya's figures on smaller deals point the same way: the typical customer spending $25,000 or more a year fell from 75% to 41%, and the largest MRR-per-client band is now $1,000 or less. If your average contract is shrinking, fixed onboarding and account-management effort is spread over less revenue, which is a margin argument for raising prices on small accounts first.

ScalePad also makes a point worth keeping. It says top performers demonstrate business impact more effectively, which may explain why they are less likely to say price increases affect customer satisfaction. That is the report's interpretation, not a measured cause, but it matches the practical advice in this guide: an increase lands better when the client can see what they received.

Which clients should get the increase first?

Start where the gap between price and cost is widest, not with the clients least likely to complain. Rank every client by gross margin and by technician hours consumed, then sort them into four groups. Under-priced legacy accounts and high-effort accounts go first. Healthy, loyal accounts get the standard annual step.

This segmentation is MSPCoach editorial judgement. ScalePad's report notes that some high performers report higher client churn than average and suggests they are comfortable losing bad-fit customers. That is also an interpretation, but it is a useful reminder that losing the wrong client is not the same as losing revenue you needed. You need per-client margin to do this properly; if you do not have it, build it before you send any letter. The profit margins guide explains how to calculate it.

How should you structure the increase?

Pick the mechanism that fits the contract and the size of the gap. A scheduled annual escalator written into the agreement is the lowest-friction option, because the client agreed to it at signing. A one-off reset at renewal or a phased catch-up suits accounts that have drifted. Repackaging suits accounts where you are adding services.

On timing, Arcserve (a data protection software vendor) advised in a 2018 blog post to give 60 to 90 days' notice, raise prices in small steps more often rather than rarely, and not to hide an increase in a work order. The post cites no data, so treat it as an opinion. It does fit the break-even logic above, because a smaller step lowers the churn it can cause. Read the notice and change clauses in your own agreements first. They set the real minimum.

What should the letter and the call say?

Keep the letter short and specific. Say what changes, when, and why, then say what the client keeps. Follow it with a call or meeting from someone who knows the account. The letter protects you; the call keeps the relationship. Here is an outline you can adapt.

Send it after a good quarterly review, not after an incident. Do not apologise and do not over-explain: a long defence reads as doubt. If you have no recent evidence of value to put in step 3, fix that first, because it is also the thing that determines whether clients stay. Kaseya's 2026 survey found 19% of MSPs now struggle to demonstrate value quickly, up from 10%.

How do you handle pushback?

Treat each objection as information about the account. Most pushback is about budget timing or about scope clarity, and both can be answered without cutting your price. Decide in advance how far you will move, using the break-even table, so the conversation does not set the policy.

This table is editorial judgement. No public study we found measures which responses reduce churn. Log every objection and its outcome for a quarter and you will have your own data.

When is the wrong time to raise prices?

Not during an unresolved incident, a run of missed SLAs or a staffing gap that clients can feel. An increase tied to bad service looks like a penalty, and it gives the client a reason to leave that has nothing to do with price. Wait until service has recovered before you act.

Fix the service first, wait for a visible win such as a clean quarterly review, then send the letter. The same applies if you cannot answer the question "what did the client get for this?"

How do you know it worked?

Measure the outcome against the break-even you set. Compare seats retained with the share you could afford to lose, gross profit per client before and after, and churn over the next 90 days. Also count disputes and late payments, which often show friction before cancellations do.

Put the numbers into the KPI benchmark checker to see how your margin compares with the Kaseya distribution, and into the pricing calculator to set the next step. Our pricing models guide covers review cadence, and the pricing and profitability hub collects the rest of the series. If your increase includes new security services, read how to package and price managed security. If a sale is on the horizon, a documented history of scheduled increases helps; see how MSPs are valued.

A note on method

The break-even formula is arithmetic and can be checked by hand. The cost-pressure figures are as printed in Kaseya's 2026 report (30% rising costs; deal-size shifts) and ScalePad's 2026 report (Chapter 5, growth challenges), both read in the source PDFs on 11 October 2026. The Arcserve post was opened on the same date. We did not open the other price-increase guides that appear in search results, so we do not cite them. Our methodology page explains how we source and verify data.