Sales Pipeline Report: 5 Reports Every B2B Sales Team Needs

Here is a scenario that plays out constantly at the end of every quarter.

The pipeline report says $3.4M USD in open deals with a weighted forecast of $1.8M. Leadership reviews the number before the all-hands. Then, one by one, they start asking about specific deals. The rep explains that the $320K deal closed last week — lost. The $180K deal the report shows as "Proposal Sent" has not had a real conversation in six weeks; the prospect went dark. The $500K deal at "Contract Sent" is actually more like $280K because scope changed and nobody updated the amount.

The report was not wrong about what the CRM said. It was wrong about what was actually in the pipeline.

This is the root problem with most sales pipeline reports: they reflect what reps typed into the CRM, not the current state of the deal. A pipeline report can only be as accurate as the data feeding it. Fix the reporting before you fix the data, and you are polishing a number nobody can trust.

Why Most Pipeline Reports Fail Before Anyone Reads Them

The failure happens upstream. Pipeline reports pull from fields that reps fill in manually: deal amount, close date, stage, next step. Each of those fields goes stale the moment the underlying deal situation changes and the rep does not update the record.

Three failure modes cause most of the damage:

Stale close dates. A rep creates a deal in January with a close date of March 31. March passes, the deal does not close, and the rep moves on to other conversations. The close date stays at March 31 because updating it requires logging into the CRM and doing work that does not feel urgent when there is a hot prospect on the phone. By the time someone looks at the report, the forecast includes revenue that has no realistic path to closing this quarter.

Ghost stages. A deal moves to Proposal Sent when the rep sends a deck. The deck goes nowhere. The prospect goes dark. Three months later, the deal still shows as Proposal Sent because there is no signal telling the CRM it stalled. The stage is a timestamp of the last action the rep logged, not a description of where the deal actually stands.

Missing activity. A report with no activity date is a report about a deal that may not exist. When the last logged activity is from six weeks ago, you cannot tell whether the rep is working the deal quietly or has mentally moved on and just forgotten to mark it closed.

These failure modes compound. A pipeline report that has stale close dates, ghost stages, and no activity data is not a forecast. It is a historical artifact. For a practical look at the data quality layer underneath any reliable report, see the guide on CRM data hygiene for sales teams.

The 5 Pipeline Reports Every B2B Sales Team Needs

There is no single pipeline report. There are five, each answering a different question. Teams that try to answer all five with one dashboard end up with a report that answers none of them clearly.

1. Weighted Pipeline Forecast

What it tells you: How much of your current open pipeline is likely to close, based on historical close rates at each stage.

How it works: Each deal stage has a close probability. A deal in Discovery might have a 15% probability; a deal at Contract Sent might have 80%. The weighted forecast multiplies each deal's amount by its stage probability and sums the result. This number is more useful than raw pipeline value because it accounts for the reality that most deals in early stages do not close.

How to build it:

In HubSpot, create a Sales report with Pipeline as the type. Select Weighted deal amount as the metric rather than Deal amount. Group by deal stage and filter by close date within your target period. The stage probabilities live in Settings, under CRM, then Deals, then Deal Stages; set these to match your actual historical win rates, not default values.

In Salesforce, the Opportunity report with Amount multiplied by Probability gives you the weighted value. Salesforce calls this the Expected Revenue field and populates it automatically if your opportunity stages have probability values configured.

In Pipedrive, the weighted pipeline view is available in the Pipeline tab. Pipedrive multiplies each deal's value by the probability set on the stage. Check and update those stage probabilities in the Settings under Pipeline to reflect your actual conversion rates.

Common mistake: Leaving stage probabilities at CRM defaults (often 10%, 25%, 50%, 75%, 90%) rather than calibrating them to your actual historical win rate at each stage. A 50% probability on a Proposal Sent stage is accurate only if half your proposals actually close. If your real rate is 30%, your forecast overstates by two-thirds of a deal for every proposal in the pipeline.

2. Stage Conversion Report by Rep

What it tells you: Where deals stall in your pipeline, and whether the stall point differs by rep.

What to look for: Compare conversion rates at each stage transition across your team. If one rep converts 60% of Discovery to Demo and another converts 20%, that gap is a coaching opportunity. If the whole team drops off at Contract Sent, that is a pricing or legal process problem, not a rep skill problem. The stage conversion report makes that distinction visible.

