Sell the Market Read, Not the Agency
Every HR leader with open reqs already gets agency pitches. What they almost never get is intelligence: what candidates for their exact roles are actually being paid this quarter, how thin the local pool really is, and how long a req like theirs typically sits open. A staffing firm carries that knowledge as a byproduct of doing the work — and a first email that leads with it reads like a market briefing, not a solicitation.
Lemlist is the tool that makes that briefing scalable. Its liquid syntax variables assemble a different market snapshot for every prospect, its personalized images and per-prospect landing pages turn the snapshot into something visual, and its multichannel sequences deliver it across email and LinkedIn. ColdRelay is the layer underneath: the secondary domains, mailboxes, and dedicated IPs Lemlist sends from. This guide covers building an intelligence-led BD motion on that stack.
Why Run Lemlist on ColdRelay Infrastructure
Lemlist's edge is depth of personalization rather than raw volume: liquid syntax variables with conditionals and fallbacks, dynamic images rendered per prospect, individual landing pages, and sequences that interleave email with LinkedIn visit, connect, and comment steps. For a staffing firm, that's exactly the toolkit a market-snapshot opener needs — the comp figure, the time-to-fill stat, and the candidate-availability line all change per prospect, and liquid variables are how one campaign carries thousands of different briefings.
What Lemlist doesn't supply is the sending infrastructure itself. That's ColdRelay: dedicated mailboxes on isolated Azure tenants with dedicated IPs, DNS (SPF, DKIM, DMARC) pre-configured, live in about an hour, with no warmup period before sending. ColdRelay supports 100-150 mailboxes per domain, and each mailbox runs a budget of 4 sends/day total — 2 outbound + 2 warmup, with warmup running continuously on ColdRelay's side. Lemlist's own lemwarm exists, but you should leave it off here; double-warming the same mailbox adds risk, not reputation.
The two are complementary layers, not competitors: Lemlist composes and orchestrates the briefing, ColdRelay makes sure it reaches the inbox. An email built on real market data deserves better than a spam folder.
Visit Lemlist →Building a Market-Snapshot BD Campaign in Lemlist on ColdRelay Mailboxes
Provision ColdRelay mailboxes on secondary domains
Order mailboxes on domains adjacent to your firm's brand — never the primary domain that carries contracts and submittals. They provision on isolated Azure tenants with dedicated IPs in about an hour, DNS (SPF, DKIM, DMARC) pre-configured, with no warmup period before sending. Intelligence-led lists are researched rather than huge, so a modest pool goes far — and ColdRelay supports 100-150 mailboxes per domain when you grow into more verticals.
Connect the mailboxes in Lemlist and switch lemwarm off
Add each ColdRelay mailbox as a sending account in Lemlist via SMTP/IMAP and cap it at 2 outbound emails per day. That mirrors ColdRelay's per-mailbox budget of 4 sends/day total — 2 outbound + 2 warmup. Warmup already runs continuously on ColdRelay's side as part of that budget, so leave lemwarm disabled rather than warming the same mailbox twice.
Build the snapshot dataset as custom variables
For each prospect, your enriched CSV carries the intelligence: the roles they have open (roleFamily, openCount), and your market read for those roles in their metro — currentCompRange, compTrend, typicalTimeToFill, and a one-line candidateAvailability note. Comp surveys, public wage data, and above all your own placement records feed these columns. Lemlist's liquid syntax renders them per prospect, and fallbacks like {{compTrend | "moving fast in your region"}} keep the email clean when a column is blank.
Write the sequence around the briefing, then make it visual
Step one leads with the snapshot in prose: the roles they're hiring, what the market is doing to those roles, and what that means for their timeline. Step two attaches a Lemlist personalized image — a small chart card with the prospect's metro, role family, and comp range rendered in — and links a per-prospect Lemlist landing page that works as a one-screen market report with a booking CTA. The pitch is implicit: the firm that already knows your market is the firm that fills your seats.
Add LinkedIn steps and read campaign reports by variable
Wrap the emails in Lemlist's multichannel steps: a LinkedIn profile visit before the first email so your name is vaguely familiar, a connect or comment step after it for non-responders. Then use Lemlist's campaign reports to compare reply rates across role families and metros — when warehouse ops leaders in one region reply at twice the rate, that's your cue to deepen the dataset there.
The Market-Intelligence BD Playbook for Lemlist
Lead with what they can't see from inside
The prospect already knows they have eight open roles; telling them so is table stakes. What they can't see is the outside view — that comp for those roles in their metro moved 7% in two quarters, or that reqs at their posted rate are averaging seven weeks to fill. Build the liquid-variable opener around the market fact, not the posting, and the email becomes information they'd pay for rather than a pitch they'll delete.
Let liquid fallbacks protect your credibility
One wrong number undoes the entire positioning — a firm claiming market mastery can't misquote the market. Use Lemlist's liquid conditionals so a precise stat only renders when you trust the data, and fall back to a softer role-family-level line when you don't. A vaguer true sentence always beats a specific wrong one in an intelligence-led email.
Make the landing page the leave-behind
A briefing earns a forward, and forwards are how BD emails reach the actual decision-maker. Build the per-prospect Lemlist landing page as a one-screen snapshot — their roles, your comp and time-to-fill read, three anonymized placements you made in that market — so whoever it gets forwarded to sees a market report with your firm's name on it, not a stripped-out email thread.
Mine your own placements before you buy data
Every fill your desk completed is a proprietary data point — actual accepted comp, actual days-to-fill, actual fall-off — that no competitor and no public dataset has. Pipe those into your snapshot variables first and use external comp data only to fill gaps. The line 'we placed nine of these roles in your metro in the last two quarters' is the one claim a pure software stack can never fake.
Typical Intelligence-Led BD Benchmarks (Lemlist + ColdRelay)
| Metric | Benchmark | Notes |
|---|---|---|
| Inbox placement rate | 95%+ | Dedicated IPs and isolated tenants — a market briefing that lands in spam briefs no one |
| Reply rate on market-snapshot openers | 6-10% | A specific comp or time-to-fill line outperforms generic agency intros several times over |
| Landing page open-to-visit rate | 15-25% | Per-prospect Lemlist pages framed as a one-screen market report for their roles |
| 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 mailboxes; the snapshot dataset is the real prep work |
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 because intelligence-led lists are curated rather than sprayed, most firms start with a compact pool and add mailboxes as new verticals get their own snapshot datasets.
Lemlist is a separate subscription covering liquid variables, personalized images and landing pages, multichannel sequences, and campaign reports — priced per its current plans.
Lemlist's cost buys the personalization engine; ColdRelay's buys deliverable capacity. The expensive ingredient in this motion is actually neither — it's the market data your own placements generate for free — so the software stack stays lean while the moat compounds.
| 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, per-prospect landing pages, multichannel sequences, and reports. ColdRelay is the infrastructure underneath: secondary domains, mailboxes, and dedicated IPs on isolated Azure tenants that Lemlist sends from. Staffing firms run both together — Lemlist builds the briefing, ColdRelay gets it into the inbox.
Should we run lemwarm on our ColdRelay mailboxes?
No. ColdRelay mailboxes are warmed continuously on ColdRelay's side as part of each mailbox's 4 sends/day budget — 2 outbound + 2 warmup — with no warmup period needed before sending. Running lemwarm on top of that double-warms the same mailbox, which wastes budget and adds pattern risk. Connect the mailboxes for outbound only and leave lemwarm off.
Where does the market data behind the liquid variables come from?
Three places, in order of value: your own ATS and placement history (actual accepted comp and days-to-fill for roles you've filled — data no one else has), public wage and labor statistics for the metros you serve, and commercial comp benchmarks where you have gaps. You assemble these into per-prospect columns in your contact CSV, and Lemlist's liquid syntax renders them — with fallbacks covering any prospect where a column is empty.
How many mailboxes does an intelligence-led campaign need?
Less than almost any other staffing motion, because the constraint is research, not sending capacity. A desk producing well-researched snapshots for 150-300 prospects a month is comfortably served by 15-30 mailboxes at 2 outbound sends/day each (4/day total with 2 warmup), including follow-up steps. That fits on a single secondary domain — ColdRelay supports 100-150 mailboxes per domain — with plenty of headroom as more verticals come online.