A Playbook for Recruiters Pitching Candidates to Clients and Hiring Managers

Why this playbook exists

Pretty much every recruiter has lived this moment: you submit a genuinely great candidate to a hiring manager, and the response is…a shrug. Not a rejection, exactly but not pure excitement, either. Enough hesitation to make them want to keep looking. 

A week later, someone with a weaker background gets an interview because the recruiter who submitted them told a better story.

This isn't a fluke. It's a pattern, and a measurable one, to boot. By and large, studies have shown that, when asked what they value most from a recruiting partner, clients’ answers often revolved around not simply “finding great people” but communication, at every stage.

In an anonymous survey (conducted in 2021, but arguably more relevant than ever), Comrise attempted to pin down which factors were most important to clients when partnering with recruiting firms. 

• 49.6% of clients said clear communication with delivery managers is the most important factor when choosing a recruiting firm at all — ahead of industry expertise (41%) and even ease of the submission process (9.3%)
• 55.6% of clients said excellent communication throughout the interview process is what they value most — more than speed-to-hire (31.1%) or candidate qualifications alone (13.2%)
• 58.2% of clients said a clear understanding of the candidate's feedback from the recruiter debrief is the most important thing once interviews wrap — more than double the group focused on compensation alignment (32.6%)

Read those three data points together and a clear theme emerges: Clients aren't only evaluating recruiters on who they find, but how clearly they can communicate why. The submission, the pitch, the debrief — every one of these is a communication moment, but most recruiters are leaving the “why” on the table.

That's what this playbook revolves around: Presenting candidates in a way that earns them the interview they deserve.

Part 1: The hidden reason great candidates don't get interviews

You probably know this better than anyone: Sometimes the problem isn't the candidate;t may simply be that the hiring manager isn’t able to see why the candidate is the right person for the role.

Great candidates get passed over every day — and often it isn't because they lack the experience, but because no one helped the hiring manager picture them succeeding in the seat. 

A resume lists what a person has done. It doesn't answer the question actually sitting in the hiring manager's head: Why should I interview this person, specifically, for this role, right now?

This gap matters more than most recruiters realize, because it's exactly where the data above lives. Hiring managers aren't rejecting submittals for lack of information — resumes have plenty of information. They're hesitating because no one has connected the dots for them. And when they don't immediately see the connection, they're likely to want to keep looking.

Not only does this cycle cost precious time and momentum for all involved, it can also have a damaging impact to your own credibility every time it happens. 

In short: Learning how to present candidates more effectively is beneficial to the candidate, yes. But it’s also beneficial to you and your reputation. 

The takeaway: Great recruiters don't simply present talent, they create confidence. And confidence is built through story. Which is a great segue into our next section… 

Part 2: Did you stop believing in storytelling too soon? 

If you’re reading this playbook, you probably already know the power of narrative, because nearly every recruiter has coached a candidate through the STAR method before an interview. 

Let’s review. STAR = Situation, Task, Action, Result.

The following comes from MIT’s guide to behavioral interviewing: 

Situation: Set the scene. Briefly explain the context of the event, where you were, and who was involved (keep it to 10-15 seconds).

Task: State the problem, challenge, or goal. What specifically needed to be accomplished?

Action: This is the core of your answer (about 60-70% of your time). Detail the exact steps you took, focusing on "I" rather than "we," and highlight your skills.

Result: Explain the outcome. Use quantifiable data, numbers, or positive feedback to prove your success (e.g., "Increased sales by 15%").

 We teach candidates to use the STAR method because it works. It's far more memorable than a list of responsibilities, and much more compelling because it demonstrates impact instead of expecting people to infer it. This framework provides so much more context than a bullet point ever could, while building the candidate's confidence walking into the room. 

So here's the question worth sitting with: If storytelling is what earns candidates their interviews — and what helps them excel in the interviews themselves — why do recruiters stop telling stories the moment they submit that candidate to the hiring manager?

The irony is that the exact moment recruiters most need to persuade someone — the submission — is the moment most recruiters default to the least persuasive format available…a resume summary. (What’s the opposite of a drumroll? Because we can just go ahead and insert that here.) 

This gap shows up directly in outbound and business development too. Recruiters who write cold outreach as generic “we've been in business 15 years, we specialize in X” pitches get ignored, because that framing answers a question the hiring manager never asked. 

The recruiters who instead frame their outreach the same way they'd coach a candidate — situation, action, measurable result, then the specific tie to the role — get response rates that dramatically outperform the generic ask. The mechanism is identical whether it's a submission or a cold email: specificity and story beat credentials and volume, every time.

