The Professional Services Renewal Call Script for Saving a Firm Account After a Bad Year

1. 1

   Before the call: the renewal autopsy, firm edition

   Do not fake this. Pull and read: — **Every ticket from the last 12 months.** ID, open date, first response, resolution, sentiment. Flag anything over 48 hours. Know your three worst by number. Cross-reference the dates against their pursuit calendar — a nine-day response in the second week of a public-sector RFP window is a different failure to a nine-day response in August. — **Usage by practice, month over month.** Not 'adoption is 40%.' Instead: 'Supply Chain is at 71% weekly active on 18 seats. Technology Transformation peaked at 22% in March. Nine practices have never logged in.' — **What never got switched on.** Did the prior-engagement library ever get past legal? How many SOWs are actually in the corpus versus what you scoped? If the answer is 40 out of a promised 400, that is your implementation failure, not their compliance failure. — **Your own turnover.** Three CSMs in eighteen months is your fault and you name it before they do. — **Every QBR commitment you missed.** The redaction workflow. The rate-card integration. The training session for the Resource Management team that got rescheduled twice. — **Their org changes.** Did the Head of Knowledge Management who championed this get pulled onto a client engagement? Did the Chief Growth Officer who co-signed leave? Is the person on this call still the one with authority? **Get internal alignment before you dial.** Written confirmation from Support leadership on the new SLA and named engineer. Written confirmation from your CS lead on the onboarding hours you can commit. Know your floor on price, term and seat count. A second broken promise ends this account permanently and it will be attributed to you personally.

2. 2

   Opening: you go first, in the first thirty seconds

   "Thanks for the time. I know the contract's up on the [date] — I'm not here to talk about renewal yet, I want to talk about this year, because from where I'm sitting it wasn't the year we sold you. Here's what I can see. Ticket 41-882 sat nine days without a first response in June, and looking at your calendar that was the week you had three pursuits in flight. You had two CSM changes, in November and again in April. The prior-engagement library never got past your risk partner, so your team has been running on 40 documents against the 400 we scoped. And adoption stopped at Supply Chain — nine of your twelve practices have never had a user log in. That's what I've got from my side. What am I missing, and what did it actually cost you?" Then stop talking. Do not fill the silence. This is where the meeting is won.

3. 3

   The listening phase: 40-50% of the call

   Fifteen minutes minimum on a thirty-minute call. Rules: — **No 'but.' No 'to be fair.'** Even the ticket where their manager never replied to your engineer. You may be right and you will lose the renewal being right. — **No premature fixing.** The instant you say 'so what we've done since is...' while they're still describing the damage, you've told them the acknowledgement was a technique. — **Ask what it cost them politically.** "Who did you have to explain this to?" "Did this come up at the partners' meeting?" "Whose originations did this land on?" The COO who sponsored this has taken heat from a Managing Partner. That's the real wound, not the ticket. — **Follow the emotional word.** They say "we were flying blind through Q2" — "tell me about those weeks." — **Read it back visibly.** "So: response times in Q2 during your busiest pursuit stretch, the library that never got cleared, adoption that never left one practice, and you found out about the March outage from your own manager rather than from us. Anything else?" Ask "anything else?" twice.

4. 4

   The apology: once, specific, no hedging

   "The Q2 response times were a failure on our side. We reorganised support in March and your tickets got queued behind larger escalations. That's an explanation, not an excuse — you paid for a 24-hour first response and we missed it eleven times, and we missed it in the exact eight weeks you needed it. The library is the one I'd flag as worse, honestly. We should have had your General Counsel in the room in week two of implementation, not left it to your Head of Knowledge Management to chase a risk partner between engagements. That's an implementation design failure and it's ours." One apology. Then move. Do not apologise again later in the call — repetition reads as anxiety, and anxiety reads as a discount coming.

