Show the Product Wearing Their Data
SaaS cold email has a structural advantage no other industry gets: the thing you're selling has a screen. A prospect can't picture your consulting engagement or your logistics contract from an email — but they can absolutely picture your dashboard with their logo in the corner and their industry's metrics on the chart. The cold emails that book SaaS demos aren't the ones that describe the product; they're the ones that show it already working in the prospect's world.
Lemlist is built for exactly this kind of outreach. Its liquid syntax variables, personalized images, and per-prospect landing pages let you generate a tiny, tailored product moment for every contact in a campaign — and its multichannel sequences add LinkedIn touches around the email spine. What Lemlist doesn't provide is the sending infrastructure underneath. This guide covers how SaaS teams pair the two: ColdRelay supplying the secondary domains, mailboxes, and dedicated IPs, Lemlist turning each send into a miniature personalized demo.
Why Run Lemlist on ColdRelay Infrastructure
There's an irony in highly personalized outreach: the more effort you put into each email — custom images, dedicated landing pages, researched first lines — the more it costs you when that email lands in spam. A generic blast that misses the inbox wasted a template; a Lemlist campaign that misses the inbox wasted real creative work, per prospect. Personalization raises the stakes on deliverability rather than lowering them.
That's the case for putting real infrastructure under it. ColdRelay provisions dedicated mailboxes on isolated Azure tenants with dedicated IPs, DNS (SPF, DKIM, DMARC) pre-configured, ready in about an hour — built for 95%+ inbox placement so the personalized image actually gets seen. And because cold sends run from ColdRelay secondary domains, your primary @company.com domain — the one your trial emails, billing receipts, and password resets depend on — never touches outbound at all.
The layers are complementary, not competing: Lemlist is the sending and sequencing layer where the personalization happens; ColdRelay is the infrastructure layer that gets it delivered. One note on warmup: Lemlist ships with lemwarm, but ColdRelay mailboxes already warm continuously as part of their daily budget — leave lemwarm off for these accounts rather than warming the same mailbox twice.
Visit Lemlist →Connecting ColdRelay Mailboxes to Lemlist
Provision mailboxes on ColdRelay
Order mailboxes on secondary domains adjacent to your SaaS brand — ColdRelay supports 100-150 mailboxes per domain, and most teams running personalized campaigns start with 25-100 since per-prospect creative work caps volume anyway. 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
In Lemlist, add each ColdRelay mailbox as a sending account via SMTP/IMAP. When Lemlist offers to enable lemwarm on the account, decline it — ColdRelay's warmup already runs continuously as half of each mailbox's 4 sends/day budget (2 outbound + 2 warmup), and stacking lemwarm on top just double-warms the same mailbox.
Cap sending limits at 2 outbound emails per mailbox per day
Set each account's daily sending limit in Lemlist to 2 campaign emails. That mirrors the ColdRelay budget exactly — 4 sends/day total per mailbox, split 2 outbound + 2 warmup — and keeps Lemlist's scheduler from outrunning the infrastructure underneath it.
Build the personalization layer with liquid syntax, images, and landing pages
This is where the Lemlist pairing earns its keep. Enrich your prospect list with the fields the creative will use — company name, logo URL, industry, a relevant metric — then reference them with liquid syntax variables in the copy, drop the logo into a personalized image of your dashboard, and attach a per-prospect landing page hosting a short tailored walkthrough. Every prospect opens an email showing your product already running in their context.
Add LinkedIn steps and launch as a multichannel sequence
Wrap the email spine with Lemlist's multichannel steps — a LinkedIn profile visit before the first email, a connection request or post comment between follow-ups. SaaS deals are multi-threaded; a prospect who saw your face on LinkedIn yesterday treats today's personalized email as a second touch, not a first one. Launch, and watch open-to-click behavior in Lemlist's campaign reports.
The SaaS Lemlist Playbook
Make the personalized image a product screenshot, not a meme
Lemlist's image personalization is often used for novelty — names on coffee cups. SaaS teams have something better: render your actual dashboard with the prospect's logo in the workspace switcher and plausible numbers for their industry on the chart. The image stops being a gimmick and becomes the demo's first frame.
Treat the per-prospect landing page as a micro-demo, not a brochure
Point the email's CTA at a Lemlist landing page built for that prospect: their name in the headline, a 60-90 second walkthrough of the one workflow that matters to their role, and the calendar embed underneath. Clicking through should feel like the demo already started — the meeting just formalizes it.
Personalize one variable deeply instead of five shallowly
Liquid syntax makes it tempting to mail-merge every field you have. Resist it. A {{company}} token in a generic sentence reads as automation; one genuinely specific element — the right metric for their industry in the dashboard image, the right workflow in the landing page video — reads as effort. Pick the variable your product demo hinges on and spend the enrichment budget there.
Use LinkedIn steps to open a second thread, not echo the first
Lemlist's LinkedIn visit, connect, and comment steps work best when they add a new angle — comment on the prospect's recent post about the problem your product solves, rather than restating the email in a connection note. In multi-threaded SaaS deals, the email sells the workflow and the LinkedIn touch sells the person; together they survive the forward to a colleague that single-channel outreach rarely gets.
Typical SaaS Outbound Benchmarks (Lemlist + ColdRelay)
| Metric | Benchmark | Notes |
|---|---|---|
| Inbox placement rate | 95%+ | Dedicated IPs and isolated tenants — the prerequisite for personalized creative being seen at all |
| Reply rate with personalized images/pages | 4-8% | Product-in-their-context creative outperforms text-only sequences; depends on enrichment quality |
| Landing page click-through rate | 8-15% | Per-prospect pages with a tailored micro-demo; track in Lemlist campaign reports |
| Outbound capacity per mailbox | 2/day | 4 sends/day total per mailbox — 2 outbound + 2 warmup; lemwarm stays off |
| Time from provisioning to first campaign | Same day | ~60 minutes on ColdRelay; the creative setup in Lemlist is the longer half |
What It Costs: Lemlist + ColdRelay
Infrastructure is priced 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 personalized campaigns run leaner mailbox counts than volume blasts, most Lemlist pairings start small.
Lemlist is billed separately on its own per-seat plans, which cover the sequencing, image and landing page personalization, multichannel LinkedIn steps, and campaign reports.
The split mirrors where the work happens: Lemlist's cost tracks the seats doing creative personalization, ColdRelay's tracks the sending capacity underneath. High-personalization motions spend more per prospect on creative and less on raw mailbox volume — the stack prices accordingly.
| 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 a Lemlist alternative?
No — they sit at different layers and are used together. Lemlist is the sending and sequencing layer: liquid syntax personalization, images, landing pages, LinkedIn steps, and campaign reports. ColdRelay is the infrastructure layer underneath: the secondary domains, mailboxes, and dedicated IPs that Lemlist campaigns actually send from. Neither replaces the other.
Should I enable lemwarm on ColdRelay mailboxes?
No. ColdRelay mailboxes warm continuously as part of their daily budget — 4 sends/day total per mailbox, split 2 outbound + 2 warmup — so warmup is already handled at the infrastructure layer. Enabling lemwarm on top would warm the same mailbox twice and add volume the budget doesn't account for. Point Lemlist at outbound sending only.
Does heavy personalization change how many mailboxes I need?
Usually it lowers the count. At 2 outbound sends/day per mailbox (within the 4/day total alongside 2 warmup sends), 25 mailboxes carries 50 personalized sends/day — and most teams find enrichment and creative review, not sending capacity, is the bottleneck on a personalized-image motion. Start lean and scale mailboxes on ColdRelay, up to 100-150 per domain, as the creative pipeline speeds up.
Do personalized images and landing page links hurt deliverability?
Images and links carry more spam-filter weight than plain text, which is exactly why the infrastructure underneath matters more for Lemlist-style campaigns than for text-only ones. Sending from ColdRelay's dedicated IPs on isolated Azure tenants with pre-configured SPF, DKIM, and DMARC keeps placement at 95%+ — and it all happens on secondary domains, so even a heavy creative campaign never touches your product domain's reputation.