Pipeline stages that move themselves
If your team drags cards, your board is a to-do list with extra steps. Stages should advance on events, and every stage needs an answer to "what moves it, and what if nothing does?"
6 min read
The test for a good stage
A stage is well designed when you can answer two questions about it without thinking: what event moves a card in, and what happens if nothing happens for a week.
If the answer to the first is "someone notices", the stage will always lag reality. If there's no answer to the second, that stage is where your pipeline silently dies.
A default set for a services business
Six stages cover most businesses. Fewer is usually better than more.
- 01New enquiry — entered by form submission, ad lead or inbound call.
- 02Qualified — entered when the qualification criteria are met, automatically where they're structured.
- 03Call booked — entered by a calendar booking event.
- 04Call attended — entered by appointment status, not by hand.
- 05Proposal out — entered when the proposal is sent, ideally from the same system that sends it.
- 06Won / Lost — entered by deposit or by a lost reason being recorded.
Wiring the triggers
Each transition needs a real event. Form submitted, appointment status changed, payment received, tag applied by a scoring step. Where no event exists, create one — a button that a salesperson presses is still an event, and still beats dragging.
The silence rule
Every stage gets a maximum age. When a card exceeds it, something must happen: a follow-up fires, the owner gets a nudge, or the card moves to a holding stage with a reason.
This single rule surfaces more lost revenue than any new campaign, because it makes forgetting impossible rather than unlikely.
Exit conditions belong with the stage
Sequences attached to a stage must stop when the card leaves it. Reply, booking, opt-out, stage change — all four should end the cadence. Chasing someone who already booked is worse than not chasing at all.