The Show-Your-Work Opener, Run Through Lemlist
Every prospect a marketing agency emails has already received fifty emails claiming results. Claims are free, so claims are ignored. What almost nobody sends is proof of competence performed on the prospect's own work: a screenshot of their actual ad, landing page, or lifecycle email with three specific improvements annotated on it. That's a teardown — and an agency that opens with one isn't asking to be trusted, it's demonstrating why it should be.
The problem with teardowns has always been scale: a designer marking up screenshots one prospect at a time caps you at a handful a week. Lemlist is the tool that systematizes it — personalized images drop the prospect's name, logo, and screenshot into a templated visual, and per-prospect landing pages give the full mini-audit a home of its own. ColdRelay is the layer underneath: the secondary domains, mailboxes, and dedicated IPs Lemlist actually sends from. This guide covers wiring the two together into a teardown machine.
Why Run Lemlist on ColdRelay Infrastructure
Lemlist's whole identity is personalization that goes beyond mail merge — liquid syntax variables in the copy, personalized images in the body, per-prospect landing pages behind the CTA, and multichannel sequences that add LinkedIn visits, connections, and comments between email steps. For a teardown motion, that feature set is the production line: the screenshot goes into an image template once, and every prospect gets their own version.
What Lemlist doesn't do is provision the sending infrastructure. It sends from whatever mailboxes you connect, and the deliverability of those mailboxes — the domains, the DNS, the IP reputation — is yours to solve. That matters double for image-heavy email: a teardown that lands in spam is hours of audit work nobody ever sees. ColdRelay fills that layer. You order mailboxes on isolated Azure tenants with dedicated IPs — SPF, DKIM, and DMARC pre-configured — live in about an hour, with ColdRelay supporting 100-150 mailboxes per domain.
The pairing is additive, not competitive: ColdRelay is the infrastructure, Lemlist is the sending and personalization layer on top. You keep Lemlist's images, landing pages, and multichannel steps — you just send the work through mailboxes built to land it.
Visit Lemlist →Connecting ColdRelay Mailboxes to Lemlist
Provision the teardown pool on ColdRelay
Order mailboxes on one or two secondary domains close to your agency brand — ColdRelay supports 100-150 mailboxes per domain, and everything provisions on isolated Azure tenants with dedicated IPs in about an hour, with SPF, DKIM, and DMARC pre-configured. Teardown outreach is lower-volume and higher-effort than spray campaigns, so most agencies start smaller here than they would elsewhere.
Connect the mailboxes in Lemlist — and leave lemwarm off
In Lemlist, add each ColdRelay mailbox under Settings → Email Accounts via SMTP/IMAP. Lemlist offers lemwarm as its warmup product, but ColdRelay mailboxes already warm continuously — 2 warmup sends/day per mailbox as part of the 4/day total budget (2 outbound + 2 warmup). Don't double-warm; let Lemlist spend only the outbound half.
Build the teardown image template with liquid syntax
In the Lemlist campaign editor, create a personalized image template: the annotated-screenshot frame stays constant, while liquid syntax variables pull in each prospect's {{companyName}}, logo, and the custom screenshot field from your CSV. Upload the per-prospect screenshots as a custom variable column — the annotation overlay does the rest, and every email carries an image of the prospect's own ad or page marked up.
Put the full mini-audit on a per-prospect landing page
The email shows one annotated improvement; the landing page hosts all three. Use Lemlist's dynamic landing pages so each prospect's CTA resolves to a page with their company name, their screenshots, and your full markup — plus a calendar embed. The ask stops being 'book a call to hear our pitch' and becomes 'see the rest of your audit,' which is a much easier click.
Add LinkedIn steps that echo the teardown
Use Lemlist's multichannel sequences to wrap the email in LinkedIn touches: a profile visit the day before the teardown email, and a connection request two days after referencing it ('sent over a quick markup of your pricing page — curious if you saw it'). Then watch Lemlist's campaign reports per step to see whether the image email or the LinkedIn follow-up is actually generating the replies, and rebalance the sequence accordingly.
The Agency Teardown Playbook for Lemlist
Tear down what you sell
The teardown subject must match the retainer you want. A paid-media agency screenshots the prospect's live ad and annotates the hook, the creative, and the offer mismatch; a CRO shop marks up the landing page; a lifecycle agency forwards their own welcome email back to them with notes. If the markup proves competence in the exact service you're pitching, the prospect's next thought is 'what would they find in the rest of it' — which is the meeting.
Annotate three things: one obvious, one sharp, one withheld
The obvious fix earns agreement ('yes, we know the CTA is buried'). The sharp fix earns respect — something their team plausibly missed. The third improvement gets named but not explained: 'there's also a measurement issue in how this page hands off to your CRM — too long for email.' Agreement, respect, and an open loop is the reply formula; the per-prospect landing page is where the loop closes.
Build the screenshot pipeline before the campaign
The constraint in teardown outreach isn't sending — it's producing the markups. Standardize the pipeline: a VA or junior strategist captures screenshots into the CSV's custom variable columns, a senior eye writes the three annotations per prospect in fifteen minutes, and Lemlist's image template assembles the visual automatically. Run it as a weekly batch — capture Monday, annotate Tuesday, launch Wednesday — so the campaign never waits on production.
Send fewer, heavier emails — the math still works
Teardown outreach inverts the usual volume logic: each email costs real production effort, so the motion runs on small, precise lists where every prospect was chosen because their public work has a visible, fixable flaw. At 2 outbound sends/day per mailbox (of the 4/day total, with 2 warmup), a 15-mailbox pool supports about 200 teardowns a month — and because each one demonstrates the service instead of describing it, reply rates run multiples above claim-based outreach. You don't need a bigger list; you need a sharper markup.
Typical Teardown Outreach Benchmarks (Lemlist + ColdRelay)
| Metric | Benchmark | Notes |
|---|---|---|
| Inbox placement rate | 95%+ | Dedicated IPs and isolated tenants outperform shared Google/Microsoft pools |
| Reply rate (teardown-led sequences) | 6-12% | Annotated proof on the prospect's own work; runs well above claim-based agency outreach |
| Landing page visit rate from teardown emails | 15-25% | Per-prospect Lemlist pages with the full mini-audit; 'see the rest of your audit' beats 'book a call' |
| Teardown production time per prospect | 15-20 min | Screenshot capture batched by a VA; senior annotation pass; Lemlist image template does assembly |
| Outbound capacity per mailbox | 2/day | 4 sends/day total per mailbox — 2 outbound + 2 warmup |
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 because teardown outreach runs on smaller, sharper lists, the pool is often the cheapest line in the whole motion.
Lemlist is billed separately on its own subscription for the campaign editor, personalized images, dynamic landing pages, multichannel sequences, and reports — priced per its current plans.
Infrastructure cost scales with mailbox count; Lemlist's cost scales with seats and plan tier. The real cost center in a teardown motion is annotation time, not software — which is exactly why both layers being fixed, predictable line items keeps the per-meeting math easy to defend.
| 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, not competitors. Lemlist is the sending and personalization layer: liquid syntax variables, personalized images, per-prospect landing pages, multichannel sequences, and campaign reports. ColdRelay is the infrastructure layer underneath: the secondary domains, mailboxes, and dedicated IPs Lemlist sends from. You use both together — Lemlist builds and sends the teardown, ColdRelay makes sure it reaches the inbox.
Should I use lemwarm with ColdRelay mailboxes?
No. ColdRelay mailboxes warm continuously on ColdRelay's network — 2 warmup sends/day per mailbox, built into the 4 sends/day total budget alongside 2 outbound sends. Running lemwarm on top would double-warm the same mailboxes and spend budget that should go to teardown sends. Connect the mailboxes to Lemlist for outbound only, leave lemwarm off, and there's no warmup waiting period before the first campaign either.
Do personalized images and landing pages hurt deliverability?
Image-heavy email is less forgiving of weak infrastructure, not inherently worse — the senders who get burned are the ones sending from shared pools with shaky reputations. On ColdRelay mailboxes — isolated Azure tenants, dedicated IPs, SPF, DKIM, and DMARC pre-configured — teardown emails with a single personalized image and one landing-page link land normally at 95%+ placement. Keep it to one image and one link per email and let the landing page carry the heavy content.
How do we do teardowns at scale without the quality collapsing?
Separate what templates from what doesn't. The visual frame, the email copy, and the landing page layout are built once in Lemlist; the screenshots are captured in batches by a VA into custom variable columns; only the three annotations per prospect need senior judgment, at roughly fifteen minutes each. At 2 outbound sends/day per mailbox (4/day total with 2 warmup), even a 15-mailbox ColdRelay pool — about 200 sends a month — is deliberately modest, because the constraint you're protecting is annotation quality, not sending capacity.