The Coverage-Gap Opener, Run Through Lemlist
Ask any producer which cold emails get answered and you'll hear the same thing: the one where the broker clearly noticed something. Not 'we work with businesses like yours' — but 'most electrical contractors at your crew size carry a GL aggregate that stopped matching their contract requirements two growth spurts ago.' The observation is the offer. A business owner who reads a sentence that's true about their specific operation assumes the rest of the email is worth reading too.
Lemlist is the sending platform built around that kind of opener: liquid syntax variables that assemble a different first paragraph for every prospect from your list's data fields, personalized images and per-prospect landing pages that extend the observation past the inbox, and multichannel sequences with LinkedIn steps that turn a good email into a recognizable local advisor. ColdRelay is the infrastructure underneath — the secondary domains, mailboxes, and dedicated IPs that Lemlist actually sends from, so the agency domain carrying binders, certificates, and claims correspondence never appears in a cold campaign. This guide covers how to wire the two into a personalization-first motion.
Why Run Lemlist on ColdRelay Infrastructure
Lemlist's edge is depth per send, not raw volume. Liquid syntax lets one campaign render a contractor-liability opener for the roofing company, a workers-comp-rate opener for the restaurant group, and a professional-liability opener for the accounting firm — each pulled from custom fields on the lead, with conditional fallbacks so no prospect ever sees a broken variable. Personalized images and landing pages carry that same specificity into a one-page risk snapshot the prospect can click into. What Lemlist doesn't do is provision the mailboxes any of it sends from; it sends through whatever accounts you connect, and their deliverability is the infrastructure layer's job.
That's where ColdRelay fits. You provision dedicated mailboxes on isolated Azure tenants with dedicated IPs, with SPF, DKIM, and DMARC pre-configured, ready in about an hour — and there's no upfront warmup period before sending, because warmup runs continuously as part of each mailbox's 4 sends/day budget (2 outbound + 2 warmup). For a motion where every email took real research to build, that matters doubly: a coverage-gap opener that lands in spam wasted both the send and the homework. ColdRelay's 95%+ inbox placement is what makes the personalization effort pay.
The pairing is additive, not competitive: ColdRelay is the infrastructure layer — domains, mailboxes, dedicated IPs — and Lemlist is the sending and sequencing layer on top. You keep Lemlist's liquid variables, personalized assets, and LinkedIn steps; you just point them at mailboxes built to land.
Visit Lemlist →Connecting ColdRelay Mailboxes to Lemlist
Provision mailboxes on ColdRelay
Personalization-first volume is deliberate, so size the pool to your research capacity rather than to a blast target. ColdRelay supports 100-150 mailboxes per domain on isolated Azure tenants with dedicated IPs; brokerages running this motion typically start with 20-60 mailboxes on one secondary domain — never the agency domain. Everything provisions in about an hour with SPF, DKIM, and DMARC already configured.
Connect the mailboxes in Lemlist
In Lemlist, go to Settings → Email Accounts and connect each ColdRelay mailbox via SMTP/IMAP using the credentials from the ColdRelay dashboard export. Each mailbox connects as its own sending identity so Lemlist can rotate campaign sends across the pool.
Set sending limits to 2 per day and skip the second warmup
Cap each connected account at 2 outbound emails per day in its Lemlist sending settings, mirroring ColdRelay's per-mailbox budget — 4 sends/day total, split 2 outbound + 2 warmup. Lemlist's lemwarm exists, but ColdRelay already runs warmup continuously inside that budget; leave lemwarm off rather than double-warming the same accounts.
Build the risk-profile fields and liquid-variable opener
Before any copy, structure the lead list: add custom fields for industry risk profile (e.g., 'GL aggregate gaps common at this crew size', 'workers comp mod pressure', 'liquor liability exposure'), growth stage, and the specific observation your research surfaced. Then write the campaign's first paragraph in liquid syntax so each prospect's opener renders from their own fields — with a conditional fallback line for any record missing data, so nothing ships half-merged.
Add the landing page and LinkedIn steps, then launch
Attach a personalized image or per-prospect landing page as the second touch — a one-page 'risk snapshot' that restates the coverage-gap observation with the prospect's company name on it reads like a prepared advisor, not a mail merge. Then add Lemlist's LinkedIn steps (profile visit, connection request, comment) around the email touches so the producer's face becomes familiar before the ask. Enroll the list, monitor campaign reports, and route replies to the producer who did the research.
The Insurance Broker Lemlist Playbook
Open with what you noticed, not who you are
The first line should be an observation only a broker who looked at their business could make: the contractor whose bonding capacity probably lags their bid sizes, the restaurant group whose workers comp class codes likely drifted as they added catering. Build these as liquid-variable templates keyed to industry-risk fields, so one campaign renders a genuinely different opener per segment. The agency introduction can wait until the prospect already believes you see their risk.
Stage the observation by depth, not by calendar
Structure the sequence as a deepening of the same insight rather than a series of nudges: email one names the gap, the personalized landing page in email two shows it laid out as a one-page snapshot, email three adds the so-what ('here's what that gap costs firms your size at claim time'). Each step earns the next because the specificity compounds — a 'just bumping this' follow-up would squander the opener that got the first open.
Use LinkedIn steps to become the local advisor, not just a sender
Commercial insurance is bought from someone the owner feels they half-know. Interleave Lemlist's LinkedIn steps — a profile visit before email one, a connection request after the landing-page touch, a comment on the prospect's company post where one exists — so by the time the call ask arrives, the producer is a recognizable local face with a license, not a stranger's signature block. The channel mix isn't about more touches; it's about turning specificity into familiarity.
Keep the observation factual; keep the quote off the page
A coverage-gap opener walks closer to the compliance line than generic copy, so discipline the language: describe what's typical for their industry and size ('most firms at your headcount carry X; contracts increasingly require Y'), never assert what their policy contains or promise savings. The personalized landing page states the pattern, the licensed conversation diagnoses their actual program — that's the handoff, and it's also what keeps the email defensible.
Typical Insurance Outbound Benchmarks (Lemlist + ColdRelay)
| Metric | Benchmark | Notes |
|---|---|---|
| Inbox placement rate | 95%+ | Dedicated IPs and isolated tenants outperform shared Google/Microsoft pools |
| Reply rate with a risk-specific opener | 4-7% | Liquid-variable openers built on industry risk fields outperform generic broker intros; the research is the lever |
| Landing-page click-through | 8-15% | Per-prospect 'risk snapshot' pages with the company's name and gap laid out; clicks are a strong producer-call trigger |
| 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 on ColdRelay; the longer pole is building the risk-profile fields, not the infrastructure |
What It Costs: Lemlist + ColdRelay
You pay per mailbox per month for the infrastructure, with volume tiers that drop as you scale (see the table below). DNS, dedicated IPs, and isolated Azure tenants are included — and since ColdRelay supports 100-150 mailboxes per domain, even a scaled-up personalization operation fits comfortably on one or two secondary domains.
Lemlist is billed separately on its own subscription for liquid variables, personalized images and landing pages, multichannel sequences with LinkedIn steps, and campaign reports — priced per its current plans.
The economics fit a depth-over-volume motion: because each send carries real research, you run fewer mailboxes than a blast operation would — and the infrastructure bill scales with that smaller pool at per-mailbox rates that drop in higher tiers. One bill for mailboxes built to land, one for the personalization engine on top.
| 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, not competitors. Lemlist is the sending and sequencing layer: liquid-variable personalization, personalized images and landing pages, LinkedIn steps, and campaign reports. ColdRelay is the infrastructure layer underneath — the secondary domains, mailboxes, and dedicated IPs that Lemlist sends from. The coverage-gap motion uses both together.
Should we run lemwarm on ColdRelay mailboxes?
No. ColdRelay mailboxes warm continuously as part of their built-in budget — each mailbox sends 4 emails/day total, 2 outbound + 2 warmup — so there's no upfront warmup period and no need for a second warmup layer. Leave lemwarm off for ColdRelay accounts and let Lemlist handle outbound sending only; stacking two warmup systems on one mailbox muddies the sending pattern without improving placement.
Where does the coverage-gap data for the liquid variables come from?
From structuring research you mostly already do. Industry plus headcount plus state implies a risk profile — contractors at a given crew size tend toward GL aggregate and bonding gaps, restaurants toward workers comp class-code drift and liquor liability, professional firms toward E&O limits that lag revenue. Encode those patterns as custom fields on each lead (risk category, growth stage, the specific observation), and Lemlist's liquid syntax assembles the opener per prospect — with conditional fallbacks so a record with thin data still gets a clean, generic-safe first line.
Is it compliant to tell a prospect their coverage has a gap?
Frame it as a pattern, not a diagnosis. You can't know what their policy contains, so the copy should describe what's typical — 'most firms your size in your trade carry limits that predate today's contract requirements' — and invite a licensed review rather than asserting a deficiency or promising savings. Keep premium figures and savings percentages out of cold copy entirely, on the email and on the personalized landing page alike; the producer's licensed conversation is where the actual program gets assessed.