Beta

Pipeline Momentum Monitor

Compares recent stage velocity and forward-conversion rate against the window before it from a single stage-history export, and flags when a blended conversion number looks stable only because it is propped up by an earlier, stronger period while the most recent window has already turned over.

Any CRM

The problem

A pipeline dashboard reports one number for right now. It can hold steady, or even look healthy, for weeks after the underlying motion has already started to decay, because a blended average across the whole export gets propped up by an earlier, stronger period.

How it works

  1. 01Reads a single stage-history export and splits its transitions into a recent window and the window immediately before it
  2. 02Computes median time-in-stage and forward-conversion rate separately for each window
  3. 03Flags deceleration when recent velocity has slowed or recent conversion has dropped past a threshold
  4. 04Flags a divergence specifically when the full-export blended conversion rate still looks fine while the recent window on its own has already turned over

Verified on real test data

Pipeline Momentum Monitor

An 84-row synthetic stage-history export: a strong 10-week early period across two segments, then a recent 3-week window where Mid-Market held steady but Enterprise stalled and slipped backward, plus a thin-history case and a genuinely stable case run separately to confirm the tool never flags a trend that isn't there.

Yes

Deceleration correctly caught

Yes

Divergence correctly flagged

Enterprise

Declining segment isolated

  • Correctly computed a blended forward-conversion rate of 87.9% across the full export, while the most recent 21-day window on its own had already fallen to 64.7%, the exact "headline still looks fine" pattern the tool exists to catch.
  • Correctly isolated Enterprise as the segment losing momentum, a drop from 100% to 33.3% forward-conversion between its own prior and recent windows, while Mid-Market stayed healthy in the same period.
  • On a separate thin-history export (3 transitions), correctly reported insufficient_history instead of fabricating a trend, and on a separate genuinely stable export, correctly reported no deceleration and no divergence.

The full-export number said conversion was fine. The most recent three weeks, on their own, said otherwise, and the tool caught the gap between the two instead of reporting only the reassuring one.

See the full test run →

Questions about Pipeline Momentum Monitor

Do I need multiple saved snapshots over time to run this?

No. One stage-history export already carries a timestamp on every transition, so the recent-versus-prior comparison is reconstructed from that single pull, not from comparing two separate exports taken weeks apart.

How is this different from Pipeline Velocity Monitor?

That tool reads the same kind of export and answers a point-in-time question: is this specific deal stalled right now, was this backward move healthy. This tool doesn't look at individual deals at all, it compares the pipeline's aggregate motion in the most recent window against the window before it.

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