MSP Client Retention: Why Clients Leave And How To See It Coming

MSP client retention for small MSPs: why clients leave, the warning signs, a save play, and how open work and predictable bills keep clients.

Keeping MSP clients

MSP client retention is the share of clients who stay with you over a period, new signings excluded. Clients can leave when the service stops fitting their needs, the work goes unseen, or a bill surprises them. Some leave without a single complaint.

What changed in this update · Nov 9, 2026
  • Rewritten as a full retention guide; the transparency habits now sit under "Be Transparent."
  • Our customer journey and customer experience posts are merged into "Retention Across The Client Journey."

This guide comes from the team behind SherpaDesk, a helpdesk and professional services automation (PSA) tool a small IT team can run alone.

What Is MSP Client Retention?

For an MSP, client retention means managed services agreements that renew instead of ending. The formula leaves new clients out, so a good sales quarter can't hide losses:

Retention rate = (clients at the end − new clients still active at the end) ÷ clients at the start × 100

Example: you start the year with 40 clients, sign 4 who are all still active, and end with 40. That's (40 − 4) ÷ 40 × 100 = 90%.

Why Client Retention Matters For A Small MSP

Winning a new client costs much more than keeping one you have. In a 2025 r/msp thread, one MSP billing about $100,000 a month in recurring revenue said it was "at risk of losing 40% of it in the next few months." Its small clients were cutting back at renewal.

Lost accounts, annualized

$25,200annualized fees from lost accounts

Monthly fee × 12 × clients lost. Your numbers stay in the browser.

Why MSP Clients Leave

In a 2026 r/msp thread, one member described losing a ten-year, $1,800-a-month client with "Not a single billing complaint nor a single complaint at all."

Common reasons MSP clients leave
ReasonWhat the client experiencesWhat you can do
The value is invisibleNothing breaks, so they wonder what they pay forShow the work every month
A bill they didn't expectAn overage or a new line with no warningWarn before included hours run out
Recurring disruptionsThe same fault returns, or repeat fixes they never reportFind the cause and agree a change
Needs that changedMore staff, a new site, new rules to followReview the agreement against how they work now
A new decision makerSomeone who doesn't know your historyMeet them in the first month
Budget cutsIT looks like a cost to trimOffer a smaller scope or a pause
Sold, merged, or closedThe buyer has its own IT, or the owners retireLittle; plan a clean handover

When the service no longer fits

A client can outgrow the service. At each existing review, ask: "What change in your business in the next 90 days does the current agreement not cover?" Agree the scope change, owner, and decision date.

Example

A dental office's imaging PC drops off the network on Monday mornings, and a technician fixes it weekly. The cause: weekend updates reset its network adapter settings. You block that driver update, reapply the setting by script, and check the PC remotely before Monday opening. The office manager confirms the X-ray screen loads.

Be Transparent: Show The Work, The Bill, And The Mistakes

Openness breeds loyalty and credibility, and it starts with communication: the client hears what you did, what it cost, and what went wrong before they have to ask.

Show the work they never see

Good managed service is easy to miss: patches install and nobody calls.

  • A client portal where their staff check ticket status without calling you.
  • A one-page monthly summary: tickets closed, response times, problems caught early.
  • Updates on open incidents in a set format, so nobody has to chase you.

Example

What happened: incoming email was delayed about 40 minutes this morning after a filter update. Impact: two client quotes reached your team late. What we're doing: the update is rolled back, and we're releasing held messages. Owner: Sam. Next update: 2 p.m. today, even if nothing changes.

Make the bill predictable

Link labor charges to tickets and time entries; explain fixed fees against the agreed scope. If the agreement includes a block of hours, warn the client before it runs out, not on the invoice.

Price the exceptions, too, or a free 4 a.m. call-out becomes part of the service. In the ten-year client thread, the top reply said "any of that over the top stuff you mentioned needs to be a conversation about billing them." Another member added: "When you undercharged / overserved the client, they undervalued your work."

Say what to expect, then keep the promise

Clients want to know what to expect: how fast you answer, what counts as urgent, what happens after hours. Put response targets in writing, using our Service Level Agreement Template. If you can't keep a promise, say so before the deadline.

Tell them about mistakes and changes early

Be transparent with your customers about failures. If your patch breaks a printer, tell the client what happened, how you fixed it, and what you changed. Give planned price, service, and staff changes the notice period you agreed. Tell clients about unexpected changes once they're confirmed. Thank them for renewals and referrals.

