Staffing / Recruiting · Renewal Call
Staffing / Recruiting Renewal Call Script: How to Save an Account Six Weeks From Expiry
Your contract with a 140-recruiter firm ends in six weeks. The IT staffing practice lead loves the redeployment cadence he built himself. The eight commercial branches never logged in past onboarding. Support went quiet for nine days in June — during their peak ramp — and a competitor who sits in the Bullhorn marketplace has already put a number in writing that's roughly a third under yours. The VP of Recruiting took this meeting, and they took it partly to say out loud what went wrong before they leave.
This Staffing / Recruiting renewal call script treats that meeting as what it actually is: a save call where the paperwork is the last five minutes, not the first five. If you open with the order form, the discount, or "so what would it take to get this done," you confirm the thing they already suspect — that you only show up when money is due. If you open with ticket numbers, dates, their redeployment rate against last year's, and what broke on your side, the same VP starts negotiating with you instead of against you.
Everything below assumes you did the autopsy first. Staffing leaders live in numbers — fill rate, spread, submittal-to-interview, bench days — and they will test whether you know theirs within the first ninety seconds. Bring their data, not yours. Drill the opening and the silence after it out loud before you dial; the thirty seconds where you name the failure and then stop talking is the hardest part of this call to execute cold.
The renewal call script
Say it in your own words. The structure is the part that matters.
- 1
Pre-call: the renewal autopsy (staffing edition)
Don't dial until you can answer these from memory: — Every ticket in the last 12 months: ID, open date, first response, resolution. Know your three worst by number and by what was happening on their desk that week. A nine-day response in June is a different crime if June is their peak ramp. — Usage by division, not company-wide. Not "adoption is 40%." It's "IT staffing practice is at 88% weekly active on 31 seats; the eight commercial branches peaked at 11 users in February and have been flat since." — Their outcome numbers as your platform reports them: redeployment rate on contractors rolling off, submittal-to-interview ratio, placements per recruiter per month, fall-off inside 30–90 days. Pull the same numbers for the quarter before they bought. — Headcount changes on their side. Did they RIF recruiters in Q3? Then some of your "unused seats" are desks that no longer exist and they'll say so. Get ahead of it. — CSM turnover on your side. Two CSMs in eight months is your fault and you name it before they do. — Every QBR commitment that never shipped. The VMS integration you promised. The training session for the commercial branches that got rescheduled twice and then dropped. — Who signed last time and whether they still have budget authority. If a Managing Director signed and the firm has since centralised delivery under a Head of Talent Delivery, you're pitching the wrong person. Before you promise anything: get written internal confirmation of what support can actually commit — named engineer, response SLA, escalation path — and what your CS lead will fund for onboarding. A second broken promise ends this account permanently, and it gets attributed to you by name.
- 2
Opening: name the bad year before they have to
"Your term ends [date] and I'm deliberately not opening with the renewal. I want to talk about this year first, because from where I'm sitting it wasn't the year we sold you. Three things I can see. Ticket [44-118] went [nine] days without a first response in [June] — that was the middle of your [Q2 ramp]. You've had two CSMs in eight months, which is on us, not you. And you're paying for [120] licences with [46] weekly active users — your [IT] practice adopted it, the [eight commercial branches] never did. That's my side. What am I missing, and what did it actually cost you?" Then stop. Do not fill the silence. The meeting is won or lost in the four seconds after that question.
- 3
Listening phase: let it be worse than you thought
Budget 40–50% of the call here. Fifteen minutes minimum on a thirty-minute call. Rules: no "but," no "to be fair," no defending a single ticket — including the one where their recruiter never actually mapped the assignment-end field. You may be right and you will lose the renewal being right. Probes that work on staffing leaders: — "What did the redeployment number do while that was broken? Give me the actual percentage." — "How many contractors rolled off in that window?" — "Did any of that show up in the ops review?" — "Who did you have to explain this to — your CRO? The owner?" — Follow the emotional word. If they say "my Director of Contractor Care was working off a spreadsheet," say: "Tell me about the spreadsheet." Write it down visibly and read it back: "So — the June response times during your ramp, the redeployment sequences misfiring on assignment-end dates, the two CSM changes, and the commercial branches that were never onboarded. Anything else?" Ask "anything else?" twice.
- 4
The apology: once, specific, no hedge
"The June response times were a failure on our side. We reorganised support in Q1 and your tickets got queued behind enterprise escalations — that's an explanation, not an excuse. You bought a 24-hour first-response commitment and we missed it [eleven] times, including the week you had [40-plus] contractors rolling off. And the commercial branches never got the onboarding I sold you in the original scope. That one's mine." One apology. Then move. Do not apologise again later in the call — repeating it reads as a negotiating tactic.
- 5
Proof of change: their numbers, not a company stat
"Three things I want to show you, and none of them are 'we're really investing in support.' First — structural, with a date. We split the support queue by segment on [Sept 1] and staffed it. Your median first response since then is [3.2] hours across [nine] tickets. Here's the list; check it against your own inbox. Second — I cleared the three open tickets in your queue last week, including the assignment-end date mapping for the [commercial] branches. You should have seen those close Thursday. I didn't ask first because I didn't want to walk in here asking for credit for something that should have happened in June. Third — [Firm name], similar size, similar VMS mix, had the same queueing problem in Q2. Their Director of Delivery has agreed to take a call from you. I'll make the intro today, and I'm not going to be on that call." If nothing structural has changed, say so and change what you control: your own coverage cadence, a named escalation path, an executive sponsor. Do not manufacture progress. They will check.
- 6
Rebuild on what works: find whose Monday breaks
"You said the redeployment sequences your [IT Practice Lead] built are the one thing your team would miss. Walk me through that — who's actually in it and what did it replace?" Then quantify it in their language, out loud: "So on that desk, redeployment on rolling-off contractors went from [22%] to [41%] over two quarters. At your average spread, that's [X] placements a quarter you didn't pay to source — no job board spend, no re-screening someone you already background-checked. And that's one practice out of eleven." Then the real question: "If this went away Monday, whose day breaks first?" Get the name. That person is your remaining champion and they were almost certainly not invited to this call. Ask to get them into the next one. Say the switching cost plainly, once: "The number on a competitor's quote isn't the cost of leaving. The cost of leaving is rebuilding what [Practice Lead] spent two quarters tuning, and running your contractor care team blind through the migration window."
- 7
Handling the competitor
Surface it yourself: "I'd assume you've talked to [Competitor] — I'd be surprised if you hadn't. What did you like?" Then find out how far it's gone, in this order: — "Have they put pricing in writing?" — "Have they scoped the migration — including two years of contact history and your right-to-represent records?" — "Has security or your MSP compliance team looked at it?" — "Who's sponsoring it internally?" A lunch is a different conversation to a signed order form. Never disparage. Reframe from price to total switching cost: re-implementation during your busy season, retraining the one practice that did adopt, historical activity data that won't map cleanly, the quarter where nobody can report on submittal-to-interview because you're mid-migration, and — say it plainly — the risk of inheriting a new vendor's version of the same support problem with none of the goodwill you've now got from me. Do not match on price here. Price is the last section of this call.
- 8
The seat-count conversation (before they raise it)
If they cut recruiters this year, get there first: "You reduced the desk count in Q3 — I'm not going to pretend 120 seats is still the right number and then discount my way out of it. I'd rather right-size the contract to the desks you actually have and be correct than keep the seat count and give you a percentage off shelfware. Tell me what the real recruiter headcount is going into Q1, including the branches, and let's build from that." This kills the "we're paying for shelfware" objection permanently and it costs you less than a blanket discount.
- 9
The 90-day plan: built live, in their words
"I want to build this with you now, not send it after. Four fields per line: what, who by name — mine and yours — by when, and what done looks like. One. Commercial branch adoption. [Named CSM] runs onboarding for the [38] recruiters in the [eight] branches, week of the [14th], on-site at your [Dallas] hub. Done = [24] of [38] weekly active by day 60, and redeployment sequences live on every contract desk. Two. Support. Named escalation contact, direct mobile, four-hour first response on P1, effective at signature — and written into the contract, not into an email. Three. Governance. 30/60/90 reviews with a written usage report by division. First one dated [date] — put it in your calendar now. Four. The measurement we agree on up front: redeployment rate on contractors rolling off, and submittal-to-interview ratio on the reqs running through the cadence. Baselines are [22%] and [1 in 6.4] as of today. We review those numbers at day 90 and you tell me whether this earned its keep. Five — the thing I can't do. The direct write-back to your VMS isn't on the roadmap before Q3. I'm not going to tell you otherwise. Now: what do you and your team own on this list? Because last year nobody on your side owned the branch rollout, and that's half of why it didn't happen." Get at least two line items with their name on them. A plan where only the vendor has obligations is a wish list. Then tie a commercial consequence to it: "I'll sign a break clause at six months against the day-60 adoption number. If we miss it, you walk with no penalty. I'd rather do that than discount, because a discount doesn't cost me anything if I fail you again."
- 10
Only now: the commercial conversation
Earn the transition explicitly: "If you're satisfied that plan is real — can I walk you through what a renewal looks like?" Structure before number: — Seats matched to actual desk count, not last year's headcount. — Term: shorter for their comfort, or longer for price protection — their choice, priced accordingly. — Service credits for the affected months. "You paid for a service in [April through June] you largely didn't receive. I'm crediting [X]. That's specific, it's finite, and it's the honest instrument. A price cut would just tell you I was overcharging you all along." — Any discount is traded, never given: multi-year, a reference call with another Head of Talent Delivery, an earlier signature, a case study on the redeployment numbers. Never hand a discount as an apology. It reframes a service failure as a pricing dispute and resets your floor forever.
- 11
Multi-thread and close
"Walk me through what happens between now and [date]. Who else signs — does this go through your CFO? Does procurement need a redlined MSA? Does the CRO have to approve any vendor renewal over [$X] this year?" Then: "I want three people on the next call — you, [Practice Lead, the power user], and whoever owns the budget line. Thirty minutes, we review the plan, and my [VP of Customer Success] will be on it. He should be the one telling you what changed in support, not me." Book it live. Never "I'll follow up." Temperature test, and take the honest answer: "On a scale where 1 is you've already decided to leave and 10 is you're signing — where are we right now, and what specifically moves it a point?" Within 24 hours, send four things: the 90-day plan with names and dates, the ticket data you quoted, the intro to the reference customer, and a one-page summary of what they told you went wrong — in their words, not yours. That last document does more work than any proposal.
How the call actually sounds
Prospect on the left, the rep on the right.
Rep
Your term ends October 14th and I'm not opening with the renewal. I want to talk about this year, because it wasn't the year we sold you. Three things I can see: ticket 44-118 went nine days without a first response in June — the middle of your contract ramp. You've had two CSMs in eight months, which is on us. And you're paying for 120 licences with 46 weekly active — the IT practice adopted this, the eight commercial branches never did. That's my side. What am I missing?
Buyer
What you're missing is what nine days costs in June. We had 43 contractors rolling off inside a three-week window and the redeployment sequences were half-firing — pulling the wrong assignment-end dates out of Bullhorn. My Director of Contractor Care ended up working a spreadsheet by hand. We redeployed 19 percent that month. June last year, before you, we did 31.
Rep
19 against 31. I'm writing that down. Tell me about the half-firing — was it the sequences themselves, or the date field mapping?
Buyer
Nobody could tell me. That's the whole point. I opened the ticket, my IT practice lead escalated it, and we heard nothing for a week and a half. And in that window two of your sequences went to contractors who were still on assignment at a client site. Their MSP program manager flagged it as poaching. I had to get on a call and explain why my vendor was messaging their workers.
Rep
Who else did you have to explain that to internally?
Buyer
Our CRO. In the September ops review. With the owner in the room. I'm the one who brought you in, so it was my name on it.
Rep
Understood. Anything else on the list before I respond to any of it?
Buyer
Yes — the branch training. You scoped on-site onboarding for the commercial side in the original deal. It got rescheduled twice and then it just stopped being mentioned. So I've got eight branch managers who think this is an IT staffing toy, and I'm paying for their seats anyway.
Rep
That one's mine specifically. The June response times were a support failure — we reorganised the queue in Q1 and your tickets sat behind enterprise escalations. That's an explanation, not an excuse; you bought a 24-hour first response and we missed it eleven times in the exact three weeks you had 43 people rolling off. And the branch onboarding I sold you never happened. I'm not going to distribute that one.
Buyer
I appreciate you saying it, but I'll be straight with you. I've got pricing in writing from a competitor at 28 percent under your renewal number, they're a Bullhorn marketplace partner so the integration is native — no middleware, no date mapping issue — and they've scoped a six-week migration. My CRO has seen the quote. I don't have a lot of room here.
Rep
I'd have been surprised if you hadn't looked. What did you like about them, genuinely — is it the native integration or the number?
Buyer
Both. Mostly that they don't need a two-week ticket to tell me why an assignment-end date didn't sync.
Rep
Fair. Two questions and then I'll show you what changed. Have they scoped the data migration — two years of contact history and your right-to-represent records? And has your IT practice lead looked at what it takes to rebuild the redeployment cadence he tuned? Because the last number I've got says that desk went from 22 percent redeployment to 41 over two quarters, and that's the piece I'd be nervous about losing during a Q1 migration.
Buyer
He'd rebuild it. He's motivated — he was the one screaming at me in June. And frankly, 41 percent on one desk out of eleven doesn't save this. If it worked, my placements per recruiter should have moved firm-wide and it didn't.
Rep
It didn't move firm-wide because it's live on one desk out of eleven — which is my failure, not evidence the thing doesn't work. So here's what I want to build with you right now, on the call. Commercial branch onboarding, on-site in Dallas, run by Maria week of the 14th, done means 24 of the 38 branch recruiters weekly active by day 60. Named support engineer with a direct mobile and a four-hour P1 response, written into the contract, effective at signature. Baselines we agree today: redeployment at 22 percent firm-wide, submittal-to-interview at one in 6.4. Reviewed at day 90 with a break clause — if we miss the day-60 adoption number, you walk, no penalty. Would you rather have that clause or 28 percent off?
Buyer
The clause is more interesting than the discount. But I want two things: my contractor care director on the next call, because she's the one who got burned, and I need to know what you're doing about the seat count. We cut 14 recruiters in Q3. I'm not renewing 120 seats and pretending.
Rep
I wasn't going to ask you to. I'd rather right-size to your real desk count going into Q1 than discount shelfware — tell me the number including the branches and I'll rebuild the quote off that. Next call: you, your contractor care director, your IT practice lead, and my VP of Customer Success, because the support answer should come from him. Thursday at 8 or Friday at 4?
Buyer
Thursday at 8. And I'll tell you now, we're at about a 4 out of 10 on staying. What moves it is whether those branch recruiters are actually in the system by December, not whether you send me a nice plan.
Rep
Then that's what I'll be measured on. You'll have the plan, the ticket data I quoted, and an intro to the Director of Delivery at a firm your size who had the identical queueing problem in Q2 — in your inbox by tomorrow morning.
Objections you will hear
What they say, and what you say back.
| Objection | How to answer it |
|---|---|
| “Bullhorn's own automation module ships with our licence now. Why are we paying you separately?” | Most ATS platforms have the module — the question is never whether it exists, it's whether it fires. Open your ATS while we're talking and tell me what percentage of submittals from last month have three or more logged touches after the shortlist went out. If it's like most firms, the feature is licensed and dark because it depends on a recruiter remembering to set the sequence at 6pm from memory. I'm not asking you to rip out the ATS. I'm asking whether the follow-up happens when nobody remembers — and separately, whether your redeployment number moves. If the native module gets you both, I'd rather you use it and I'll close this out honestly. |
| “Margins are gone. MSP has us at a 14% cap and ownership has frozen new spend — renewals included.” | Then let's not talk about spend, let's talk about redeployment. You're at 19 to 22 percent on contractors rolling off. Every point you move that is a placement you don't pay to source — same bill rate, no job board spend, no re-screening someone you already background-checked and know performs, and no recruiter hours against a capped margin. Right-size the seats to the desks you actually have after the Q3 cuts, and if the math on redeployment doesn't clear the reduced number by itself, I'll say so and we'll part cleanly. But show me the number first. |
| “My recruiters won't touch it. They're in the ATS, LinkedIn Recruiter, the VMS portal and their inbox already — this was a fifth login and it died.” | That's exactly what happened, and it's the honest diagnosis. The IT practice adopted because their lead configured it to fire out of the ATS record they were already in; the branches never got that configuration or the training, so it was a fifth login for them and they voted with their feet. The 90-day plan is about closing that gap specifically — Maria on-site, sequences firing from the Bullhorn record, recruiter sees only the touches that need a human voice. And I'd want your branch managers to own attendance, because last time nobody on your side did. |
| “Your sequences went out to contractors who were still on assignment and the client's MSP called it poaching. That's a compliance problem, not a feature gap.” | You're right, and I'm not going to explain the date-mapping around it. It reached your program manager and it reached your CRO, which makes it your problem, not just mine. Two things: the assignment-end field mapping was corrected and closed last Thursday, and I'll put an on-assignment suppression rule in writing as part of the plan, with your Director of Contractor Care signing off on the trigger logic before anything goes live again. If that's not enough control for your MSP accounts, tell me now and we'll scope it out of those clients entirely. |
| “We're a relationship shop. Nine accounts do 70% of our revenue. Automated follow-up is going to make us look like a job board.” | Then the reqs going dark hurt you more, not less — a volume shop can absorb a dead shortlist, you can't. What I'm describing is structure, not blast: your recruiter's own voice, a defined cadence, an actual reason to reach out each time. The alternative isn't high-touch, it's the recruiter emailing a hiring manager twice and quietly giving up. How many of those nine accounts went silent on a submittal last quarter — and did anyone find out why, or did the req just close in the system as filled elsewhere? |
| “We tried this with you for a year and it didn't stick. Why would year two be different?” | Because I can tell you exactly what broke, and it isn't mysterious. Nobody on either side owned the branch rollout, your onboarding got rescheduled twice, and when you escalated in June we didn't answer for nine days. Two of those three are mine and both are fixed with a name and a date attached. The third — someone on your side owning branch adoption — is the line item I'm asking you to put your name against. And I'll sign a break clause at six months on the day-60 adoption number, so if it doesn't stick you leave without paying for the privilege. |
| “Just send me the renewal quote and I'll circulate it internally with the other one.” | I'll send it, but a quote next to a cheaper quote only answers one question and it isn't the one you'll get asked in the ops review. Give me thirty minutes Thursday with you, your contractor care director and your IT practice lead — we'll walk the 90-day plan, my VP of Customer Success answers for support directly, and you'll have redeployment and submittal-to-interview baselines in writing. If after that you still prefer the other number, you'll be able to defend the decision with data instead of a price sheet, and I'll help you exit cleanly. |
Questions reps ask about this call
- What should I open with on a staffing renewal call when I know the year went badly?
Open by naming the failures yourself, with specifics: ticket number, date, days to first response, adoption by division, and what was happening on their desk that week. Something like: "Ticket 44-118 sat nine days in June, in the middle of your contract ramp; you had two CSMs in eight months; you're paying for 120 seats with 46 weekly active." Then hand them the floor and stop talking. Never open with "how's everything been going?" when you have their ticket history on screen — a VP of Recruiting will read it as unprepared or evasive and spend the rest of the call testing which.
- How much of the call should be spent on the renewal itself?
The last five minutes. On a thirty-minute save call, budget fifteen minutes for listening, five for proof of change and rebuilding on what works, five to build the 90-day plan live, and only then move to commercials — and ask permission to make that transition: "If you're satisfied that plan is real, can I walk you through what renewal looks like?" Leading with the order form or "what would it take to get this done" confirms their suspicion that you only appear when money is due.
- Should I discount to save a staffing account that had a bad service year?
No. A discount offered as an apology reframes a service failure as a pricing dispute, tells them list price was always soft, and resets your floor permanently. Use service credits for the specific months affected — they're finite and specific — and right-size seats to the actual recruiter headcount, especially if they cut desks during a downturn. That kills the shelfware objection for good and usually costs less than a blanket percentage. Any real discount is traded: multi-year, an earlier signature, a reference call with another Head of Talent Delivery, a case study on their redeployment numbers.
- How do I handle a competitor quoting 25–30% less with a native ATS integration?
Surface it yourself, never disparage, and ask genuinely what they liked. Then establish how far it's gone: pricing in writing, migration scoped, security or MSP compliance review, internal sponsor. Reframe from price to total switching cost — re-implementing during their busy season, retraining the one practice that did adopt, migrating two years of contact history and right-to-represent records, a quarter with no reliable submittal-to-interview reporting, and the risk of inheriting a new vendor's version of the same support problem with none of the goodwill. Don't match on price in this call; you haven't re-established value yet.
- Which metrics should appear in a staffing renewal conversation?
The ones the buyer is compensated on. Redeployment rate on contractors rolling off assignment is the single most persuasive number in a staffing save call, because every point is a placement they don't pay to source. Pair it with submittal-to-interview ratio, placements per recruiter per month, fall-off inside 30–90 days, and time-to-submit. Quote their baselines as of today, in writing, and agree to review the same numbers at day 90 — measurement you propose before they ask for it is the strongest signal that you expect to be held to the plan.
- Who else needs to be in the room besides the person taking the renewal call?
Most stalled renewals die in procurement or with an economic buyer who has already seen the competitor's quote. Get three people onto the next meeting: the power user whose workflow would break if you left — often a Practice Lead in IT staffing or a Director of Contractor Care — the budget holder, who may be a CRO or the Managing Director rather than the VP of Recruiting who signed last time, and your own executive sponsor. An exec-to-exec acknowledgement of the bad year carries more weight than anything an AE can say alone. Book it on the call; never say "I'll follow up."