Networked Business Development, at Outreach Scale
Legal work is referred, not sold. A general counsel doesn't pick outside counsel from an email blast — they pick the lawyer whose name they've seen before: at a panel, in a comment thread, through a mutual connection. Which is why pure cold email, sent to a stranger with no prior touchpoint, underperforms for law firms relative to almost every other industry. The fix isn't to abandon outreach; it's to rebuild the warm-introduction pattern at scale.
That's the specific thing Lemlist is built for. Its multichannel sequences interleave LinkedIn steps — visit the prospect's profile, engage with their posts, send a connection request — before the first email ever goes out, so by the time your message lands, the general counsel has seen the attorney's name twice. Lemlist's liquid syntax then lets each email reference the prospect company's actual jurisdiction and stage-specific legal situation, not a generic pitch. ColdRelay is the infrastructure underneath: the secondary domains, mailboxes, and dedicated IPs Lemlist sends from, kept entirely separate from the domain that carries the firm's privileged correspondence. This guide covers how to wire the two together into a digital version of how lawyers have always built books of business — familiarity first, ask second.
Why Run Lemlist on ColdRelay Infrastructure
Lemlist is a sequencing and engagement platform — it orchestrates the LinkedIn touches, personalizes the emails with liquid variables, and tracks the whole journey in its campaign reports. But it sends from whatever mailboxes you connect to it; provisioning the domains, the mailboxes, and the sending reputation behind them is the infrastructure layer's job.
That's where ColdRelay fits. You order dedicated mailboxes on isolated Azure tenants with dedicated IPs, fully DNS-configured (SPF, DKIM, DMARC) and ready in about an hour — never on the primary domain your clients and the courts use to reach you. Connect them to Lemlist and the firm can be sending the same day, because warmup runs continuously as part of each mailbox's send budget rather than as a multi-week waiting period.
The pairing is additive, not competitive: ColdRelay is the infrastructure layer, Lemlist is the sequencing and engagement layer on top. And for a relationship-led sequence, the infrastructure quality is what makes the choreography pay off — a prospect who accepted the attorney's connection request three days ago and then finds the follow-up email in spam is a worse outcome than no sequence at all. With 95%+ inbox placement underneath, the email arrives where the LinkedIn groundwork pointed it: the inbox, from a name the prospect now recognizes.
Visit Lemlist →Connecting ColdRelay Mailboxes to Lemlist
Provision mailboxes on ColdRelay
Pick secondary domains adjacent to the firm's name — never the primary domain that carries client correspondence and court filings. ColdRelay supports 100-150 mailboxes per domain, but a relationship-led program starts deliberately small: 10-20 mailboxes is typical, because each sequence is anchored to a named attorney whose LinkedIn profile does half the work. Everything provisions 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 connect each ColdRelay mailbox via SMTP/IMAP using the credentials from the ColdRelay dashboard. Name each sending identity after a real attorney — the from-name on the email must match the LinkedIn profile that visited and connected, or the whole familiarity effect collapses.
Cap sends to the ColdRelay budget and skip lemwarm
Set each mailbox's daily sending limit in Lemlist to 2 outbound emails, mirroring ColdRelay's per-mailbox budget — 4 sends/day total, split 2 outbound + 2 warmup. Lemlist offers its own warmup tool, lemwarm, but leave it off for ColdRelay mailboxes: warmup already runs continuously inside the 4/day budget, and double-warming the same mailbox from two networks creates a send pattern that looks engineered rather than human.
Build the multichannel sequence — LinkedIn before email
In Lemlist's campaign builder, structure the sequence the way a referral relationship actually forms: a LinkedIn profile visit on day one, a thoughtful comment on one of the prospect's recent posts, a connection request a few days later, and only then the first email. Lemlist executes the LinkedIn steps as tasks or automated touches and times the email to land after the connection — so the subject line arrives from a name the general counsel has already seen twice that week.
Load liquid variables for jurisdiction and stage
Enrich your prospect CSV with two custom columns — the company's operating jurisdiction(s) and its growth stage — and reference them in copy with Lemlist's liquid syntax: a Delaware-incorporated company hiring in California gets a sentence about California-specific employment exposure; a company that just opened a UK entity gets cross-border data-handling language. Use liquid conditionals to swap whole sentences by stage, so a 30-person startup and a 300-person scale-up never receive the same paragraph. Launch, then watch Lemlist's campaign reports to see which touches — the comment, the connection, the email — actually precede replies.
The Law Firm Lemlist Playbook
Make the attorney the sender, not the firm
Referrals attach to people, not letterheads — and so does this sequence. Every campaign should be anchored to one named attorney whose real LinkedIn profile performs the visits, comments, and connection requests, and whose name is the from-line on the ColdRelay mailbox underneath. The prospect's experience is meeting a specific lawyer who noticed their work, not receiving marketing from a firm. That also means the attorney must be genuinely willing to take the resulting conversations; a sequence in a partner's name that the partner won't follow through on burns the exact trust it built.
Engage before you ask — and make the engagement real
The LinkedIn comment step is where this play is won or lost. A generic 'Great post!' is worse than silence; a two-sentence comment that adds a genuinely useful legal observation to the general counsel's post about, say, a new hiring market is a credibility deposit. Have the attorney write or approve comment templates per topic, and keep the cadence unhurried — visit, then comment, then connect over the course of a week. By the time the email arrives, it's the fourth touch from a familiar name, which is as close to a referral as outreach gets.
Use liquid variables for legal specificity, not party tricks
Lemlist is known for personalized images and per-prospect landing pages — and for most industries that playfulness converts. For a law firm, redirect the same machinery toward substance: liquid variables that name the prospect's jurisdiction and the specific obligations attached to it, conditionals that swap copy by company stage, and — if you use Lemlist's per-prospect landing pages at all — a sober one-pager listing the attorney's relevant matters and credentials for that prospect's situation. Skip the meme images and name-on-a-coffee-cup graphics entirely; the personalization a general counsel respects is evidence you understand their legal posture.
Keep every channel inside the bar's lines
Multichannel raises a compliance question single-channel programs don't face: attorney advertising and solicitation rules in many jurisdictions cover written communications broadly, which can include LinkedIn messages, not just email. Apply the same conservative standard to every step — factual statements of experience and credentials, no outcome promises, no pressure — and check whether your jurisdiction requires labeling or record-keeping for outreach to prospective clients before launching. Lemlist's campaign reports double as an activity record of who was contacted, when, and through which channel. Nothing on this page is legal advice about your own compliance obligations.
Typical Relationship-Led Benchmarks (Lemlist + ColdRelay)
| Metric | Benchmark | Notes |
|---|---|---|
| Inbox placement rate | 95%+ | Dedicated IPs and isolated tenants — the email has to land where the LinkedIn groundwork pointed it |
| Reply rate after LinkedIn pre-touches | 4-7% | Connection-accepted prospects reply well above the 2-5% cold-email norm for legal BD; email-only sends to the same lists sit at the bottom of it |
| LinkedIn connection acceptance rate | 25-40% | A real attorney profile with a substantive comment history; bare profiles with no activity land far lower |
| Outbound capacity per mailbox | 2/day | 4 sends/day total per mailbox — 2 outbound + 2 warmup |
| Touches before the first email | 3 | Profile visit, post comment, connection request — spread over roughly a week so the cadence reads as interest, not pursuit |
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 a relationship-led program runs narrow and attorney-anchored, the 10-20 mailbox footprint most firms need keeps this a small line item.
Lemlist is billed separately on its own subscription for the multichannel sequences, LinkedIn steps, liquid personalization, and campaign reports — priced per its current plans, typically per seat.
Infrastructure cost scales with mailbox count; Lemlist's cost scales with seats. The two stack cleanly — one bill for sending capacity, one for the sequencing and engagement software — and the combination costs less per year than the bar-association memberships and event circuit it quietly outperforms.
| 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 multichannel sequences — LinkedIn visits, comments, and connection requests, liquid-personalized emails, and campaign reports. ColdRelay provides the underlying domains, mailboxes, and dedicated IPs that Lemlist's email steps send from. ColdRelay is the infrastructure layer; Lemlist is the sequencing and engagement layer on top — a relationship-led program uses both together.
Should we use lemwarm with ColdRelay mailboxes?
No — and this matters. ColdRelay mailboxes warm continuously as part of each mailbox's send budget: 4 sends/day total, split 2 outbound + 2 warmup, with no waiting period before the first campaign. Running lemwarm on top of that double-warms the same mailbox from two separate networks, which inflates the send count past the budget and produces a traffic pattern that looks automated. Connect the mailboxes, set Lemlist's limit to the 2 outbound sends, leave lemwarm off, and let ColdRelay handle the warmup half.
Do the LinkedIn steps create bar-compliance problems that email alone wouldn't?
They can, if treated casually — many jurisdictions' attorney advertising and solicitation rules cover written communications to prospective clients regardless of channel, so a LinkedIn message can carry the same obligations as an email. The safe posture is to hold every step to the same standard: profile visits and substantive public comments are generally low-risk professional activity, while connection notes and messages should stay factual and conservative, with any required labeling applied. Check your own jurisdiction's rules before launching; nothing on this page is legal advice about your compliance obligations.
Why send the email from a ColdRelay mailbox if the LinkedIn activity comes from the attorney's real profile?
Because the two carry different risks. The attorney's LinkedIn profile builds familiarity and carries no deliverability exposure — but cold email volume from the firm's primary domain would put the reputation of the domain that handles privileged client correspondence at risk. The split gives you both halves safely: the real profile does the relationship work, and the email arrives from a matching attorney name on a ColdRelay secondary domain with dedicated IPs on isolated Azure tenants. The prospect sees one consistent person; the firm's primary domain never touches a cold send.