Staffing / Recruiting · Upsell Call
The Upsell Script for Staffing / Recruiting Customers: Turning a Quarterly Check-In Into a Redeployment Expansion
Your customer is a VP of Recruiting who spent this morning in a pipeline review arguing about whether a slipping fill rate is a sourcing problem, a client problem or a recruiter problem — because half the 'last contacted' fields in the ATS are fiction and everybody knows it. Her contract desk has forty-odd assignments ending this quarter, her redeployment rate is somewhere in the twenties, and her CRO has told the branch managers that with MSP bill-rate caps where they are, nothing that raises cost-per-placement gets signed. She picked up your call expecting fifteen minutes of 'how's everyone finding the platform.'
That question is the fastest way to lose this call. She knows you can see her usage. If you make her narrate it, you've told her you didn't look. This playbook assumes you did: you know which branches are live and which never onboarded, you know what her submittal-to-interview ratio did after go-live, and you know her renewal date and whether the person who signed the original order form still works there.
The expansion you're selling here is the end-of-assignment seam — the contractor who finishes a nine-month engagement on Friday and is on a competitor's payroll by Wednesday because nobody has spoken to them since onboarding. It is the single easiest expansion to sell into a margin-compressed staffing firm, because redeployment is the one placement they don't pay to source. But you only get to raise it after she has said, out loud and in her own numbers, that what she already bought worked. All figures in the script blocks are placeholders — fill them from her instance, not from a benchmark deck.
The upsell call script
Say it in your own words. The structure is the part that matters.
- 1
0. Pre-call usage audit — do not dial without these seven lines
Fill these in from your own systems before you touch the phone: 1. ADOPTION: [X] licensed seats, [Y] weekly active. Which branches/desks are live, which never onboarded. Name the dark corner out loud: 'Tampa has 18 seats and 4 weekly actives, and they're a direct-hire desk.' 2. DEPTH: which sequences are running (submittal follow-up? offer-to-start? reference chase?) and which they've never switched on. Last login of the exec sponsor. 3. OUTCOME: one number YOUR product moved in THEIR data — submittal-to-interview ratio, time-to-submit, or placements per recruiter per month. Pre-go-live vs. last full quarter. 4. THE GAP METRIC: their redeployment rate on contractors rolling off, and how many assignments end next quarter. This is the wedge. Pull it before the call. 5. COMMERCIALS: contract value, renewal date, who signed, are they still there, discount level, co-term implications. 6. SUPPORT: open tickets, last escalation, anything touching ATS sync or 'last contacted' fields. A live sync ticket changes the whole call. 7. CHAMPION: still in seat? Promoted? Quietly sidelined after a branch reorg? Test: can you say one thing about their desk they'd be mildly surprised you knew? If not, do the work.
- 2
1. Frame it honestly in the first 30 seconds
'Thanks for the time. Two things. First — I pulled your usage across the last two quarters and there's a pattern in it I want to check with you, because I think it means something about your contract desk specifically. Second, depending on what you tell me, there's a piece of the platform I think is relevant to it, and if it isn't I'll say so and we'll spend the rest of the call on something more useful. Fair?' Do not ambush, do not sandbag. Pre-committing to walking away lowers a delivery leader's guard faster than any rapport-building.
- 3
2. Anchor on the result they already own — in their metric
'Before we started, Dallas and Chicago were running roughly [1 in 5.8] on submittal-to-interview. Last full quarter both desks are sitting around [1 in 3.9], and time-to-submit came down about [a day and a half]. Does that match how it feels on your side, or am I reading it optimistically?' Let them correct you. Their correction is worth more than your number — it tells you which metric they defend in front of the owner. Write it down verbatim; it becomes line one of the business case they take to their CRO. IF THEY CAN'T CONFIRM A RESULT: stop the upsell. 'Then let's not talk about anything new today. Let's fix the fact that you're paying for something you can't point to in a pipeline review.' That's a value-realization call, and it's the only version of this call that protects the renewal.
- 4
3. Say the underuse objection out loud before they do
'Here's what I'd push back on if I were sitting in your chair: you've got [85] seats and about [51] weekly actives, and Tampa is [18] of those seats with [4] people in there. Why would you buy more before you've used what you've got. So let me tell you what I think those [34] are actually doing — they're not idle. Tampa is a direct-hire desk and the submittal cadence we built is tuned for contract reqs. That's an onboarding gap on my side, not a licensing problem on yours, and I'd rather fix it than bill you for it. What I want to talk about today is a different desk and a different seam entirely.' Reframe unused capacity as unrouted work — and if the honest answer is 'you have an adoption problem, not a product gap,' say it. That sentence buys you the right to come back next quarter.
- 5
4. Find the seam — diagnostic questions for the end-of-assignment gap
Do not lead with the module. Lead with where value leaks out of the desk: - 'Walk me through what happens on a Friday when a nine-month assignment ends. Who talks to that contractor, and when was the last conversation before that?' - 'How many assignments are ending next quarter across the contract desks?' - 'What's your redeployment rate on people rolling off right now — and does anyone own that number, or does it sit between the recruiter and the account manager?' - 'When you re-source a contractor you already recruited, background-checked and know performs — what does that cost you in ad spend and recruiter hours?' - 'Who's asking you for a bench-days report you can't produce today?' - 'What did we deliberately leave out of scope in the original deal because it was too big a bite?' That last one is the highest-yield question on this call. Most upsells were already scoped and cut once.
- 6
5. Build the incremental case in their arithmetic
Structure it as unit, volume, capture rate, net — and say the price in the same breath as the value. 'So let's do it in your numbers. [41] assignments ended last quarter on the contract desks. At [24%] redeployment, that's about [10] you kept and [31] who went and found their own next thing. You told me your average spread per contract placement is around [$19K]. If the assignment-end cadence takes you from [24%] to [35%] — and I'd rather under-promise, so push back if you think that's generous — that's roughly [four and a half] extra redeployments a quarter. Call it [$85K] of spread with no job ad, no sourcing hours, no new right-to-represent. It's [$3,100] a month on top of what you're paying, so [$9,300] a quarter against that. If you think 35% is fantasy, give me the number you believe and we'll rerun it right now.' Handing them the pencil on the assumptions is what separates a business case from a pitch.
- 7
6. Cost the rollout in hours and names, not phases
'Bandwidth is the real question, not the money, so let me scope it honestly. One 90-minute config session with whoever owns contractor care — is that Priya? — where we map to the assignment end-date field in your ATS. Then about two hours a week from that one person for three weeks while we tune the touchpoints. My CS team writes the first sequence drafts in your recruiters' voice and Priya edits rather than authors. That's the whole ask. No project team, no steering committee. If it needs more than that I've mis-scoped it and I'll tell you before you sign anything.' Put the work you can absorb on the table here — templates, config, the enablement session — not later as a concession.
- 8
7. The ask: one desk, one quarter, reversible, co-termed
'I don't want the whole firm. Give me the [Chicago IT contract desk] for one quarter — the [22] assignments ending between now and [March]. You define what success looks like, right now, on this call. My suggestion is redeployment above [35%] on that cohort and bench days trending down, but if the number you care about is fall-off inside 30 days or placements per recruiter, we use yours. If we miss it, we pull it out at the end of the quarter and there's nothing further owed. If we hit it, we roll it to [Dallas] and we co-term the whole thing to your [March 14] renewal so you're negotiating one contract instead of two and procurement sees an amendment, not a new purchase. Which number do you want to be judged on?'
- 9
8. Buying-committee check — ask it before you build the paper
'Last time this went through [Tom] on the revenue side and legal signed off in about a week. Is that still the path, or has the threshold moved since the MSP renegotiation? And is [Rich] going to want a say now that Tampa's on the same paper?' If a new CRO, a new procurement policy or a three-bid rule over [$25K] has landed since the original deal, you are running a fresh evaluation, not an expansion. You need to know that today, not in week six.
- 10
9. Park signals — walk away from the upsell, keep the account
Park it, don't push, if any of these are live: an open P1 or an unresolved ATS sync escalation; a champion who changed roles or lost a branch in a reorg; a renewal inside 60 days with value questions still open; a flat or declining weekly-active curve you can't explain; a hiring freeze or cost review announced at the firm in the last quarter. The line: 'I'm going to take the expansion off the table until the sync ticket is closed and you've got two clean weeks of last-contacted data. It's the wrong week to ask you for money. Let's book 30 minutes after that.' Pushing through any of these turns a renewable account into a churn risk for an incremental deal.
- 11
10. Same-day written recap — this is the artifact, write it for the CRO
Send within four hours, containing exactly: (1) the result they confirmed in their words and their metric; (2) the redeployment gap they described, with their numbers; (3) the value math with their capture rate, not yours; (4) the price, stated plainly; (5) the implementation ask in hours and named people; (6) the pilot desk, the success metric they chose, and the decision date; (7) the co-term to the existing renewal. Subject line: 'Chicago contract desk pilot — redeployment 24% → 35%, decision by [date]'. Your champion forwards this email. Write it for the person who reads it without you in the room.
How the call actually sounds
Prospect on the left, the rep on the right.
Rep
Dana, thanks for the twenty. Two things I want to cover. First, I pulled your usage for the last two quarters and there's a pattern on the contract side I want to sanity-check with you. Second, depending on what you say to that, there's a piece of the platform I think is relevant — and if it isn't, I'll tell you and we'll drop it. Fair?
Buyer
Fair, though I'll warn you now, Tom has frozen anything that adds to cost-per-placement. We just re-papered two VMS programs at a 12% cap. So if this is a new-module call, save us both the time.
Rep
Noted, and I'd rather talk about placements you don't pay to source than about spend. Start with what you already own though. Before go-live, Dallas and Chicago were running about one interview for every 5.8 submittals. Last full quarter both desks are around 1 in 3.9, and time-to-submit is down roughly a day and a half. Does that match how it feels, or am I reading it optimistically?
Buyer
Chicago, yes. Marcus would say the submittal follow-up is the reason his hiring managers actually respond now. Dallas I'd argue with — they got two big MSP releases last quarter that inflate everything. And honestly, I don't trust the underlying data. My recruiters log activity at six o'clock from memory. 'Last contacted' in our ATS is fiction.
Rep
That's the fairest objection I'll hear today, and it's half the reason I called. The submittal touches in our system aren't recruiter-logged — they fired, so they're timestamped whether or not anyone remembered. Which means for those two desks you've got one clean data set. That's actually the thing I want to use. Before I go further though — you've got 85 seats and about 51 weekly actives, and Tampa is 18 of those seats with 4 people in there. Why would you buy anything more from me before you've used that.
Buyer
You're saying my objection for me. It's a good line but it doesn't make the 14 dead seats less annoying.
Rep
It shouldn't. Tampa's a direct-hire desk and the cadence we built is tuned for contract reqs and submittal follow-up — Rich's team has nothing to run. That's an onboarding gap on my side. I'll bring you a perm-desk sequence in January at no charge and we'll either light those seats up or I'll take them off the contract at renewal. What I want twenty minutes on is a different desk entirely. Walk me through what happens on a Friday when a nine-month contractor finishes an assignment.
Buyer
In theory the account manager and the recruiter both reach out at 30 days out. In practice? The recruiter's in LinkedIn Recruiter covering four open reqs, and the contractor gets a text on their last day saying 'great job, let us know what you're looking for.' We're at 24% redeployment. I know. I don't need a lecture on it — I've had it from the owner.
Rep
No lecture. How many assignments end next quarter across Dallas and Chicago?
Buyer
Forty-one ended last quarter. Next quarter's similar, maybe a bit heavier in Chicago.
Rep
So at 24% you kept about ten and thirty-one walked. What's your average spread on a contract placement?
Buyer
Around nineteen thousand over the life of an assignment, blended.
Rep
Then here's the arithmetic. Same trigger mechanism you already trust on submittals, pointed at the assignment end-date field instead: 45 days out, 30, 15, and a day-five check-in on the redeploy. If that takes you from 24% to 35% — and push back if you think 35 is generous — that's about four and a half extra redeployments a quarter. Call it eighty-five thousand of spread with no job ad, no sourcing hours, no new right-to-represent. It's $3,100 a month, so $9,300 a quarter against that number.
Buyer
I think 35 is generous. And there's a bigger problem — Marcus's team is drowning. Q1 req volume is up and I've got recruiters covering eleven reqs each. I cannot hand them a rollout in January. Also, our ATS vendor told us at their user conference that redeployment sequences are in the winter release. Why am I paying you for something I may already own?
Rep
Take them one at a time. Run it at 30% instead of 35 — that's two and a half extra placements, about forty-seven thousand against $9,300. Still clears. Use 28 if you like, it still clears. On the ATS: you may well own it in the winter release. Same question I'd ask about any module — pull up your current instance and tell me what percentage of your submittals have three or more logged touches after the shortlist went out. If the answer's low, it's not because the feature was missing, it's because it depended on a recruiter remembering to set the sequence. That's the part I'd want to test before you wait two quarters on a release note.
Buyer
And the bandwidth? Because that's the one that's actually true. Last time you rolled something out I lost two weeks of Marcus.
Rep
Then Marcus isn't in this one. This lives with Priya on contractor care — one 90-minute config session to map the end-date field, then two hours a week from her for three weeks. My team drafts the touch copy in your recruiters' voice and Priya edits rather than writes. If it needs more than that I've mis-scoped it and I'll tell you before you sign. And I don't want the firm — give me Chicago's contract desk for one quarter, the 22 assignments ending before March. You pick the success metric.
Buyer
If I did anything it'd be Chicago, yes. But it's not my signature anymore — anything over 25k annualised goes to Tom now, and since the VMS renegotiation he wants two comparables on new spend.
Rep
That's the most useful thing you've said. Then let's not make it new spend. Co-term the pilot to your March 14 renewal so it lands as an amendment on paper Tom already signed, and price the quarter at $9,300 — under his threshold. He gets one negotiation in March instead of two, and by then you'll have a redeployment number on 22 real assignments instead of my forecast. What number do you want to be held to on that cohort — redeployment above 35%, or would you rather it be bench days?
Buyer
Redeployment above 35% and no fall-offs inside 30 days on the redeploys. If we miss either, we pull it and I don't want a renewal conversation about it.
Rep
Written down. Above 35% redeployment on the 22, zero fall-offs inside 30 days on redeployed contractors, decision date the first week of March, pull-out with nothing further owed if we miss. I'll have that in your inbox by five today in a form you can forward to Tom, with the math at your 30% assumption rather than my 35. Can you get me 90 minutes with Priya the week of the 12th?
Objections you will hear
What they say, and what you say back.
| Objection | How to answer it |
|---|---|
| “Our ATS already claims to do redeployment sequences — it's in their next release.” | It probably will be, and the module will exist. Pull up your current instance and tell me what percentage of your submittals had three or more logged touches after the shortlist went out. If it's like most firms, the feature is licensed and unused, because it depends on a recruiter remembering to set the sequence at six o'clock after covering eleven reqs. I'm not asking you to replace the ATS — the triggers fire off your end-date field and write back to the record. The question is whether the assignment-end follow-up actually happens without someone remembering. |
| “MSP caps have crushed our margins and new spend is frozen this year.” | Which is exactly why I want to talk about redeployment rather than about spend. What's your rate on contractors rolling off — 24%? Every point you move it is a placement you don't pay to source: same bill rate, no job ad, no re-screen, no new right-to-represent on someone you already background-checked. It's the only lever left that doesn't raise cost-per-placement. Show me the number and if the math doesn't clear $9,300 a quarter at your own assumption — not mine — I'll leave it until budgets open. |
| “We barely use what we've already bought. Tampa hasn't logged in since March.” | Agreed, and I'll say it before you do: 18 seats, 4 weekly actives, and that's on me. Tampa's a direct-hire desk and the cadence we built is tuned for contract submittals — they've got nothing to run. That's an onboarding gap, not a product gap, and I'll bring them a perm-desk sequence in January or take the seats off at renewal. But it's a separate problem from the one I'm here about. Dallas and Chicago are at 51 of 67 weekly and they're the desks with 41 assignments ending a quarter. |
| “My recruiters are underwater — Q1 req volume is up and I can't hand them a rollout.” | That's true and I'm not going to argue with it. So the recruiters aren't in this rollout. It's one person — whoever owns contractor care — for 90 minutes of config and two hours a week for three weeks. My team writes the first drafts of the touchpoints and they edit. And the recruiter only sees the redeploys that need a human: a contractor who replies 'I'm interested but I need $4 more an hour' lands in their queue, the rest run themselves. If you'd rather start after your Q1 crunch, I'll take a start date of April 7 — but I'd want the date on the calendar today, not a circle-back. |
| “We tried a candidate-engagement tool two years ago and it died by month three.” | What broke — the tool or the ownership? Nine times out of ten nobody owned the cadence, nothing got reported on, and it quietly stopped. So who owned it, what did the first 30 days look like, and was anyone reviewing touch counts in the Monday pipeline meeting? If that's the story, it's a fixable problem and I'd rather fix it than sell against a ghost. On this one the ownership is named on the order form and the pilot has a success metric you write, with a pull-out clause at the end of the quarter. |
| “Automated outreach to contractors at end of assignment is going to feel like spam. These people know their recruiters.” | A contractor who gets a generic drip on their last week is a contractor who blocks your number, so yes. What I'm describing is structure, not blast — the recruiter's own voice, on a defined cadence, with an actual reason each time: 45 days out it's 'what do you want next,' 30 days it's two live reqs that fit, 15 days it's a rate conversation. The alternative isn't high-touch. It's a text on their last day saying 'great job, let us know.' That's what's producing 24%. |
| “Send me something and I'll circulate it to Tom and the branch managers.” | I'll send it by five today and I'll write it so Tom can read it without me. But a PDF won't tell you whether it clears your desk math — that needs your redeployment rate, your assignments-ending count and your average spread, and you're the only one who has all three. Give me twenty minutes with you and whoever owns contractor care, we'll build the number together, and if your own arithmetic doesn't beat the price you've got a clean data point for your next ops meeting and I'll stop asking. |
Questions reps ask about this call
- What should I open with on an upsell call to a staffing customer?
Open with their usage data and one result the core product already moved — submittal-to-interview ratio, time-to-submit, or placements per recruiter per month for the desks that are actually live. Then name the agenda honestly: you looked at the numbers, there's a pattern, and depending on their answer there may be a piece of the platform that's relevant. Never open with 'I wanted to walk you through something we just launched.' A VP of Recruiting knows you can see her instance; making her narrate her own adoption tells her you didn't look, and it's the specific thing that moves you from partner to vendor.
- Which expansion sells best into a staffing firm right now?
Anything attached to redeployment. With MSP and VMS bill-rate caps compressing spread, ownership has told every branch that nothing raising cost-per-placement gets signed — so the only expansions that survive are the ones that produce placements without new sourcing cost. A contractor rolling off an assignment is already recruited, background-checked and proven on the job. If their redeployment rate sits in the twenties and they have thirty or forty assignments ending a quarter, the arithmetic writes itself in their numbers, not yours. Fall-off reduction inside 30–90 days is the second-best wedge for the same reason.
- How do I handle 'budget is frozen because margins are down'?
Don't discount — discounting teaches them the original contract was overpriced and that waiting produces a better price. Ask what the budget is committed to and when it resets, then look for three paths: a line item in the same budget that isn't performing, the budget of the desk that benefits rather than the central one, or a signed order form now with a start date at renewal. Co-terming to the existing renewal is the most underused unlock on this call: it turns a new purchase into an amendment on paper procurement already approved, and often keeps the annualised figure under a new-CRO approval threshold.
- The customer says their ATS already has this. What do I say?
Concede that the module probably exists and move to whether it fires. Ask them to open the ATS on the call and tell you what percentage of submittals have three or more logged touches after the shortlist went out, or what percentage of contractors 45 days from assignment end have a scheduled next contact. The feature usually depends on a recruiter remembering to set a sequence at 6pm from memory — which is the same reason 'last contacted' fields are fiction. Position your product as firing from the record they already live in, writing back to it, and surfacing only the responses that need a human.
- When should I not run the upsell on a staffing account?
Park it if there's an open escalation — especially anything touching ATS sync or activity write-back, because that's the trust issue this buyer is most sensitive to. Also park it if your champion has just moved branches or lost a vertical in a reorg, if renewal is inside 60 days with value questions still open, if weekly actives are flat or falling and you can't explain why, or if the firm has announced a cost review or recruiter headcount cut in the last quarter. Say so out loud — 'it's the wrong week to ask you for money' — and book the follow-up. Pushing through any of these converts a renewable account into a churn risk.
- How big should the first ask be?
One desk, one quarter, reversible, with success criteria they write on the call. Name the cohort precisely — 'the 22 assignments ending in Chicago before March' — and let them choose the metric they'll be judged on, whether that's redeployment above 35%, bench days, or zero fall-offs inside 30 days on redeployed contractors. Add a pull-out clause with nothing further owed, and co-term to the existing renewal. A branch-level pilot at a quarter's price often lands under the approval threshold that would otherwise trigger three competing bids, and a real number on 22 assignments beats any forecast you could bring to the renewal conversation.