Optimized Sales Optimized Marketing Target Accounts For CROs For CFOs For CMOs Blog News Glossary Compare Tools About Schedule a Demo
Sales Forecasting

How to Build a Sales Report: Lead With the Forecast Call, Not the Dashboard

Pete Furseth 6 min read
sales reportsales forecastingforecast callpipeline coverageRevOps
How to Build a Sales Report: Lead With the Forecast Call, Not the Dashboard
Home/ Blog/ How to Build a Sales Report: Lead With the Forecast Call, Not the Dashboard

What makes a sales report worth reading?

A sales report earns its place when it changes a decision, and most reports change nothing. They open with a wall of charts, one per metric, ordered by whatever the tool exported first. The room scrolls, nods, and leaves with the plan it walked in with. A report that drives decisions does the opposite. It leads with the forecast call and puts the three metrics that can move the number ahead of everything else.

The reports I trust read less like a dashboard and more like an argument. Here is the number, and here is what would have to change for it to be wrong. Everything else is an appendix.

Put this to work on your numbers
Run your own numbers with the free Forecast Accuracy Scorecard, then see how ORM builds it into a custom model.

Why does the dashboard dump fail?

The dashboard dump fails because it shows everything and ranks nothing, so the reader has to do the analysis the report was supposed to do. Thirty tiles of equal weight tell you the author never decided what mattered. Total pipeline coverage with no context is the worst offender. It makes an executive feel informed while hiding the risk underneath. A CRO reads 4x coverage and calls the quarter safe, when the coverage sits in the wrong segment or leans on aged deals that rarely close at their CRM value.

A report is a set of choices about what to leave out. Leave nothing out and you have built a data export, not a report.

What should lead a sales report?

Open with the forecast call: the number you are committing to and the path the quarter takes to reach it. Pipeline coverage is an input to that call and never the conclusion, because pipeline does not equal revenue. The question a forecast answers is not whether you have enough pipeline. It is whether you understand how the quarter will happen before it begins.

That means decomposing the number into the three places revenue actually comes from:

- Carry-over deals already in the pipeline on day one and expected to close this quarter. - In-quarter deals that do not exist yet but will be created, qualified, and closed inside the quarter. - Pull-forward deals from a future period that may close early, usually at a discount or a future-quarter cost.

Most teams over-trust the pipeline they can see and under-model the revenue they cannot see yet. They inspect the deals sitting in the CRM and barely forecast how much business will be created and closed inside the quarter. Put the decomposition at the top, and the forecast call stops being one guarded number and becomes a plan with parts you can inspect.

Which three metrics belong at the top?

Three metrics decide the call: qualified coverage, slippage, and realized win rate with deal size. Each answers a question the headline number cannot.
MetricWhat it tells the roomWhere teams go wrong
Qualified coverageWhether the pipeline can cover the gap, and whether it is the right pipelineReading a raw multiple as a yes. Most ORM customers run about 3.5x coverage and still miss when the mix is wrong.
SlippageWhether the close dates you are counting on are holdingTrusting commit. A rep moving a close date is the strongest slippage signal there is.
Realized win rate and deal sizeWhether deals close, and at the value sitting in the CRMForecasting the CRM amount. Deals routinely close below it.
Qualified coverage is coverage read for composition, not a raw multiple. The standard rule runs 3x to 5x, and most of the ORM customer base sits around 3.5x. A company at 4x still misses when the pipeline leans on a handful of large deals or fills with stale opportunities that will not close this quarter. Report coverage with its composition beside it, or do not report it. The raw multiple creates more noise on a forecast call than any other number. Slippage shows up first as a moved close date. A rep changing the close date on a deal is the strongest signal that it is slipping, and a deal that slides one quarter is less likely to close at all, even sitting in commit. The quieter signal comes earlier: no field changes and a buyer who has stopped replying. Slippage belongs on the report because it looks forward. Of the pipeline carrying in-quarter close dates on the first day of the quarter, about 20% actually closes that quarter. The other 80% of that value moves or dies, so a report that flags which dates are drifting hands the room something to act on while the deal is still open. Realized win rate ties the forecast to the value you will actually book. Pipeline amounts run high against what closes. Take a book where the average open deal reads $80,000 and the average closed-won deal lands at $40,000. Forecasting the CRM value doubles the number you should trust. Put realized deal size next to win rate so the report reflects what closes rather than what the CRM hopes for.

What should you leave off the report?

Leave off any metric that does not change what someone does next. Vanity coverage with no composition beside it, and activity counts nobody ties back to pipeline, add length and subtract focus. If a chart cannot attach to a decision, it belongs in the system, not the report. Seasonality is worth keeping, since Q2 and Q4 tend to run stronger than Q1 and Q3, and the third month of a quarter usually outperforms the first two. That context changes how you read a slow start instead of panicking over it.

When does a sales report actually change the quarter?

A report changes the quarter only when it lands early enough to act on, which means day one, not the final week. Getting the forecast right in the last week helps no one, because the quarter has already happened. Knowing the shape of the number on day one is what lets you create pipeline or protect a deal before its close date moves again. ORM targets 95% forecast accuracy on new and expansion business and holds it from day 1 to day 90, without the manual re-forecasting that leaves most reports stale by the time they land. Traceability closes the loop: when a number sits on the report, ORM Radar points back to the deals and signals that produced it, so the room argues about the business instead of the spreadsheet.

Build the report as a decision. Lead with the forecast call, let three metrics carry the weight, and leave the dashboard where it belongs.

Frequently Asked Questions

What should a sales report include?

Lead with the forecast call, then the three metrics that can move it: coverage read for composition, slippage measured by close-date changes, and realized win rate against average deal size. Everything else supports those or comes off the page. A sales report exists to change a decision, so rank what drives the decision and cut the rest.

What is the difference between a sales report and a sales dashboard?

A dashboard displays every metric at once and leaves the ranking to the reader. A report makes the ranking for them and ties each number to a decision it should trigger. A dashboard is a system of record. A report is an argument about what happens next.

Why is pipeline coverage not enough for a sales report?

Coverage hides composition. A 4x multiple can sit on stale pipeline or a few oversized deals and still miss the number. Most ORM customers run about 3.5x coverage and some still fall short when the mix is wrong. Report coverage with its composition beside it, or leave it off.

How often should you produce a sales report?

Match it to the forecast cadence, which for most B2B SaaS teams means weekly inside the quarter. The point is to see the shape of the number early, since a forecast that only becomes accurate in the final week arrives after the quarter is already decided. A good model holds its accuracy from day 1 to day 90, so the report stays worth reading the whole way through.

What is the strongest signal that a deal will slip?

A sales rep moving the close date. A deal that slides from one quarter to the next is less likely to close at all, even when it sits in commit. The earliest warning is quieter than that: a deal with no field changes and a buyer who has gone quiet on email and calls.

PF
Pete Furseth
ORM Technologies
Pete has built custom revenue forecast models for B2B SaaS companies for over a decade.

See how ORM turns these insights into action

ORM builds custom revenue forecast models for B2B SaaS companies. Not dashboards. Prescriptive analytics that tell you what to do next.

Schedule a Demo