5. 5

   Proof of change: show, don't promise

   Only three things carry weight. Use whichever you actually have. **1. Structural change with a date and their own data.** "We split the support queue by segment on 1 September and added a professional-services pod. Your median first response since then is 3.2 hours across nine tickets — I'll send you the list, not a company average, yours." **2. A comparable firm that had the same problem and stayed.** "There's a 300-person firm on the East Coast whose Head of KM hit exactly your library problem — their risk partner blocked the ingest for five months. I'll introduce you to her rather than just quoting her. Twenty minutes, no one from my side on the call." **3. Something already done, unasked.** The strongest move in the call, and mention it in passing rather than as a flourish: "I had the team clear the three open tickets in your queue last week and run the redaction pass on the 60 SOWs your KM lead had staged — those should have landed Thursday." If nothing has genuinely changed, say so and change what you control: your own coverage, a named escalation path, an executive sponsor. Do not manufacture progress. They will check.

6. 6

   Rebuild on the one thing that worked

   Something survived. Usually it's whatever the Head of Knowledge Management or one senior manager built a workflow around. Go find it. "You mentioned the SOW retrieval is the piece Supply Chain would miss. Who's actually using it, and what did it replace?" "If we went away on Friday, whose Monday breaks?" — that person is your remaining champion and probably wasn't invited to this call. Get their name. Then quantify it in firm language, not software language: "Before this, when a client called Thursday wanting something early the following week, what did that take? And what does it take now?" "How many unbillable pursuit hours went into a closed deal in that practice this quarter versus last year?" "Has anything in their RFP-received-to-proposal-submitted number moved?" That last one is the number a Practice Leader will actually defend in a partners' meeting. Get it, even approximately, out loud, in their words, before you go anywhere near price. It is also your quiet competitive defence: the switching cost isn't the licence, it's rebuilding what the KM lead spent a year tagging.

7. 7

   Handling the cheaper competitor

   Surface it yourself: "I'd assume you've had [Competitor] in — I'd be surprised if you hadn't. What did you like?" Ask it genuinely. Then find out how far it's gone, because a lunch and a signed order form are different meetings: "Have they done a security review with your GC?" "Have they scoped the migration — specifically, who re-tags the SOW corpus your KM lead built?" "Is the quote with procurement, or still with the Chief Growth Officer?" Never disparage. Reframe from price to total switching cost, in their vocabulary: "The licence delta is real, I'm not going to argue it. What I'd want you to price alongside it: six months where Supply Chain's retrieval is broken during their heaviest pursuit season, the re-tagging your KM lead does a second time, another conflicts and NDA review with your risk partner — which took five months the first time — and the risk that you inherit a new vendor's version of the same support problem with none of the goodwill and none of the history. And the honest version: if the answer is that you want a boutique because we behaved like a big firm this year, I understand that. I'd rather lose that argument than pretend it isn't the argument." Do not match on price here. Price is the last section.

8. 8

   The 90-day plan: build it live, and make them own half of it

   This is the artefact that changes the decision. Four fields per line: what, who by name on both sides, by when, and what 'done' looks like. "Can I build this with you now rather than send you something? Four lines, and two of them are yours." — **Adoption:** onboarding for the 22 users in Supply Chain and Operations Transformation who were never trained. Run by [named CSM], week of the 14th. Done = 15 of 22 weekly active by day 60. — **The library:** [named solutions engineer] runs the redaction and matter-level access walls with your GC and risk partner. Session booked before the 30th. Done = 400 sanitized SOWs live, signed off by risk. — **Support:** named escalation contact, direct line, four-hour first response on anything flagged pursuit-critical. Effective at signature, written into the contract. — **Governance:** 30/60/90 reviews with a written usage report by practice. First one dated today. — **The thing I can't do:** the rate-card write-back to your practice management system isn't on the roadmap before Q3. I'm not going to pretend otherwise, and I'd rather you decide with that in front of you. Then the harder half: "What do you need to commit to? Adoption failed partly because nobody on your side owned it, and a plan where only the vendor has obligations is a wish list. I need one Practice Leader who'll put their pursuit hours on the line, and I need thirty minutes of your GC's time in the next fortnight." **Tie a commercial consequence to it.** A break clause at six months, or SLA credits written into the contract. Signing a service credit is worth more than a discount because it proves you expect to be held to it.

