Deal Sequence Automation with Task-Gated Blocking: A Cadence That Waits for the Human Step

A sales cadence exists to make sure a deal gets a consistent sequence of touches instead of whatever a salesperson remembers to do that week. But a cadence that fires its next automated step on a fixed timer, regardless of whether the previous step's human task was ever actually done, produces exactly the failure mode it was meant to prevent: a follow-up email that references a call that never happened, sent with total confidence, to a contact who now has good reason to distrust the next message too.

A purely timer-driven cadence is easy to build precisely because it never has to check whether anything actually happened — it just waits a fixed number of days and moves on regardless. Making a step genuinely wait on a human action means the system has to create a real, trackable task tied to that exact sequence and that exact step, hold the sequence in a paused state rather than advancing it, and then reliably detect the moment that specific task — not just any task on the deal — gets marked done, without double-advancing if two people mark it done at once or a duplicate task exists for the same step.

A sequence is a form-based list of steps — wait, send a message, create a task, or add a timeline note — configured once and reused across deals, with no drag-and-drop canvas to build. A deal enters a sequence three ways: manually, from a dialog on the deal itself; automatically the instant a new deal is created, if a sequence is configured to trigger on deal creation; or automatically the instant a deal moves into a specific pipeline stage, if a sequence is configured to trigger on that stage — both auto-enroll paths run off real database triggers on the deal record, confirmed directly in the migration that defines them, and both refuse to double-enroll the same deal into the same sequence twice.

A background dispatcher checks every five minutes for enrollments due to run their next step. A "wait" step and a timeline-note step execute immediately and move the sequence forward on their own. A message step is queued for a separate, atomic sender that renders real deal data — contact name, company, owner, deal value, deal title — into the message template and delivers it by email when the organization has a sending account configured and the contact has an email on file, logging the message either way rather than losing it silently if delivery conditions are not met. A task step is different by design: it creates the task — a call, a meeting, or a generic follow-up — links it to that exact sequence and that exact step, and then holds the sequence there, doing nothing further, until a database trigger on that task's own completion resumes precisely the step it was blocking. If a deal is marked won or lost while a sequence is still running against it, any active enrollment for that deal is automatically canceled — a closed deal stops receiving cadence steps meant for one still open.

A deal enters a "new opportunity" pipeline stage and is auto-enrolled into a three-step sequence: an introductory email, a follow-up call task two days later, and a proposal-reminder message a week after that. The email step queues, renders the contact's name and the deal's value into the template, and sends. Two days later the dispatcher reaches the call step, creates a task — "Follow-up call — step 2" — assigned to the deal's owner, and stops the sequence right there. The reminder message does not go out on schedule regardless; it waits until the salesperson actually marks that specific call task done, at which point the sequence resumes and schedules the reminder for the configured delay after that.

A cadence stops assuming a human step happened just because a clock ran out, and starts actually waiting for it — closing the exact gap where an automated follow-up used to reference work that was never done. Deals can enter the right cadence automatically based on what actually happened to them (being created, reaching a stage) instead of relying on someone remembering to enroll them by hand, and a closed deal stops accumulating cadence steps meant for one still in play.

This is a newly activated engine — confirmed running end to end in production for the first time on 2026-09-01, after two stacked structural bugs (an org-wide dispatcher that had been a stub doing nothing, and a helper function present in the source but missing from the live database) were found and fixed. A team looking for a feature with a long, proven production history should weigh that recency honestly rather than assume otherwise. This is also a different mechanic from Centriu Axis's Checkpoint feature, which is manual outcome logging with cadence follow-up surfaced to a salesperson, not an automated multi-step engine that executes and blocks on its own — the two should not be confused.

A cadence that advances its next automated step purely on a schedule has no way to know whether the human step it was supposed to follow actually happened, and eventually sends a message that contradicts reality. Centriu Orbit's task-gated steps instead create a real, trackable task and hold the entire sequence at that exact point until the task is genuinely marked done — trading a small amount of automatic speed for the much larger reliability of never assuming completed work that was not.