→ Want more info on crafting compelling outreach? Check out this playbook all about outreach that’s rooted in copywriting best practices. 

Part 3: Resume vs. story — the same candidate, two very different outcomes

To demonstrate this point in action, let’s consider a real hiring scenario: a VP of Product at a growing SaaS company preparing for international expansion.

Presentation A — The simple resume summary:

The candidate managed a team of 12 product managers, led product strategy across three verticals, and implemented a new roadmap process.

Presentation B — The story-driven presentation:

The candidate walked into a product org with no shared roadmap process and three verticals pulling in different directions. From there, they built a unified strategy and prioritization framework that got engineering, sales, and leadership aligned for the first time — and did it while scaling the team from 4 to 12. That alignment work is exactly what this company will need heading into a multi-market expansion.

Ask a hiring manager to react to each, and the responses are likely to diverge sharply, right up until it's revealed that Presentation A and Presentation B describe — now you can drumroll— the exact same candidate.

In Presentation B, nothing was fabricated. Nothing was exaggerated. The recruiter didn't add any brand new information. They simply added meaning and story. 

This is the single most important mindset shift in this entire playbook: Presenting talent isn't a writing exercise, it's an interpretation exercise. The facts themselves don't change — what changes is whether someone did the work of connecting those facts to the hiring manager's actual problem.

Part 4: Why recruiters default to resume summaries (and why that decision costs interviews)

If storytelling so clearly outperforms resume summaries, why is the resume summary still the default? In practice, it typically comes down to a few reasons:

• “The resume speaks for itself.” It doesn't, and it hasn’t in years. Especially not to someone who didn't do the job themselves and doesn't know the context behind the bullet points.
• “I don't want to sound salesy.” There's a real difference between skeezy salesmanship and interpretation. Interpretation is factual; it just does the connecting work the hiring manager would otherwise have to do themselves. You’re not selling them something they don’t want, you’re just showcasing why this particular candidate meets their need. 
• “I'm busy.” Fair enough — and exactly why a repeatable framework (we’ll get to that in Part Five) matters more than raw effort or writing talent.

Here's the reframe that matters most: Hiring managers rarely reject candidates because they lack information, but they hesitate because the dots haven’t been connected. 

Resume summaries answer: What has this person done? 

Great presentations answer: Why should I interview this person?

Two quick side-by-sides, just to really make the difference concrete:

Resume language

Presentation language

“Managed a recruiting team.”

“Built a recruiting function that helped the company scale during rapid growth.” 

“Implemented a new ATS.” 

“Walked team through onboarding and usage training for a new ATS. Introduced a hiring workflow that gave managers better visibility and helped the company hire faster.” 

The recruiter's job isn't to repeat the resume. It's to interpret it through the lens of the role they’re filling. That interpretation then becomes the “why” that the client communication data above shows hiring managers are hungry for.

Part 5: The STORY framework

If you’ve been waiting for this framework ever since we first teased it in Part 4, it’s finally time. 

If the STAR method helps candidates tell compelling stories in the interview room, the STORY Framework helps recruiters earn their place in that room in the first place.

Situation: Set the stage. What was broken, missing, or at risk before this person arrived? This is what makes the eventual outcome mean something — impact only lands in contrast to a real starting point.

Transformation: Show what changed because they were there. This is the bridge between “situation” and “outcome” — it's the part of the story that resume bullets almost always skip, and it's usually where the most persuasive material is hiding.

Outcomes: Prove it with numbers, timelines, retained revenue, reduced attrition — whatever is measurable and true. Outcomes are what make the Transformation part of the story credible, instead of just a nice narrative.

Relevance: Connect the dots explicitly. Don't make the hiring manager do the work of mapping this candidate's past to their present problem — say it directly: “This is exactly the kind of gap you're trying to close with this hire.” This single step is where the earlier survey data becomes actionable: Hiring managers said, repeatedly, that they want clarity connected directly to their situation. This Relevance is that clarity, packaged up with a nice little bow on it.

Your recommendation: Here’s the fun part, where you tell the hiring manager what you actually think. A recruiter who has screened dozens of candidates for this exact role has a perspective worth stating plainly: “Of everyone I've spoken to, this is the person I'd want you to meet first, and here's why.” 

Part 6: Moving from a consultant to a trusted advisor

One benefit of using the STORY framework is that it allows you to use your understanding of your client’s mission to really make your candidates stand out from the crowd.

For example, a Certified B Corp is likely to value sustainability. An AI company may want people who embrace new technology, whereas a fast-growing startup may look for candidates who enjoy building things from scratch.

Asking candidates questions that reveal a passion for your client's mission, then highlighting those insights in your candidate submission, shows hiring managers why the candidate is qualified and why they're likely to thrive in the role.