9. 9

   Only now: the commercial conversation

   Earn the transition out loud: "If we agree that plan is real, can I walk you through what a renewal looks like?" — **Structure before number.** "Twelve months with a break at six, reviewed against the plan. Or twenty-four with price protection if you want the CFO to stop seeing an increase every year. Your call which problem you'd rather have." — **Right-size seats to actual usage rather than discounting the whole thing.** "You're paying for 120 seats and 38 are active. I'd rather cut you to 60 and grow it back as the practices come on than hold you to a number that makes your CFO right about shelfware." This kills the shelfware objection permanently and it costs you less than a headline discount. — **Service credits, not a guilt discount.** "For Q2 I'd rather give you credits against the months we missed the SLA than cut the price. A price cut isn't an apology, and if I take 25% off now, both of us know that's what the product was always worth." — **Any discount is traded.** For the multi-year, for a reference call with another firm's COO, for a case study your Chief Growth Officer approves, for signature before the [date] partners' meeting.

10. 10

    Multi-threading and close

    Six weeks is tight and most stalled renewals die in procurement, not in the business. "Walk me through what actually happens between now and signature. Does this go to the partners' meeting, or can you sign it? Does your GC need to re-review given the library changes? Is there a procurement step, and do they already have [Competitor]'s quote?" Get the economic buyer in the room. If the Firm CFO is the one looking at the overhead line, your exec sponsor should be apologising to them directly, not through the COO. "I'd like to get my VP and your CFO on twenty minutes together to review the plan. Exec to exec, so it's not me relaying a commitment." Book the meeting on the call. Never 'I'll follow up.' Temperature check, and take the honest answer over the polite one: "On a scale where 1 is you've already decided to leave and 10 is this is done — where are we right now, and what moves it?" **Within 24 hours, send four things:** the written 90-day plan with names and dates, the ticket data you referenced, the reference intro, and a one-page summary of what they told you went wrong, in their words. That last document does more work than any proposal.

1. Rep

   Thanks for making the time, Priya. Contract's up on the 30th of next month, and I'm not going to talk about the renewal yet — I want to talk about this year, because it wasn't the year we sold you. Ticket 41-882 sat nine days without a first response in June, which was the same fortnight you had the health system RFP and two other pursuits running. You've had two CSMs. The prior-engagement library never cleared your risk partner, so your team has been working off 40 documents instead of the 400 we scoped. And nine of your twelve practices have never had a single user log in. That's my side. What am I missing, and what did it cost you?

2. Buyer

   None of that's new. I put most of it in the July QBR deck and nobody came back to me. What it cost me is that I sponsored this. I stood up in the January partners' meeting and said this would take our RFP-to-submission time down, and in June we lost a supply-chain diagnostic to a four-person boutique who turned a proposal around on a Friday afternoon. Our senior manager was still hunting for the 2022 analogue on the Sunday.

3. Rep

   Tell me about that Sunday.

4. Buyer

   She's at 88% utilization. She'd already written down half of March. So she spent seven unbillable hours on a Sunday looking for a deck that we own, that we paid for, that's sitting in a SharePoint folder called 'FINAL v7 - JG edits.' That's precisely the problem you sold us on solving. And she wasn't quiet about it — she raised it with her Practice Leader, and he raised it with the Managing Partner.

5. Rep

   So it landed on you at partner level. Who did you have to explain it to, and what did they say?

6. Buyer

   The Managing Partner and our CFO. Realization's at 86% this year, we're having partner conversations about it, and I'm the one carrying a software line in overhead that half the firm has never opened. The CFO's exact words were 'remind me what this buys us in billable hours.' I didn't have a great answer.

7. Rep

   Understood. Anything else on the list before I respond to any of it?

8. Buyer

   Yes. The library. Our risk partner sat on it for five months because nobody from your side would get on a call with him about matter-level access walls and the two MSAs that prohibit reuse of client material. My Head of Knowledge Management chased it between engagements, unbillable, because he cared. That shouldn't have been his job.

9. Rep

   Anything else?

10. Buyer

    That's enough.

11. Rep

    Then two things. The Q2 response times were a failure on our side — we reorganised support in March and your tickets queued behind bigger escalations. You paid for a 24-hour first response and we missed it eleven times, in the eight weeks you needed it most. And the library is the worse one: we should have had your GC and your risk partner in the room in week two of implementation. Leaving that to your KM lead to chase was a design failure in how we ran the rollout, and it's ours. That's the only time I'm going to apologise on this call.

