kyslan

Kyslan / Library

Price rises

Raising MSP prices without losing clients

Updated 27 August 2026 · 11 min read · By Kyslan, a Northbeams product

The short answer

Raise prices annually and by a modest amount rather than rarely and by a large one. The mechanics that decide the outcome are: fix your own billing accuracy first so you are not asking for more while absorbing unbilled work, give at least 60 days notice in writing, raise everyone in the same cycle so nobody feels singled out, lead with what changed on your side rather than with your costs, and offer a longer term as the alternative to the rise. Handled that way, churn from a single-digit increase is normally very low.

Kyslan finds the unbilled work in your own PSA, then writes the change order that bills it. First report free, read-only. Claim it back →

Do this before you raise anything

There is one step that comes before every other piece of advice here, and skipping it is the most common reason a price rise goes badly.

Fix the billing first

Reconcile what you are delivering against what you are invoicing, for every client, before you write a single letter. Published billing research puts unbilled work at 5 to 15% of revenue for a typical provider. If that is your position, you are about to ask clients for 6% more while giving away 10% for free, and you will have burned the goodwill without fixing the problem. Correcting seat counts, block balances and non-billable flags is invisible to the client, costs no relationship capital, and frequently closes most of the gap on its own. See where the money goes.

The second reason to do it first is evidential. Walking into a pricing conversation knowing exactly what you delivered for that client last year, with the hours attached, changes the tone completely. You are not asserting that you provide value. You are showing it.

When to raise, and how often

Annually, on a fixed date, for everybody. That single decision removes most of the difficulty:

An MSP that has not raised prices in three years is not being generous. It has taken a real cut in margin every year while wages, tooling and security requirements rose, and it now needs a rise big enough to be frightening. The uplift clause exists to prevent exactly that, which is why an uplift clause that is never applied is one of the more expensive administrative failures in this business.

How much

Three inputs, in order:

  1. Your input cost movement. Wages first, because delivery labour dominates cost of goods sold, then tooling, then anything new you have been forced to add.
  2. The gap between the client's price and your current list. A client 30% below list needs a different plan from one already at list.
  3. What the contract permits. If there is an uplift clause with a stated mechanism, use it. A rise inside the terms the client already signed is an administrative notice, not a negotiation.

Keep the standard annual rise modest and applied without exception. Where a specific client is materially below list, that is a separate, individual conversation, and it should be staged over two years rather than corrected in one jump. A 30% correction delivered in one letter reads as a penalty however it is worded.

Sequencing the conversations

Do not send them all at once on day one. Work outward from safety:

OrderGroupWhy here
1Two or three friendly clientsYou will discover which objection you have not prepared for, on relationships that will forgive you
2Your lowest margin clientsThe ones who most need it. If one leaves, that is a result, not a loss
3The main body of the bookBy now the letter and the answers are tested
4Your largest clientsBy phone or in person first, letter afterwards. Never a letter cold

Your biggest client should never learn about a price rise from an email. A five minute call from the owner beforehand costs nothing and prevents the single worst outcome, which is a large client feeling processed.

The letter that works

Five paragraphs, one page, no apology anywhere in it.

  1. What we did this year. Specific to them. Tickets resolved, projects delivered, incidents prevented, response times. Numbers from their own account, not marketing.
  2. What changed on our side. What you added or improved, and honestly, what got more expensive. Security tooling and wage inflation are both true and both understood.
  3. The new price, stated plainly. Old figure, new figure, the date it applies. No burying it, no percentage-only phrasing that makes them do arithmetic.
  4. The alternative. A longer term at the current rate, or a lower tier. Giving a choice converts a rise from something done to them into a decision they make.
  5. An open door. A named person, a direct number, and an invitation to talk. Most clients will not use it, and the ones who do were going to call anyway.

Send it at least 60 days before it applies, in writing, and put the effective date in the subject line. Notice periods are usually a contractual requirement, and they are also what separates a professional adjustment from a surprise.

Handling pushback

