Logistics Outbound, Run Through Lemlist
Open the inbox of any logistics manager at a mid-size manufacturer and you'll find the same email fifteen times: 'we have capacity on your lanes, can we earn a shipment?' It's not that the pitch is wrong — it's that nothing in it proves the sender knows anything about this shipper. The email that gets answered is the one that names the prospect's actual shipping profile: where their freight originates, what their product category demands from a carrier, what's happening to rates on the corridors they ship.
That level of specificity at volume is exactly what Lemlist's liquid syntax was built for — one template, rendered differently for every prospect from the data in your list. Add Lemlist's LinkedIn steps to reach ops managers in the long quiet stretch between RFP cycles, and you have an outbound motion built on fluency rather than volume. ColdRelay is the layer underneath: the secondary domains, mailboxes, and dedicated IPs that Lemlist's email steps actually send from. This guide covers how logistics teams wire the two together.
Why Run Lemlist on ColdRelay Infrastructure
Lemlist's strength is making one campaign read like a hundred hand-written emails: liquid syntax variables render per-prospect lines from your list data, conditional logic swaps whole sentences based on what you know about each shipper, and personalized images and landing pages extend that customization beyond text. Its multichannel sequences add LinkedIn visits, connections, and comments alongside email — useful in freight, where ops managers ignore cold email from strangers but respond to names they've seen before. What Lemlist doesn't do is provision the domains and mailboxes its email steps send from. In logistics that infrastructure layer carries unusual weight, because your operating domain also moves rate confirmations, BOLs, and carrier communications that can never be exposed to prospecting risk.
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, with no warmup waiting period before sending — warmup runs continuously as part of each mailbox's 4 sends/day budget (2 outbound + 2 warmup). ColdRelay supports 100-150 mailboxes per domain, so a brokerage's full pool typically fits on one or two secondary domains.
The pairing is additive, not competitive: ColdRelay is the infrastructure, Lemlist is the personalization and sequencing layer on top. You keep Lemlist's liquid variables, personalized images, LinkedIn steps, and campaign reports — you just point the email steps at mailboxes built to land. One note: skip lemwarm for these mailboxes. ColdRelay handles warmup on its side as part of the 4/day budget, and double-warming the same mailbox from two systems creates sending patterns you don't want.
Visit Lemlist →Connecting ColdRelay Mailboxes to Lemlist
Provision mailboxes on ColdRelay
Pick secondary domains adjacent to your brand but separate from the operating domain your shippers and carriers know. Shipper-profiled campaigns run tighter lists than generic blasts, so most brokerages start with 30-80 mailboxes — well within ColdRelay's 100-150 mailboxes per domain. Everything provisions on isolated Azure tenants with dedicated IPs in about an hour, with SPF, DKIM, and DMARC already configured and no warmup waiting period before you can send.
Connect the mailboxes in Lemlist — and skip lemwarm
From the ColdRelay dashboard, export your mailbox list with SMTP/IMAP credentials and add each one in Lemlist under email accounts. Set each mailbox's daily sending limit in Lemlist to 2 outbound emails per day, mirroring ColdRelay's per-mailbox budget of 4 sends/day total (2 outbound + 2 warmup). Don't enable lemwarm on these accounts: ColdRelay's warmup already runs continuously as half of that 4/day budget, and warming the same mailbox from two systems at once works against you.
Build the shipper-profile columns before you build the campaign
Liquid variables are only as good as the list behind them, so structure your CSV with a column per profile fact: origin region (where their plants or DCs actually sit), product category and what it demands (temp control, tarping, hazmat paperwork), primary mode, and a rate-context note for the corridors they ship. Fifteen minutes of research per account, captured as structured columns, is what turns one template into a hundred emails that each sound researched.
Write one template with liquid syntax doing the heavy lifting
In the Lemlist campaign builder, write the email once and let liquid variables render the specifics: an opening line built from the origin-region and product-category columns ('moving temp-controlled dairy out of the Wisconsin plants'), and a conditional rate-context sentence that only renders when the column is filled — with a fallback that stays specific rather than collapsing into 'we have great rates.' Every variable should pass one test: could a competitor send this exact sentence to this exact shipper? If yes, it's not done.
Add LinkedIn steps and personalized assets, then launch
Use Lemlist's multichannel sequence builder to wrap the email in LinkedIn touches — a profile visit before the first email, a connection request after it, a comment on the prospect's company post mid-sequence — so the ops manager has seen your name twice before the second email lands. For the largest accounts, attach a personalized image or per-prospect landing page that names their company and the corridors you're proposing to cover. Launch, then watch Lemlist's campaign reports for which profile columns correlate with replies and deepen the research where it pays.
The Logistics Lemlist Playbook
Research the shipper once, render it everywhere
The unit of work in this motion isn't the email — it's the shipper profile. Capture each prospect's origin region, product category, mode requirements, and lane rate context as structured list columns, and let Lemlist's liquid syntax render them across every step of the sequence: first email, follow-up, even the connection-request note. One research pass per account powers four or five touches that each read hand-written.
Make the rate-context line do the credibility work
Nothing proves freight fluency faster than naming what's happening on the prospect's corridors: 'outbound rates from the Southeast are up on produce season pressure' tells a Georgia shipper you watch their market, not just your own. Maintain a short rate-context note per origin region — a sentence, refreshed every few weeks — and merge it through a liquid variable. It's one column to maintain, and it's the line prospects quote back in replies.
Use LinkedIn steps to be a known name before the RFP opens
Most shippers award lanes during a bid cycle and ignore carrier pitches the rest of the year — which is exactly why the quiet months matter. Run Lemlist's LinkedIn visit, connect, and comment steps against ops managers between cycles, when there's no ask on the table and accepting a connection costs them nothing. When their routing guide opens, your bid invitation comes from a familiar name instead of a cold inbox — and the liquid-personalized email you send that week lands as a continuation, not an interruption.
Engineer the fallbacks as carefully as the variables
A liquid variable with no fallback is a loaded gun: one blank column and the prospect sees the template behind the curtain — or worse, raw syntax. Write a deliberate fallback for every variable, and make the fallback specific to the segment rather than generic: if the rate-context column is empty, fall back to a mode-level line ('reefer capacity heading into Q3'), not 'we'd love to help with your shipping needs.' Then sort Lemlist's preview by your sparsest column and read the worst-case render before launch — the email your least-researched prospect receives is the real quality bar of the campaign.
Typical Logistics Outbound Benchmarks (Lemlist + ColdRelay)
| Metric | Benchmark | Notes |
|---|---|---|
| Inbox placement rate | 95%+ | Dedicated IPs and isolated tenants outperform shared Google/Microsoft pools |
| Reply rate on shipper-profiled copy | 3-6% | Liquid-rendered origin, product, and rate-context lines; template-only freight pitches sit at 1-2% |
| LinkedIn connection acceptance from ops managers | 25-35% | Visit-then-connect steps between RFP cycles, with a note that names their freight, not your service |
| 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 list research, not the infrastructure, is the long pole |
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 because shipper-profiled campaigns trade raw volume for relevance, most teams start with a smaller pool than a blast-style operation would need.
Lemlist is billed separately on its own per-seat plans, which cover the campaign builder, liquid syntax personalization, personalized images and landing pages, multichannel sequences with LinkedIn steps, and campaign reports.
Infrastructure cost scales with mailbox count; Lemlist's cost scales with seats. The two stack cleanly — one bill for sending capacity, one for the personalization and sequencing on top — and skipping lemwarm means you're not paying twice for warmup either.
| 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 of the same stack. Lemlist handles the personalization and sequencing: liquid variables, personalized images and landing pages, LinkedIn steps, and campaign reports. ColdRelay provides the underlying domains, mailboxes, and dedicated IPs that Lemlist's email steps send from. Logistics teams use them together: Lemlist on top, ColdRelay underneath.
Should I turn on lemwarm for my ColdRelay mailboxes?
No. ColdRelay mailboxes warm continuously on ColdRelay's side — 2 warmup sends/day per mailbox as part of the 4/day budget (2 outbound + 2 warmup) — so there's no warmup waiting period and nothing for lemwarm to add. Running two warmup systems against the same mailbox creates overlapping send patterns you don't want; leave Lemlist pointed at outbound campaign sends only.
What data do I actually need per shipper to make liquid variables work?
Four columns cover most of it: origin region (where their plants or distribution centers sit), product category and its mode demands (temp control, tarping, hazmat), primary mode, and a short rate-context note for the corridors they ship. That's roughly fifteen minutes of research per account from their website, import records, or LinkedIn — and because Lemlist renders the same columns across every step of the sequence, one research pass powers the whole campaign. Always pair each variable with a segment-specific fallback so a blank cell never exposes the template.
Do Lemlist's LinkedIn steps count against my mailbox sending budget?
No. The 4 sends/day per mailbox budget (2 outbound + 2 warmup) applies to email only. LinkedIn visits, connection requests, and comments run through the LinkedIn account connected to Lemlist, on Lemlist's own activity limits. That's part of why the multichannel approach suits the per-mailbox math: LinkedIn touches build familiarity with ops managers between RFP cycles without spending a single email send, so your 2 daily outbound emails per mailbox land on prospects who already recognize the name.