Staffing / Recruiting · Demo Call
The Staffing / Recruiting Product Demo Script for VPs Who Are Looking for Where It Breaks
Your buyer has already sat through the pitch. The VP of Recruiting said yes to a demo, pulled in the Director of Delivery, and maybe a Practice Lead from the IT vertical who has opinions about anything that touches a candidate record. They are not on this call to learn what your product does. They are on it to find out where it breaks — specifically, whether it turns into the same licensed-and-unused module sitting inside their ATS right now.
Every staffing leader on that call has a scar. Somebody bought Bullhorn Automation and nobody owned the sequences. Somebody rolled out a texting tool and a contractor got a generic message while standing in a client's building. Somebody was promised a redeployment lift and got a report nobody reads. So the interruptions come fast: whose name is on the email, what happens on Fieldglass accounts where we can't contact the hiring manager, who's updating the assignment end date when half the 'last contacted' fields in the ATS are fiction. Each of those is a buying question wearing a disqualification mask.
This script gives you the opening contract, three core demo loops built on the moments that actually cost them money — the shortlist that goes dark, the contractor rolling off in three weeks, the pipeline review that turns into a debate — plus cold answers on integration, ownership, failure modes and time-to-value. Run three workflows completely instead of twelve partially, and let them stop you. The silence is the thing to be afraid of, not the interruption.
The demo call script
Say it in your own words. The structure is the part that matters.
- 1
Confirmation email (send 48 hours out)
"Quick one so I don't waste twenty minutes showing you things that don't apply: 1. What are you running for ATS — Bullhorn, JobDiva, Avionté, Ceipal, something else? And is your back office in the same system or separate? 2. Do you have Bullhorn Automation / Sense / TextUs already licensed, and is anyone actually using it? 3. Roughly what's the split between your direct accounts and your MSP/VMS volume — Fieldglass, Beeline, Wand? 4. Send me two live req titles and two contractor assignments rolling off in the next 90 days. I'll build the demo on those instead of 'ACME Corp — Software Engineer.' And who's joining? If your Director of Delivery is on, I'll run it differently than if it's just you." [If they won't share reqs, use their actual verticals and job titles. A demo with 'Test Candidate 1' tells a Managing Director you didn't prepare.]
- 2
Opening — 90 seconds, no company slide
"Last time you told me three things. Your submittal-to-interview ratio has been sliding on your top accounts and you can't tell whether it's the client or the desk. Redeployment on contractors rolling off is somewhere in the low twenties. And half your pipeline reviews turn into an argument about whether the ATS data is real. Still the picture, or has something moved?" [Wait. Let them correct you — the correction is free discovery.] "Two ground rules. First, please interrupt me. If you're thinking 'that won't work on our MSP accounts,' say it while I'm on the screen, not in the recap email. That's the useful part of this call. Second — what's the one thing that, if this can't do it, we don't need to keep talking? I'd rather demo in that order."
- 3
Loop 1 — The shortlist that goes into the void
**Problem:** "Tuesday, your recruiter submits three profiles on the Senior Data Engineer req. Hiring manager says 'great, reviewing this week.' Then nothing. Two of the three take other offers. Six weeks later your account manager finds out it got filled internally. The req is still sitting in Bullhorn as 'submitted.'" **Screen:** "Here's that req in your system — I'm using the one you sent me. Recruiter submits, and the cadence starts from the record they're already in. Day two, day five, day nine. Each one has a reason to exist: 'candidate two has a second interview elsewhere Thursday, do you want to move?' It goes from your recruiter's mailbox, their signature, their mobile number on the text." **Consequence:** "What changes is that the req can't go quiet without somebody knowing. Day nine with no response, it lands on the account manager's list as a client problem, not a sourcing problem." **Check:** "Is that how your submittals actually die, or am I describing somebody else's desk?"
- 4
Loop 2 — Redeployment on the contractor rolling off
**Problem:** "You've got a contractor finishing a nine-month assignment on the 28th. Nobody's spoken to them since onboarding. They're on somebody else's payroll by the Wednesday, and you pay to re-source a person you already recruited, background-checked and know performs." **Screen:** "This pulls the assignment end date from your back office, not from a field a recruiter remembers to update. Thirty days out, it doesn't text the contractor — it puts a task on their recruiter with the assignment, the bill rate, the client, and the three open reqs that match their skill set. Fourteen days out, if there's no logged conversation, it escalates to your Director of Contractor Care." **Consequence:** "Every point you move redeployment out of the twenties is a placement with no ad spend and no sourcing hours against it. Same spread, cheaper to earn." **Check:** "Where does redeployment actually sit for you right now — and who owns that conversation today, the recruiter or the account manager?"
- 5
Loop 3 — Making the pipeline review a decision instead of a debate
**Problem:** "You said pipeline reviews turn into arguments. Recruiter says they've been all over it, the client says nobody called, and nobody can prove either." **Screen:** "This is the view for a Managing Director. Reqs by account, with logged touches after submittal — not activity typed in at 6pm from memory, actual sends and calls. This account has eleven submittals and an average of 1.4 touches after the shortlist. This one has nine submittals and 4.2. Same recruiter. Different client behaviour." **Consequence:** "Now the Monday meeting is about which account is stalling, not whose fault it is." **Check:** "If you had that number by account last quarter, would it have changed who you put on what desk?"
- 6
When they ask 'will it handle X?' — slow down first
"Before I answer that — give me the actual case. When you say right-to-represent, do you mean you want the RTR chased inside the cadence, or do you mean you need it suppressed on candidates already submitted elsewhere?" Then pick one of three, honestly: - **Yes, here it is.** Go show it live. This is the strongest thing that happens on a demo. - **Yes, but not how you'd expect.** "You don't do it on the req. You do it on the candidate record and it's two extra clicks." Buyers forgive ugly. They don't forgive finding ugly in month three. - **No.** "No. We don't write into the Fieldglass portal and we're not going to. How often does that come up — daily, or is it a quarter-end thing?" Never say "we can build that." To a VP of Recruiting who's been burned, that is the exact sentence their last vendor used. "Let me write that down where you can see it — VMS suppression by client. I'll have a straight answer to you Thursday." Then do it Thursday.
- 7
Pressure line 1 — Integration (what they're really asking: how much lands on my ops team?)
"Name the method, not the word: "We read from Bullhorn over the REST API — reqs, submittals, assignment end dates, candidate contact fields. Every fifteen minutes. We write back one thing: a logged note on the record with the touch and the response. That's it. What we don't touch: we don't write to your back office, we don't touch pay or bill rates, and we don't post anything into Fieldglass or Beeline. Your MSP process stays exactly as it is. If you're on JobDiva instead, it's the same read pattern but the write-back is a note type your admin creates — that's a fifteen-minute call with whoever administers your instance. Who is that, by the way, internal or your Bullhorn partner?" [Saying what you *don't* touch calms a Director of Delivery down more than any capability claim.]
- 8
Pressure line 2 — Who owns it after you're gone
"Straight answer: this needs one owner, and it should not be your busiest biller. Ongoing it's about two hours a month, and it's not technical — turning cadences on for a new client, adjusting the redeployment trigger from 30 days to 45 for a vertical where extensions land late. Your Director of Delivery or a delivery coordinator does that. It is not an IT job. Setup is different: someone on your side has to sign off on the cadence copy, because it goes out in your recruiters' names. That's a two-hour working session, once. And if that person leaves — the cadences don't stop. They're not tied to a login. Handover is one recorded session and a one-page doc, and I'll show you the doc before you sign anything."
- 9
Pressure line 3 — What actually happens when it breaks
"I'm not going to quote you an uptime number, because nobody's ever bought anything because of a decimal. Here's the failure mode. If we go down, nothing sends. Your recruiters keep working in Bullhorn exactly as they do today — we're not in the path of anything they need to do their job. When we come back, queued touches don't all fire at once; anything older than 24 hours drops and surfaces as a task instead, so a hiring manager never gets a Tuesday follow-up on a Friday. Support: P1 is a phone number and a human answers. Anything else is email, next business day. I'm not going to pretend otherwise. Your named contact after go-live is the same person who runs your implementation, and above them is [name the role]. Want me to tell you about our last outage? I'd rather you hear it from me than from a reference call."
- 10
Pressure line 4 — Time-to-value, in three dates not one
"Three dates, not one. **Live** — connected to your ATS, cadences firing on one desk. [Use your real number, e.g. two weeks from kickoff.] **Useful** — your IT practice stops chasing submittals by memory and you can see touches-after-submittal by account. That's the first number you can put in front of ownership. **Fully rolled out** — all desks, contractor redeployment triggers live across the book. What you owe me: a user list, your cadence sign-off, and two hours from whoever administers your ATS. That's it, and I'd rather tell you now than have your team discover it in week three and stall. One thing on timing — you said your billing week is a nightmare and your contractor start dates cluster on Mondays. We wouldn't switch anything on in that window."
- 11
Recovering when the room goes quiet
Signs: shorter answers, 'mm-hm', typing, camera off, a flat 'yeah, no, that makes sense.' Stop. Do not talk faster and do not add a feature. "I've been talking for six minutes. Is this the part you care about, or should I jump to the contractor side?" Or: "Let me stop the tour. What's the thing you're worried about that I haven't touched yet?" Or hand over the keyboard: "Do you want to drive? Tell me what to click and I'll follow." Or cut it honestly: "I think I'm showing you the wrong things. Can I stop, spend ten minutes understanding how your MSP accounts actually work, and come back with a version built for that?" Losing twenty minutes to save the deal is a good trade.
- 12
Closing the demo
"Let me say back what I think happened. Three things landed: the follow-up firing from the recruiter's own mailbox, the day-30 redeployment task off the assignment end date, and the touches-by-account view for your Monday review. Two things are open. VMS suppression on your Fieldglass accounts — I owe you a straight yes or no on that. And whether your Bullhorn instance lets us write the note type without your partner involved. Both answered by Thursday. Where does this sit for you now — worth pursuing, or is there something you've already heard that rules it out?" [Let them say no. A clean no beats four weeks of chasing.] "Who else needs to see this before it's real? If your CRO wants the spread and placements-per-recruiter angle, that's a different twenty minutes and I'd run it separately. Can we put the next one in now while we're both here — Thursday or Friday?" [Invite sent before you hang up. 'I'll follow up next week' is where demos go to die.]
How the call actually sounds
Prospect on the left, the rep on the right.
Rep
Before I share anything — last time you said submittal-to-interview is sliding on your top three accounts, redeployment's in the low twenties, and pipeline reviews turn into an argument. Anything moved since then? And what's the one thing that, if this can't do it, we stop?
Buyer
I'll tell you the one thing. We already pay for Bullhorn Automation. It's been licensed for two years and nobody uses it. So before you show me a single screen, tell me why you're not the same shelfware with a different logo.
Rep
Fair, and I'd rather know what actually killed it than talk around it. Who built the sequences, and what was the moment your recruiters turned them off?
Buyer
Marketing built them. Generic copy, our logo at the top. Then one of our contractors got a 'checking in!' email while he was sitting in the client's office and the hiring manager saw it. My Practice Lead for the IT desk shut the whole thing down that afternoon and I don't blame him.
Rep
So the problem wasn't automation, it was that it didn't sound like a recruiter. Let me show you the req you sent me — the Senior Data Engineer at the Charlotte account. Submittal goes out Tuesday. Day two, day five, day nine, and each one goes from Marcus's mailbox with his signature and his mobile number on the text. Marcus approves the copy once, at setup.
Buyer
Whose name is in the reply-to field? Because if a hiring manager hits reply and it bounces to a no-reply address, my account manager's relationship is done and I've made things worse.
Rep
His mailbox. It sends through his account, replies land in his inbox, and the second a reply comes in the rest of the cadence stops. He doesn't have to remember to kill it. Does that clear the bar your Practice Lead set?
Buyer
It's closer. But you're demoing a direct account. Sixty percent of my volume is MSP — Fieldglass and Beeline. On those we're contractually barred from contacting the hiring manager. If your system emails a manager on a Fieldglass req I lose the program, not the placement.
Rep
Then straight no on part of that: we do not write into the VMS portal and we won't touch a hiring manager on a suppressed account. What I'd need to know is whether your client records in Bullhorn are flagged MSP versus direct cleanly enough for us to suppress off that field. Are they?
Buyer
Mostly. Not perfectly. And if it's suppressed on sixty percent of my book, what exactly am I buying?
Rep
Two things that don't depend on hiring manager contact. Your forty percent direct — where the ghosted shortlist is costing you the most, because those are your relationship accounts. And the contractor side, which is the whole book, MSP included. Can I show you that one? It's the assignment you sent me ending on the 28th.
Buyer
Go ahead, but I'll tell you now where this falls over. If your tool texts my contractor at day 30 saying 'what's next,' and the client hasn't decided on the extension yet, you've just told my billable consultant the assignment is ending. He starts looking. I lose the extension and the person.
Rep
That's exactly why nothing goes to the contractor. Day 30 out, it creates a task for his recruiter with the assignment, the bill rate, the client, and the matching open reqs. The recruiter makes the call and decides what to say. Day 14, if there's no logged conversation, it escalates to your Director of Contractor Care. The system never speaks to the contractor.
Buyer
Which brings me to the other problem. It's reading the assignment end date from where — the field my recruiters are supposed to update? Because half those are wrong and 'last contacted' in my ATS is pure fiction. Garbage in, garbage out, and now I've got a tool escalating on bad dates.
Rep
Agreed, and if it read the recruiter-maintained field I wouldn't demo it to you. It pulls the end date off the assignment record in your back office — the one your billing runs against, because that one's right or you don't get paid. Is that assumption true at your firm, or does your back office sit somewhere separate?
Buyer
No, that's Avionté and it's accurate. Fine. So realistically — what does this cost my team in hours before anyone sees a number they can show the owner?
Rep
Two hours from whoever administers Bullhorn, and two hours with Marcus and your Director of Delivery signing off the cadence copy. That's your total workload. I'd rather say that now than have you find it in week three. Two things I still owe you: suppression logic on your MSP flags, and whether your instance lets us write the note type without your Bullhorn partner. Both by Thursday — can we get twenty minutes Friday to close them out, and should your Director of Contractor Care be on that one?
Objections you will hear
What they say, and what you say back.
| Objection | How to answer it |
|---|---|
| “Our ATS already does this — we've got the automation module licensed.” | Most firms do; the module exists. Can you pull up Bullhorn right now and tell me what percentage of your submittals in the last 90 days had three or more logged touches after the shortlist went out? If your team's like most, it's licensed and unused because it depends on a recruiter remembering to set the sequence at the moment they're already behind. I'm not asking you to rip out the ATS — I'm asking whether the follow-up actually happens when nobody remembers. |
| “Margins are thin. Bill rates are capped at 12-15% on our MSP programs and new spend is frozen this year.” | Then let's not talk about spend, let's talk about redeployment. What's your rate on contractors rolling off assignment? If it's in the twenties, every point you move it is a placement you don't pay to source — same spread, no job board spend, no recruiter hours, on a person you've already background-checked. Give me the number and if the math doesn't clear the cost I'll leave it alone until budgets open. |
| “My recruiters live in four systems already. They will not adopt a fifth login.” | If it's a fifth login it fails, and I'd rather say that than argue. Your team lives in Bullhorn and their phone, right? The cadences fire off the record they're already in, and the only thing that shows up for them is a task when a human is actually needed — the day-30 redeployment call, the reply that came in. There's no new place to go. But you'd know better than me: what happened the last time you rolled something out, and who owned it? |
| “We're a relationship shop, not a volume shop. Automated follow-up will feel like spam to clients we've had for twelve years.” | Then the ghosting hurts you more, not less. A high-volume desk can absorb a dead shortlist; you've got fewer, bigger accounts and each one that goes quiet is real revenue. And what I'm describing isn't a blast — it's your recruiter's voice, their mailbox, a defined cadence, with an actual reason to reach out each time. The alternative isn't high-touch, it's your recruiter following up twice and quietly giving up. How many of your top ten went dark on a submittal last quarter, and did anyone find out why, or did the req just close in the system? |
| “We tried something like this two years ago. It died in month two.” | What broke — the tool or the process around it? Usually it's that nobody owned the cadence and there was no reporting on touches, so it decayed and nobody noticed. I'd want to know who owned it, what the first thirty days looked like, and whether anybody was reading a number weekly. If that's the story, it's fixable and I'd rather solve it than sell against a ghost. |
| “This looks fine. Send me the deck and I'll circulate it internally.” | Happy to send the four screens that mattered today — but a PDF won't tell your Director of Delivery whether this fits the desk math. Give me twenty minutes with the two of you. I'll bring redeployment and submittal-to-interview benchmarks from firms your size in your verticals, and if your numbers already beat them, we're done and you've got a data point for your next ops meeting. |
Questions reps ask about this call
- How is a staffing demo different from a normal software demo?
The buyer is measured on numbers you can name out loud — fill rate, time-to-submit, submittal-to-interview ratio, redeployment on contractors rolling off, placements per recruiter per month, fall-off inside 30-90 days. A demo that doesn't move one of those is a tour. Build every screen around a moment in their week: the shortlist that went dark on Tuesday, the assignment ending on the 28th, the Monday pipeline review that turns into an argument. Then hand the mic back and ask whether that's actually how their desk works.
- What should I ask before the demo so the script lands?
Four things in the confirmation email: which ATS and back office (Bullhorn, JobDiva, Avionté, Ceipal — and whether front and back office are the same system), whether they already license Bullhorn Automation, Sense or TextUs and if anyone uses it, their rough split between direct accounts and MSP/VMS volume, and two live req titles plus two assignments rolling off in the next 90 days. Build the demo on their reqs. A Managing Director who sees 'ACME Corp — Software Engineer' knows you didn't prepare.
- How do I handle 'our ATS already does that' when they say it mid-demo?
Don't argue with the feature list — they're right, the module exists. Ask them to open the ATS on the call and tell you what percentage of submittals in the last 90 days had three or more logged touches after the shortlist went out. The gap between licensed and used is the entire conversation. Then be explicit that you're not replacing the ATS, and name exactly what you read from it and the one thing you write back.
- What do I say when they raise MSP and VMS restrictions?
Say no, clearly, and early. You don't write into Fieldglass, Beeline or Wand, and you don't contact a hiring manager on a suppressed account. Then find out whether their client records are flagged MSP versus direct cleanly enough to drive suppression, and pivot to the two things that survive the restriction: their direct accounts, and contractor redeployment across the whole book. Trying to talk your way past a program contract is how you lose a Director of Delivery permanently.
- How do I answer the reliability question without quoting uptime?
Describe the failure mode in their world. Nothing sends, recruiters keep working in the ATS exactly as they do today, and queued touches older than 24 hours don't fire late — they surface as tasks, so a hiring manager never gets a Tuesday follow-up on a Friday. Then give the support reality: what's a phone number with a human, what's email and next business day, and who their named contact is after go-live. Nobody in staffing has ever bought because of a decimal point.
- What's the biggest mistake reps make on staffing demos?
Two, usually. Starting with a dashboard or admin setup instead of the one workflow the VP of Recruiting complained about on the previous call. And saying 'we can build that' to dodge a no — to a leader whose last automation rollout died in month two, that sentence is a memory, not a promise. Say no, ask how often it comes up, write the gap down visibly, and come back with the answer when you said you would.