How to build a sales report: KPIs and examples

Every Monday morning the same email arrives: a pile of numbers, a few colorful tables, and a "weekly sales report" with no story in it. Nobody opens it, because the report answers no question; it just wraps raw CRM data in a nice file. Lots of figures, no meaning.

A good sales report is the opposite: it starts with a question, answers that question, and leads to a decision. In this article we walk through, step by step, how to build a sales report that actually gets used, from picking the right KPIs to the activity-pipeline-outcome structure, cadence, audience, and the most common mistakes. We will deal not in monetary amounts but in the metrics that drive a decision.

Activity KPIsPipeline KPIsOutcome KPIsDecision to actionSales report

A report answers a question

Every report should have a question it is meant to answer at the very top. "Will we hit quota this month?" "Which source brings the highest-quality deals?" "Which stage is the team getting stuck at?" If you pick metrics before clarifying the question, the report turns into a bulletin board: it shows everything and says nothing. Decide the decision first, then the question, and only then the metric.

That order sounds simple but is the step most often skipped. The decision a manager will make from a report is concrete: shift budget to a source, coach a stage, pull the forecast up or down. If the report is designed to feed that decision, it gets read; if it has no link to a decision, it gets ignored no matter how elegant it looks.

Choosing the right KPIs

The heart of a sales report is the KPIs you choose. A good framework splits metrics into three layers: activity, pipeline, and outcome. This trio makes the chain from effort to output visible end to end and lets you see where you are bleeding.

Activity KPIs

Calls made, meetings completed, proposals sent, new deals added. These are leading indicators; because they measure today's effort, they signal the outcome early. To set up the relationship between activity and outcome correctly, place the logic from our leading versus lagging indicators piece into the backbone of your report.

Pipeline KPIs

Deal count and value by stage, conversion rates, average time to close, and pipeline coverage ratio. These are forward-looking metrics. In particular, the pipeline coverage ratio tells you in advance whether you have enough opportunity in hand to hit quota, which makes it an indispensable line in every sales report.

Outcome KPIs

Deals won, conversion rate, average deal size, and quota attainment. These show the output of the work but, on their own, only describe the past. To tie outcome to a process, add a composite metric like sales velocity; by combining deal count, size, conversion, and cycle length into one number, it explains where revenue is coming from.

Structure and flow of the report

A good report is built like a pyramid: a one-sentence headline finding at the top, a few supporting key metrics below it, and the detail at the bottom. In the first ten seconds the reader should get an answer to "are things good or bad," and if curious, be able to drill down into detail. Put the detail at the top and nobody will find the main message.

At the core of the structure is comparison. A number alone is meaningless; "40 deals this week" only says something when compared to last week, to target, or to the same period last year. To spot the stage that is clogging the pipeline, add a funnel layer to your report; funnel conversion and bottleneck analysis is one of the most instructive views for showing at which stage you are losing deals.

For whom? A report matched to its audience

The same data yields three different reports, because there are three different audiences. The rep wants to see their own activity and deals; the manager tracks team performance and pipeline health; leadership wants the trend, the forecast, and the big picture. Sending everyone the same report leaves everyone a little disengaged.

A good report does not show all the data; it shows the data that serves the decision the reader has to make.

Clarifying the audience shortens the report. A report going to leadership does not have to show how many calls a rep made; quota attainment, forecast accuracy, and the growth trend are enough instead. Next to every line, ask "who does this serve"; if there is no answer, cut that line.

Cadence: daily, weekly, monthly

The frequency of a report determines its content. A daily report is short and activity-focused; it keeps momentum alive. A weekly report focuses on pipeline and conversion; it is where coaching happens. A monthly report deals with outcome, trend, and forecast; it is the rhythm where strategic decisions are made. Showing the wrong metric at the wrong cadence causes confusion: watching the daily swing of closed revenue is mistaking noise for signal.

Building the report by hand is the most common reason it gets abandoned. When someone gathers the data manually every week, the report becomes a burden and eventually slips. Instead, automate it: scheduled and automated reports deliver the right summary to the right people, on a steady rhythm, without you having to ask.

Visualization: choosing the right chart

The same data can lie with the wrong chart. Use a line for change over time, a bar for category comparison, a funnel for stage flow; never use a pie chart for more than three slices. Starting the axis at zero, choosing colors meaningfully, and loading each chart with a single message keep the report readable. We gathered the principles of building an honest chart in our data visualization principles article.

The rule is simple: every chart should answer a single question. If you try to fit three messages into one chart, none of them gets read. If the reader can see the main finding without reading the title, the visualization has done its job.

Building a sales report in Rocketly

The hardest part of building a report is usually pulling the data together; calls sit in one place, deals in another, emails in a third tool. Because Rocketly gathers all this activity in a single CRM, the report is fed from one source. To decide who is shown which metric while designing the dashboard, the principles in sales dashboard design are a good guide.

If you want to go beyond standard dashboards and build a report specific to your own question, the custom report builder lets you pick the metrics, filters, and breakdowns you want and produce reports by territory or team. That way the report is shaped around your decision process rather than being squeezed into a ready-made template.

From report to action: tie it to a meeting

A report creates value not merely when it is read, but when it turns into an action. The best practice is to tie the weekly report to the weekly pipeline review meeting. In that meeting, every metric below target should have an owner and a next step; "conversion dropped" must be converted into a concrete action like "this person will coach that stage this week." A number without interpretation hangs in the air; a number with an owner starts to move.

The next week, the same report should also show what last week's actions were. That way the report becomes not an archive but a feedback loop: measure, decide, act, measure again. A report that does not track action soon slips back into that pile of numbers nobody reads.

Common mistakes

The mistakes that ruin a good report are usually the same. Recognizing them upfront is far cheaper than rewriting your report:

• Vanity metrics: highlighting numbers that look good but serve no decision, like total emails sent.
• No comparison: giving a number alone without comparing it to target, history, or segment.
• Overcrowding: cramming twenty metrics onto one screen and drowning the main message.
• Data without interpretation: showing the number and leaving "so, what should we do" to the reader.
• Inconsistent definitions: the word "deal" or "won" meaning different things across reports.

The last mistake is the most insidious: if metric definitions are not nailed down, two reports count the same event differently and destroy trust. Before you start reporting, write a single definition for each metric and make sure everyone uses the same glossary.

Example: a weekly sales report template

Let us make it concrete. A weekly sales report that works sits on a skeleton like this: a one-sentence status summary at the top ("quota on track, pipeline slightly below target"); below it, this week's activity (calls, meetings, new deals) compared to last week; then pipeline health (value by stage, coverage ratio, clogged stage); then outcomes (deals won, conversion, forecast); and at the bottom, three concrete actions for next week. This skeleton gives the report a beginning, an end, and above all a purpose.

If you want to build your own sales report on this structure, in real time and automatically, open a free Rocketly account and turn your data into a report that drives decisions.