How to build it: In HubSpot, the built-in Sales Analytics suite includes a deal stage funnel report. Filter by rep to compare. In Salesforce, a Matrix report grouped by Stage and Owner with a Count metric gives the same view. In Pipedrive, the Conversion report under Statistics shows stage-by-stage conversion grouped by user.

Prerequisite: Your stage definitions need clear exit criteria, or reps will move deals forward inconsistently and your conversion data will be noise. A deal should only be in Discovery if a live conversation is happening, only in Proposal Sent if a real proposal went to a real decision-maker in the last two weeks. For a framework on setting stage exit criteria, see the guide on sales pipeline stage definitions.

3. Activity Coverage Report

What it tells you: Which deals have had recent logged activity and which have gone quiet.

The question it answers: For every open deal, when was the last time a rep did something with it? Sent an email, logged a call, scheduled a meeting? A deal with no logged activity in 14 days is either being worked invisibly (activity not logged) or genuinely stalling (no contact). You need to know which.

How to build it: Create a deals report filtered to open deals, with last activity date as a column. Sort ascending to bring the oldest deals to the top. Set a threshold: any deal with no activity in 21 days shows as amber; any deal in 45 days shows as red.

In HubSpot, the Last Activity Date field updates automatically when email is synced or calls are logged through the CRM. If your team has email sync and calendar sync configured, this report becomes reliable immediately. If they are logging activity manually, expect gaps.

The automation leverage point: This is the report where automated activity capture pays the most obvious dividend. When email, calendar meetings, and calls sync automatically, the last activity date stays current without any rep action. A deal that went quiet shows up in the report based on actual contact history, not based on whether a rep remembered to click "Log Activity." For more on setting up that sync, see the guide on automatically logging sales activity to your CRM.

4. Deal Aging Report

What it tells you: How long deals have been sitting in each stage, and which ones have exceeded their expected time.

What to look for: Every stage should have a typical time range. Discovery might average 10 days before moving to Demo. Negotiation might average 14 days before closing or stalling. When a deal has been in Discovery for 45 days, it is either not a real deal or it is stuck on something specific a manager needs to address.

How to build it: Use Time in Stage as the key metric if your CRM supports it. HubSpot's sales analytics suite includes average time in stage and can flag deals exceeding a threshold. Salesforce requires a formula field or a custom report. Pipedrive tracks days in stage in its Pipeline view.

Set your benchmarks based on historical data, not optimism. Pull the average time-in-stage for deals that actually closed in the last 12 months. Use that as your threshold, not a round number you invented. For a related framework on catching deals that are aging out, see the guide on sales pipeline aging.

5. Closed-Lost Analysis

What it tells you: Why deals are lost, at which stage they are lost most often, and whether the pattern is changing.

Why it matters: Most teams treat closed-lost deals as sunk costs and move on. A monthly review of closed-lost reasons reveals patterns that surface product gaps, pricing issues, competitive dynamics, and pipeline stages where qualification is breaking down. If 40% of deals lost in the last month were lost at Contract Sent with "Timing" as the reason, that is worth examining before it becomes a quarterly trend.

How to build it: Your CRM needs a required close reason field — a dropdown, not a text field — that reps must fill in before closing a deal as lost. Common categories: Pricing, Timing, Chose Competitor, No Budget, No Decision, Lost Contact. For guidance on configuring this field, see the guide on CRM closed-lost reasons.

In HubSpot, build a Deals report filtered to deals closed as lost in the last 30 days, grouped by your close reason field. Add a secondary grouping by deal stage to see at which point in the funnel different reasons cluster. In Salesforce, a summary report on Opportunities grouped by Stage and Loss Reason gives the same view.

Review this report monthly with your sales manager. Look for three things: the most common reason, whether it changed from last month, and whether it clusters at a particular stage.

The Data Foundation These Reports Require

No report architecture fixes a data quality problem. The five reports above produce useful output only when the underlying CRM fields are accurate and current.

The fields that these reports depend on most:

Close date. If reps can enter any close date without consequence, close dates will be optimistic and stale. The weighted forecast requires accurate close dates to be meaningful. Review close date accuracy weekly and flag any deal with a close date in the past that has not been updated. For a deeper look at this specific problem, see the guide on CRM close date accuracy.

