Selling Into Staffing and Recruiting: Pitching People Who Live on the Phone

The first ten seconds are a peer review

When you dial a staffing firm, the person who picks up does your job for a living. Not something adjacent to your job. Your job. They cold call, they leave voicemails, they build sequences, they get hung up on, they handle "send me some information" nine times before lunch. A recruiter's whole week is outbound plus objection handling plus a candidate who ghosts the interview.

So the opener you use on a marketing director does not survive contact here. The false-familiarity thing, the fake pause, the "did I catch you at a bad time," the manufactured urgency about a deadline that does not exist — they will name it out loud. I have had a branch manager stop me mid-sentence and say, "That's the permission opener, right? I use that one." That is either the end of the call or the beginning of a good one, and which one it becomes depends entirely on whether you flinch.

Do not flinch. Agree with them. "Yeah, it is. You want me to just tell you why I called?" Every time I have done that, the temperature of the call dropped by half. You are not selling to a buyer here so much as you are being evaluated by someone in the same trade. That is actually a gift. You can drop about half the packaging and go straight to substance, and the substance is what they wanted anyway.

The practical version of this is a shorter opener with a harder reason for calling. Name the role, name the pain, ask for a specific, small thing. Something like: "Tim with [company]. I call branch managers about the reqs that sit open past two weeks and nobody wants to talk about on the Monday call. Is that a thing at your branch or are you clean right now?" That is a peer question. It also gives them a graceful exit, which they will respect, and it gives you real information if they take the exit. I built out the longer version of this in the staffing and recruiting cold call script, including how the approach has to change between a VP line and a branch line, but the core principle is the one above: strip the technique, keep the reason.

Learn the four numbers that run a branch

You cannot fake your way through a staffing conversation with generic productivity language. "Help your team do more with less" means nothing to a branch manager whose comp is tied to gross profit. There are four numbers that actually run the place, and if you can talk about them the way an operator talks about them, you get treated as an operator.

Fill rate

Fill rate is the percentage of open orders the branch actually fills. It is the scoreboard number. It is also the number most likely to be politically loaded, because a bad fill rate can be a sourcing problem, a pricing problem, a client problem, or a sales problem — and every one of those has a different owner. When you ask about fill rate, you are stepping into an argument that already exists inside the building. Ask carefully. "When a req doesn't get filled, where does that usually break down for you — is it candidate supply, or is it the client dragging on feedback?" That question tells you who your ally is before you ever pick a champion.

Time to submit

Time to submit is how long between receiving a req and getting qualified candidates in front of the client. In contract and light industrial, this is close to everything. Whoever submits first frequently wins, not because their candidate is better but because the hiring manager stops looking once they have someone decent in hand. Recruiters know this in their bones. If your product touches speed of first submission, that is your wedge, and you should say it in those words rather than in words like "efficiency."

Redeployment rate

Redeployment is what percentage of contractors get placed on a new assignment when their current one ends. This is the most underrated number in the industry and, in my experience, the one the VP cares about far more than the branch does day to day. A redeployed consultant costs nothing to source. The margin on that placement is close to pure. A branch that redeploys well can be structurally more profitable than a branch that does more gross placements, and every VP of Recruiting I have talked to knows that and is frustrated their branches let people fall off the bench.

This is also the cleanest expansion story you will ever get, which is why I wrote the upsell script around turning a quarterly check-in into a redeployment conversation as its own playbook. If you land on time to submit, you expand on redeployment. Note it in the account plan on day one.

Consultant margin

Bill rate minus pay rate, roughly, before burden. This is the number that makes staffing people the negotiators they are. They spend their entire working life squeezing a spread. When you eventually talk price, remember that you are talking to a professional in exactly that discipline. More on that below.

You do not need to interrogate all four on a first call. You need to be able to use the vocabulary without a wobble in your voice. A recruiter can hear a rep reading terminology off a battlecard the same way you can hear a candidate reading a resume they did not write.

"Reqs go dark" is the pain nobody will volunteer

Here is the thing nobody in a staffing firm says out loud on a first call: a meaningful chunk of the reqs on the board are not real anymore. The client filled it internally and did not tell anyone. The hiring manager left. The budget got pulled. The req is technically open in the ATS and technically being worked by a recruiter who is technically submitting candidates into a black hole.

Everybody in the building knows this happens. Nobody wants to be the one who says how much of the board it represents, because saying it out loud means admitting the pipeline number in the Monday meeting is inflated. So it lives in the gap between what the system says and what people actually believe.

That gap is your discovery target. You will not get there by asking "what are your biggest challenges." You get there sideways, with a question that gives them permission. My version is some flavor of: "When you look at the open orders on the board right now, how many of those do you privately think are still live?" The word privately is doing all the work. It signals that you already know the answer is not "all of them," and that you are not going to make them defend it.

When a branch manager answers that honestly, the whole call changes. Now you are talking about wasted recruiter hours, about candidates who got their hopes up for a role that evaporated, about the credibility hit the branch takes with its own recruiters when they work dead reqs for two weeks. That is real pain with a real cost attached, and it is a cost they can articulate better than you can. Let them do it. I laid out the full twenty-five minute structure for getting there in the staffing discovery call playbook, because the sequencing matters — ask that question too early and you sound accusatory, ask it too late and you never get to the money.

The VP and the branch manager are two different sales

This is where most reps selling to staffing agencies lose the deal without noticing.

