A sales pipeline report. What good ones actually contain.

The short answer. A snapshot, not a status update.

A sales pipeline report lists every open deal in one view: which stage it sits in, what it is worth, how long it has been there and who owns it. It is a snapshot rather than a live feed, pulled on a fixed schedule so the same version of the truth is in front of everyone reading it, from the rep who owns a deal to the founder who has to say something credible about the quarter on a Monday call.

It is easy to confuse the report with the pipeline review it feeds. The report is the document. The review is the meeting where someone actually interrogates it, deal by deal. A report nobody reads on a schedule is not really a report, it is an export sitting in a downloads folder, and a review run without a proper report underneath it is a conversation built on memory rather than data.

The report also sits next to, and is often confused with, the forecast report. A pipeline report shows everything open, regardless of how likely it is to close. A forecast report is a narrower, weighted projection of what will actually land in a set period. Most founder-led teams need both, read at different cadences, rather than trying to make one document do both jobs.

What belongs in it. Eight fields, not eighteen.

A pipeline report earns its keep by being complete enough to answer real questions and short enough that someone actually opens it every week. Eight fields cover almost everything a founder-led team needs.

Weighted value is the field most founder-led reports skip, and it is the one that matters most. A report showing only raw value invites everyone reading it to assume the full total is coming in, which is almost never true. Multiplying each deal's value by its stage's historical close probability, a figure you build from your own closed-deal history rather than borrow from a generic benchmark, gives a second, more honest number sitting next to the first. The gap between the two numbers is itself useful information: a wide gap usually means the pipeline is full of early-stage deals, a narrow one means most of what is left is close to the finish line.

A team past ten or so reps usually adds two more fields once the basic eight are working properly: a forecast category (commit, best case, pipeline) set by the rep, and a product or service line, where a business sells more than one thing. Both are genuinely useful once the underlying report is trusted, and both are a mistake to add early, because a report with fourteen columns nobody has learned to read yet is worse than one with eight columns everybody checks every week. Add complexity only once the simple version has earned its keep.

How to structure it. By stage first, then cut it three ways.

The base view sorts every open deal by stage, oldest first within each stage, because age within a stage is the fastest way to spot a deal that has quietly stopped moving. From that base view, three further cuts do most of the remaining work: by rep, so a manager can see whether one person's pipeline looks structurally different from the team's; by segment or deal size, so a report does not let three large deals mask a thin middle; and by source, so marketing and sales can see which channel is actually filling the pipeline rather than just talking about which one should be.

Cadence matters as much as structure. A weekly pull, read by whoever runs the pipeline review, catches stalled deals while there is still time to act on them. A monthly pull, read by leadership, looks at the same data from further back: stage conversion trends, coverage ratio against quota and whether the shape of the pipeline is changing quarter over quarter. Running only the monthly version means individual stalled deals sit unnoticed for weeks. Running only the weekly version means nobody steps back far enough to see a pattern, a stage that consistently leaks deals, a source that quietly stopped producing.

What good looks like. Someone reads it and something changes.

A pipeline report earns its place the same way any report does: a named reader, a fixed slot on the calendar, and a decision that actually changes because of what it shows. A good one makes three things obvious within thirty seconds of opening it: which deals have gone quiet, whether this quarter's weighted pipeline covers quota at a realistic multiple, and which stage is thinner than it should be given the target two stages further down.

Format matters less than most teams assume. A well-built spreadsheet, refreshed on a fixed schedule and read by a named person, does the job at small scale just as well as a dedicated reporting tool. The point at which a spreadsheet stops being enough is usually the point more than one person needs to trust the same number at the same time, since that is when a shared, live view earns its cost over a document someone rebuilds and re-emails every Monday.

A good pipeline report also tells you what it is not covering. A weighted total built from six months of closed deals is a reasonable guide for a team with a steady sales motion, and a weak one for a team that just changed its pricing, its ICP or its lead source last quarter, because the historical close rates the weighting depends on no longer describe how the current pipeline actually behaves. Flagging that caveat once, in a line under the report rather than burying it in a meeting nobody who reads the export attends, is a small habit that stops a genuinely good report from being trusted more than the moment allows.

Pitfalls to avoid. The ways a report quietly stops being honest.

Deal count instead of value. A pipeline with forty small deals and a pipeline with four large ones can carry the same total value and completely different risk profiles; a report that only counts deals hides that difference.

No ageing column. Without days-in-stage, a deal that has sat untouched for six weeks looks identical to one that entered the pipeline yesterday, and the report cannot tell anyone which deals actually need attention.

Blended forecast categories. Mixing "best case," "commit" and "pipeline" into one undifferentiated total is how a report ends up presenting a hope as a number.

Sent to the wrong reader. A pipeline report belongs to whoever runs the sales process day to day. Sending the full deal-level version to a board, rather than the rolled-up monthly view, buries the one number they actually need under detail that is not theirs to act on.

Built once and never questioned. Stage definitions drift as a team grows, a rep starts marking deals "proposal sent" the moment a call goes well, well before a proposal exists, and the report keeps producing numbers built on a definition nobody agreed any more. Gartner's research on sales pipeline analytics makes the same point at scale: organisations that treat pipeline reporting as a discipline worth actively managing, rather than a static export, consistently see better forecast accuracy than those that build a report once and leave the definitions to erode. Revisiting what each stage actually means, at least once a quarter, is what keeps a report's numbers meaning the same thing six months apart.

How Lauren would build one. The report I inherit most often, and what I change first.

Most founder-led teams I work with already have something called a pipeline report. It is usually a CRM export sorted by close date, showing raw value only, with no ageing column and no weighted view. It looks complete because every field the CRM offers is switched on, and it is almost never actually read on a schedule, because nobody trusts a number that has quietly overstated the quarter before.

The fix is rarely a new tool. It is normally three changes to an existing export: add a weighted-value column built from the team's own historical stage conversion, add days-in-stage and sort the base view by it within each stage, and split the report into the weekly deal-level version and the monthly trend version rather than sending the same crowded spreadsheet to everyone. Take a hypothetical, but representative, ten-person B2B services team, built to reflect the kind of engagement I see often rather than one named client: adding those three changes to their existing export surfaced eleven deals that had sat untouched for over a month, worth close to a third of the quarter's stated pipeline, none of which had been flagged in any prior review because nobody had a column that made their age visible.

My rule: if a pipeline report cannot show me, inside thirty seconds, which deals have stopped moving and whether the weighted total actually covers quota, it is not a report yet, it is a list. Build the report to answer those two questions first, and every other field is a genuine addition rather than a distraction from them.