How to present candidates so clients act.

Why good candidates get parked

Clients rarely reject a good candidate. They defer them. You send a resume with a note that says "really strong guy, let me know your thoughts," and the hiring manager opens it, sees a wall of text with no decision attached, and closes it to deal with later. Later never comes. The candidate cools, the req collects other options, and three weeks on you're chasing feedback on a submission nobody remembers reading.

The failure isn't the candidate and it isn't the client. It's the submission. A resume is a document about a person. A submission is an argument for a decision, and most recruiters send the first while believing they sent the second.

So set the bar where it belongs: a submission succeeds when the client does something. Books the phone screen, asks a sharp question, tells you what's missing. Anything but silence.

What does a 30-second submission look like?

Picture the hiring manager reading on a phone, walking between meetings, or standing in a trailer on a job site. That's your reader. Write for that moment.

The structure that survives it: one positioning line that says who this person is against this req, not in general. A handful of evidence bullets, each one a fact from real work. The logistics that kill deals late, stated early: comp expectations, notice period, location, when they can interview. And the one risk you're not hiding, named by you before the client finds it, with your read on why it doesn't sink the deal. Full resume attached underneath, for after they've decided to care.

Then the test: can the reader reach "book the screen" or "here's what's missing" in about 30 seconds? If not, you wrote it for yourself. Cut until the decision is the only thing left on the page.

Evidence over adjectives

"Strong leader, great communicator, excellent culture fit." Every one of those is you asking the client to take your word for it. Adjectives are claims about your judgment. Evidence lets the client form their own, which is the only kind of convinced that survives an interview.

The rewrite discipline is simple: for every adjective you're tempted to type, name the fact that made you believe it. "Strong leader" becomes what he actually ran, for whom, and what happened. "Loyal" becomes the tenure line the client can verify on the resume. "Great communicator" becomes the thing he said in your screen that made you write it down. If you can't find the underlying fact, the adjective was decoration, and the client's skepticism was correct.

This matters more than polish because the client is pattern-matching on risk. A superintendent presented with evidence reads like a sure thing. The same superintendent presented with adjectives reads like a recruiter's pitch. On a $28K fee, that difference is the difference between a same-day phone screen and a submission that dies in a tab.

When the client is stuck, go side by side

A client staring at one candidate is answering a hard question: is this person right? A client staring at two is answering an easier one: which of these is right? When a search stalls with good people in play, the fix is usually not another candidate. It's a comparison that turns an open question into a choice.

Build it against the job description, not against each other in the abstract. On the requirements the client said mattered, who carries each one better, and what's the trade? One candidate is stronger on preconstruction, the other has run bigger self-perform crews. Say so, plainly, and then do the thing most recruiters flinch from: recommend one, and say why. A comparison without a recommendation is just a spreadsheet, and spreadsheets get parked too.

How RecruiterClaw builds the presentation with you

All of the above is craft, and craft takes time you're not billing for. This is the part your Chief of Staff takes off your plate.

Drop a resume into Slack and it builds a candidate packet from it: the write-up ready for your read and your edits instead of a blank page at the end of the day. Hand it the job description and your candidates and it ranks them against the req, so the order you present in is defensible when the client asks why this one's on top. When the client is stuck, ask for a side-by-side candidate comparison and get the choice framed instead of the pile restated.

Interviews feed it too. It builds interview summaries from meeting transcripts, so the debrief your candidate gave you at lunch becomes a clean summary for the client instead of notes you reconstruct from memory that night. And it isn't picky about inputs: digital PDFs, scanned PDFs, Word docs, screenshots, a photo of a resume taken on your phone. OCR runs on-device, so nothing leaves your machine.

One boundary, on purpose: nothing reaches your client without you. Drafts come back in your own voice, learned from your real sent mail, and sending requires you to type an exact confirmation phrase. The presentation is yours. The assembly is what got delegated.

When the client pushes back

A submission that lands still draws fire: comp is high, the tenure looks short, they wanted degree-holders. Pushback is part of the presentation, and handling it is craft the Field Manual covers. Every install ships with it: a playbook built from 30+ years of desk experience, including objection handling on both sides of the desk. Your Chief of Staff coaches from it, adapted to your niche, before you pick up the phone. If you've built your own playbook over a career of these calls, upload it, and yours takes precedence.

Present the decision, not the person. Clients don't pay for descriptions. They pay for the confidence to act.