Share what you know

When a problem keeps coming back, explain the cause in plain words and give the client a short guide to prevent it. For example, show staff how to spot the phishing emails that keep reaching them.

Answer questions about price, process, and documentation

When a client asks about pricing, documentation, or who holds the admin passwords, acknowledge it the same day, name an owner, and give an answer date. Our Managed Services Agreement guide covers those clauses.

Good managed service is easy to miss: patches install and nobody calls.

Warning Signs To Review Each Week

Some signs can appear before a cancellation. In a 2026 r/msp thread on catching churn risk, one member tracks review attendance, satisfaction, and profitability: "Usually these start to crash 2 of 3 at a time."

Review accounts weekly. For each, compare the month with its usual activity, record any concern, name an owner, and set the next contact date.

Warning signs and what to do this week
SignCompare withWhat to do this week
The client raises canceling or switchingNothing; this one is enoughCall the decision maker today
Reviews pushed or skippedPast attendanceAsk the decision maker for 20 minutes on their plans
Slower replies, fewer side questionsTheir usual reply patternCall the main contact instead of emailing
Questions about invoice linesPast invoice questionsWalk through the invoice line by line
Low satisfaction scoresTheir usual scoresCall about the lowest score and agree a fix
No survey replies at allPast response rateAsk for feedback on your next call
A new owner, manager, or finance leadTicket contacts and signaturesBook an introduction meeting
Ticket volume well above or below normalThe last six monthsAsk why: fewer tickets can mean things work, or a test of in-house IT
The fee no longer covers delivery costLabor and tool cost for the accountReview scope and price before renewal

Two or more signs on one account are a reason to investigate, not proof the client is leaving. For one r/msp member helping a friend's MSP, churn started with questions about pricing and the bill.

Subscribe to the SherpaDesk Blog.
Get Tips for Running IT With a Small Team.

Loading form…

A Save Play For An At-Risk Client

Run it when the weekly review flags an account, or the same day a client raises canceling.

  1. Confirm the signs

    Pull the last 90 days: tickets, response times, invoice questions, and meeting history.

  2. Call the decision maker

    Talk to the person who signs the renewal, not only the contact who files tickets. Ask for 30 minutes about their business.

  3. Ask what has changed

    Ask about plans, budget, staff, and IT frustrations, and whether they're looking at other providers.

    Example: "If you were choosing an MSP today, would you choose us again? What would make that a yes?"

  4. Agree which problem to fix first

    Agree the fix and a date, then tell them when it's done. A workaround is fine while you fix the cause, if you say which it is.

  5. Reset scope and price in writing

    If the agreement no longer fits, change it: a smaller scope, a pause, or a price for the free extras. Set a check-in date and ask then whether the fix held.

    Common mistake: agreeing to everything on the call and leaving the old agreement unchanged.

A pause can work when the problem is cash. One r/msp member's clients lost all income for two months in the pandemic. "We offered a pause on their contract with the option renegotiate when they had a better outlook on the future." They kept almost all of them.

When to let a client go

In the ten-year client thread, many replies said $1,800 a month for 45 users was too little for the after-hours work expected. If keeping a client means delivering below cost, plan a clean handover.

Retention Across The Client Journey

Retention at each stage of the client journey
StageTouchpointsRetention job
Before signingWebsite, social posts, proposal, sales callPromise only what your agreement covers
OnboardingKickoff, documentation, first ticketsFix early problems the client can name
Everyday supportEmail, phone, portal, after-hours lineAnswer within the target; status they can check
BillingInvoices, pre-paid hours, overageNo line the client can't trace
ReviewsQBRs, the decision makerTalk about their business and plans
Renewal and changePrice changes, scope updates, new contactsGive changes the agreed notice

Map one journey this month:

  1. Pick one client and one recent request, such as a new-hire setup.
  2. Trace it from first contact to close: the channel they used (email, phone, portal, a social media message), each handoff, each wait, and every repeated explanation. A named person moves social messages into a ticket and tells the client where to continue.
  3. Separate the roles. The person who submitted the ticket and the person who approves IT spend may see different journeys.
  4. Ask the client where it got frustrating. Listen for friction they can name: forms filled in twice, calls to chase status, repeated logins.
  5. Pick one improvement, name an owner, and set a review date.

