Stale-deal alerts
Every stage gets a staleness threshold: three days in "New enquiry", seven in "Quote sent", fourteen in "Negotiation". A daily workflow checks the time since the last stage change and, when a deal crosses its threshold, creates a task for the owner and posts a short alert to the manager's channel with the deal name, value and days stale. Nobody has to remember to look; the pipeline tells them.
Automatic stage moves
Reps should rarely drag a deal by hand. A booked appointment moves it to "Survey booked". Opening the quote email three times moves it to "Engaged". A signed proposal moves it to "Won". Manual moves stay possible, but the default is that customer behaviour drives the board, which keeps it accurate even on a busy week.
Automated moves should only go forward. A deal that's "Won" must never bounce back to "Quote sent" because someone re-opened an old email. Add a condition on each move: only if the current stage is earlier than the target.
Tasks from behaviour
A task queue full of "follow up" items nobody trusts is worse than none. We create tasks only from events: a quote opened but not accepted after 48 hours, a reply that contains a question, a form filled in twice. Each task has a due time and a one-line reason ("Opened quote 3 times, no reply"). Reps clear them because they're relevant.
The weekly summary
Every Monday at 8am a workflow emails the owner five numbers: new deals last week, deals moved forward, deals gone stale, pipeline value by stage, and the three biggest deals with no activity in seven days. It takes ninety seconds to read and it replaces the hour-long pipeline meeting. When the numbers look wrong, that's the conversation to have.
Hygiene rules
Two rules keep the pipeline believable. A lost reason is required to move a deal to "Lost", captured as a dropdown so it can be reported on. And any deal with no activity for ninety days is closed automatically as "Lost: went quiet", with a gentle re-engagement message and a tag so it can be revived if the customer reappears. A pipeline with realistic numbers is one people will actually use.
Key takeaways
- Define "stale" per stage in days, and alert the owner and manager when a deal crosses it.
- Let behaviour move deals: a booked survey, an opened quote, a signed document.
- Create tasks from what the customer did, not from a calendar. Fewer tasks, all relevant.
- A Monday summary with five numbers replaces the pipeline review meeting.
- Require a lost reason and close deals automatically after a long silence, so the pipeline stays believable.