Candidate-Grade Personalization, Pointed at Hiring Managers
Recruiters are strange about personalization. When pitching a candidate to a client, every line is bespoke — the right title, the right comp expectation, the exact reason this person fits that team. But when the same recruiter prospects for new clients, the BD email goes generic: 'we specialize in placing top engineering talent.' The hiring manager deletes it because it could have been sent to anyone.
Lemlist exists to close exactly that gap. Its liquid variables, personalized images, and per-prospect landing pages let you build a BD email around the prospect's actual open roles — the req that's been sitting for six weeks, the comp band it's fighting in, the time-to-fill it's blowing past. ColdRelay is the layer underneath: the secondary domains, mailboxes, and dedicated IPs Lemlist sends from. This guide covers how recruiters wire the two together to make BD emails read like candidate submittals.
Why Run Lemlist on ColdRelay Infrastructure
Lemlist's whole pitch is depth over volume: liquid syntax that swaps copy per prospect, images rendered with the prospect's name and company, landing pages built per lead, and multichannel sequences that add LinkedIn touches between emails. None of that matters if the email never reaches the inbox — and Lemlist sends from whatever mailboxes you connect. The deliverability of those mailboxes is the infrastructure layer's job, not Lemlist's.
That's where ColdRelay sits. You provision dedicated mailboxes on isolated Azure tenants with dedicated IPs, DNS (SPF, DKIM, DMARC) pre-configured, live in about an hour — and warmup runs continuously as part of each mailbox's send budget, so there's no waiting period before the first campaign. Your agency's real domain, the one carrying submittals and offer letters, never touches cold outbound.
The two are complementary layers, not alternatives: ColdRelay supplies the domains, mailboxes, and IPs; Lemlist orchestrates the personalization and sequencing on top. Highly personalized email deserves infrastructure that actually lands it.
Visit Lemlist →Building a Role-Specific BD Engine in Lemlist
Provision mailboxes on ColdRelay
Personalization-heavy BD is a lower-volume, higher-depth motion, so most desks start at 10-30 mailboxes on one or two secondary domains adjacent to the agency brand — well under the 100-150 mailboxes a single domain supports. Everything provisions on isolated Azure tenants with dedicated IPs in about an hour, with SPF, DKIM, and DMARC already configured.
Connect the mailboxes in Lemlist and skip lemwarm
Add each ColdRelay mailbox under Lemlist's email accounts via SMTP/IMAP, and cap each at 2 outbound sends/day — mirroring ColdRelay's per-mailbox budget of 4 sends/day total, split 2 outbound + 2 warmup. Lemlist ships with lemwarm, but leave it off: ColdRelay's warmup already runs continuously inside that budget, and double-warming just burns sends and muddies the pattern.
Build the lead list with role-level custom variables
This step is the whole angle. For each hiring manager, import custom columns Lemlist can drop into liquid syntax: the exact open role title, how many days the req has been posted, the comp band the posting advertises, and the market median time-to-fill for that role in that metro. A line like 'your {{roleTitle}} req has been open {{daysOpen}} days — median time-to-fill for that seat in {{city}} is {{marketTTF}}' reads like you already work their desk.
Add liquid-conditional copy, personalized images, and a per-prospect landing page
Use Lemlist's liquid syntax to branch the pitch by situation — one variant when {{daysOpen}} exceeds the market median ('this search is already late'), another when the req is fresh ('here's who's available before it goes stale'). Layer a personalized image with the prospect's company name on your comp-band chart, and link a per-prospect landing page showing two or three anonymized candidate profiles matched to that exact role.
Sequence email and LinkedIn steps together, then read the campaign reports
Hiring managers live on LinkedIn, so build the Lemlist sequence multichannel: a profile visit before email one, a connection request after it, a comment or manual LinkedIn touch before the final email. Then use Lemlist's campaign reports to compare reply rates by liquid variant — if the 'req is running late' branch out-pulls the fresh-req branch, you've learned which pain to lead with.
The Role-Specific BD Playbook for Lemlist
Write the BD email like a candidate submittal
The skill recruiters already have — framing one person against one role with comp and fit evidence — is the skill that wins BD. Use liquid variables to aim that same specificity at the hiring manager's own open req instead of sending the generic agency intro every competitor sends.
Make the open req's age do the selling
A req that's been open 45 days against a 30-day market median is a quantified, undeniable pain. Lead with {{daysOpen}} versus {{marketTTF}} in step one — you're not claiming you're a great recruiter, you're showing the search is measurably behind and you noticed.
Let the landing page replace the attachment
Instead of attaching a PDF that triggers filters and dies unread, point each prospect to their Lemlist landing page: their role title at the top, your comp-band data for that seat, and anonymized profiles of two or three placeable candidates. The page visit itself is an intent signal you can prioritize in follow-up.
Use LinkedIn steps as the warm-up act, not the encore
A profile visit and a connection request before the first email means your name is faintly familiar when the role-specific opener lands. Recruiters already have credible LinkedIn presences — sequence the visit-connect-email order in Lemlist so the channel where hiring managers already live does the introduction.
Typical Role-Specific BD Benchmarks (Lemlist + ColdRelay)
| Metric | Benchmark | Notes |
|---|---|---|
| Inbox placement rate | 95%+ | Dedicated IPs and isolated tenants outperform shared provider pools |
| Reply rate, role-specific liquid openers | 5-9% | Referencing the prospect's own open req and its market data beats generic agency intros |
| LinkedIn connection acceptance before email | 25-40% | Recruiter profiles are credible on LinkedIn; the accepted connect lifts email reply rates |
| Outbound capacity per mailbox | 2/day | 4 sends/day total per mailbox — 2 outbound + 2 warmup |
| Time to first campaign | Same day | ~60 minutes to provision, plus variable enrichment and sequence setup in Lemlist |
What It Costs: Lemlist + ColdRelay
Billed per mailbox per month, with volume tiers that drop as you scale (see the table below). DNS, dedicated IPs, and isolated Azure tenants are included — and a personalization-first desk's 10-30 mailbox footprint keeps the infrastructure bill small.
Lemlist is a separate subscription covering liquid variables, personalized images and landing pages, multichannel sequences with LinkedIn steps, and campaign reports — priced per its current plans.
A depth-over-volume motion keeps both bills proportional: a Lemlist seat for the personalization machinery, a small ColdRelay pool for sending capacity. Scaling means enriching better data and adding a few mailboxes — not re-platforming.
| Mailboxes | ColdRelay price / mailbox / month |
|---|---|
| 1–199 | $1.00 |
| 200–999 | $0.85 |
| 1,000–4,999 | $0.70 |
| 5,000+ | $0.55 |
Each mailbox sends 4 emails per day — 2 outbound to prospects + 2 warmup. ColdRelay provisions mailboxes on isolated Azure tenants with dedicated IPs; Lemlist handles the sending, sequencing, and inbox rotation on top.
Frequently Asked Questions
Is ColdRelay an alternative to Lemlist?
No — they're complementary layers of one stack. Lemlist is the sending and personalization software: liquid variables, personalized images and landing pages, LinkedIn steps, campaign reports. ColdRelay is the infrastructure underneath: the secondary domains, mailboxes, and dedicated IPs Lemlist sends from. Recruiters use both together.
Should I run lemwarm on ColdRelay mailboxes?
No. ColdRelay mailboxes warm continuously as part of their send budget — 2 warmup sends/day within the 4/day total per mailbox (2 outbound + 2 warmup). Running lemwarm on top double-warms the same mailbox, wastes capacity, and adds nothing. Connect the mailboxes for outbound only and leave warmup to ColdRelay.
Where does the role data for the liquid variables come from?
From the prospect's own job postings plus your desk's market knowledge. Pull the open role title and posting date from job boards or the company's careers page, then add the comp band and time-to-fill medians you already track for the niches you place in. Import them as custom columns in Lemlist and reference them with liquid syntax — the enrichment effort is exactly why these emails out-pull generic BD.
How many mailboxes does a personalization-heavy desk need?
Fewer than a volume desk. At 2 outbound sends/day per mailbox (4/day total including 2 warmup sends), 15 mailboxes is 30 deeply personalized emails a day — and since each lead also gets LinkedIn touches that don't consume email capacity, total prospect coverage runs higher than the send count suggests. Most desks start at 10-30 mailboxes, far below the 100-150 one domain supports.