How To Measure Client Retention And Collect Feedback

Measure client retention each quarter against the same quarter last year. Record the monthly fees of lost accounts next to the count, so one large loss doesn't hide behind a good percentage.

Ask about the conversation too: did the technician understand the business impact and explain the next step? Use two kinds of feedback:

  • Numbers: a satisfaction question on closed tickets, tracked by client each month. Our Helpdesk Metrics Guide covers how to read CSAT.
  • Conversations: two open questions at every review: what should we stop doing, and what should we start?

Then close the loop: asking for feedback and doing nothing can frustrate clients more than not asking. For each issue, assign an owner, agree a response date, and later ask whether the fix worked.

When a client leaves anyway, book a short exit call. Ask what changed and what would have kept them, and log the answer against the account.

Worked Example: An Accounting Firm Goes Quiet

Example

The account. Say you run a five-technician MSP. A 14-user accounting firm pays $2,100 a month and renews in October.

The signs, in the May 6 review. The quarterly review was moved twice, the office asked about two April invoice lines, and a new operations manager copies herself on tickets. You investigate.

The call. The managing partner says the new manager is collecting quotes. The firm can't see what the agreement covers, and weekend server work keeps arriving as extra invoice lines.

The change. By May 20 you send a one-page summary of last quarter's work, and invoices show time per ticket. The $2,100 agreement now includes a monthly Saturday maintenance window.

The follow-up. At the June 24 check-in, the operations manager confirms the June invoice matched the agreement, with no questions.

The result. In October the firm renews for 12 months. Losing them would have meant $25,200 in annualized fees.

Keep The Work And The Bill In View

How this works in SherpaDesk

Portal, contracts, and invoices that clients can follow

Keep clients informed. Your clients can log in to check the status of their tickets and update them, and you can give each account its own portal.

Keep the bill predictable. A contract can carry pre-paid hours. Alerts fire when a pre-paid pack nears or passes its included hours, and overage can move into a new pre-paid pack. Uninvoiced time and expenses collect in "Ready to Invoice," organized by contract, before they reach an invoice.

A helpdesk and PSA a small IT team can run alone. No contract. No implementation project. No dedicated admin.

Base Camp is $45 per agent per month ($40 billed annually). The first agent is free, forever, so a team of three pays $90 a month ($80 billed annually). The trial is 14 days free with no card.

Invoicing And Billing In SherpaDesk

Who this isn't for

This guide is for MSPs with managed services clients. If you use SherpaDesk, it has no built-in survey tool: you add your survey link to the closed-ticket email message.

Frequently Asked Questions

How do you calculate client retention?

Subtract the new clients still active at the end from the clients you have at the end of the period. Divide by the clients you had at the start, and multiply by 100. Start with 40, sign 4, end with 40, and your rate is 90%.

What is a good client retention rate for an MSP?

Judge it at the scale of your own portfolio. With 40 starting clients, each loss moves your rate by 2.5 percentage points, so one departure can swing the number. Review every lost account on its own: why it left, its monthly fee, and whether you saw signs first.

Why do MSP clients leave without complaining?

If the work goes unseen, the service stops fitting, or a bill surprises them, some clients collect quotes instead of calling you. Signs such as pushed reviews or questions about invoice lines can show up first, so review every account weekly and investigate when two appear.

How often should an MSP meet with a client's decision maker?

Bring the decision maker and their business plans into your existing reviews (see our MSP QBR Template). Add a conversation when circumstances change, such as a new owner or a budget cut. One r/msp member moved check-ins with decision makers from yearly to every six months, mostly in person. Another warned that "a QBR (for most) is about the MSP not the business you’re servicing."

What is the difference between client retention and churn?

Retention is the share of starting clients who stay, new signings left out. Churn is the share of starting clients who leave during the period. Together they make 100%: a 90% retention rate means 10% of the clients you started with churned. Track the lost monthly fees beside both.

About the author
Patrick Clements Co-founder & CEO, SherpaDesk

Patrick co-founded SherpaDesk and has led it as CEO since 2013. He has worked with IT service providers since 1998, first on network projects for schools and government offices, then on the helpdesk software their technicians use every day.

Published Apr 19, 2023 by

Run a help desk your clients can set their watch by

Tickets, SLAs, time tracking and invoicing in one place. Your first agent is free, with no contract.