# Sales report: what to put in it, and how to build it from your CRM automatically

https://salesbond.app/blog/sales-report-what-to-include-built-from-crm/
Published: 2026-11-01 · Updated: 2026-11-14

A sales report shows what the sales team sold, what is still in the pipeline and what needs attention, for a set period and a named reader. A good one has few sections, uses numbers taken straight from the CRM and says how reliable those numbers are.

That last part is the one almost every template skips. A report is a claim about the business, and the claim is only as good as the deal records behind it. If a third of the open deals have no amount, “pipeline value” is a guess with a currency sign in front of it. A sales report should therefore tell the reader whether to trust it before the reader acts on it.

## Three readers, three reports

Ask who opens the report before you decide what goes in it. The same CRM produces three honest reports and they are not interchangeable. If the numbers still live in a sheet, a [sales tracking spreadsheet in Pipedrive](https://salesbond.app/blog/sales-tracking-spreadsheet-pipedrive/) shows how to move them into the CRM first.

The owner wants to know whether the quarter is safe. Plan versus actual, how much of the open pipeline is realistically going to close, how much money is sitting in deals that have gone quiet, and which customers the business depends on. The owner does not want a list of deals. If a deal is named in the owner’s report, it should be because losing it would change the quarter. A shorter owner’s version, eight lines long, is the [KPI report for a business owner](https://salesbond.app/blog/kpi-report-business-owner/).

The head of sales wants the same picture one level down: per rep, per stage, per week. Which rep’s pipeline is thinning, where deals pile up, which stage has turned into a parking lot. This reader will open deals, so deal lists are fine here as long as they are short and sorted by money.

The rep wants their own book. Deals with no next step, deals past their expected close date, customers who usually reorder by now and have not. For a rep teh report is a to-do list, and anything they can’t act on personally is noise.

Send one report to all three and you know what happens. The owner skims, the head of sales argues with the numbers, the rep ignores it. We would rather build one data model and three views of it. Of the full set of sections, the owner gets the top half, the rep gets the bottom half, the head of sales gets everything with names attached. Our longer piece on [which reports an owner and a head of sales each need, and how often](https://salesbond.app/blog/crm-reporting-owner-head-of-sales-report-set-weekly-cadence/) walks through the split in detail.

## The sections every sales report needs

Every row here answers one question, and every answer comes from a field that already exists in a CRM. If a row needs a number your CRM does not store, drop the row rather than invent the number.

| Section | The question it answers | Where it comes from in the CRM |
| --- | --- | --- |
| Header | Which period, which pipelines, when was the data pulled | Report settings; the export timestamp |
| Results | What was sold against plan | Won and lost deals in the period: won revenue vs target, win rate, sales cycle length |
| Money at risk | How much open pipeline is in deals that are stalled, overdue or missing basics | Open deals filtered by last activity, next activity, expected close date, amount |
| Data reliability | Can the numbers below be trusted | Share of open deals with empty amount, no close date, no owner, no contact |
| Top findings | The three things the reader should act on this week | Derived from the rows below, sorted by money |
| Reps | Who is carrying the pipeline, who is falling behind | Deals grouped by owner: open value, won, lost, created in period |
| Deal health | How many deals are fine, how many need attention, how many are at risk | Rule checks on each open deal (no next activity, stuck in stage, date passed) |
| Pipeline bottleneck | Which stage holds deals the longest | Days in stage per deal, aggregated by stage |
| Repeat customers | Which regular buyers are late for their usual order | Won deals per customer over time; days since the last purchase |
| Top-10 clients | How concentrated the revenue is | Won deals per organisation, summed for the period |
| What to fix | The few changes that free the most money | The findings above, each tied to a deal set and an amount |

Results answers what the team sold, and it is the row most readers look for first. Keep it short, though. It tells you how the period went, while the rows under it tell you why and what to do about it.

Activity counts, email open rates and call volume are left out on purpose. They can explain a pipeline number once you have one. On their own they are the easiest things in the CRM to inflate and the least connected to money.

## What to cut

Most reports we see are too long, and they are long in the same ways. Vanity totals go first. “Total pipeline value” with no filter is the biggest number on the page and the least meaningful one, because it counts the deal created two years ago that nobody has touched since. Replace it with open pipeline that has had activity in the period, and put the stale remainder under money at risk, where it belongs. Activity tables per rep go the same way: keep activity only where it explains a pipeline change, in a sentence.

Then the lists nobody opens: every deal won, every deal lost, every deal created. The head of sales can pull these in the the CRM in ten seconds. A report should carry the deals that need a decision and leave the archive in the CRM. The weekly version gets cut even harder, because its reader has five minutes; that case has [its own article](https://salesbond.app/blog/weekly-sales-report-what-to-include-and-what-to-cut/).

## A one-page sales report template and example

The template runs top to bottom in this order: header, results, money at risk, data reliability, top three findings, reps, deal health, pipeline bottleneck, repeat customers, top-10 clients, and what to fix. It fits on one page in portrait. Trust and money come before detail on purpose.

![One-page sales report template: eleven stacked blocks from header to what to fix, with grey placeholder bars instead of numbers](https://salesbond.app/wp-content/uploads/2026/11/sales-report-what-to-include-built-from-crm-2.png)

The header carries the period (the last 30 days, say, or a calendar month if this is your monthly sales report), the pipelines included and the moment the data was pulled. Without that timestamp two people with two exports will argue about which one is right.

Results is one line: won revenue against plan, win rate, average cycle. Then [money at risk](https://salesbond.app/blog/revenue-at-risk-sales-pipeline/), which is one figure and one sentence: the open pipeline value sitting in deals that are stalled, past their close date or missing a basic field, and how that compares with the previous period. Data reliability follows immediately, as the shares of open deals with no amount, no expected close date, no owner, no contact. If any of these is high say so here in plain words. Then the top three findings, three sentences, each naming a deal set and an amount.

Reps, deal health, bottleneck, repeat customers and top-10 clients get one short block each, in that order: names and amounts sorted by money, no commentary longer than a line. The page closes with what to fix, up to five items, each with the money attached and the field or habit that would change it.

Now the example, with a warning. Every number below is invented to show the shape of the report. Do not quote it, benchmark against it or put it in a deck.

A hypothetical team of four reps, last 30 days, one pipeline. Won: 180,000 against a plan of 220,000. Open pipeline with activity in the period: 410,000. Money at risk: 96,000, of which 61,000 is in eleven deals with no next activity and 35,000 in six deals past their expected close date. Data reliability: 18% of open deals have no amount, 9% have no close date, 3% have no owner. Top finding: the Proposal stage holds deals for a median of 34 days, twice as long as any other stage, and most of the money at risk sits there. Second: one customer accounts for 27% of won revenue in the period. Third: four repeat customers are overdue for their usual order.

Read that paragraph again. The data reliability line changes how you read the money at risk line: with 18% of deals missing an amount, 96,000 is only a floor, because every deal without an amount counts as zero in it.

## Why the report lies when the CRM is half-filled

A report cannot be more accurate than the records it summarises, and three gaps do most of the damage.

Empty amounts. A deal with no value contributes zero to every total, so the pipeline looks smaller than it is and money at risk looks smaller too. You won’t see the gap in the report itself, which is why the data reliability block has to name it.

Missing expected close dates. Forecast by month becomes impossible. Worse, the “deals past close date” check silently skips exactly the deals most likely to be in trouble, because a rep who does not know when a deal will close has often lost touch with it.

Deals without an owner. They vanish from every per-rep view. The team total still includes them, so the per-rep blocks no longer add up to the top line, and the first person who notices stops trusting the whole page.

![Three CRM record gaps (empty amount, no close date, no owner) and the report block each one distorts](https://salesbond.app/wp-content/uploads/2026/11/sales-report-what-to-include-built-from-crm-3.png)

So fixing a sales report usually starts in the CRM, before anyone opens the spreadsheet. Making amount and expected close date required at a given stage does more for next month’s report than any redesign of the layout. We keep a separate list of [the CRM data quality metrics worth tracking](https://salesbond.app/blog/crm-data-quality-metrics/) for teams that want to measure the gaps before plugging them.

## Building it automatically: what CRM Report puts on the page

CRM Report builds this report from CRM data: a free audit of the connected CRM over a fixed 30-day period, which then becomes a weekly report. Disclosure, since this is where the article meets our own work: we build SalesBond, a sales management layer on top of the CRM a team already uses; we started with Pipedrive. CRM Report is one of its products, and the sections from money at risk down are its sections. Results against plan is not on its list; in SalesBond, target and attainment live in Sales Plan.

The output has three parts. First, what is wrong: money at risk, a CRM score with five sub-scores, the top three findings and a short summary. Second, what is happening: managers, deal health, the pipeline bottleneck, repeat customers and the top-10 clients. Third, what to fix, as up to five cards sorted by money. It also reviews the pipelines and their stage names, exports to PDF and can be sent to a manager.

Two of those blocks lean on other SalesBond products. The deal health block uses Deal Health, which checks every open deal against more than 20 rules and gives each deal a [score from 0 to 100](https://salesbond.app/blog/deal-health-score/), computed only when at least three rules apply; otherwise the deal shows “not enough data” rather than a number. The repeat customers block uses Repeat Sales. Its idea is simple and deterministic: a customer who buys regularly has a buying cycle, the median interval between purchases, and the time since the last purchase tells you whether the next order is on track, overdue or probably not coming.

Two limits, stated plainly. All the numbers in the report are deterministic, computed from the CRM records; AI writes only the summary text and the stage-name suggestions, so the same CRM data always gives the same figures. And the report names the deals and the money, but a person decides what to do with them. SalesBond does not create CRM tasks without a person: in Sales GPS, accepting a card creates one task in the CRM.

SalesBond works with Pipedrive, HubSpot, Salesforce, Zoho CRM, Microsoft Dynamics 365, Freshsales, Close, monday CRM, Copper, Zendesk Sell, Nutshell, Insightly, Attio, Bitrix24 and Kommo (amoCRM). If you want to see what your own CRM produces as a report before you redesign the spreadsheet, [Check your CRM with SalesBond](https://salesbond.app/).

## After the 30-day audit

The audit is the baseline. After it, CRM Report becomes a weekly report with a weekly-change view, because once you have a baseline the interesting thing is what moved since the last issue. How each of the three readers uses that rhythm is covered in [the owner and head of sales report set](https://salesbond.app/blog/crm-reporting-owner-head-of-sales-report-set-weekly-cadence/).

For the live view between reports, a dashboard does a different job. The Sales Dashboard in SalesBond has a Business Impact tab with plan, forecast and revenue-at-risk widgets and a Team Performance tab for per-rep execution; it shows the state today, while the report is the written record of the week. We compared the two in [which tiles and fields belong on a CRM dashboard for an owner and a head of sales](https://salesbond.app/blog/crm-dashboard-owner-head-of-sales-tiles-and-fields/). Teams need both, and the report is the one a manager can be held to a week later.

## FAQ

**What is a sales report?**
 A document, for a set period and a named reader, that shows what was sold, what is in the pipeline, and what needs attention, built from the CRM’s deal records. The useful ones also state how complete those records are.

**How do I write a sales report?**
 Decide who reads it and for which period, pull the deals from the CRM, and fill the sections of the template above in order, sorting every list by money. Cut anything the reader cannot act on. If you need it every week, generate it from the CRM instead of rebuilding it by hand.

**What are the three types of sales reports?**
 By reader: the owner’s report (plan, forecast, risk, concentration), the head of sales’ report (per rep, per stage, per week) and the rep’s report (their own deals that need a next step). Splitting by period, daily, weekly, monthly, is the other common cut; we wrote about the [daily version](https://salesbond.app/blog/daily-sales-report-close-the-day-in-pipedrive/) and the [weekly version](https://salesbond.app/blog/weekly-sales-report-what-to-include-and-what-to-cut/) separately.

**What should a sales report template include?**
 Few sections, each answering one question, each traceable to a CRM field. The template in this article has eleven. If yours has twenty, the extra nine are probably activity counts and archives.