Expect a small proportion to respond, and most of those to be asking rather than objecting. Four answers worth having ready:

"We were not budgeting for this."

Offer the timing, not the money. Applying it a quarter later costs you one quarter and keeps the increase permanent. Discounting the rise itself costs you every year afterwards.

"Someone quoted us less."

Ask what is in their number. Out of hours, onboarding, security tooling, backup and offboarding are the usual gaps, and the comparison is almost never like for like. Then show what you delivered for them last year, in hours. If they still prefer the other number, they are buying a different product.

"What are we actually getting for the extra?"

The honest answer is usually continuity rather than a new feature, and saying so plainly lands better than inventing a benefit. Costs rose, the service continues, and the alternative to a small annual rise is a large occasional one.

"Can we have a discount instead?"

Trade, do not concede. A longer term, a payment method that costs you less, a case study, a reference call. A discount given for asking is a discount every client learns to ask for.

When someone threatens to leave

First, work out whether you want them to stay. Run their gross margin and their effective hourly rate before you respond. Some accounts should be allowed to go, and it is far better to know that at the start of the conversation than to discover it after you have made concessions to keep them.

If you do want them:

Six things not to do

  1. Do not apologise. A rise framed as regrettable invites negotiation.
  2. Do not blame inflation alone. It is true and it is also what everyone says. Lead with what you delivered.
  3. Do not raise prices while your billing is inaccurate. You are asking for a rise while giving away more than the rise is worth.
  4. Do not exempt the difficult clients. Exemptions leak, and the client who shouted loudest becomes the template.
  5. Do not bundle a price rise with a model change. Two changes at once reads as a rise in disguise. Handle the model change separately.
  6. Do not give less than the contractual notice. It converts a commercial conversation into a contractual dispute, which you will lose.

The underlying point is that a price rise is a test of whether you can evidence your value. If you can show a client exactly what you delivered for them last year, with the tickets and hours behind it, the conversation is straightforward. That evidence is a by-product of accurate billing, which is the same work that stops the leak in the first place. Kyslan produces it read-only from your PSA, and the first audit is free.

Common questions

How often should an MSP raise prices?

Annually, on a fixed date, applied to every client in the same cycle. Yearly rises are expected, stay small enough not to trigger a procurement review, and mean nobody feels singled out. The alternative pattern, raising rarely and by a large amount, produces exactly the size of increase clients resist and leaves margin eroding in every year between.

How much notice should an MSP give for a price increase?

At least 60 days, in writing, with the effective date stated plainly and ideally in the subject line. Check the contract first, because a notice period is usually a contractual requirement, and giving less than the agreed notice turns a commercial conversation into a contractual dispute.

What do I do if a client refuses an MSP price increase?

Work out first whether you want to keep them by checking their gross margin and effective hourly rate. If you do, take the conversation to the phone, find out whether price is the real objection or a proxy for an unresolved service issue, and offer scope changes rather than price cuts. Moving a client to a tier that matches what they actually use is legitimate. Same service for less money is not.

Should I raise prices for all clients at once?

Apply the increase to everyone in the same cycle, but sequence the conversations. Start with two or three friendly clients to find the objection you have not prepared for, then your lowest margin accounts, then the main book, and speak to your largest clients by phone before any letter reaches them. Exempting difficult clients is the one thing to avoid, because exemptions become the template.

Why should an MSP audit billing before raising prices?

Because unbilled work typically runs at 5 to 15% of revenue, so a provider in that position is about to ask for a single-digit increase while giving away considerably more for free. Correcting seat counts, block balances and billing flags is invisible to clients, costs no relationship capital, and often closes most of the margin gap on its own, which makes any rise that follows smaller and easier to justify.

Keep reading

See your own number, then send the invoice for it

Kyslan reads 90 days of your tickets, time entries and contracts, finds the work you delivered and never billed, then writes the change order that puts it back on the invoice. Read only, nothing installed, first report free.

Claim it back

Free · read-only key · no card · HaloPSA, ConnectWise Manage, Autotask PSA or a CSV export