A VP of Recruiting thinks in aggregate. Consistency across branches. Why does the Dallas office redeploy well and the Phoenix office does not. Why does reporting take four days to assemble. Why do we have three ways of doing the same intake. A VP is buying standardization, visibility, and something they can defend to a CFO or a private equity sponsor. They will ask you about implementation across offices, about adoption by tenured recruiters who hate new systems, about what happens when they acquire a firm next year. They are also, frequently, buying a story they can tell upward.

A branch manager thinks in this week. Their comp is close to the ground. They have a number, they have a small team, and they have a client screaming about a shift that needs covering Monday. A branch manager does not care about cross-office consistency. A branch manager cares whether this thing makes Thursday easier or harder, and whether their two best recruiters will actually use it or quietly go back to the spreadsheet.

If you pitch a branch manager on standardization, you sound like corporate. If you pitch a VP on making Thursday easier, you sound small. Same product, two entirely different value stories, and you often need both because the VP writes the check and the branch decides whether it survives.

The move I have had the most success with is to be openly transparent about running both plays. To the branch manager: "I'm also talking to your VP, and I'll be honest, I'm telling her a different story than I'm telling you, because you two care about different things. What I need from you is whether the version I'm telling you is actually true on the ground." Staffing people appreciate that kind of directness at a level that surprised me the first few times. They spend all day managing two-sided conversations between clients and candidates where each side hears a slightly different framing. You naming it is not a scandal. It is craft recognition.

One warning. Do not let the branch manager become your only voice. Branch managers turn over, and branch managers sometimes lack the political weight to defend a line item when the year gets tight. And do not let the VP be your only voice either, or you will win a signature and lose the renewal to non-adoption. You need both, and you need them to have talked to each other before you get to the demo.

Seasonality will wreck your forecast if you let it

Staffing demand is not evenly distributed across the year, and the shape of it depends heavily on the vertical. Light industrial and retail-adjacent staffing have their own rhythm around peak season. Healthcare staffing moves with contract cycles and census. Professional and IT staffing follow client budget calendars. Education staffing lives and dies by the school year.

What that means for you is simple and painful: a branch that is drowning in orders will not take your meeting, and a branch that is quiet has no budget. Those are not the same objection and you should not treat them the same. The first is a timing problem you can work around by scheduling into the shoulder period. The second is a qualification problem that no amount of persistence fixes this quarter.

So ask about it directly, early, on every account. "What does your calendar look like — when's your heaviest stretch, and when do you actually get to work on the business instead of in it?" Then build your forecast around their calendar, not yours. I have watched good reps put a staffing deal on the board for end of quarter because the champion said "we'd love to have this in place before peak," not realizing that before peak means the champion is about to disappear for eleven weeks and nobody is signing anything until the surge is over.

The corollary is that the quiet period is when you land. Get your discovery done during the busy stretch, in short bursts, on their terms. Do the deep work when the phones slow down. If you invert that, you will spend your best selling weeks trying to get a call back from someone who is covering shifts personally at ten at night.

The demo has to survive a room of negotiators

Here is what a demo looks like in a staffing firm. Five people on the call. At least three of them close deals for a living. Two of them will be looking specifically for where your product breaks, not out of hostility but out of professional habit, because that is what they do to every vendor, every client contract and every candidate's story.

They will ask about the edge case. They will ask what happens when data is dirty, because their data is dirty, because everyone's data is dirty and recruiters are the ones who left the fields blank. They will ask what happens when a recruiter refuses to use it. They will ask about the thing you glossed over, specifically because you glossed over it, and they clocked the gloss.

So do not run a happy-path demo. Run the ugly path on purpose and narrate it. "This is where it gets messy — here's a record with no phone number and a duplicate. Watch what it does." Showing a flaw before they find it buys you more credibility with this audience than any polished workflow. They know software has flaws. They are testing whether you are the kind of vendor who will tell them the truth in month seven when something is broken and their client is angry.

The other thing that plays well: let a recruiter drive. Hand them the mouse, metaphorically or literally, and let them try to break it while everyone watches. It is uncomfortable and it is the single highest-conversion thing I have done in a demo to this audience. That whole approach — running the demo for people who are hunting for the failure mode rather than admiring the feature — is what the staffing demo script is built around.

Then comes pricing, and you should walk in knowing you are the least experienced negotiator in the room. These people negotiate rates every single day. They will silence you. They will anchor low with a straight face. They will tell you the incumbent quoted less, and sometimes that will be true. The counter is not clever tactics, because they know all the tactics and they will find your use of them a little insulting. The counter is a price you can defend on the numbers we talked about earlier — time to submit, redeployment, hours recovered from dead reqs — and the willingness to say no. Discount without a trade and you have just told a room of professional negotiators that your first number was fiction. They will remember that at renewal, and they will remember it out loud.

What I would do next

If I were picking up a staffing patch on Monday, I would spend the first week not selling. I would call ten recruiters and ask them to explain their week to me, and I would take notes on the words they use — not the words the industry blog uses, the ones they use. Then I would build my opener out of those words and go run it a hundred times.

The part that is hard to shortcut is the reflex. Sounding like a peer instead of a rep in the first ten seconds is not a script problem, it is a reps-under-pressure problem, and you cannot get it by reading. That is the whole reason I built DrillCall — so you can run the branch manager who cuts you off, the VP who asks about multi-office rollout, and the room full of people looking for where it breaks, twenty times before you do it once on a live line. Whether you use us or a colleague on the other end of a Zoom, drill it before you dial it. This audience only gives you the first ten seconds once.