Skip to content
GuidePipelineIntermediate

Working the Pipeline report

Where pipeline comes from, how it moved, and how it closed: the reports that make a weekly pipeline review something other than a spreadsheet.

RRRevTech RevOpsRevenue operations team 5 minUpdated
Part 1 of 5

Three questions, four reports

Pipeline answers the three questions every RevOps cadence has to answer. Pipeline Source: where is pipeline coming from. Pipeline Movement: how did it change this period, and why does this quarter look different from last. Then the outcome half, which the product splits into two reports rather than one — Won Deals and Lost Deals: how is it actually closing.

Each is a standalone report with its own card on Reporting and its own route, so the agenda is a set of links rather than a page you scroll. Used that way it is a thirty-minute review with a defensible shape: generation health, then in-quarter mechanics, then outcomes. Set fiscal year, quarter and team first in each; every card and chart reflects the active scope.

The Pipeline category holds more than these four. Deal Risk, Slippage & Aging and Pipeline Hygiene find the deals that need a conversation, and have their own guide. New Pipeline Created shows what was created in the period, and My Pipeline is where reps update their own deals. Weekly Change Log, in the Forecast category, is the "what changed" read that opens most pipeline reviews.

Part 2 of 5

Pipeline Source is an investment decision

Pipeline Source puts Total Pipeline, Win Rate, Avg. Time to Close and Velocity together, then breaks them out by source. Source quality plots each source's win rate against its average sales cycle, sized by open pipeline, and Source detail lists them with win rates well above or below the period's rate highlighted. That combination is the reason to come here. Volume alone tells you where pipeline came from, and volume with win rate and cycle tells you where the next generation dollar should go.

The trap it is built to expose: a source producing a large share of pipeline amount at a win rate below your average is manufacturing coverage, not revenue. It looks like strength on a volume chart and costs you a quarter when the deals do not close. Two limits to keep in mind: sources are the CRM's lead source, and cycle times count from when RevTech first synced a deal rather than from the CRM's own created date.

Part 3 of 5

Pipeline Movement is the weekly review

The Pipeline bridge on Pipeline Movement is the single most useful object in the report. Read it left to right: the starting pipeline, what was added and pulled in, what was pushed out, won and lost, net amount changes, and the current open book. That sequence is your weekly agenda, already ordered. Where the pipeline went draws the same flow as a picture of what came in and where it went.

Then do the thing that separates a review from a readout: click the largest red bar. Clicking a bar filters the Deals that moved table beneath the charts to that step, with the largest pipeline impact first, and every row opens its deal. A push-out figure is a statistic; the deals inside it are a conversation with names attached. The table's own filter panel narrows further, by movement step, owner, amount and close date.

Read the ends of the bridge with care. The end is the current open book as of today, and the start is the balancing figure between it and the period's movements, which the cards label as such. That makes the bridge reliable for the current period and approximate for a past one.

RevTech: Pipeline Movement shows how the pipeline changed through the selected period.
Pipeline Movement shows how the pipeline changed through the selected period. Captured from the current application with illustrative sample data. Screenshot of the RevTech application; sample data.
Period-over-period movement — what was added, what was removed, and what moved between. The bars are the agenda; each one narrows the deals behind it.
Part 4 of 5

Won and Lost, read honestly

The post-mortem half is two reports, not one: Won Deals and Lost Deals. Each carries its own revenue, win rate, average deal size and a filterable table of the deals behind them, with the CRM's own close reason on every row. Won revenue by month pairs each month's wins with the win rate to date, and Lost revenue by reason ranks why deals were lost.

Average sales cycle is measured per report — won deals on Won, lost deals on Lost — which is exactly why the pair is worth reading together. A win-rate jump that arrives with a longer cycle on Won is not automatically good news. It can mean you are over-qualifying and walking away from deals you would have won. Compare both against the prior period before drawing a conclusion. Cycle counts from when RevTech first synced the deal, so for deals that predate your connection it reads short.

  • Open Lost Deals for the last thirty days and read the loss reasons, not the count
  • Bring the top three to the next forecast call rather than the next QBR
  • The URL carries your filters — paste it into the meeting invite so everyone opens the same view
Part 5 of 5

Making it a rhythm

Pipeline pays off as a standing agenda rather than a page you visit when the number looks wrong. One pass per team: Weekly Change Log for what moved, Pipeline Source for generation health, Pipeline Movement for in-quarter mechanics, Won and Lost Deals for outcomes.

End the review with moves, not observations: a deal re-dated by its owner, a loss reason taken to the forecast call, a source that gets less budget next month. The mechanical habit that makes it stick is copying the URL of the report you end on into the next meeting invite, so nobody re-applies filters from memory and gets them slightly wrong.

What to take away

  • Pipeline Source, Pipeline Movement, then Won and Lost Deals each answer one question. Use them as the agenda, in that order.
  • A high-volume channel with a low win rate is a coverage trap, not a strength.
  • Read the Pipeline bridge left to right, then click the largest red bar: Deals that moved narrows to the deals behind it.
  • Won Deals and Lost Deals are separate reports. Read them as a pair — a win-rate move only means something next to the cycle underneath it.
Demo

See how the work gets done.

Explore how agents prepare work across your revenue teams, and how people review it, guide it and decide what happens next. Fictional data. Real product.

Explore the demo