Asset-Specific Outreach, Run Through Lemlist
There's one email a commercial property owner reliably opens: the one that's visibly about their building. Not their market, not their portfolio category — the actual asset, pictured in the email body, with numbers attached to it. That's the specific thing Lemlist is unusually good at: personalized images that drop a per-prospect photo, comp summary, or market-position snapshot into every email, liquid variables that carry asset-level details through the whole sequence, and per-prospect landing pages that turn a cold email into a one-page property memo. ColdRelay is the layer underneath — the secondary domains, mailboxes, and dedicated IPs Lemlist actually sends from.
This guide covers the visual-outreach workflow specifically: structuring your property data so Lemlist's variables can use it, building image templates around the asset instead of your brand, wiring ColdRelay mailboxes into Lemlist, and sequencing owners and investors who get pitched generically every week — but almost never about their own building.
Why Run Lemlist on ColdRelay Infrastructure
Lemlist's edge is depth per prospect, not raw volume. A personalized image with the prospect's building and a custom landing page with its comp set take real preparation — which means every send is expensive in effort, and a send that dies in spam wastes more than a generic blast would. The infrastructure under a Lemlist campaign matters precisely because each email carries so much work.
That's the layer ColdRelay covers. Mailboxes run on isolated Azure tenants with dedicated IPs, with SPF, DKIM, and DMARC pre-configured, ready in about an hour — and they hold 95%+ inbox placement so the image you built around someone's asset actually renders in their inbox instead of a junk folder. ColdRelay also handles warmup continuously as part of each mailbox's standard budget of 4 sends/day — 2 outbound + 2 warmup — so there's no waiting period before your first campaign. Lemlist ships its own warmup tool, lemwarm, but you should leave it off for ColdRelay mailboxes: warmup is already running on the infrastructure side, and double-warming just burns budget without adding reputation.
The pairing is additive, not competitive: ColdRelay is the infrastructure, Lemlist is the personalization and sequencing layer on top. Lemlist makes the email unmistakably about the prospect's property; ColdRelay makes sure it lands.
Visit Lemlist →Connecting ColdRelay Mailboxes to Lemlist
Provision mailboxes on ColdRelay
Choose secondary domains that read like a named principal or boutique brokerage — owners reply to people pitching their asset, not platforms. ColdRelay supports 100-150 mailboxes per domain; because Lemlist campaigns are deep rather than wide, most teams start with 20-50 mailboxes on a single domain. 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, go to Settings → Email accounts and connect each ColdRelay mailbox via SMTP/IMAP. Set each account's daily sending limit to 2 outbound emails per day — that mirrors ColdRelay's per-mailbox budget of 4 sends/day total, split 2 outbound + 2 warmup. Leave lemwarm disabled for these accounts: ColdRelay's warmup already runs continuously inside that budget, and stacking a second warmup layer on top adds sends without adding reputation.
Build the lead list with asset-level custom variables
This is where the whole angle lives or dies. Before importing, enrich each owner record with the fields your images and copy will pull from: property address, asset photo URL, square footage, an estimated value or recent comp, and the submarket name. Import the CSV into a Lemlist campaign and map each column to a custom variable — Lemlist's liquid syntax can then drop {{propertyAddress}} or {{compSummary}} into any step, and branch copy with liquid conditions when a field like the comp figure is missing.
Create the personalized image around the property
In Lemlist's image personalization editor, build a template where the dynamic element is the asset, not your logo: the property photo as the base layer, with text layers pulling {{propertyAddress}}, {{squareFootage}}, and a one-line market-position note from your variables. For higher-value targets, pair it with a Lemlist per-prospect landing page — a one-page memo with the comp set and your read on the asset — so the email's CTA is "see the two-minute breakdown" instead of "hop on a call."
Sequence with LinkedIn steps and launch
Build the campaign as a multichannel sequence: the image-led email first, a LinkedIn profile visit the next day, a connection request after the second email, and a final email that references the landing page. Owners and principals check who viewed their profile — the visit confirms the email came from a real person who actually looked at their building. Launch, and use Lemlist's campaign reports to compare reply rates between image variants per asset class.
The Asset-Specific Lemlist Playbook
Make the image the property, never the pitch
The personalized image that earns a reply is a photo of the prospect's building with their address and one number they care about — not your team photo with their first name on a coffee cup. Owners scan-delete branded creative instantly, but a picture of their own asset triggers the same reflex as mail from the county: this is about something I own, I should read it. Keep your branding to the signature; spend the image entirely on their property.
Carry the asset through the sequence with liquid variables
One personalized first touch followed by generic bumps reads as a mail merge that ran out of data. Use liquid variables so every step stays asset-specific — the second email references {{submarket}} cap-rate movement, the third cites the {{compSummary}} from the landing page. Write liquid fallbacks for thin records, so a missing comp figure degrades to a clean sentence about the submarket instead of an empty bracket that exposes the automation.
Use the landing page as a one-asset memo
Lemlist's per-prospect landing pages are usually used as fancy calendars. In CRE they can be something better: a one-page memo on the prospect's specific building — the photo, three comps, your estimate range, and one paragraph on why now. A page visit is also your strongest intent signal: an owner who clicked through to a valuation memo on their own asset is live, and gets a call that day rather than email step four.
Send fewer, richer emails — and size the fleet accordingly
Asset-specific outreach inverts the usual volume math. Enriching photos and comps for 60 properties a day is a real workload, so build target lists you can personalize properly — likely-seller signals like long hold periods, maturing debt, or recent vacancy — instead of every parcel in the county. At 2 outbound sends/day per mailbox (4/day total with 2 warmup), 30 ColdRelay mailboxes covers 60 daily sends, which is more genuinely-personalized outreach than most CRE teams can feed with data anyway.
Typical Asset-Specific Outreach Benchmarks (Lemlist + ColdRelay)
| Metric | Benchmark | Notes |
|---|---|---|
| Inbox placement rate | 95%+ | Dedicated IPs and isolated tenants — critical when each send carries hours of image and comp preparation |
| Reply rate (image-personalized owner outreach) | 3-8% | Asset-specific images and comps run well above the 1-4% typical of generic owner blasts |
| Landing page visit rate | 10-20% | Of delivered emails; a visit to a memo on their own building is a same-day-call 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; image templates and variable mapping in Lemlist 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). DNS, dedicated IPs, and isolated Azure tenants are included — and because asset-specific campaigns run on smaller, enriched lists, most teams need a leaner fleet than volume senders.
Lemlist is billed separately on its own per-seat plans, which cover the sequencing engine, image personalization, per-prospect landing pages, liquid variables, and multichannel LinkedIn steps.
The two costs scale on different axes: Lemlist with the seats building campaigns, ColdRelay with the mailboxes those campaigns send from. For a deep-personalization motion, the practical budget ceiling is usually data enrichment time rather than either subscription — 30 mailboxes covering 60 sends/day keeps both bills light while saturating what a CRE team can genuinely personalize.
| 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 compete with Lemlist?
No — they're complementary layers of the same stack. Lemlist is the personalization and sequencing layer: liquid variables, personalized images, per-prospect landing pages, and multichannel sequences with LinkedIn steps. ColdRelay is the infrastructure layer underneath: the domains, mailboxes, and dedicated IPs that Lemlist connects to and sends from. Lemlist makes the email about the prospect's property; ColdRelay makes sure it reaches them.
Should I run lemwarm on my ColdRelay mailboxes?
No. ColdRelay mailboxes warm continuously as part of the standard budget — 4 sends/day per mailbox, split 2 outbound + 2 warmup — so there's no waiting period before your first Lemlist campaign and no need for a second warmup layer. Leave lemwarm off for these accounts and point Lemlist at outbound sending only; double-warming spends sends without adding reputation.
Won't a personalized image in every email trip spam filters?
Image-bearing email is filtered on sender reputation far more than on the image itself — which is exactly why the infrastructure layer matters for this play. Keep the email text-first with one personalized image (not a wall of graphics), host it on Lemlist's standard image delivery, and send from ColdRelay's dedicated IPs on isolated Azure tenants with DNS pre-configured. That combination is what holds 95%+ placement; a property photo on a reputable sender lands, the same photo from a shared pool doesn't.
What data do I need before launching an asset-specific Lemlist campaign?
Five fields per owner record do most of the work: property address, a photo of the asset (a street-view capture works), approximate square footage, one comp or estimated value, and the submarket name. Map those to Lemlist custom variables and your images, copy, and landing pages all pull from the same columns. Records missing a field aren't disqualified — liquid fallbacks let the copy degrade gracefully — but the property photo is the one input the whole angle depends on.