Mockup-First Outbound, Run Through Lemlist
There's a cold email only a web design agency can send: an image of the prospect's own homepage, redesigned. Not a description of what's wrong with their site, not a link to your portfolio — a picture of what their site could look like, sitting right there in the first email. It's spec work, the thing agencies are told never to give away, except it costs minutes instead of days once it's systematized. A business owner can ignore a pitch; ignoring a better version of their own homepage is much harder.
Lemlist is the one sending platform built around exactly this play. Its personalized images let you design a mockup layout once and have Lemlist swap in each prospect's brand per send, and its per-prospect landing pages give every recipient their own page — a before/after of their actual site — instead of a generic portfolio link. What Lemlist doesn't do is provision the sending infrastructure underneath: the secondary domains, mailboxes, and dedicated IPs the images actually travel on. That's where ColdRelay fits. This guide covers how design agencies wire the two together, and how to turn one mockup template into hundreds of per-prospect redesign previews that land in the inbox.
Why Run Lemlist on ColdRelay Infrastructure
Lemlist is a sending and personalization platform — it sends from whatever mailboxes you connect, fills its liquid syntax variables and personalized images per prospect, and tracks the results in campaign reports. It doesn't create the domains or mailboxes; that's the infrastructure layer's job.
The mockup play raises the stakes on that layer in a specific way: image-heavy cold email is less forgiving than plain text. An email carrying a redesign preview has more weight, more HTML, and more for a spam filter to frown at — so the sending reputation underneath needs to be spotless before the first image goes out. ColdRelay supplies that footing: mailboxes provision on isolated Azure tenants with dedicated IPs, with SPF, DKIM, and DMARC pre-configured, ready in about an hour, holding 95%+ inbox placement. When the infrastructure is doing its job, your mockup renders in the inbox instead of describing itself from a spam folder.
The pairing is additive, not competitive: ColdRelay is the infrastructure, Lemlist is the sender and personalization engine on top. You keep Lemlist's personalized images, landing pages, and multichannel sequences — you just run them on mailboxes built to land. One note on warmup: Lemlist offers lemwarm as an add-on, but ColdRelay mailboxes already warm continuously as part of their sending budget, so leave lemwarm off and let the infrastructure handle it.
Visit Lemlist →Connecting ColdRelay Mailboxes to Lemlist
Provision mailboxes on ColdRelay
Pick secondary domains adjacent to your agency brand — never the domain that hosts your portfolio. The mockup model is craft-paced rather than blast-paced, so most agencies start with 15-40 mailboxes; ColdRelay supports 100-150 mailboxes per domain, so the whole pool fits on one or two domains. 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
Export your mailbox credentials from the ColdRelay dashboard, then connect each mailbox in Lemlist via SMTP/IMAP under your email accounts settings. Lemlist will offer lemwarm for the new accounts — decline it. ColdRelay's warmup already runs continuously as part of each mailbox's 4 sends/day budget (2 outbound + 2 warmup), and double-warming the same mailbox from two systems muddies the sending pattern instead of strengthening it.
Set daily limits to match the ColdRelay budget
Set each mailbox's daily sending limit in Lemlist to 2 outbound emails per day, mirroring ColdRelay's per-mailbox budget of 4 sends/day total — 2 outbound + 2 warmup. The low per-mailbox ceiling suits this play: every send carries a piece of design work, so you want a steady drip of high-effort emails, not a firehose.
Build the mockup template with personalized images and liquid syntax
Design one redesign-preview layout — a browser-frame mockup with a hero section, clean navigation, and a visible CTA — and turn it into a Lemlist personalized image with dynamic layers: the prospect's logo, brand color, company name, and a screenshot crop slotted in per prospect from your CSV columns. Write the copy around it with liquid syntax variables, so the line above the image reads "here's what {{companyName}}'s homepage could look like" and falls back gracefully when a field is missing. One template, every prospect sees their own brand.
Attach per-prospect landing pages and a LinkedIn step, then launch
For the prospects worth more than a glance, enable Lemlist's landing pages so the image clicks through to a personal page: their current homepage on the left, your mockup on the right, and a booking link underneath. Add Lemlist's LinkedIn steps — a profile visit before the first email and a connection request after it — so your name is faintly familiar when the mockup arrives. Launch, and watch the campaign report for image clicks specifically; a prospect who clicked the mockup is warm even if they haven't replied yet.
The Mockup-First Lemlist Playbook
Show the redesign, don't describe it
Every other agency email tells the prospect something about their website. Yours shows them a different website. The mockup does the qualifying for you: prospects who don't care about design ignore it, and prospects who do can't help comparing it to what they have. Keep the copy almost silent — two lines and the image — because the moment you explain the mockup, you've turned a demonstration back into a pitch.
Template the layout once, let the brand swap do the personalizing
The trap in mockup outreach is redesigning every site by hand — that's a day per prospect and it never scales. Instead, design two or three strong layout templates per industry (one for service businesses, one for restaurants, one for professional firms) and let Lemlist's personalized image layers swap in each prospect's logo, colors, and name. The prospect experiences a bespoke redesign; your designer built it once. Reserve true hand-drawn mockups for the handful of dream clients where an hour of spec work is a fair bet.
Make the landing page do the before/after
An inline image gets three seconds; a landing page gets a scroll. Lemlist's per-prospect landing pages let every recipient click through to their own URL — current homepage beside the mockup, on mobile and desktop, with one booking link. That side-by-side is the whole sales argument rendered visually, and it works while you sleep. It also rescues the email itself: if an inbox clips or hides the inline image, the link still carries the full reveal.
Treat image clicks as your real intent signal
In mockup campaigns, the reply is not the first signal — the click is. Lemlist's campaign reports show who clicked through to their landing page, and a prospect who studied their own before/after and said nothing is a follow-up away from a conversation. Sequence accordingly: the second email goes only to clickers ("noticed you took a look — want the homepage version in your brand font?") while non-clickers get a different subject line and a re-cropped image. You're A/B testing the artwork, not just the words.
Typical Mockup-First Outbound Benchmarks (Lemlist + ColdRelay)
| Metric | Benchmark | Notes |
|---|---|---|
| Inbox placement rate | 95%+ | Dedicated IPs and isolated tenants matter more for image-heavy sends than plain text |
| Reply rate on mockup-led campaigns | 4-8% | A personalized redesign preview out-pulls text-only openers; local SMBs respond strongest |
| Landing page click-through rate | 8-15% | Clicks on the before/after page run well ahead of replies — the early intent signal |
| 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 mockup template is the long pole, 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, IPs, and isolated Azure tenants are included — and because the mockup model runs on modest send volume, most agencies sit comfortably in a small-to-mid pool.
Lemlist is billed separately on its own subscription for sequencing, personalized images, landing pages, multichannel steps, and campaign reports — priced per its current plans. You won't need the lemwarm add-on, since warmup is already part of every ColdRelay mailbox's budget.
The economics favor effort-per-send over send count: a small ColdRelay pool carries a campaign where every email contains design work, and Lemlist's subscription buys the personalization engine that makes per-prospect mockups a template operation instead of a production queue. One bill for sending capacity, one for the software that fills it with your best opener.
| 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
Does ColdRelay replace Lemlist?
No. They're complementary layers. Lemlist handles sequencing, personalized images, per-prospect landing pages, LinkedIn steps, and campaign reports. ColdRelay provides the underlying domains, mailboxes, and dedicated IPs that Lemlist sends from. You use them together — infrastructure underneath, sending and personalization software on top.
Should I use lemwarm with ColdRelay mailboxes?
No — and this is worth getting right. ColdRelay mailboxes warm continuously as part of their 4 sends/day budget (2 outbound + 2 warmup), with no waiting period before your first campaign. Running lemwarm on top of that double-warms the same mailbox from two systems, which distorts the sending pattern rather than improving it. Connect the mailboxes, decline lemwarm, set Lemlist's daily limit to 2 outbound, and launch.
Do image-heavy emails hurt deliverability?
They're less forgiving than plain text, which is exactly why the infrastructure layer matters more for this play. Keep the email light — one personalized image, two lines of copy, one link — and let ColdRelay handle the rest: dedicated IPs, isolated Azure tenants, pre-configured SPF/DKIM/DMARC, and a conservative 4 sends/day budget per mailbox (2 outbound + 2 warmup). That combination is how mockup campaigns hold 95%+ inbox placement despite carrying more weight than a text-only opener. The per-prospect landing page is your safety net too — if a client's inbox suppresses images, the link still delivers the full before/after.
Isn't sending a redesign mockup just giving away free spec work?
Hand-built, yes — which is why you don't hand-build it. The Lemlist version is a templated layout with the prospect's logo, colors, and name swapped in by personalized image layers: minutes of setup amortized across an entire campaign, not a day of design per prospect. The prospect sees a credible preview of their brand on a modern layout; you've spent design effort once. The mockup isn't the deliverable — it's the proof that the real engagement is worth a call, and the discovery conversation it opens is where the actual redesign gets scoped and sold.