MSP Renewal MSA Selling — 60-Min Training

The renewal that gets shopped, and the one that doesn't

Picture two account managers at the same 40-person MSP, both holding a $15K MRR manufacturing client whose Master Services Agreement renews on March 31.

The first AM opens the PSA on March 15, exports the current contract line items, adds a 3% bump, and emails a PDF quote with the subject line "Renewal — please review." The client's controller forwards it to the CFO. The CFO has never met the AM. The only artifact the CFO has ever seen from this MSP is an invoice. So the CFO does what any reasonable finance person does with an unexplained recurring expense: sends it to two competitors for a comparative quote. Now the AM is defending a number in a spreadsheet against firms who have never touched the environment and can therefore promise anything. The renewal closes at a 6% discount, one-year term, no expansion, and the client is measurably closer to leaving than they were a month prior.

The second AM starts on January 30 — sixty days out. She pulls twelve months of ticket history tagged by priority, mean time to resolution, and SLA attainment. She counts endpoints: the client signed at 85, and the environment now runs 142. She prices that gap at the firm's published per-endpoint rate and lands on roughly $3,400 a month of service the MSP has been absorbing without billing. She pulls the risk register — end-of-life hardware, workstations off the patch baseline, three backup restore tests that were never validated. She identifies three named expansion plays with real numbers attached. She books a 45-minute meeting for March 1 with the CFO in the room, not just the IT manager.

By the time the March 1 meeting happens, the renewal is effectively decided. The CFO spends forty minutes learning what the MSP actually delivered, seeing the unbilled gap quantified, and understanding the security exposure sitting in the environment. The price conversation occupies the last ten minutes and lands as a correction rather than an increase. That is the whole thesis of the training: the renewal is won in the 30 days before the QBR, not in the QBR itself.

The distinction matters more in managed services than in most subscription businesses because MSP scope drifts silently. A SaaS seat count is enforced by the product. An MSP's scope is enforced by nobody — a client adds a location, onboards fifteen people, spins up a new SaaS tenant, and the tickets simply start arriving. Nothing bounces. The service absorbs it. Which means the annual MSA renewal is the only structural moment where the contract gets re-synced to reality. Skip that sync for three consecutive years and you are running a business at a materially worse gross margin than your own pricing model says you should.

The same dynamic shows up in adjacent service businesses and is worth naming in the room, because it makes the lesson portable. Marketing agencies on monthly retainers experience it as deliverable creep. Outsourced accounting firms experience it as transaction-volume creep. Staffing and RPO firms experience it as req-count creep. In every one of these, the renewal is the only enforcement mechanism the contract has, and the firms that run a disciplined pre-renewal data motion hold materially better margins than the ones that renew by email.

How the pre-renewal motion actually works

The mechanism is a timeline, not a meeting. Give every AM the same clock and the same artifact.

T-60: pull the data pack. This is the non-negotiable input. Whether the team runs ConnectWise PSA, Datto Autotask, HaloPSA, or Kaseya BMS, the same six blocks come out: account identity and tenure; twelve months of ticket volume by priority with MTTR and SLA attainment; a scope-creep tally listing every endpoint, user, site, and out-of-scope SaaS app added since signing; project work delivered outside the MRR; the open risk register; and three named expansion targets. No data pack, no QBR. That rule needs to be stated as a rule, because the failure mode is always an AM who "knows the account well" and skips the export.

T-50: dollarize. The single highest-leverage translation in the whole motion is converting units into dollars. "You've gone from 85 endpoints to 142" is a fact the client can shrug at. "That's roughly $3,400 a month of service we've absorbed at our standard unit rate" is a number the CFO has to respond to. Do the same for added users, added sites, and out-of-scope applications. Present the total as absorbed cost, not as a bill.

T-45: name three expansion plays. Three, specifically. One is an afterthought and five is a menu that stalls the decision. In current MSP practice the three that recur most are a Microsoft 365 Copilot deployment and adoption service, a managed detection and response overlay, and a vCISO or compliance-as-a-service wrap for clients in regulated verticals.

T-30: book the QBR with the decision maker. If the person who signs cannot attend, reschedule. Running the QBR with the IT manager alone converts the meeting into a relay race where your best material gets summarized by someone who doesn't own the budget.

