Bulk Cold-Outreach Sequences: Personalized, Nothing Made Up

4 cold sequences, validated and exported for Instantly

Summary

Lead prep. 6 rows in, 4 ready to draft, 2 excluded:

prep_leads: 6 rows -> 4 ready, 2 excluded  [leads.csv, encoding utf-8-sig]
  mapped: Email Address->email, FirstName->first_name, LastName->last_name, Organization->company, Job Title->title, Industry->industry, LinkedIn URL->linkedin, Recent News->trigger
  excluded: 1 duplicate email, 1 invalid email syntax
  tiers: A 4 (specific signal) | B 0 (company+role/industry) | C 0 (thin)

The duplicate was a second Dana Osei row (same address, different capitalization); the invalid one was lee.park@parkline. All 4 leads have a specific signal, so every step 1 opens on it.

Sender brief, confirmed. Alex Rivera, Founder, Lanternway Ops. Offer: "Lanternway turns how your best operators already work into written, trainable playbooks." These three proof points are the only results any email is allowed to state:

• Helped a two-site 3PL cut new-site ramp-up from 10 weeks to 6
• Documented 40+ ops procedures for a 120-person logistics company in 30 days
• New CS hires at a Series B SaaS client reached full ramp in 5 weeks instead of 9

Cadence: day 0 (PAS), day 3 and day 10 (AIDA), follow-ups as replies in the step-1 thread. A CA/US compliance footer goes in every body.

Validation, round 1:

WARN lead_northwind_robotics (Northwind Robotics) - 0 fail, 2 warn
  WARN s1  grounding   names not in lead row/brief: Nevada
  WARN s1  length      103 words (aim <= 100)
WARN lead_coastal_freight_co (Coastal Freight Co) - 0 fail, 1 warn
  WARN s2  personal    only 1/4 sentences tied to this lead
WARN lead_bright_path_health (Bright Path Health) - 0 fail, 1 warn
  WARN s2  personal    only 1/4 sentences tied to this lead
RESULT: PASS - 4 leads / 12 emails, 0 FAIL, 4 WARN (1 leads clean)

"Nevada" isn't in Dana's row, so I cut it and tightened the paragraph, which also fixed the length. In the same pass I removed two specifics no row supports: "two or three senior dispatchers" (Coastal) and "a CS team doubles after a raise" (Fielder).

Validation, final:

WARN lead_coastal_freight_co (Coastal Freight Co) - 0 fail, 1 warn
  WARN s2  personal    only 1/4 sentences tied to this lead
WARN lead_bright_path_health (Bright Path Health) - 0 fail, 1 warn
  WARN s2  personal    only 1/4 sentences tied to this lead
RESULT: PASS - 4 leads / 12 emails, 0 FAIL, 2 WARN (2 leads clean)

The two step-2 warnings are yours to call: both emails name the company and stay on its own expansion (Coastal's state-line handoff, Bright Path's patient intake). Warnings don't block export.

Sequence: Dana Osei, VP Operations, Northwind Robotics

Signal: "Opened a second fulfillment center in Reno last quarter". Proof point: the two-site 3PL result, verbatim from the brief.

Step 1, day 0 (PAS). Subject: Reno site playbooks

Hi Dana,

Congrats on getting the Reno fulfillment center open last quarter. Second sites usually run on whatever the first site's best leads carry in their heads, and that knowledge doesn't travel on its own.

It tends to surface as pick and receiving errors the original site solved long ago.

Lanternway turns how your strongest ops people already work into written, trainable playbooks, so a new site ramps on process instead of on phone calls. We helped a two-site 3PL cut new-site ramp-up from 10 weeks to 6.

Open to a 20-minute call next week?

Alex Rivera
Lanternway Ops

123 Example St, Suite 400, Vancouver, BC V6B 0A1, Canada | alex@lanternway.example
Not relevant? Reply "no" and I won't email again.

Step 2, day 3 (AIDA), reply in thread

Hi Dana,

One more thought on Reno. The fastest second-site ramps I've seen start with the five or six processes where a mistake costs the most, usually receiving and returns, and write those down first rather than documenting everything.

If it helps, I can share the short checklist we use to pick those processes for a robotics fulfillment operation like Northwind's.

Worth a look?

Alex Rivera
Lanternway Ops

123 Example St, Suite 400, Vancouver, BC V6B 0A1, Canada | alex@lanternway.example
Not relevant? Reply "no" and I won't email again.

Step 3, day 10 (AIDA), reply in thread

Hi Dana,

Last note from me. If Reno is running smoothly already, ignore this. If the second site still leans on calls back to the original team, that's the pattern Lanternway fixes, and I'd be glad to walk through how.

Either way, good luck with the ramp-up.

Alex Rivera
Lanternway Ops

123 Example St, Suite 400, Vancouver, BC V6B 0A1, Canada | alex@lanternway.example
Not relevant? Reply "no" and I won't email again.

The other 9 emails (Fielder Analytics, Coastal Freight Co, Bright Path Health) are in the review file.

Export

wrote export_instantly/sequences_import.csv (4 rows, 11 columns, tool=instantly, newlines=br)
wrote export_instantly/sequences_review.md
note: thread_replies is on - step 2+ have no subject column; leave those subjects EMPTY in the tool
note: step day columns are for reference; set the delays on the sequence steps in the tool

A tool-neutral copy (plain newlines) is in export_generic/.

Next steps

Read sequences_review.md and decide on the two step-2 warnings: keep them, or have me add a lead-specific line to each.
2.

Set up Instantly: import the CSV and map the Step columns as custom variables. Leave the step 2 and 3 subjects empty so they send as replies, and set the step delays to match day 0 / 3 / 10.
3.

Lee Park (Parkline Labs) was dropped for the invalid address. Send a corrected email and I'll run that lead through the same checks.