12. Buyer

    Fine. I'll take that. But I should tell you our Chief Growth Officer had your competitor in three weeks ago. They've quoted, it's about thirty per cent under what we're paying, and procurement has had it since the start of the month.

13. Rep

    I'd have been surprised if you hadn't. What did the Growth team like about them?

14. Buyer

    Honestly? They're smaller and they were in the room in four days. Which is the same reason we keep losing to boutiques, so there's a certain irony in it.

15. Rep

    That's fair and I'm not going to argue the licence delta. Two questions I'd want you to price alongside it. Have they scoped who re-tags the corpus your KM lead has built — the pricing assumptions, the practice tags, the sanitization? And have they been through your risk partner yet on access walls?

16. Buyer

    No, and no. But you're describing a switching cost on a thing that only one practice uses. I can't renew a firm-wide licence on the strength of one Head of Knowledge Management's workflow.

17. Rep

    Agreed, so let's not. I'd rather cut you from 120 seats to 60 and grow it back as practices come on than hold you to a number your CFO is right to question. And I'd rather earn the next twelve months on one practice's pursuit numbers than on a firm-wide argument. Which Practice Leader has the worst RFP-to-submitted time right now?

18. Buyer

    Supply Chain. Marcus. He's losing Friday-afternoon turnarounds to three-person shops every quarter and he knows it. But I want to be clear about something: I can't make Marcus do anything. He doesn't report to me, he bills seven hundred an hour, and if I mandate a tool at the partners' meeting what I'll get is twelve people nodding and nothing changing. That's how the last rollout died — not rejection, just nobody bothering.

19. Rep

    Then it shouldn't be your mandate, it should be his number. Here's what I'd build with you now, four lines, and two of them are yours. Mine: my solutions engineer runs the redaction and access-wall session with your GC and risk partner before the 30th — done means 400 sanitized SOWs live and signed off. Named escalation contact with a four-hour first response on anything flagged pursuit-critical, written into the contract, not a promise on a call. Yours: Marcus commits his practice for 90 days, and we baseline two numbers on day one — average days from RFP receipt to submission, and unbillable pursuit hours per closed deal. He walks the delta into the partners' meeting himself. What I can't do, and I'll put it in writing: the rate-card write-back to your practice management system isn't happening before Q3.

20. Buyer

    If Marcus's numbers don't move by day 90 I'm in exactly the same position, only later.

21. Rep

    Which is why I'd write a break at six months into the term, and service credits against the eleven SLA misses in Q2 rather than a discount. A price cut isn't an apology — if I take thirty per cent off today, we've both agreed the year was a pricing dispute rather than a service failure, and it wasn't. Where are we honestly, on a scale where 1 is you've already decided to leave?

22. Buyer

    Three. It moves if Marcus sees something real before the partners' meeting on the 12th, and if my CFO hears the Q2 story from someone senior on your side rather than from me.

23. Rep

    Then I'll get my VP and your CFO twenty minutes together next week — exec to exec, so it's not me relaying it. Can you get me twenty minutes with Marcus before the 12th? And I'll have the plan, the ticket log and a one-page summary of what you told me today, in your words, with you by tomorrow afternoon. What day works for the CFO session — Tuesday or Thursday?

How is a professional services renewal call script different from a standard SaaS renewal?

Two things change everything. First, the person on the call usually can't mandate anything — a COO of Firm Operations or a Chief Growth Officer is negotiating with twelve Practice Leaders who run their own P&Ls and don't report to them, so a firm-wide save plan is a plan that dies politely. Build the save inside one practice with one named partner owner. Second, the value has to be expressed in utilization, realization and unbillable pursuit hours, not in seats and logins. A Firm CFO looking at realization under 85% will not renew a software line item that lives in overhead unless someone can tie it to hours that became chargeable.

What should I open with if adoption never got past one practice?

Name it before they do, with the practice-level numbers. "Supply Chain is at 71% weekly active on 18 seats. Nine of your twelve practices have never had a user log in." Then hand them the floor and stop talking. Do not open with "how's everything been going?" when you have a screen full of nine-day first-response times — they know you know, and they'll spend the rest of the call working out whether you're unprepared or evasive. Partial adoption in a partnership is almost always a rollout design failure, not a product failure, and saying so buys you the right to propose a different rollout.