T-14: hold the QBR and put the redline on the table. Not "we'll send paperwork after." The document is physically present at minute 35.

T-7 to T-0: countersign before auto-renew triggers. An MSA that auto-renews on your behalf is a safety net, not a strategy — a client who lets it trigger without a conversation is a client who has stopped valuing the relationship.

Note what the diagram does not contain: a step called "send quote." The quote is an output of the motion, not the motion itself. When an AM's renewal process collapses to a single email, everything upstream of that email has been quietly deleted.

Real numbers, ranges, and what the expansion math looks like

Train the arithmetic on a whiteboard with a representative account, because AMs sell expansion far more confidently once they have built the stack once with their own hand.

Take the 142-endpoint, roughly 100-user client at $15K MRR.

Scope-and-CPI correction. A single-digit percentage adjustment on the base — commonly in the 5-8% range depending on how much drift has accumulated — is the floor. On $15K that is $750 to $1,200 a month. This is the least glamorous line and the most reliably winnable, because it is backed by the tally rather than by a market argument.

Microsoft 365 Copilot deployment. Microsoft's list price for the Copilot add-on has been $30 per user per month, and partners buy through CSP at standard program margin. The MSP's actual revenue is layered on top: deployment, tenant readiness, data-governance review, permission remediation, training, and prompt-library buildout. Charged as a managed adoption service in the $15-$25 per user per month range, a 100-user client lands roughly $4,500-$5,500 MRR on the combined line. The margin lives in the service wrap, not the license resale.

MDR overlay. Endpoint-priced managed detection runs in the single-digit-to-low-teens dollars per endpoint per month at cost depending on vendor — Huntress and Blackpoint sit toward the lower end, SentinelOne's Vigilance service toward the higher. At 142 endpoints and a blended $10 cost, that's about $1,420 monthly in COGS. Sold at typical managed-security markup, the line contributes roughly $3,000-$4,000 MRR. Gartner has tracked MDR as one of the fastest-growing managed security categories, and it is the expansion play with the shortest explanation time in a CFO meeting because the risk register you just presented is the proof.

Agentic support pilot. AI-assisted L1 triage — password resets, access requests, software provisioning, routine how-to deflection — is now a sellable managed line rather than an internal efficiency project. Priced in the $15-$25 per user per month band, even a modest 100-user pilot adds $1,500-$2,500 MRR. Be honest about deflection rates in the sale; overpromising here poisons the second-year renewal.

vCISO and compliance. Retainers commonly land in the low-to-mid four figures monthly and scale higher for SOC 2, HIPAA, or CMMC programs with audit support. This is the natural attachment for MSPs who have specialized into a vertical, which a majority of the market now has.

Stack the plays and a $15K MRR account plausibly clears $23K-$25K MRR on the same logo — call it 55-65% account growth with zero new-logo acquisition cost. That comparison is the argument for why renewal discipline outranks prospecting discipline in a mature MSP: existing-client expansion carries no CAC, closes on a known relationship, and lands against a decision maker who has already survived an onboarding with you.

Two term structures to price against each other. A one-year renewal at the corrected rate with a standard annual escalator built in. A three-year renewal at the corrected rate with the escalator capped meaningfully lower and a headline deliverable — the Copilot deployment, typically — converted from time-and-materials to fixed fee. On a mid-five-figure MRR account, the capped-escalator difference compounds into a genuinely large number over the term, and letting the CFO compute that number in silence is more persuasive than any slide you could build.

Hold a discount ceiling of roughly 4% and discount on term length, never on base rate. A base-rate concession teaches the client that your price is a starting position, and it will be tested harder every cycle thereafter.

Trade-offs: hold the line, or trade the concession

Not every renewal should be maximized. The training has to teach judgment about which lever to pull, or AMs will apply the aggressive script to accounts where it costs the relationship.

When to hold firm. The client has grown, the scope tally is large and documented, SLA attainment is strong, and the risk register gives you a legitimate expansion story. Here the correct move is to hold the corrected rate and let the client choose between one-year and multi-year. AMs who hold in this scenario close at broadly the same rate as AMs who fold — they simply close at higher MRR.

