Your recruiting firm is good at placing people. What you're terrible at is getting companies to call you in the first place.
You're stuck in the same position most technical recruiting firms are in: you have great placement rates, solid relationships with your current clients, and a steady stream of candidates. But new client acquisition is painful. You're either waiting for referrals that come too slowly, or you're paying a sales team to pound the pavement and chase leads that go nowhere.
Cold email works for recruiting firms because it targets the exact person who needs you - the hiring manager or head of engineering who suddenly has open reqs and needs bodies fast. The problem is that most recruiting cold email is written by people who don't understand what actually motivates a hiring manager to respond.
Why Hiring Managers Actually Respond to Recruiting Cold Email
A hiring manager opens your email for one reason: they believe you can reduce their time-to-hire. Not because you have a great process. Not because you've "helped 100+ companies." Because you sound like you have access to qualified candidates right now.
The email needs to prove three things in the first three lines:
- You've filled this type of role recently (not hypothetically)
- You have candidates in your pipeline that match their specific needs
- This email is about them, not about what you do
Here's what works: specificity about recent placements, specificity about the role they're hiring for, and a reason to respond that isn't "let's grab coffee."
The Email Structure That Actually Converts
Most recruiting emails start with "I help companies find talent" or "We've been in recruiting for 15 years." Hiring managers don't care. They care if you can find them a Senior Backend Engineer who knows Go and has shipped production systems in the last two years.
Your opener needs to reference something specific about their recent hiring activity or a specific technical skill gap. This takes research, but it's the only thing that separates you from the 50 other recruiting emails in their inbox.
Here's the structure:
- Line 1-2: Reference a recent hire or confirmed open role + the specific position
- Line 3-4: One sentence about a relevant placement you made recently
- Line 5-6: One specific ask - do you have capacity to meet with someone you're interviewing this week?
- Line 7: Close with a specific date/time or a soft next step
The total email is 4-6 sentences. Nothing longer.
Here's a real example:
Hi [Name], Saw you hired [New CTO/VP Eng recently] - congrats. We just placed a Senior Full-Stack Engineer with [similar company] who had done exactly what you'd be looking for: 3+ years shipping React + Node in a fast-growth environment. We've got another candidate in the pipeline with the same background. Would it make sense to grab their resume and see if they're a fit for your open [role title]? Let me know. [Your name]
Notice what this does: it shows social proof (recent placement), it's specific about what you placed them for, and it gives a single, clear action - send a resume. No "let's connect" or "let me learn more about your needs." That comes later.
Finding the Right Companies to Target
Your list is everything. A mediocre email to the right person beats a great email to the wrong person every time.
For recruiting, target companies that are:
- Funded (Series A or later) - they have hiring budgets and hiring urgency
- Growing fast - hiring 20+ people in the last 6 months
- In your technical specialty - if you place DevOps engineers, target companies building infrastructure, not e-commerce platforms
- In industries where engineering talent is tight - fintech, crypto, deep tech, B2B SaaS
You find these on Crunchbase, Pitchbook, or LinkedIn by filtering for companies in your geographic area or industry with recent funding rounds. You're looking for companies that announced a Series B in the last 12 months - they're actively hiring and they have the budget to pay recruiting fees.
The research step matters more than your email template. Spend 60% of your time building the right list, 40% on the email itself.
The Response Loop That Actually Books Calls
Your first email is the hook. The follow-up sequence is what actually converts.
Here's what most recruiting firms do wrong: they follow up once, then move on. Or they follow up with another generic message about their firm.
Your follow-up should do one of three things:
- Add new information (we just placed someone similar at a company they'd recognize)
- Reference another open role at their company that you can fill
- Ask a direct question that requires an answer
Here's an example of a second email that works:
Hi [Name], Quick follow-up - we just placed another candidate with similar backend experience at [company in their network]. He's now filling their Principal Engineer role. If you're still actively hiring, I can introduce you to someone with his background. [Your name]
That's your second email. It's sent 4-5 days after the first. Then you stop for recruiting - they either respond or they don't. Hiring managers who have open reqs will respond. Those who don't won't, and no amount of follow-up will change that.
The Numbers You Should Expect
For recruiting cold email to the right list of technical companies:
- Open rate: 35-45% (recruiting subject lines get opened)
- Reply rate: 3-7% (the ones with open reqs will respond)
- Call rate: 40-60% of replies convert to an actual meeting
That means if you send 100 emails to the right list, you'll get 3-7 replies, and 1-4 actual calls. Each call has a 15-25% chance of turning into a placed candidate (depending on your placement quality).
The math works if you're consistent. Send 500 emails a month and you're looking at 15-35 calls, which should convert to 2-8 placements depending on your hit rate.
What Actually Kills Your Campaign
The biggest failure point for recruiting cold email isn't the email. It's one of these three things:
- Bad list quality: You're emailing companies that aren't hiring, or emailing the wrong person (recruiter instead of the hiring manager). This tanks your response rate to near-zero.
- Generic reference lines: You say "we've placed 100+ engineers" instead of "we placed a Senior DevOps engineer who knew Kubernetes and infrastructure-as-code at [Company]." One gets 8% response rates, the other gets 3%.
- Asking for a call too early: If your first email asks to "chat about their hiring needs," you'll get rejected. If it asks to "review a resume," you'll get yesses.
Fix the list. Fix the specificity. Fix the ask. Everything else is secondary.
When to Bring In Help
Building a cold email campaign for a technical recruiting firm is straightforward in theory - build a list, write an email, send it, track responses, follow up. But doing it well at scale requires infrastructure most firms don't have: a clean email sending setup that doesn't get flagged as spam, list building that actually targets the right hiring managers instead of just scraped CEO names, and a system for tracking which responses are real opportunities versus noise.
If you've got the capacity to do all of this yourself, do it. If you'd rather focus on what you're actually good at - recruiting and placing candidates - that's where working with a firm that handles the entire campaign becomes valuable. They manage the list, write and send the emails, handle the replies, and book the calls. You focus on converting those calls into placements.