Live sequence editor for outbound sales teams

The moment a rep realizes their open rates dropped on step 3 of a running campaign — and then discovers they cannot change a single word without killing the sequence and starting over — is when the damage is already compounding. Every day the broken sequence runs, contacts are burning through a cadence that isn't working.

This gap persists because the major AI sales tools are built around a 'compile and launch' mental model borrowed from email marketing, where immutability protects deliverability infrastructure. The vendor's incentive is to keep sequences atomic and simple so their sending pipeline stays predictable. Fixing mid-flight editing requires per-contact state tracking — knowing exactly where each prospect is in the sequence — and that's architecturally messy to bolt onto a system not designed for it. So vendors leave it broken and call it a feature ('prevents accidental changes').

What users actually need: the ability to change a subject line on step 2 and have it apply only to contacts who haven't reached step 2 yet. Or swap out the call-to-action copy across all remaining untouched steps. Or add 15 new contacts directly into step 3 of a running sequence without cloning. Or set variable wait times — 2 days after step 1, 5 days after step 2 — rather than a single uniform interval applied to the whole sequence. None of this exists cleanly today.

This is a business and not a feature because the problem recurs every single campaign cycle. A team running 10 active sequences a month hits this wall constantly — every performance insight they pull from a running campaign is actionable only in the next campaign, not the current one. The cost is real: burned contacts who got the wrong message, wasted sending reputation, and reps doing manual workarounds like individually emailing prospects outside the sequence to course-correct.

What to build

Build a sequence management layer — deployable as a standalone web app with API connectors to common sales engagement tools — that tracks per-contact step state and allows edits to message copy, subject lines, and step timing on live sequences, applying changes only to contacts who haven't yet passed the edited step.

Where to start

Start with teams already exporting sequence activity data to a CRM like HubSpot or Salesforce — where per-contact step history is already logged — and build the state-tracking layer on top of that existing data rather than fighting the native tool's API.

The hard part

Getting real-time per-contact sequence state out of existing tools via API is the hard part — most APIs expose aggregate sequence stats, not per-contact step position, so you may have to reverse-engineer this from activity logs, which is fragile and vendor-specific.

How it makes money

Per seat per month, targeting SDR managers rather than individual reps — one license covers the manager who edits sequences, with a lower-cost view-only tier for reps who just need to see sequence status.