When to trade rather than hold. The client is genuinely price-constrained, the relationship is healthy, and the tally is modest. Trade a rate freeze for term length: a twenty-four-month price hold in exchange for a three-year commitment with the correction landing in year three. This is the cleanest concession available because it costs you a small amount of near-term MRR and buys you two additional years of retention plus a much longer runway to land expansion.

When to adjust downward. If the environment has shrunk — the client consolidated sites, went through a reduction, migrated a workload off your stack — say so before they do. An unprompted downward adjustment is the most durable trust-building move available at renewal, and it is almost always repaid with the longer term. Sandbagging a shrinking account is a short-term margin win and a medium-term termination.

When to walk. Some accounts should not be renewed. The signals are consistent: the client wants scope expansion at flat price, treats your engineers as an interchangeable vendor, escalates past the AM habitually, and has a pattern of late payment. In most MSP books, a small tail of accounts consumes a disproportionate share of support hours at the worst margins. Renewal is the only clean exit point in the contract lifecycle. Offboard with a 90-day transition plan and a documented handover — you want the reference intact even when the account isn't.

Auto-renewal versus active renewal. A 90-day notice with auto-renew is standard and worth keeping, but treat it as insurance rather than a plan. Every account that silently auto-renews is an account whose scope drift is compounding untouched and whose relationship with the signer is atrophying.

Pitfalls that cost renewals, and the language that avoids them

Most lost renewals are lost by a sentence, not by a number. Read these aloud in the room and have the AMs flinch at their own habits.

Leading with the increase. "We're going to need to raise prices this year" is passive, apologetic, and invites negotiation before you've established value. Lead with delivery, then present the correction as arithmetic that follows from the tally.

Justifying by your own costs. "Our costs have gone up" asks a client to subsidize your P&L. No buyer has ever found that persuasive. The scope tally is client-side arithmetic; your cost structure is not.

Deflecting to a vendor. "Microsoft is raising prices on us" hands away ownership of the relationship and teaches the client that your pricing is someone else's decision. Handle licensing volatility structurally instead — a vendor pass-through clause separating third-party license costs from your managed-services rate — so it never needs to be argued in a meeting.

Asking for their budget. "What's your budget for next year?" surrenders the anchor. You price the service.

Pre-conceding. "We can probably work something out" before any objection has been raised trains the client to push.

Naming competitors. Never bring a competitor's pricing into a QBR. When the client raises one, normalize scope rather than matching top-line: ask for the competing statement of work side by side and compare after-hours coverage, security tooling, vCISO inclusion, and onboarding. Most cheaper quotes are cheaper because they are a smaller product.

Rehearse the standing objections. *"We're already paying you a lot"* is answered with the tally, framed as absorbed cost being corrected. *"We'll buy Copilot direct from Microsoft"* is answered by separating license from outcome — Microsoft sells entitlement, not tenant readiness, permission hygiene, change management, or adoption, and unmanaged rollouts stall at low usage often enough that the service wrap is the whole point. *"MDR feels like fear-selling"* is answered with the client's own risk register and a cost comparison against published breach-cost research; the annualized MDR spend on a mid-market environment is a small fraction of a single incident. *"Just give us one more year at the current rate"* is answered by holding both options open and letting the client choose.

Scaling the format wrong. A $5K MRR client does not need a 90-minute QBR with a full deck. Give it 30 minutes and a one-page data pack. A $50K MRR client gets the full 90 minutes with the CFO. Scale the format; never scale away the discipline.

Treating the QBR as separate from the renewal. They are the same meeting. Firms that run them separately give the client two chances to disengage and lose the compounding effect of showing value immediately before asking for a term.

Letting the motion die after the signature. Quarterly QBRs should run for the entire term, including years two and three of a multi-year deal. The renewal QBR is then simply the last quarterly review with a redline on the table — no ramp-up, no relationship reconstruction, no scramble.

Close the 60-minute session with three written commitments per AM, taped to the monitor: the next five renewals get a data pack at T-60 and a QBR booked at T-30, calendared by Friday; every renewal QBR ends with a signed redline inside seven days; and each AM carries a target renewal MRR uplift with at least one named expansion attached. Commitments that aren't written down don't survive the walk back to the desk.

Related questions

How long before the renewal date should the data pack be built?

Sixty days. That leaves ten days to dollarize scope creep, five to select expansion plays, and thirty days of runway to book the QBR with the actual signer before the auto-renew window closes.