Deal stage. Stage should reflect the last confirmed exit criterion, not the last action a rep took. A discovery call is not enough to move a deal to Demo; a scheduled demo with a confirmed decision-maker present is. Define exit criteria per stage, train reps on them, and review stage distribution weekly for deals that look stuck.

Last activity date. This field is only reliable if activity is logged — either by the rep or by automatic sync. If your team relies on manual logging, expect gaps. The activity coverage report will show phantom green deals that are actually dead.

Deal amount. Scope changes happen. A deal that started at $200K USD may be at $120K after a pricing conversation. If reps do not update amounts, your weighted forecast is wrong from the start.

The sales pipeline health score framework gives a structured way to measure whether these foundational fields are in good shape before trusting the reports built on top of them.

How Automated Data Capture Improves Report Reliability

Manual logging is the single biggest threat to pipeline report accuracy. When activity, email history, and meeting notes depend on rep memory and effort, the reports that rely on those fields reflect rep discipline more than deal reality.

When email and calendar sync automatically, the last activity date updates without rep action. When call recordings sync to the deal record, there is an activity timestamp even if the rep never typed a note. When an AI layer reads email threads and drafts suggested CRM field updates for rep review, close dates and stages stay more current because the rep is reviewing a suggested update rather than building one from scratch.

This is the model the Company Brain uses: daily email and thread sync keeps the activity layer current, and AI-drafted field updates go to the rep for approval before anything writes to the CRM. The result is that the pipeline report reflects a version of the pipeline where the data was touched recently, not a version frozen at whatever the rep last typed three weeks ago.

The pattern works because it removes the blank-page friction of CRM maintenance without removing rep judgment from the fields that drive the forecast. Reps do not spend less time thinking about their deals; they spend less time typing about their deals. The reports improve as a side effect.

What Good Pipeline Reporting Looks Like in Practice

A sales team with a trustworthy pipeline report runs the weighted forecast daily as a live view, uses the activity coverage report to prepare agenda items for the weekly pipeline meeting, reviews stage conversion monthly to identify coaching patterns, and checks deal aging weekly to surface any deal stuck in a stage longer than the historical average.

The closed-lost analysis runs monthly, takes about 30 minutes, and feeds directly into the next quarter's target-setting conversation. The weighted forecast from the previous month is compared against actual close results to calibrate stage probabilities for the next cycle.

None of this requires a business intelligence team or a custom dashboard tool. It requires a CRM with the right fields, the right stage definitions, and activity data that is current enough to trust.

Start with the activity coverage report. It is the fastest way to identify how big the data gap is before you build the other four. If 60% of your open deals have no logged activity in the past three weeks, the weighted forecast is noise until you fix that first.

Frequently Asked Questions

What should a sales pipeline report include?

At minimum, a useful pipeline report shows open deal count and total value by stage, weighted forecast (deal value multiplied by stage close probability), deal age and last-activity date, and recent stage movement. Without last-activity date and deal age, you cannot tell which deals are alive and which are phantom entries.

How do I build a weighted pipeline forecast in HubSpot?

In HubSpot, go to Reports, create a new Sales report, choose Pipeline as the type, and select Weighted deal amount as the metric instead of Deal amount. Group by deal stage. Add a close-date filter for your current quarter. HubSpot applies the stage probability percentage to each deal automatically. Set those probabilities in Settings under CRM, then Deals, then Deal Stages.

How often should a sales team run pipeline reports?

Most teams run a live pipeline snapshot daily or on demand, a stage-conversion and activity-coverage review weekly before the pipeline meeting, and a closed-lost analysis monthly. Quarterly, run a full pipeline cleanup to remove zombie deals that distort the weighted forecast.

Why does my pipeline report not match what my reps say about their deals?

Pipeline reports reflect the CRM record, not the rep's mental model of the deal. The gap appears when reps verbally update their deals in meetings but never log those updates in the CRM. Close dates slip, stages go stale, and the report freezes at whatever the rep typed last. Closing this gap requires either better logging habits or automated activity capture.

What is the difference between a pipeline report and a sales forecast?

A pipeline report shows all open deals and their current state. A forecast is a prediction of how much of that pipeline will close this period, usually calculated by applying a probability to each stage. A pipeline report is the raw input; the forecast is the output. A bad pipeline report guarantees a bad forecast, no matter how sophisticated the forecasting model.