Outcome. Every deal carries a running count of how many times it has changed pipeline stage, so reporting can flag deals bouncing back and forth instead of moving steadily forward.
flowchart TD
A[Deal stage changes] --> B[Increment deal_stage_change_count by 1]

When to use it, when not to
- UseUse it to surface deals that keep moving backward and forward between stages, a sign of an unclear process, a stuck negotiation, or bad data hygiene, rather than progressing.
- UseUse it as an input to a deal-health score alongside time-in-stage and days-since-last-activity properties.
- SkipDo not use it if the goal is simply how long a deal has been in its current stage. That is a duration question this counter does not answer. Pair with the stage-entry timestamp properties from reporting-alerts-002 for that.
- SkipDo not use it on a portal with several pipelines with very different stage counts without deciding first whether the counter should reset when a deal is moved between pipelines, see Known pitfalls.
or the reporting and alerts pack, 39 EUR
One-time, excl. VAT. 30-day refund, no questions asked. Founding prices until 31 October, then 199 and 59 EUR. Includes every spec added later, up to the full 500, and the one-click installer on the full library. Building on client portals? The agency licence at 449 EUR covers unlimited client portals.





