Silence: the most expensive sound in executive search. Few things sting more, especially after all the time you spent carefully drafting that InMail.
And yet why does it happen so often? Because silence isn’t just an occasional miss but often a regular outcome when targeting elite talent.
The way I see it, it’s built right into the math.
Think about it: the best passive candidates aren’t even job hunting at all, but you wouldn’t know it by their inboxes. All are flooded daily with low-leverage pitches asking them to jump ship.
But you and I both know, these executives aren’t ghosting you because they lack ambition or they love their current seat so much. The simple truth is that it’s a perfectly rational filter against commodity communication.
I see it all the time. The vast majority of recruiter outreach reads like an administrative announcement. Nothing says “pass” like a flat “we have X vacancy.” If you want to get past that knee-jerk filter, your outreach to senior leaders has to read less like an alert and more like an insider flagging a move before the market catches on.
The anatomy of a message that gets deleted
Nearly every executive sourcing message I see these days follows the same beat structure, and just like most of us do with AI slop, executives have learned to spot it fast. So let me break it down for you.
1. The flattery open: “I came across your impressive background at [Company] and noticed your deep experience in cloud architecture…”
2. The generic ask: “We’re representing a high-growth, venture-backed SaaS company looking for a dynamic VP of Engineering…”
3. The high-friction close: “Do you have 30 minutes this week for a discovery call?”
I give this template an immediate fail. Like, what value is even being offered here? Because realistically, no serious candidate would consider, let alone commit, without clear justifiable evidence.
A senior executive protects their time like some engineers lock down private repositories against AI-scraping. Red flag jargon like “dynamic leader,” “fast-growing startup,” “vetted opportunity,” immediately signals to them that the sender hasn’t done a lick of the work to understand their actual role. So to someone managing a live roadmap or steering a corporate turnaround, that vocabulary isn’t a hook, it’s a straight up tell.
Job description vs lifecycle stage
Strong executive copy talks peer to peer. It speaks to the specific business lifecycle stage the candidate suits most.. Talent at the elite level tends to fall into 4 distinct operational modes:
- Builders (take infrastructure from zero to one, fast)
- Operators (run a mature, steady-state operation at scale)
- Transformation architects (rebuild something broken over a year or two)
- Stabilizers (stop the bleeding before it sinks the company)
What I’m saying here is that someone who takes infrastructure from zero to one thinks nothing like an operator running a thousand-person global team, and your message needs to convey that difference.
So that means, and I can’t stress this enough, your opening move can’t be a job description. Instead, it has to be a specific operational bottleneck your client is facing, anchored directly to the exact kind of problem this candidate has already solved. Get that right, and the message stops reading like a pitch. It starts reading like a case study written specifically for them.
Drafting InMail that won’t get ignored
1. Lead with market intelligence
In this context, flattery will get you nowhere, so cut the compliments entirely. Instead, open with an observation about a shift, a bottleneck, or a milestone specific to their world. The first sentence should prove you understand their world, not that you read their profile.
2. Frame the role as a puzzle, not a listing
You need to skip any mention of funding rounds or perks, which I know sounds counter-intuitive, but it works. Surprisingly, it’s actually way better to lead with the friction. Maybe it’s a legacy migration under regulatory pressure, or a fractured engineering culture that needs rebuilding, or whatever matches their exact track record. The match is the key here. You’re not offering a job change. You’re naming a problem only someone with only their specific history can solve by implying “hey, you know the solution to this problem has your name on it.”
3. Ask for permission, not effort
“Quick call” and “30-minute block” are two of the biggest drivers of ghosting, because demanding time before any trust exists always fails. But you can easily bypass resistance with a low-friction, text-first ask instead. Specifically, ask permission to provide a one-page brief or market report they can read on their own schedule.
Before and after
Here’s a hypothetical scenario for the same candidate, but with two very different emails.
The status quo (high ghost rate)
Subject: Career Opportunity: VP of Engineering Position
Hi David, I hope this message finds you well. I’ve been following your career at CloudScale and am incredibly impressed by your leadership background. I’m currently partnering with an elite, Series B fintech client that is expanding rapidly. They’re looking for a world-class VP of Engineering to manage their growing tech team and drive product innovation. Given your background in engineering architecture, I think you’d be a fantastic culture fit. Do you have some time for a brief introductory call this Tuesday or Thursday afternoon?
The Executive Writers Room approach (high engagement)
Subject: CloudScale’s multi-region migration / Legacy architecture friction
David, I read through your team’s engineering notes on the framework you built to resolve CloudScale’s multi-region latency issues last quarter. That kind of structural discipline is rare at scale-up speed.
I’m currently advising the board of a cross-border fintech platform at a similar inflection point, scaling from 40 to 120 engineers, with throughput degrading under strict regulatory constraints. They don’t need a manager. They need an architect who can scale a high-throughput transaction ledger without the platform buckling.
I’ve put together a two-page diagnostic on the platform’s current bottlenecks and the board’s 18-month roadmap. If you’re open to seeing how this maps to your CloudScale work, reply “send” and I’ll drop it in this thread.
Why the second message works
The Executive Writers Room version works because it respects the candidate’s time and status instead of asking for both upfront. Drop the live-call requirement, replace it with a text-based asset, and the barrier to engagement shrinks down to a single word: “send.” That word is the whole ask. And once they’ve said it, they’ve already engaged on their own terms, not yours.
I’ve watched enough of these campaigns to know the pattern by now. The firms that get replies treat executive outreach as corporate narrative like this and you can expect consistent engagement. Treat it as a vacancy notice and you can expect to be ghosted, every time. Because when it comes to passive candidates, the fix is never more volume, but messages that are actually worth reading.
Executive Writers Room builds high-performance executive recruitment copy for firms that place top leaders. DM me with samples of your current outreach assets, and I’ll provide you with a 1-page audit review of what you’ve got right now.