Rep-Quality Personalization at Sequence Speed
Every SDR team eventually hits the same fork: emails the reps write by hand get replies but cap out at a couple dozen a day, while templated sequences hit volume but read like templated sequences. Teams pick Lemlist because it attacks that trade-off directly — liquid syntax variables that branch copy per prospect, personalized images that drop a prospect's name or logo into a screenshot, and multichannel sequences that mirror how a good rep actually works an account.
But personalization only pays off if the email arrives. A line of copy that took real research effort lands in spam exactly as fast as a lazy blast when the mailbox underneath has a burned reputation. This guide covers the full quality-at-volume stack: ColdRelay supplies the sending infrastructure — secondary domains, dedicated mailboxes, dedicated IPs — and Lemlist runs the personalization machinery on top, so what your SDRs send looks hand-built and actually gets seen.
Why Personalization-Heavy Sending Needs Its Own Infrastructure
There's a quiet irony in how teams adopt Lemlist: they invest hours building liquid variable logic, custom image templates, and per-prospect landing pages — then send all of it from corporate mailboxes or bargain-bin accounts where deliverability was never anyone's job. The craft survives; the delivery doesn't. When you're sending fewer, better emails, every email that lands in spam wastes more invested effort than it would in a volume-first motion. Personalization raises the cost of a missed inbox.
ColdRelay is the layer that protects that investment. You provision dedicated mailboxes on isolated Azure tenants with dedicated IPs, DNS (SPF, DKIM, DMARC) pre-configured, ready in about an hour — and there's no warmup waiting period, because warmup runs continuously as part of each mailbox's standard budget of 4 emails/day total, split 2 outbound + 2 warmup. With 95%+ inbox placement, the personalization your team built actually reaches the person it was built for.
The two products are complementary layers, not rivals: ColdRelay is the infrastructure underneath — domains, mailboxes, dedicated IPs — and Lemlist is the sending and sequencing layer on top, deciding what each prospect sees and across which channels.
Visit Lemlist →Connecting ColdRelay Mailboxes to Lemlist
Provision the sending pool on ColdRelay
Pick a secondary domain or two adjacent to your brand and provision the pool — ColdRelay supports 100-150 mailboxes per domain, and personalization-led SDR teams typically start smaller than volume shops, around 20-60 mailboxes, because each send carries more research. Everything lands on isolated Azure tenants with dedicated IPs, SPF, DKIM, and DMARC pre-configured, ready in about an hour.
Connect the mailboxes in Lemlist and set limits to 2
Add each ColdRelay mailbox as a sending account in Lemlist's email settings, then set each account's daily sending limit to 2 outbound emails. That mirrors ColdRelay's per-mailbox budget — 4 emails/day total, 2 outbound + 2 warmup. Skip lemwarm entirely: warmup is already running continuously on ColdRelay's side, and double-warming just spends budget twice on the same job.
Build the variable layer before the campaign
Lemlist's liquid syntax is where the quality-at-volume math happens — conditional lines like a different opener per industry, a fallback when a custom field is empty, a competitor mention only when that field is populated. Define the custom variables your copy will branch on (trigger event, tool in their stack, a one-line observation), and make those columns mandatory in your lead list template before any campaign is created.
Add personalized images and landing pages to the high-value tier
Use Lemlist's image personalization to drop the prospect's name, company, or logo into a screenshot or mock-up, and attach per-prospect landing pages for your highest-value segment. These assets are built once as templates and rendered per prospect automatically — the hand-built look at sequence speed. Reserve them for the accounts where a meeting moves real pipeline; plain liquid-variable copy carries the rest.
Layer LinkedIn steps and launch
Build the sequence the way your best rep already works: a LinkedIn profile visit before the first email, a connection request after it, a comment or message step between follow-ups. Lemlist's multichannel steps draw nothing from the mailbox budget, so the email sends stay at 2/day per mailbox while total touches per prospect climb. Launch the same day the infrastructure was provisioned and read results in Lemlist's campaign reports.
The Quality-at-Volume Lemlist Playbook
Treat variable data quality as a team workflow, not a rep habit
A liquid variable is only as good as the column behind it — one rep's half-filled CSV turns {{firstName}} elegance into 'Hi ,' embarrassment at scale. Make list prep a gated step: a shared lead-list template with required personalization columns, a named owner who spot-checks 10 rows before any import, and a standing rule that a campaign never launches with empty mandatory fields. Lemlist will render whatever you feed it; the team's job is making sure what's fed is true.
Write one email with ten branches, not ten emails
The leverage move with liquid syntax is a single master email whose opener, proof point, and CTA branch on prospect attributes — industry, tool stack, trigger event. One SDR maintains one asset that reads differently to every segment, instead of ten templates drifting out of date independently. Review the branch logic monthly in Lemlist's campaign reports: branches that underperform get rewritten or collapsed, and the master email keeps compounding.
Match personalization depth to account value, explicitly
With a fixed 2-outbound-per-mailbox budget (4/day total with the 2 warmup sends), the question isn't how many emails to send — it's how much craft each send deserves. Tier it: top accounts get personalized images, a custom landing page, and a researched first line; mid-tier gets full liquid-variable branching; the long tail gets clean variables and a sharp offer. Write the tiers down so reps spend research minutes where pipeline justifies them.
Let LinkedIn steps do the warm-up a first email can't
A profile visit and a connection request before the first email means the prospect has seen the rep's face and title before the send lands — the cold email arrives semi-warm, which is exactly how top reps have always sequenced by hand. Because Lemlist's LinkedIn steps cost nothing against the mailbox budget, front-load them: visit on day one, connect on day two, first email on day three. The email budget stays untouched while reply rates move.
Typical Personalization-Led SDR Benchmarks (Lemlist + ColdRelay)
| Metric | Benchmark | Notes |
|---|---|---|
| Inbox placement rate | 95%+ | Isolated Azure tenants with dedicated IPs — the floor that makes per-prospect personalization effort worth spending |
| Reply rate on personalized sequences | 4-8% | Liquid-variable branching plus LinkedIn pre-touches trend well above template-blast averages; image personalization lifts the top tier further |
| Outbound capacity per mailbox | 2/day | 4 sends/day total per mailbox — 2 outbound + 2 warmup, with warmup running continuously on ColdRelay |
| Touches per prospect per sequence | 7-10 | 2-4 email steps from the mailbox budget plus LinkedIn visit, connect, and comment steps that draw nothing from it |
| Lead-list prep time per 100 prospects | 1-2 hours | Filling and spot-checking the personalization columns liquid variables depend on — the real cost of quality at volume, and where it's paid |
What It Costs: Lemlist + ColdRelay
Infrastructure is billed per mailbox per month, with volume tiers that drop as you scale (see the table below). Dedicated IPs, isolated Azure tenants, and pre-configured DNS are included — and because personalization-led teams send fewer, better emails, the pool they pay for tends to be leaner than a volume shop's.
Lemlist is billed separately on its own per-seat plans, covering liquid variables, image and landing-page personalization, multichannel sequences with LinkedIn steps, and campaign reports.
The costs track different things: Lemlist scales with the reps doing the personalizing, ColdRelay scales with the sending capacity behind them. A team can deepen personalization without touching the infrastructure bill — and add mailboxes on ColdRelay without adding a Lemlist seat.
| 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 the same stack and teams run both together. Lemlist is the sending and sequencing layer: liquid variables, personalized images and landing pages, multichannel sequences, and campaign reports. ColdRelay is the infrastructure layer underneath: the secondary domains, mailboxes, and dedicated IPs that Lemlist's campaigns actually send from.
Should we run lemwarm on ColdRelay mailboxes?
No. ColdRelay mailboxes warm continuously as part of their standard budget — each mailbox sends 4 emails/day total, 2 outbound + 2 warmup — so there's no warmup period to schedule and nothing to enable in Lemlist. Leave lemwarm off, keep each account's daily limit at 2 outbound sends, and the budget does the rest. Double-warming spends the same capacity twice without improving anything.
If we're personalizing every email, do we still need dedicated sending infrastructure?
More than a volume sender does, arguably. Each personalized email carries minutes of research and template work, so every send that lands in spam wastes more invested effort than a generic blast would. Sending hand-crafted copy from a corporate domain or a reputation-pooled account puts the most expensive emails on the least reliable rails — ColdRelay's isolated Azure tenants with dedicated IPs and 95%+ inbox placement are what make the per-prospect effort pay back.
How many mailboxes does a personalization-led SDR team need?
Fewer than a volume motion, usually. Work backwards from how many researched, variable-complete prospects the team can prepare per day — if 3 SDRs can prep 60 quality prospects daily, that's 60 sends/day, which at 2 outbound per mailbox (4/day total with warmup) is a 30-mailbox pool. With 100-150 mailboxes supported per domain, that fits on a single secondary domain, and you scale the pool when list-prep throughput — not ambition — grows.