Stop reporting pipeline. Start reporting movement.

Pipeline is a snapshot: how much is in the funnel right now. Movement is a delta: what changed since the last time anyone looked. Most reviews we sat through reported the snapshot and called it analysis. The teams that actually changed behaviour week to week were reporting the delta instead.

A snapshot answers the wrong question

“We have $840,000 in pipeline” tells you almost nothing about what to do this week. Was it $840,000 last week too? Did $200,000 of it just get added and $180,000 quietly slip a stage? The total can sit still while the underlying accounts churn through it constantly. A snapshot flatters a team that’s treading water, because treading water looks identical to standing still from a distance.

Presenting movement in a meeting

Movement presents better as a short list of named changes than as a chart. “Meridian moved from evaluation to negotiation. Two accounts slipped a stage. One new account entered at $40,000.” That’s four sentences and it tells the room everything a pipeline total was hiding.

The three deltas worth showing

• Stage delta: which deals moved forward or backward a stage since last week, named individually.

• Value delta: how much the total changed, split into new, expanded, and lost, rather than one net number.

• Age delta: which deals have sat in the same stage longer than your median time-in-stage for that stage.

What to do when the delta is noise

Not every week has a meaningful delta, and that’s fine. The mistake is manufacturing significance out of a quiet week: reading three stage changes as a trend, or treating one late renewal as an emerging pattern. If nothing crossed a threshold you set in advance, say so and move on. A short meeting because nothing happened is a better outcome than a long one built to justify its own existence.

We run this with Zevara pulling the week-over-week stage and value changes automatically, so nobody is manually diffing two exports of the same CRM view before the meeting starts.

A pipeline total is a photograph of a moving car. The delta is the speedometer. Only one of them tells you whether to brake.

Snapshots aren’t useless — they’re the right tool for a board deck, where the audience wants one number and a trend line. The mistake is using the board’s number in the team’s own weekly meeting, where the goal isn’t to summarize the quarter but to catch what happened since Tuesday.

The age delta is the one teams resist most, because it points at deals people are still hoping will close. A deal sitting in “negotiation” for ninety days when your median is three weeks isn’t necessarily dead, but it deserves a specific question — what has to happen for it to move — rather than another week of being carried forward unexamined.

We’ve also found that value delta hides more when reported as one net figure. A pipeline that grew by $50,000 net might be $300,000 in new deals minus $250,000 lost, or it might be $60,000 in new deals minus $10,000 lost. Those are different businesses wearing the same headline number.

Most teams that make this switch report the same surprise: the delta view takes less time to prepare, not more, because there’s no need to recompute a total from scratch every week. It only requires storing last week’s numbers alongside this week’s, which any connected system already does automatically. That’s the whole trick.

Teams new to this approach sometimes ask what happens when there is no delta at all for several weeks running. That’s useful information too — a pipeline that isn’t moving in either direction is its own signal, usually pointing at a stalled top of funnel rather than a healthy plateau.

We’d rather a team walk out of a ten-minute meeting having confirmed nothing changed than sit through forty minutes of a snapshot dressed up to look like progress. The shorter meeting is not a consolation prize; it’s the more honest one. Track how many consecutive weeks a deal has produced zero delta, and treat a high count as its own flagged item, the same way you’d flag a silent account.

Report the total once a quarter for the board. Report the delta every week for the team. They answer different questions, and only one of them is useful on a Monday morning.