Sequences for email and LinkedIn. Researched, personalized, multi-step, written per lead against the signal that fired, and pushed to Instantly or HeyReach.
Not every buyer lives in their inbox. The runtime routes each lead to its channel: sequences written for email push to Instantly, sequences written for LinkedIn push to HeyReach. And written FOR the channel matters: a LinkedIn touch is not an email with the subject line deleted. Different lengths, different openings, different asks, same grounding in your profile, thesis, and persona.
Nothing here is a model freestyling. Each part of the email executes a specific piece of your config. Here is the mapping.
The dissection below is an email; the same mapping writes the LinkedIn version with the channel's own prompts.
The signal that fired (competitor detected, hiring spike, funding round) and the argument you attached to it.
Fresh research on the company and contact, run before a word is written. Actual reading, not enrichment fields.
The CFO hears cost. The ops lead hears workflow. The lead is matched to a persona you defined, and the email argues that persona's case.
Built once through a guided interview. The prompts that shape your voice are yours to read and edit, not a black box.
You decide what the email asks for. We just make sure the three lines above it earn the ask.
Most AI outbound generates each touch in isolation, which is why the follow-up cheerfully re-introduces the product the first email already pitched. Distrosauce writes the sequence as one play: the opener makes the argument, the follow-ups advance it, the last step earns the ask. If a lead replies, the sequence stops. Nobody gets email four after answering email two.
Every sequence lands in your approval queue before it goes anywhere, reviewable in the app or straight from Slack. Edit anything. Here is the part nobody else measures: your edit rate is the quality metric. Teams start by editing everything. The percentage falls. When you have not touched a sequence in weeks, autopilot stops feeling like a leap and starts feeling overdue.
Real artifacts. Some published whole, some redacted. Prose untouched either way.
The thesis that fired, shown beside the sequence it produced.
Your domains, your warmup, your sending rules, your inbox. Distrosauce writes; Instantly and HeyReach send; replies land where they always did. Nothing about your sending infrastructure changes, which means nothing about your deliverability changes either.
Fed by social listening (promoted posts arrive as signals) and feeding ABM (the account that replies big becomes a brief). See the loop