They're comparing us to a boutique competitor quoting 30% less. Do I discount?

Not in this call, and not as an apology. A price cut after a bad year reframes twelve months of service failures as a pricing dispute, tells them list was always negotiable, and resets your floor forever. Two honest instruments instead: right-size the seat count to actual usage — if they're paying for 120 and using 38, cut to 60 and grow it back, which kills the shelfware argument permanently — and issue service credits against the specific months you missed SLA. Credits are finite, specific, and prove you expect to be measured. Then reframe the competitor comparison as total switching cost: re-tagging the SOW corpus, a second conflicts and access-wall review with the risk partner, and broken retrieval through a pursuit season.

What goes in the 90-day plan for a consulting firm specifically?

Four to five lines, each with what, who by name on both sides, by when, and what done looks like. Realistically: a GC-and-risk-partner session on redaction and matter-level access walls with a date; onboarding for the named users in the practices that were never trained, with a weekly-active target; a named escalation contact with a written SLA effective at signature; 30/60/90 usage reviews reported by practice; and one line stating plainly what you cannot deliver before Q3. Crucially, at least two lines must be the firm's obligations — a Practice Leader who commits their pursuit hours as a baseline, and GC time. A plan where only the vendor has obligations is a wish list, and that's part of why adoption failed the first time.

The person on the call sponsored the purchase and got burned internally. How do I handle that?

Ask about it directly and early: "Who did you have to explain this to?" "Did this come up at the partners' meeting?" The COO who championed you has usually taken heat from a Managing Partner or a Firm CFO, and that political cost is the real wound — bigger than any individual ticket. You can't fix it with a discount. You fix it by giving them something to carry back into the room: a practice-level number from a 90-day pilot, an exec-to-exec apology from your VP directly to the CFO so they're not relaying it, and a written one-page summary of what went wrong in their own words that they can forward without editing.

Six weeks isn't long. How do I avoid dying in procurement?

Ask on this call, out loud: does this go to the partners' meeting or can they sign it, does the GC need to re-review, is there a procurement step, and does procurement already have the competitor's quote? In firms, the two silent killers are a partner group that never quite convenes and a risk or GC review that nobody scheduled. Book both in the call — the exec-to-exec session with the Firm CFO and the GC session on access walls — with dates, not "I'll follow up." And run a temperature check before you hang up: "On a scale where 1 is you've already decided to leave, where are we, and what moves it?" Take the honest answer over the polite one.

• All Professional Services playbooksEvery call type for Professional Services, in one place.

Other Professional Services calls

• Cold CallThe Professional Services Cold Call Script: Getting a Practice Leader to Give You Twenty Minutes
• Demo CallThe Professional Services Product Demo Script: Running the Call for Partners Who Bill by the Hour
• Discovery CallDiscovery Call Questions for Professional Services: A 25-Minute Playbook for Selling Into Partner-Led Firms
• Manager Coaching CallSales Coaching Roleplay for Professional Services Teams: The Two-Quarters-Down 1:1
• Pricing Negotiation CallProfessional Services Pricing Negotiation Script: Holding Your Number With a Managing Partner Who Bills $750 an Hour
• Upsell CallUpsell Script for Professional Services Customers: Expanding Inside a Partnership Without Burning the Account
• Warm CallWarm Call Script for Professional Services: Cashing a Partner's Referral Before It Cools

The same call in a neighbouring market

• Renewal Call for SaaSThe SaaS Renewal Call Script for a Save Call You're Six Weeks From Losing
• Renewal Call for InsuranceInsurance Renewal Call Script: Saving a Claims Platform Account at a Carrier That's Already Halfway Out

Related reading

• The 90-Day Renewal Health Check: Catching the Churn Before It's a Save CallThe renewal risk checklist I run ninety days out on every account, the five red flags it catches, and the specific call to make the week you find each one.
• How to Open a Renewal Call When You Already Know Adoption Is DeadThe usage report is flat, the call is Tuesday, and the customer already knows. Here is how to run the first ten minutes without an apology tour or a discount reflex.