Beta

Pipeline Velocity Monitor

Reads your deal stage history and classifies every backward move as healthy re-qualification (the economic buyer or stakeholder changed) or unexplained regression, then flags deals stalled past a time-in-stage threshold, deals with no decision deadline on record, and false reactivations, a deal that sat quiet past that same threshold and finally moved again with no new evidence attached. A stage snapshot shows where a deal sits. This shows why it got there, and whether it actually came back to life.

Any CRM

The problem

A deal moving backward in stage looks the same on a dashboard whether the buyer changed or the deal is quietly dying, and a stalled-deal flag clears the moment any activity happens, whether or not that activity actually meant anything.

How it works

01Reads deal stage history for every backward move
02Classifies each one as healthy re-qualification or unexplained regression based on whether the economic buyer or stakeholder changed
03Flags deals stalled past a time-in-stage threshold and deals with no decision deadline on record
04Flags false reactivations: a deal that sat quiet past that same threshold, then finally moved, but with no new economic buyer update or decision deadline attached to that move

Tested against known answers

Pipeline Velocity Monitor

A synthetic deal stage-history export: 5 deals, including one healthy re-qualification, one unexplained regression, two stalled deals, and one closed-won deal used to check the tool correctly excludes closed deals from open-pipeline flags. Extended separately with 3 deals testing the false-reactivation check: one that went quiet then resumed with no evidence, one that resumed with a real economic-buyer update, and one clean backward move used to confirm the new check never fires on a move already classified as a regression.

1/1

Healthy re-qualifications caught

1/1

Unexplained regressions caught

2/2

Stalled deals caught

1/1

False reactivation correctly caught

→Correctly classified a deal that moved from Proposal back to Discovery as healthy re-qualification because the economic buyer changed, and a separate deal that moved from Negotiation back to Evaluation as an unexplained regression because the buyer field stayed identical.
→Flagged both deals sitting past the 30-day stale threshold, one at 41 days, one at 36, while correctly leaving a deal at 21 days in its current stage unflagged.
→Left the closed-won deal out of every stalled and missing-deadline flag despite it having no decision deadline on record and its last stage entered 60 days ago, since closed deals aren't open-pipeline risk.
→Correctly flagged a deal that sat quiet for 50 days and then moved with no economic buyer or decision deadline attached, while correctly leaving a second deal unflagged that went quiet the same way but resumed with a real buyer update on record.

Zero false positives across a clean deal, a closed deal, and both regression types in the same test set. The deal that came back from silence with real evidence and the one that came back with nothing but a reply looked identical on the stalled-deal list, and only the false-reactivation check told them apart.

See the full test run →

Questions about Pipeline Velocity Monitor

What counts as a healthy re-qualification?

A backward move tied to a real change, like a new economic buyer or stakeholder, not just a stage bumped back with no reason on record.

Does it flag closed deals as stalled?

No, closed deals are excluded from open-pipeline risk flags entirely.

What is a false reactivation?

A deal that went quiet past the stale-days threshold and then finally showed activity, clearing the stalled flag, but the move itself carried no evidence, no economic buyer update, no decision deadline. The silence broke, but nothing about the deal was actually shown to have changed.

Runs against your CRM using your own credentials, through your own AI instance. We don't copy, store, or retain your data.

Deploy this in your CRM