9h • General discussion
Write the Stop Rule Before the Start Rule
Command note: Every automation knows how to begin. Few know how to end.
A start rule says when something fires. A stop rule says when it must never fire again. Write the stop rule first, and most runaway workflows never get built.
Where stop rules matter most:
• Follow-up sequences that should end when the lead replies
• Reminders that should end when the appointment is booked
• Win-back campaigns that should end after a set number of touches
• Anything that sends, charges, or assigns on a repeat
Do it now:
1) Pick your three longest-running workflows
2) For each, write one sentence: "This stops when ___."
3) Check that the exit condition exists in the workflow, not just in your head
4) Add a cap on total sends or total days as a backstop
5) Test the stop on a single contact before you publish
If you cannot finish the sentence in step 2, that workflow is not ready to run. That is also the fastest way to find the ones already running without a brake.
AI makes it easy to build the start in minutes. That speed is exactly why the stop has to be written down first.
A workflow without a stop rule is not automation. It is a loop with a budget.
0
0 comments
Write the Stop Rule Before the Start Rule
Suggested communities
Powered by