It’s undeniable that telling a good STORY takes some extra time. Maybe it means that you submit four candidates for the role instead of ten.

But being more strategic about who you submit and showing your client that they’re getting only the best of the best… well, that, not only increases your submittal-to-interview ratio, it saves them time as well. 

Hiring managers don't just want information — they want judgment. They hired you for a reason! And when they see that their time is well spent reviewing your submissions, they trust you more.

→ Relatedly — positioning yourself as a talent advisor and strategic partner to your clients — not just a recruiter who is filling seats — is the single most important thing you can do to separate yourself from the pack. Check out our playbook on becoming a talent advisor here. 

Part 7: Putting STORY to work

STORY isn't only a framework for formal presentations; it’s an underlying logic that works whether the format is a written submittal, a cold outreach email, or a live executive readout.

In written outreach and submittals, the framework compresses naturally into a few tight sentences. 

Consider this real example built around a Community Marketing Manager search that had been open for 98 days:

In a previous role, the candidate's challenge was a stagnant organic presence and no authentic word-of-mouth marketing (Situation). They launched a customer advocacy program and a creator partnership initiative (Transformation), driving a 75% increase in engagement in six months and generating over 100 inbound leads and two referral-based deals (Outcomes), which directly maps to what this open role is trying to solve (Relevance). I think this person is worth 20 minutes of your time (Your Recommendation).

Notice what's absent: Agency tenure, years in business, generic credibility statements. None of that answers the hiring manager's actual question. Every sentence above is doing STORY's job.

In live and executive presentations, you can use the same framework, but give each of the five beats more room to breathe: a slide or two for Situation and Transformation, a data point or chart for Outcomes, a direct statement of Relevance to the specific role, and a closing recommendation delivered with real conviction rather than hedged language. The structure doesn't change, but the depth does.

A practical exercise for building this muscle: Before writing a single word of a presentation, ask what's missing rather than starting to write. Given a bare resume snippet — say, a Talent Acquisition Manager with a few scattered bullet points — the instinct is to start rewriting it into better language. Resist that. 

Instead, ask: What questions would I need answered before I could build a real STORY here? What was the actual situation? What changed, specifically? What's the number behind that? 

The moral of the story? Great storytellers don't invent better stories. They ask better questions.

Part 8: Why this matters beyond the individual pitch

The case for STORY isn't just about winning one interview. It connects to a structural problem in how recruiting and client collaboration function today.

Presenting talent well is fundamentally a communication act — and communication is the single biggest lever clients say they're evaluating recruiters on, at every stage of a search:

• When choosing a firm: Communication with delivery managers (49.6%)
• During the interview process: Communication throughout (55.6%)
• After interviews wrap: Clarity from the recruiter debrief (58.2%)

A well-built STORY presentation isn't just persuasive in the moment, it's the clearest, most repeatable way to deliver on all three of those expectations simultaneously. It's client communication and candidate advocacy, all happening within the same document.

You may be thinking (and rightfully so) that storytelling this good is hard to sustain manually, submission after submission, across a full desk. That's precisely the gap between doing this level of storytelling occasionally, when there's time, and doing it consistently, as a standard.

This is where the workflow around candidate presentation matters as much as the presentation itself. The same fragmentation that undermines great storytelling — scattered notes, inconsistent feedback, static PDF reports that go stale the moment they're sent — shows up in the client collaboration data above. Recruiters lose the thread when the system around them doesn't support the story they're trying to tell and makes it complicated to surface the insights that really make a difference. 

This is one of the reasons a Talent Intelligence Platform that puts an emphasis on both client presentations and easy access to candidate information is so critical. 

Picture a live, branded space where the STORY-driven presentation lives alongside real-time feedback, structured evaluation, and a single source of truth… rather than a PDF that's accurate the day it's sent and then immediately out of date the day after. 

When the presentation and the collaboration happen in the same place, the “why” a recruiter builds into a submission doesn't get lost in an email thread three days later.

Wrapping up: The five questions every candidate presentation should answer

If you want to get started putting this into practice today, start here. Every compelling candidate presentation — whether it's three sentences in an email or a ten-minute executive readout — should answer the same five questions:

1. What challenge did this person walk into?
2. What changed because they were there?
3. What measurable impact did they make?
4. Why are they the right fit for this role?
5. Why should I recommend them?

Great storytelling can absolutely be done manually, one submission at a time, by a recruiter with the discipline to ask better questions before writing. 

But the goal of this playbook is to make that quality of storytelling the standard, not the exception, so you achieve consistent, professional, and repeatable across every search, every desk, and every client relationship.