Becoming a Familiar Name, Run Through Lemlist
Coaching is bought on trust, and trust has a sequencing problem in cold outreach: the first time a prospect sees your name, you're asking for something. A founder opens an email from a stranger proposing a discovery call, and every instinct says delete — not because the offer is wrong, but because the relationship is starting at the ask.
Lemlist's multichannel sequences let a coach reorder that. A LinkedIn profile visit, a thoughtful comment on the prospect's post, a connection request — small, no-ask touches that run automatically before the first email ever sends. By the time your message lands, the name in the from line has a face, a headline, and a comment they half-remember agreeing with. The email isn't a cold open anymore; it's a follow-up to a presence.
ColdRelay is the infrastructure underneath the email half of that sequence: the secondary domains, mailboxes, and dedicated IPs Lemlist actually sends from, so the message that finally makes the ask also actually reaches the inbox. This guide covers how to wire the two together.
Why Run Lemlist on ColdRelay Infrastructure
Lemlist is a sending and sequencing platform — it sends email from whatever mailboxes you connect to it, and runs its LinkedIn steps through your own LinkedIn account. It doesn't provision domains or guarantee the deliverability of the mailboxes themselves; that's the infrastructure layer's job.
For a familiarity-first sequence, that layer carries unusual weight. You've spent four or five days building recognition on LinkedIn — the visit, the comment, the accepted connection — and all of that investment converges on one email landing in one inbox. If that email hits spam, the whole choreography collapses: the prospect remembers the friendly comment but never sees the message it was setting up, and the window closes. ColdRelay mailboxes run on isolated Azure tenants with dedicated IPs, fully DNS-configured (SPF, DKIM, DMARC), live in about an hour, with 95%+ inbox placement — so the payoff email arrives where the warm-up touches pointed it.
The pairing is additive, not competitive: ColdRelay is the infrastructure, Lemlist is the sequencing layer on top. You keep Lemlist's multichannel steps, liquid variables, and campaign reports — you just give the email steps mailboxes built to land.
Visit Lemlist →Connecting ColdRelay Mailboxes to Lemlist
Provision mailboxes on ColdRelay
Pick a secondary domain close to your coaching brand and provision your pool — ColdRelay supports 100-150 mailboxes per domain, but familiarity-first coaches run lean: 10-20 mailboxes is typical, because every email step is preceded by LinkedIn touches that take real calendar days. Everything goes live on isolated Azure tenants with dedicated IPs in about an hour, with SPF, DKIM, and DMARC pre-configured.
Connect the mailboxes as Lemlist senders
In Lemlist, go to Settings → Email accounts and add each ColdRelay mailbox via custom SMTP/IMAP using the credentials from the ColdRelay dashboard export. Each mailbox connects as its own sender, so your campaigns can rotate email steps across the pool while the LinkedIn steps stay on your one LinkedIn profile.
Cap email steps at 2/day per mailbox and skip lemwarm
Set each sender's daily limit in Lemlist to 2 outbound emails to mirror ColdRelay's per-mailbox budget — 4 sends/day total, split 2 outbound + 2 warmup. ColdRelay's warmup runs continuously on its side as part of that budget, so leave lemwarm off for these mailboxes; double-warming wastes sends and muddies the pattern your mailboxes have already established. The LinkedIn steps don't touch this budget at all — they run through your LinkedIn account, not your mailboxes.
Build the multichannel sequence with LinkedIn steps first
In the Lemlist campaign builder, structure the sequence so the no-ask touches lead: a LinkedIn profile visit on day 1, a comment or connection request on day 2-3 (Lemlist's Chrome extension handles the LinkedIn automation), then the first email step on day 4-5 — after the prospect has seen your name twice without being asked for anything. Use Lemlist's conditions to branch: if the connection request is accepted, the email can open warmer; if not, it opens as a well-researched cold note.
Load liquid variables and preview every email before launch
Build your prospect CSV with columns for the personal hooks — the recent post you commented on, the career move, the podcast appearance — and reference them in your copy with Lemlist's liquid syntax, including fallback values for prospects where a column is empty so no email ever renders with a hole in it. Preview each prospect's rendered email in Lemlist before launching; at 20-40 sends/day, checking every render is feasible and worth it.
The Familiarity-First Lemlist Playbook
Run the recognition ladder: visit, comment, connect — then email
Order the no-ask touches by escalating visibility. The profile visit puts your name in their notifications with zero demand. The comment — on something they actually wrote, adding a real observation — earns the first deliberate look at who you are. The connection request arrives from someone whose comment they liked. Only then does the email send, and it's no longer cold: LinkedIn has already answered 'who is this person' before the inbox asks 'what do they want.' Lemlist runs the whole ladder as one sequence with delays between rungs.
Make the liquid variable carry the research, not the flattery
Generic personalization ('loved your recent post!') reads as automation wearing a costume. The coach version uses liquid variables to restate the prospect's own thinking back to them: a column for the specific claim in their post, rendered as 'your point about {{claim}} matches what I see in almost every founder I work with.' That sentence proves you read the thing — and because your Lemlist comment step already engaged with the same post days earlier, the email and the comment corroborate each other. One research pass per prospect feeds both touches.
Replace the calendar link with a per-prospect landing page
A Calendly link in a first email is the ask wearing a bow tie. Lemlist's personalized landing pages let you swap it for something that gives before it takes: a page with the prospect's name and company rendered into it, a two-minute video or a short diagnostic relevant to their situation, and only then a booking option. For a coach, the page itself is a demonstration — this is what it feels like when someone prepares for you — and Lemlist's campaign reports show you who visited even if they didn't book, which is your warmest follow-up list.
Read connection acceptance as your real leading metric
Open rates tell you the infrastructure works; acceptance rates tell you the positioning works. In Lemlist's campaign reports, watch the LinkedIn connection acceptance rate before anything else — if fewer than a quarter of prospects accept, your profile, your comment quality, or your targeting is failing before the email ever gets its chance, and no subject line will fix that. Fix the ladder first: a sharper headline on your profile, comments that add a view instead of applause, tighter niche selection. Reply rate follows acceptance rate.
Typical Familiarity-First Benchmarks (Lemlist + ColdRelay)
| Metric | Benchmark | Notes |
|---|---|---|
| Inbox placement rate | 95%+ | Dedicated IPs and isolated tenants outperform shared Google/Microsoft pools |
| LinkedIn connection acceptance rate | 25-40% | Tight niche targeting plus a real comment before the request; the leading indicator to watch |
| Reply rate after LinkedIn touches | 6-12% | Emails preceded by visit/comment/connect outperform email-only sequences to the same list |
| No-ask touches before the first email | 2-3 over 4-7 days | Visit, comment, and connection request spaced so recognition builds without crowding |
| Mailboxes per coach | 10-20 | 20-40 outbound sends/day at 2 outbound per mailbox (4/day total, 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, IPs, and isolated Azure tenants are included — and at familiarity-first volumes of 10-20 mailboxes, the infrastructure line stays small.
Lemlist is billed separately on its own subscription for the multichannel sequences, liquid variables, personalized images and landing pages, and campaign reports — priced per its current plans.
Infrastructure cost scales with mailbox count; Lemlist's cost scales with seats and plan features. For a coach the combined stack buys something neither piece delivers alone — a sequence where the prospect already knows your name when the email lands, and an email that actually lands. Typically a fraction of one client engagement.
| 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 and this whole setup uses both. Lemlist is the sequencing layer: the multichannel campaigns, the LinkedIn steps, the liquid variables, the landing pages, the reports. ColdRelay is the infrastructure layer underneath: the secondary domains, mailboxes, and dedicated IPs Lemlist's email steps actually send from. Lemlist builds the familiarity; ColdRelay makes sure the email that cashes it in reaches the inbox.
Should I run lemwarm on my ColdRelay mailboxes?
No. ColdRelay mailboxes warm continuously as part of the standard send budget — 4 sends/day per mailbox, split 2 outbound + 2 warmup — so warmup is already handled at the infrastructure layer and there's no waiting period before your first campaign. Running lemwarm on top would double-warm the same mailboxes, spending sends without adding deliverability. Point Lemlist at outbound only and leave warmup to ColdRelay.
Do Lemlist's LinkedIn steps run through ColdRelay too?
No — the channels split cleanly. LinkedIn visits, comments, and connection requests run through your own LinkedIn account via Lemlist's Chrome extension, and they don't consume any of your mailbox send budget. Only the email steps send from ColdRelay mailboxes, within the 4/day-per-mailbox budget (2 outbound + 2 warmup). That's the appeal of the pairing for coaches: the trust-building happens on your real LinkedIn identity, while the email volume runs on infrastructure that never risks your personal domain.
Doesn't waiting 4-7 days before the first email slow everything down?
It slows the first send, not the pipeline. Once the sequence is running, prospects flow through the ladder continuously — each day, some are getting visited, some are getting commented on, and some are receiving emails that land warm. The trade is deliberate: at coaching deal sizes, a smaller number of replies from people who already recognize you converts to discovery calls far better than a faster blast to strangers. With 10-20 ColdRelay mailboxes giving 20-40 outbound sends/day, the email capacity matches the pace of the LinkedIn ladder almost exactly.