Who must be in the renewal QBR?

The person who signs the check — CFO, COO, or owner. The IT manager is a champion, not a decision maker. If the signer can't attend, reschedule rather than running a meeting whose conclusions have to be relayed secondhand.

Should the price increase be presented as CPI or as scope correction?

Scope correction, with CPI folded in quietly. Correction is backed by a client-side tally they can verify. CPI alone is a macroeconomic argument that invites a macroeconomic counterargument.

Does this motion work for non-MSP recurring-service businesses?

Yes. Agencies, outsourced finance teams, and staffing firms all suffer silent scope drift with no product-side enforcement. The T-60 data pack, dollarized creep, and QBR-as-renewal-arena transfer directly; only the unit of drift changes.

What if the client refuses a multi-year term outright?

Take the one-year at the corrected rate and keep quarterly QBRs running. A client who won't commit to term is usually telling you the relationship isn't strong enough yet — that's a retention project, not a pricing problem.

FAQ

How do I run this training if my AMs have never done a structured QBR?

Spend the first session building one real data pack live, using an actual upcoming renewal from someone in the room. Reading a template produces nodding; building one produces an artifact. Have each AM leave with a partially completed pack and a calendar hold for the QBR.

What if the client insists on a price freeze?

Trade it for term. A twenty-four-month rate hold in exchange for a three-year commitment with the correction arriving in year three is the cleanest concession in the playbook — it costs modest near-term MRR and buys two extra years of retained revenue plus room to land expansion.

How do I protect against mid-term vendor price changes?

Structurally, in the MSA. Keep third-party licensing on a documented pass-through clause, separate from your managed-services rate. Without that separation you absorb every upstream increase and end up renegotiating mid-term from a weak position.

How do I sell MDR to a client who already has antivirus?

Draw the distinction plainly: endpoint protection detects known-bad signatures and behaviors; managed detection and response adds continuous human-monitored analysis, threat hunting, and incident response activation. The client's own risk register is the strongest supporting evidence you'll have.

What's the right QBR cadence for a multi-year client?

Quarterly, for the entire term. It keeps the relationship with the signer alive, surfaces scope drift while it's still small enough to bill incrementally, and converts the eventual renewal into a routine conversation rather than an annual referendum on your value.

When should I walk away from a renewal instead of selling it?

When the client demands scope growth at flat price, has a pattern of late payment, or consumes support hours far out of proportion to the MRR. Offboard deliberately with a 90-day transition plan; a clean exit preserves the reference, a messy one costs you referrals.

Sources

1. CompTIA — MSP and channel research: https://www.comptia.org/content/research
2. ConnectWise Service Leadership — MSP financial and operational benchmarking: https://www.serviceleadership.com/
3. Kaseya / Datto — State of the MSP research: https://www.datto.com/resources/
4. Gartner — Managed Detection and Response market research: https://www.gartner.com/reviews/market/managed-detection-and-response-services
5. Microsoft — Microsoft 365 Copilot plans and pricing: https://www.microsoft.com/en-us/microsoft-365/copilot/
6. Microsoft — Cloud Solution Provider partner program: https://partner.microsoft.com/en-us/partnership/cloud-solution-provider
7. IBM Security — Cost of a Data Breach Report: https://www.ibm.com/reports/data-breach
8. NIST — Cybersecurity Framework: https://www.nist.gov/cyberframework
9. AICPA — SOC 2 and SOC for Service Organizations: https://www.aicpa-cima.com/topic/audit-assurance/audit-and-assurance-greater-than-soc-2
10. U.S. Bureau of Labor Statistics — Consumer Price Index: https://www.bls.gov/cpi/

Related on PULSE

• [MSP MSA Renewal — 60-Min Training](/knowledge/st0026)
• [60-Min Sales Training: Running a Renewal Conversation](/knowledge/st0476)
• [The Renewal Conversation Reboot — 60-Min Training](/knowledge/st167)
• [Reconciling Pipeline Coverage Between Renewal and Expansion on Dynamics 365 — 60-Min Training](/knowledge/st91)
• [The Renewal Rescue Standup — 60-Min Training](/knowledge/st0042)
• [The Renewal Risk Forecast — 60-Min Training](/knowledge/st0077)