Legal · Renewal Call
Legal Renewal Call Script: Saving a Law Firm Account That's Already Half Gone
Your contract with a 180-lawyer commercial firm ends in six weeks. It went live last October in the litigation group on one big breach-of-contract matter, and that's where it stopped — the labor and employment group never onboarded, the transactional side never even got logins provisioned. In Q2, while they were pushing a Rule 26 production out the door, three of your tickets sat for days. The associate who built the privilege log workflow made counsel and went in-house in August. And a competitor rep has been in the COO's inbox since September with a number that's about thirty percent under yours.
The person taking this meeting — usually the Chief Operating Officer or the Director of Legal Operations, sometimes with the Litigation Chair dialing in from a deposition break — has already half-decided to leave. They're taking the call partly to say out loud what went wrong, and partly because the Managing Partner asked them to "see what the vendor says." If you open with the order form, or the discount, or "so what would it take to get this done," you confirm the only thing they currently believe about you: that you show up when money is due.
This legal renewal call script inverts the order. The paperwork is the last five minutes. The first five are ticket numbers, dates, what broke on your side, and who owns the fix by name. Do that, and the same COO who was going to hand you a non-renewal letter starts negotiating with you instead of against you — because switching means re-running the risk committee, re-papering the OCG consent letters with three clients, and rebuilding the privilege log workflow their KM director spent four months on.
The renewal call script
Say it in your own words. The structure is the part that matters.
- 1
Before the call — the renewal autopsy
Do not dial until you can answer these out loud. Tickets: pull all 12 months. Know the three worst by number, open date, and first-response time. Write them on a card: "41-882, opened June 3 during their production push, nine days to first response." Flag anything over 48 hours. Usage by group, not firm-wide: "Commercial litigation is at 71% weekly active across 34 seats. Labor and employment never onboarded — 12 seats, zero logins since March. Transactional was never provisioned at all." You are paying attention to seats they're buying and not using, because that's the number the COO is going to lead with. Your own turnover: how many CSMs have they had? If it's three in eighteen months, you name that before they do. Broken commitments: the DMS integration promised at the January QBR. The two training sessions rescheduled and then dropped. The privilege log export format their Director of Knowledge Management asked for in Q1. Their org changes: did the associate who championed this leave? Did the Litigation Chair who sponsored it lose the origination fight on that client? Is the person on this call the person who signed? Internal alignment before you promise anything: written confirmation from Support leadership on the named-engineer tier, and from your CS lead on the onboarding hours you can actually commit. A second broken promise ends this firm permanently and it will be attributed to you by name. Walk-away: know your floor on price, term, and seat count. Know what you'll trade for what. And know that in a firm, procurement is the COO and Legal review is the firm's General Counsel — both of them can add three weeks.
- 2
Opening — go first, be specific
"Thanks for the time. I know the term ends December 14. I'm not here to talk about the 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 — you opened it June 3, three days before your production deadline on the Halvorsen matter, and it sat nine days without a first response. Two more went past 48 hours that same month. You had two CSM changes, in February and again in July, and the second one was mine to prevent and I didn't. The DMS integration we committed to at the January QBR hasn't shipped. And adoption never got out of commercial litigation — labor and employment has twelve seats that have never been logged into. That's what I've got from my side. What am I missing, and what did it actually cost you?" Then stop. Do not fill the silence. The meeting is won in the eight seconds after that question.
- 3
The listening phase — let it be worse than you thought
Budget half the call here. Fifteen minutes minimum on a thirty-minute call. Rules: no "but," no "to be fair," no defending the ticket where their associate genuinely mis-tagged the export. You may be right and you will lose the renewal being right. Probes that work in a firm: - "Who did you have to explain this to?" — in a firm, the answer is a named partner and it matters. - "Did this come up at the executive committee, or the technology committee?" - "When the production date moved up, what did the review team actually do instead?" - "Did any of this end up as a write-down on that matter, or did it get eaten before the bill went out?" - "Did the client's outside counsel guidelines come into it at all?" Follow the emotional word. When the COO says "we were flying blind for two weeks in June" — "tell me about those two weeks." Write it down visibly and read it back: "So: response times in June during the Halvorsen production, the rollout to L&E that never happened, the DMS integration, and the fact that you heard about the March maintenance window from your own help desk rather than from us. Anything else?" Ask "anything else?" twice.
- 4
The apology — once, specific, unhedged
"The June response times were a failure on our side. We reorganized support in April, your tickets got queued behind enterprise escalations, and nobody flagged that you were inside a production window. That's an explanation, not an excuse. You bought a 24-hour first response and we missed it eleven times, three of them in the week that mattered most. And the CSM churn is on me. You should not have had to re-explain the Halvorsen privilege log workflow to a new person in July." One apology. Then move. Do not apologize again later in the call — repeating it reads as a negotiating posture.
- 5
Proof of change — show, don't promise
"I'm not going to tell you we're investing in support. You've heard that. Three things instead. One — structural, with a date. We split the support queue by segment in August and staffed a dedicated law firm pod. Your median first response since September 1 is 3.1 hours across seven tickets. Here's the list with the ticket numbers — check it against your own side. Two — I cleared the three tickets that were still sitting in your queue last week, including the privilege log export format your KM director asked for in March. That closed Thursday. You should see it. Three — there's a firm about your size, litigation-heavy, that had the same June problem we gave you. Their Director of Legal Operations is willing to take a call. I'm not asking you to take my word on the fix; take hers." If nothing structural has actually changed, say that and change what you control instead: your own coverage, a named escalation path with a direct line, and an executive sponsor from your side. Do not manufacture progress. A firm will check, and the firm's General Counsel will put it in writing.
- 6
Rebuild on what works — find the person, not the feature
"You said the privilege log build is the one thing you'd miss. Walk me through that — who's actually using it, and what did it replace?" Then quantify it in their language, not yours: - "On Halvorsen, what was your cost per document by the end, and what was it on the matter before this one?" - "What did documents-per-reviewer-hour look like on the second-pass privilege review?" - "How much of that first-level review time got written down before the bill went out?" - "You were sitting at 84 on standard realization when we started. Where's that line item now on the matters where this was used?" And the question that finds your remaining champion: "If we disappeared on December 15, whose Monday breaks?" That person — usually the Director of Knowledge Management or a senior associate who built the coding panel — is probably not on this call and needs to be on the next one. The switching cost isn't the license. It's rebuilding what they built, in the middle of somebody's active matter.
- 7
Handling the competitor
Surface it yourself. "I'd assume you've been talking to [Competitor] — I'd be surprised if you hadn't, given the year." Then, genuinely: "What did you like about it?" Then find out how far it's gone: - "Have they been through your security questionnaire yet, or is that still ahead of them?" - "Has the risk committee seen them? Has the firm's General Counsel?" - "Do you have pricing in writing, or was that a number on a call?" - "Have they scoped the migration on the two matters that are still open?" A lunch is a different conversation than a signed order form. Then reframe: "If the number is thirty percent lower, that's real and I'm not going to pretend it isn't. Here's what I'd want you to price against it. Re-running the security questionnaire and getting it back through your risk committee — that was, what, eleven weeks last time? New OCG consent letters to the three clients whose guidelines require written notice for third-party processing. Migrating the coding decisions and the privilege log on matters that are still live, which means a protocol conversation with opposing counsel you don't currently have to have. Retraining the thirty-four people in litigation who did adopt. And the honest one: you'd be inheriting a new vendor's version of the same support problem with none of the goodwill and none of the credits I'm about to put in your contract." Do not match on price here. Price is the last section.
- 8
The 90-day success plan — build it live
"Can we build the next ninety days on this call, in your words, and I'll send it inside 24 hours? Four fields per line: what, who by name on both sides, by when, and what done looks like." Draft it out loud: 1. Labor and employment onboarding — run by Dana [your CSM], two sessions, week of the 14th and week of the 21st. Done = 9 of the 12 L&E seats weekly active by day 60. Your side: [Practice Group Leader] mandates attendance, and Legal Ops books the rooms. 2. Support — named escalation engineer, direct line and mobile, 4-hour first response on P1, effective at signature. Done = written in the order form as an SLA credit, not an email. 3. Production-window protocol — you tell us your production dates for the next quarter and we flag your matters in the queue in advance. Done = the Halvorsen problem cannot recur mechanically. 4. Governance — 30/60/90 reviews with a written usage report by group and cost-per-document on active matters. First one dated January 18, on the calendar today. 5. The thing I can't do — the DMS write-back isn't shipping before Q3. I'm not going to pretend otherwise, and I'm putting that in the plan in writing so nobody's relying on it. Then: "What am I missing, and what does your side need to own? Because part of why the L&E rollout died is that nobody at the firm had it as their job. If [Practice Group Leader] won't put his name next to line one, I'd rather we both know that today than in March." Tie a commercial consequence to it: a break clause at six months, quarterly-reviewed term, or milestone-linked billing. Signing SLA credits into the contract is worth more than any discount, because it proves you expect to be held to it.
- 9
Only now — the commercial conversation
Earn the transition out loud: "If we agree that plan is real, can I walk you through what the renewal actually looks like?" Structure before number: "First, seats. You're paying for 61 and you're using 34. I'd rather right-size to 40 with an add-on rate locked for the term than discount 61 seats you'll never fill. That kills the shelfware line permanently and it's a smaller number on the invoice than the competitor's quote for their full stack — ask them what their seat minimum is. Second, term. Twelve months with a break at six, reviewed against the plan, or twenty-four with the price held and the SLA credits baked in. Your call — the shorter one is for your comfort, the longer one is for your price protection. Third, June. That was a service failure and the honest instrument for it is service credits for the affected months, not a price cut. A discount isn't an apology, and if I hand you one now I'm telling you the year was really a pricing dispute. It wasn't." Any further discount is traded, never given: for the multi-year, for a reference call with the Director of Legal Operations at the firm you introduced them to, for a signature before the 14th, for a case study the Managing Partner will clear.
- 10
Multi-threading and close
Six weeks is tight in a firm, where the technology committee may only sit monthly and the executive committee quarterly. "Walk me through what actually happens between now and signature. Does this go back to the technology committee, and when does it next sit? Does the firm's General Counsel need to re-review anything if the terms change? Does the Litigation Chair have a veto here in practice, even if not on paper? And who signs — you, or the Managing Partner?" Then: "I'd like the plan reviewed with [Litigation Chair] in the room, and I'll bring our VP of Customer Success so the June apology comes from someone above me. Twenty minutes. Does Tuesday or Thursday work better?" Book it on this call. Never "I'll follow up." Temperature check, honestly: "On a scale where 1 is you've already written the non-renewal letter — where are we right now, and what moves it?" Take the honest answer over the polite one, and if it's a 3, ask what a 6 looks like. Within 24 hours, send four things: the written 90-day plan with names and dates, the ticket data you quoted, the intro to the reference firm, and a one-page summary of what they told you went wrong — in their words. That last document does more work than any proposal, because it's the one they can forward to the Managing Partner without editing.
How the call actually sounds
Prospect on the left, the rep on the right.
Rep
Thanks for making the time, Karen. I know the term's up December 14 — I'm not going to talk about the renewal yet. I want to talk about this year. Ticket 41-882: you opened it June 3, three days out from the Halvorsen production, and it sat nine days before anyone from us responded. Two more went past 48 hours the same month. You had two CSM changes. The DMS integration we promised at the January QBR hasn't shipped. And twelve L&E seats have never been logged into. That's my side. What am I missing, and what did it cost you?
Buyer
What it cost me is that I sat in an executive committee meeting in July and had to explain why the firm spent six figures on a review platform that one practice group uses. Ellen — our litigation chair — bills 2,200 hours and she pulled two associates off your tool in June and put them back on straight linear review because nobody could get an answer out of you. She's not on this call because she doesn't think it's worth her time.
Rep
Tell me about that week in June. What did the review team actually do when they couldn't get a response?
Buyer
They coded manually. Two associates, roughly eighty hours between them over four days, at 1am, to hit the production date. The client's outside counsel guidelines say they won't pay associate rates for first-level review, so most of that got written down before the bill went out. Ellen signed off on the write-down and then she asked me, in writing, why we were paying for software that made her associates work more.
Rep
That's the part I hadn't seen. So the failure didn't just cost you response time, it cost you realization on that matter and it cost me my sponsor. Anything else?
Buyer
Yes. Our risk committee reopened the whole thing in September. One of our top-ten clients issued new outside counsel guidelines requiring written consent before any third-party processing of their data. Our General Counsel — the firm's, not the client's — wants to know why we're re-papering consent letters for a tool half the firm doesn't use. And frankly, Ravi in IT got a quote from [Competitor] that's about thirty percent under yours and they've already sent a SOC 2 package.
Rep
Understood, and I'll come to the competitor properly in a minute because I don't think price is the interesting part of that comparison. First — the June response times were a failure on our side. We reorganized support in April, your tickets queued behind enterprise escalations, and nobody flagged that you were inside a production window. That's an explanation, not an excuse. You bought 24-hour first response and we missed it eleven times, three in the week that mattered. And the CSM churn is on me.
Buyer
I appreciate that. It doesn't get me Ellen back.
Rep
No, it doesn't. Ellen's a separate piece of work and I'll come to that. Two things that have actually changed, and you can check both. We split the support queue in August and staffed a law firm pod — your median first response since September 1 is 3.1 hours across seven tickets, and I'll send you the ticket numbers so you can verify against your own log rather than my dashboard. And I cleared the three tickets still sitting in your queue last week, including the privilege log export format Priya asked for back in March. That closed Thursday.
Buyer
Priya did mention that. She's the one person here who'd genuinely fight for you. She rebuilt the whole privilege log workflow around it and she uses it on every active matter in her group.
Rep
That's the person I need in the next conversation, not this one. Can I ask — what did the privilege log actually replace for her? Because when I look at the Halvorsen numbers, your cost per document on second-pass privilege dropped materially against the matter before it, and I want to know whether that's the tool or whether that's just Priya being good.
Buyer
It's both. Look, I'll be straight with you. Nobody here is emotionally attached to your product. What's stopping me signing the competitor is that going through the risk committee again took us eleven weeks last time, and I'd have to send new consent letters to three clients under their OCGs. That's the only thing keeping this conversation alive.
Rep
Then let's price against that honestly rather than against their per-seat number. Eleven weeks of risk committee, three OCG consent letters, migrating coding decisions and a privilege log on matters that are still live — which means a protocol conversation with opposing counsel you don't currently have to have — and retraining the thirty-four people in litigation who did adopt. And the one nobody puts in the spreadsheet: you'd be inheriting a new vendor's version of the same June, with none of the goodwill and none of the credits I'm about to put in your contract.
Buyer
Fine. But I'm not signing anything Ellen can kill in February. And I'm not paying for 61 seats again.
Rep
Agreed on both. Right-size to 40 with the add-on rate locked, so you're not paying for shelfware and I'm not pretending the L&E rollout happened. Then let's build the ninety days on this call. Line one: L&E onboarding, two sessions run by Dana, week of the 14th and the 21st, done means nine of twelve seats weekly active by day 60. Your side has to own the mandate — will your L&E practice group leader put his name next to that, or should we scope this to litigation only and stop pretending?
Buyer
Litigation only. Rob won't chase his people and I'm not going to make him.
Rep
Then that's the honest plan, and it's a smaller renewal. Line two: named escalation engineer, direct line, four-hour first response on P1, written into the order form as an SLA credit — not an email from me. Line three: you send me your production dates each quarter and we flag those matters in the queue in advance, so June is mechanically impossible. Line four: DMS write-back isn't shipping before Q3 and I'm putting that in the plan in writing so nobody plans around it. Line five: a break at six months reviewed against these numbers. If we've missed, you walk without a fight.
Buyer
The break clause is the first thing you've said that's worth something. Send it. Ravi will need to see it and the GC will want to look at the SLA language.
Rep
I'll have it to you tomorrow with the ticket data and a one-page summary of what you told me today, in your words, so you can forward it to the executive committee without editing it. Two asks. First, twenty minutes with Ellen and Priya together — I'll bring our VP of Customer Success so the June apology comes from someone senior to me. Tuesday or Thursday? Second, honestly: on a scale where 1 is you've already drafted the non-renewal letter, where are we?
Buyer
I was at a 2 walking in. I'm at a 5. Thursday works if you can get Ellen — and that's on you, not me, because she won't take my invite.
Objections you will hear
What they say, and what you say back.
| Objection | How to answer it |
|---|---|
| “"Our risk committee has reopened this. One of our clients issued new OCGs requiring written consent for third-party processing, and the default answer to any vendor holding data is no."” | "Let's read what the guidelines actually say, because most of the ones I see require notice and written consent, not prohibition. Have you got the clause in front of you? Second question: you're already running a hosted e-discovery platform and I'd guess a cloud DMS. If so, this isn't the firm's first cloud vendor, it's another vendor under a standard your General Counsel has already approved once — which is a completely different memo to the risk committee. Third, if it comes to it, we have a single-tenant deployment and I'll get the security questionnaire to Ravi this week rather than at renewal, because that's a four-week document, not a call. What I'd rather not do is have you re-run an eleven-week committee process for a competitor who hasn't been through it at all." |
| “"Our litigation chair pulled her associates off it in June and she won't take a meeting. Nothing moves here without partner buy-in and she's the partner."” | "Then getting her back is my job, not yours, and I'm not asking you to sell her. Here's what I'd propose: fifteen minutes, her calendar, our VP of Customer Success on the call, and I open with the write-down on Halvorsen rather than with the product. What she experienced was eighty associate hours she couldn't bill and a write-down she had to sign off on. If I can't show her what changes so that can't recur mechanically — the production-date flagging, the named engineer, the credits in the contract — then she's right to stay out and you should sign the competitor. Can you tell me one thing: is her objection the June failure, or was she lukewarm before that?" |
| “"We already use an ALSP for first-level review at $28 an hour and they never went dark on us. You can't beat that."” | "That's the right comparison and I don't want to beat it on the wrong axis. What's your all-in cost per document on Halvorsen including your associates' QC pass and the second-pass privilege log? Because the ALSP number covers the volume and the expensive part stays with your people. And the turnaround question: when the production date moved up two weeks in May, could they scale in three days? Most firms find the answer is yes on volume and no on privilege — which is exactly where the write-downs land and exactly the workflow Priya built. |
| “"[Competitor] quoted us thirty percent under. I can't take a higher number back to the executive committee after the year we've had."” | "You shouldn't have to. So let's not compare license to license. Right-size the seats first — you're paying for 61 and using 34, and I'd rather cut you to 40 and be right than discount 61 and be big. That closes most of the gap on the invoice line the executive committee actually sees. Then put the switching cost on the same page: eleven weeks back through risk, three OCG consent letters, migrating coding decisions on live matters, retraining the thirty-four people in litigation who did adopt. If after that they're still meaningfully cheaper, I'd want to know their seat minimum and whether their number is year-one only. Has their pricing come to you in writing?" |
| “"Send me the plan and I'll circulate it to the technology committee."” | "Happy to, and I want it to land rather than die. Who sits on that committee, and which of them actually felt this on a matter? A plan sent cold to a committee gets deferred to the next sitting. What works is a short memo written to each concern in the room: the security posture and the OCG consent question for the firm's General Counsel, cost per document and the seat right-sizing for you, defensibility and the production-date protocol for Ellen. When does the committee next sit? And can I get twenty minutes with Ellen before then, so the memo has a sponsor in the room rather than a vendor's name on it?" |
| “"Honestly, if this saves review time, that's fewer billable hours. Our associates need the hours — they're on 1,950."” | "You're not cutting billables, you're cutting write-downs. What was your realization on the first-level review line on Halvorsen? You told me most of it came off before the bill went out because the client's OCGs won't pay associate rates for first-level review — that time was never revenue, it was a costume. And on anything you're bidding as a flat fee or a capped phase, every review hour you don't spend is margin you keep. The question I'd actually put to Ellen is whether the second- and third-years have higher-value work to move into. If they don't, that's a demand problem, and it's also the thing your exit interviews keep saying." |
Questions reps ask about this call
- How is a legal renewal call script different from a standard SaaS renewal?
Three ways. First, the person on the call is usually not the only decision-maker — a law firm renewal typically has to survive the COO, the technology committee, the firm's General Counsel on the data terms, and a Practice Group Leader or Litigation Chair who can stall it indefinitely by saying "I'd want to look at that more closely." Second, the switching cost is regulatory as much as technical: re-running the security questionnaire, re-papering outside counsel guideline consent letters with clients, and migrating coding decisions on live matters. Third, the value language is different — you have to talk in realization, write-downs, cost per document, and lockup, not in "efficiency gains."
- What should I say first on a save call with a law firm that's already talking to a competitor?
Name the failures yourself, with ticket numbers and dates, before they do. Something like: "Ticket 41-882 sat nine days without a first response, three days before your production deadline. You had two CSM changes. Twelve of your seats have never been logged into. That's what I can see — what am I missing, and what did it cost you?" Then stop talking. Do not open with "how's everything been going?" when you have a screen full of nine-day response times. In a firm, where reputational memory is long and partners talk, that reads as either unprepared or dishonest.
- The firm's risk committee has reopened the data question at renewal. Is that a real blocker or a stall?
Usually real, and usually narrower than it sounds. Ask to see the actual clause in the client's outside counsel guidelines — most require notice and written consent for third-party processing rather than prohibiting it outright. Then find out whether the firm already runs a hosted e-discovery platform or a cloud document management system, because most do, and that reframes you from "first cloud vendor" to "another vendor under a standard the firm's General Counsel already approved." Get the security questionnaire in front of the CIO or Director of Legal Technology early — it's a four-week document, not a call — and note out loud that the competitor hasn't been through that process at all.
- Should I discount to save a law firm renewal after a bad support year?
No — not as an apology. A price cut reframes the entire year as a pricing dispute, tells them your list price was always soft, and permanently resets your floor. The honest instruments are service credits for the specific months affected (finite and tied to the failure) and right-sizing seats to actual usage, which kills the "we're paying for shelfware" objection that the COO will raise at the executive committee. If you do discount further, trade it: for a multi-year, an earlier signature, a reference call, or a case study the Managing Partner will clear.
- Adoption never got past the litigation group. Do I try to fix that in the 90-day plan?
Only if someone at the firm will own it by name. Adoption stalled last time partly because no partner had it as their job, and a 90-day plan where every action item belongs to you is a wish list. Ask directly: "Will your labor and employment practice group leader put his name next to the onboarding sessions?" If the answer is no, scope the renewal to litigation, right-size the seats, and say out loud that you'd rather sell a smaller honest deal than book a rollout that won't happen. That single move does more for your credibility with a COO than any roadmap slide.
- Who else do I need in the room before the contract ends?
At minimum the economic buyer and your remaining power user. In a firm that usually means the COO or Managing Partner on the commercial side, the Litigation Chair or Practice Group Leader whose people actually use it, and the Director of Knowledge Management or senior associate who built the workflow — the person whose Monday breaks if you disappear. Get the firm's General Counsel or Loss Prevention Partner sight of any SLA or data-terms change early, and confirm on the call when the technology committee next sits, because a monthly or quarterly committee cadence can consume most of your six weeks on its own.