Freelance Outbound, Run Through Lemlist
There's one cold email a freelancer can send that almost nothing else competes with: the one where the work is already started. A designer who sends a prospect an image of their own homepage, reimagined. A copywriter who rewrites the prospect's actual hero headline and puts both versions side by side. The prospect isn't being pitched a service — they're looking at a before-and-after of their own business, and the only question left is whether they want the rest.
The reason most freelancers don't run this play is scale: hand-building a mockup per prospect caps you at a few sends a week. Lemlist is the tool that breaks that cap. Its personalized images, per-prospect landing pages, and liquid syntax variables let you build the preview once as a template and have it assemble itself for every prospect in the sequence. ColdRelay is the infrastructure underneath: the secondary domain, the small mailbox pool, and the dedicated IPs that those preview emails actually send from. This guide covers wiring the two together into productized spec work — the play, systematized.
Why Run Lemlist on ColdRelay Infrastructure
Lemlist's edge for a freelancer isn't sequencing — plenty of tools sequence. It's that Lemlist treats personalization as an asset pipeline. Personalized images drop each prospect's name, logo, or screenshot into a visual template at send time. Per-prospect landing pages give every recipient their own page — your reimagined version of their homepage, hosted at a link only they get. Liquid syntax variables go beyond {{firstName}} into conditional copy that changes based on what you know about each prospect. For spec-work outreach, that's the whole production line.
What Lemlist doesn't do is provision the mailboxes that carry those emails or guarantee their deliverability — it sends from whatever accounts you connect, and the quality of those accounts is the infrastructure layer's job. That's where ColdRelay fits. A spec-work pipeline runs deliberately low-volume — typically 5-10 mailboxes on one secondary domain, far below the 100-150 mailboxes per domain ColdRelay supports. They provision on isolated Azure tenants with dedicated IPs, fully DNS-configured (SPF, DKIM, DMARC), ready in about an hour, with no warmup waiting period — warmup runs continuously as part of each mailbox's daily budget.
The pairing is additive, not competitive: Lemlist is the personalization and sending layer, ColdRelay is the infrastructure it sends from. And for this play, infrastructure matters more than usual — an email carrying a custom image and a unique link is exactly the kind of message that needs a clean dedicated IP and a healthy domain behind it, because a spec-work preview that lands in spam is hours of craft nobody ever sees.
Visit Lemlist →Connecting ColdRelay Mailboxes to Lemlist
Provision a small mailbox pool on ColdRelay
Pick one secondary domain adjacent to your brand — if your portfolio lives at janedoe.design, something like janedoedesign.co keeps the connection obvious without risking the address your contracts run through. Order 5-10 mailboxes; ColdRelay supports 100-150 per domain, but spec-work outreach is a low-volume, high-craft play and a handful of mailboxes covers it. 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
From the ColdRelay dashboard, grab each mailbox's SMTP/IMAP credentials and connect them in Lemlist as sending accounts. One important toggle: leave lemwarm off for these accounts. ColdRelay mailboxes already warm continuously — 2 warmup sends/day per mailbox as part of the 4/day budget — and double-warming the same accounts adds volume without adding benefit. Cap each mailbox at 2 outbound emails per day in Lemlist to mirror the budget: 4 sends/day total, split 2 outbound + 2 warmup.
Build the spec-work template with personalized images and liquid syntax
This is the step that makes the play systematic. In Lemlist, build a personalized image template that composites your work onto each prospect's context — a browser-frame mockup that pulls in their homepage screenshot with your redesign layered over it, or a side-by-side graphic with a {{currentHeadline}} variable on the left and your {{rewrittenHeadline}} on the right. Use liquid syntax for the copy around it, so the email reads differently for an ecommerce brand than for a SaaS site. Your prospect CSV carries the per-prospect fields; Lemlist assembles the asset at send time.
Attach a per-prospect landing page for the full preview
The image in the email is the hook; the landing page is the close. Use Lemlist's dynamic landing pages to give each prospect their own URL — the full reimagined homepage for a designer, the complete rewritten above-the-fold for a writer, annotated with two or three short notes on why each change earns money. End the page with one CTA: a 20-minute call to walk through the rest. A prospect who clicks through is reviewing finished-looking work about their own business, which is as warm as cold traffic gets.
Launch as a multichannel sequence and read the campaign report
Build the Lemlist sequence with light multichannel framing around the preview: a LinkedIn profile visit the day before the email (so your face is vaguely familiar), the spec-work email itself, then a short follow-up two or three days later — 'did the preview land?' — and a LinkedIn connection request for non-repliers. Watch the campaign report for one number above all: landing-page clicks. An email that gets opened but not clicked has a weak image hook; a page that gets visited but not replied to has a weak close. The report tells you which half to fix.
The Freelancer Lemlist Playbook
Template the frame, hand-finish the centerpiece
Pure automation makes spec work generic; pure handcraft makes it unscalable. The working middle: Lemlist's personalized images automate the frame — the browser mockup, the side-by-side layout, the prospect's logo and screenshot dropped in — while you hand-write the one field that carries the value, like the rewritten headline or the redesign concept note. Ten minutes of craft per prospect inside a template that handles everything else is what turns a few previews a week into a few previews a day.
Show one fix, not a portfolio
The spec-work email earns its reply by being specific, and specificity dies when you try to demonstrate range. Pick the single most visible flaw in each prospect's site or copy — the headline that describes features instead of outcomes, the hero section with three competing CTAs — and make the entire preview about that one fix. The implicit message is the pitch: if this is what I noticed for free, imagine the paid engagement. A portfolio link can live in your signature; it should never be the body of the email.
Qualify by what you can see, not who they are
Most freelancer targeting starts with titles and industries. Spec-work targeting starts in the prospect's actual storefront: you're only emailing companies whose site or copy has a flaw you can visibly fix. Build the list by browsing, not filtering — twenty minutes in a directory of recently funded or recently redesigned-elsewhere companies, screenshotting the ones with an obvious gap. The qualification doubles as production: the screenshot you took to qualify them is the same one Lemlist composites your preview onto.
Size the daily volume to your production rate, not your send capacity
At 2 outbound sends per mailbox per day, 5 ColdRelay mailboxes give you 10 sends/day — and for this play, that's a feature. Your real constraint is how many previews you can hand-finish to a standard you'd put your name on, which for most freelancers is 5-10 a day. Matching infrastructure to production keeps quality honest: the moment you're tempted to add mailboxes, the right question isn't 'can I send more?' but 'can I finish more previews without them getting worse?' Scale the pool only when the answer is yes.
Typical Freelancer Outbound Benchmarks (Lemlist + ColdRelay)
| Metric | Benchmark | Notes |
|---|---|---|
| Inbox placement rate | 95%+ | Dedicated IPs and isolated tenants outperform shared Google/Microsoft pools |
| Reply rate | 6-12% | Spec-work previews of the prospect's own site out-reply every text-only freelance pitch |
| Landing-page click-through | 15-30% | Per-prospect Lemlist pages showing the full preview; the leading indicator to optimize first |
| 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 image template and landing page take longer than 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). A spec-work pipeline runs on 5-10 mailboxes, so this stays a small fixed line item — and DNS, dedicated IPs, and isolated Azure tenants are all included.
Lemlist is billed separately on its own subscription for the sequence builder, personalized images, dynamic landing pages, and multichannel steps — priced per its current plans.
One small infrastructure bill plus one software subscription buys a production line for the highest-conversion email a freelancer can send. At 6-12% reply rates, a single landed project typically covers the stack for the year.
| 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 doing different jobs. Lemlist handles the sequences, personalized images, per-prospect landing pages, and multichannel steps. ColdRelay provides the underlying domain, mailboxes, and dedicated IPs that Lemlist sends from. You use them together: Lemlist builds the preview, ColdRelay makes sure the email carrying it actually lands.
Should I use lemwarm with ColdRelay mailboxes?
No. ColdRelay mailboxes warm continuously in the background — 2 warmup sends/day per mailbox as part of the 4/day budget (2 outbound + 2 warmup) — with no waiting period before your first campaign. Leave lemwarm off for these accounts and point Lemlist at outbound sending only; running two warmup systems against the same mailbox adds volume without adding benefit.
Do emails with personalized images deliver as well as plain-text ones?
Image-bearing emails are scrutinized harder by inbox filters than plain text, which is exactly why the infrastructure underneath matters more for this play, not less. Sending from ColdRelay's dedicated IPs on isolated Azure tenants with pre-configured SPF, DKIM, and DMARC keeps placement at 95%+. Help it along: one image per email, real personal copy around it, and a low, steady 2-outbound-sends-per-mailbox cadence rather than bursts.
Isn't doing spec work for free just giving my work away?
A preview isn't the deliverable — it's the proof. The headline rewrite or homepage concept you send is one visible fix, finished to ten minutes' polish inside a Lemlist template, not the full engagement. Prospects who take it and run were never going to pay anyone; prospects who reply have already seen what working with you produces, which is why this play converts at rates text-only pitches don't reach. You're spending minutes per prospect to skip the entire 'can you share relevant samples?' stage.