# Sales volume vs sales revenue: deal count, units and amount in your CRM

https://salesbond.app/blog/sales-volume-vs-sales-revenue-deal-count-units-crm-owner/
Published: 2026-10-29 · Updated: 2026-11-13

Sales volume is how much you sold, counted in units or in number of deals; sales revenue is the money those sales brought in ( [Incentivate: sales volume formula](https://incentivatesolutions.com/blogs/understanding-and-boosting-sales-volume-formula-calculation-and-tips/)). In a CRM, report closed-won deal count, units (line item quantity) and amount side by side. When volume grows and revenue does not, the gap is usually discounts or a shift to smaller deals.

Most guides stop at the definition and go straight to a list of ways to sell more ( [HubSpot: how to increase sales volume](https://blog.hubspot.com/sales/how-to-increase-sales-volume)). The owner’s problem is different. The team says “we closed more deals than ever”, the bank balance disagrees, and the dashboard can’t say who’s wrong.

## Volume, revenue and deal count: three numbers, three questions

Deal count tells you how often the team wins. Units tell you how much product left the building. Amount tells you what it was worth, and in this article revenue means exactly that: the amount on closed-won deals in the CRM. An amount-only dashboard leaves the owner guessing at the first two.

We keep all three on one line because each one fails alone. Deal count rewards reps who split one order into three deals. Units reward whoever sells the cheapest item. Amount hides the month where fifty small wins replaced ten large ones. Read together, they correct each other, because a split deal raises the count without raising the units, and a discount month lowers the amount while the units stay put.

## What counts as a unit in a CRM: deal, line item or seat

Our rule: as soon as any deal in your pipeline carries more than one product, a unit is a line item quantity. A deal is a container. The units are inside it, and units sold for the month is simply the sum of line item quantity on closed-won deals.

Both CRMs give you a place to write that quantity. In HubSpot, a line item carries its own unit price, quantity and unit cost ( [HubSpot: use line items with deals](https://knowledge.hubspot.com/records/use-line-items-with-deals)). In Pipedrive, a product linked to a deal sets the deal value automatically, and a product has a Unit field for the quantity or measurement it is sold in ( [Pipedrive: products](https://support.pipedrive.com/en/article/products)). The field exists. Whether reps fill it is another matter.

Three cases come up every time we set this up with a team. A software team selling seats uses the seat as the unit, so a 40-seat deal is one deal and 40 units; count it as one unit and it looks like a 5-seat deal. Services sold as projects have no natural unit, and inventing one (hours? phases?) adds a field nobody trusts, so those deals get “units: n/a” on the line. Hardware with accessories takes its units from line items, with the main product kept apart from the add-ons, or the accessory count swamps the number that matters.

Write the rule down in one sentence in the the team wiki. “A unit is one line of quantity on a closed-won deal; services deals report no units.” Reps will ask once and then stop asking.

## Four ways sales volume and revenue move, and what each means

Compare this month with last month. The two numbers either move together or they don’t, and each combination has its own first check.

More deals, more money: the team is selling more at about the same price. Nothing urgent, but confirm the average deal size held, so the growth isn’t one large deal.

More deals, less money: each win is worth less. That’s discounts, a cheaper product or split deals, and the first places to look are average deal size, the discount on line items and deals that now carry one line item where they used to carry three.

Fewer deals, more money usually means one big deal or a price rise. See how much of the amount sits in the top three deals, then take them out and look again.

Fewer deals, less money is plain less selling: the pipeline got fed less or the close rate fell. Start with deals created and the [conversion rate you actually track](https://salesbond.app/blog/sales-conversion-rate-which-one-to-track-crm/).

![Two-by-two grid of deals up or down against amount up or down, each cell with its meaning and the first thing to check](https://salesbond.app/wp-content/uploads/2026/10/sales-volume-vs-sales-revenue-deal-count-units-crm-owner-2.png)

The second case is the one owners mistake for good news. The sales meeting celebrates a record number of wins, and the amount line is quietly lower than last month.

## Average deal size as the bridge between them

Average deal size is amount divided by deal count, and it explains why the other two disagree. Mean or median is its own question, covered in [average deal size: mean or median](https://salesbond.app/blog/average-deal-size-median-pipedrive/).

Take an illustrative September and October. September: 40 closed-won deals, 95 units, 180,000 in amount. October: 52 deals, 110 units, 171,000. The count went up by twelve deals, units by fifteen, and the amount dropped by 9,000. Average deal size went from 4,500 to about 3,290. Amount per unit went from about 1,890 to about 1,550.

Twelve extra deals should have added roughly 54,000 at September’s deal size. Instead the total fell. So the new deals were far smaller, or everything sold cheaper, or both. Units separate the two: units grew 16 % while deals grew 30 %, so the new deals carried about one unit each. Price per unit fell too, so something was discounted or the mix shifted.

Two sentences for the planning meeting, both checkable in the CRM in five minutes. “We won twelve more deals, mostly single-unit deals.” “We earned about 340 less per unit than in September.”

The same arithmetic answers the plan question. Sales volume variance is the difference between actual and budgeted units multiplied by a value per unit; HubSpot’s guide allows profit, contribution or revenue per unit ( [HubSpot: sales volume variance](https://blog.hubspot.com/sales/how-to-increase-sales-volume)). We use the planned price per unit, so the variance reads in the same money as the amount line.

## Where discounts and mix hide in the gap

When revenue lags volume, look in two places: the price written on the line, and which products the lines contain.

Discounts first, briefly. Both HubSpot and Pipedrive keep the list price in the product catalogue and the deal price on the deal’s line. The failure is a rep typing the discounted figure straight into the amount and skipping the lines; then units and prices both drop out of the report. [Where line items, discounts and the Amount drift apart in HubSpot](https://salesbond.app/blog/hubspot-line-items-deal-amount-discounts/) has the field-by-field check, [gross sales vs net sales in your CRM](https://salesbond.app/blog/gross-sales-vs-net-sales-crm-deal-amount-owner/) walks through where each discount layer sits, and the [discount policy piece](https://salesbond.app/blog/discount-policy-sales-teams/) covers who may give what.

Mix is the quieter one. Nobody discounted anything, but October’s units were mostly the entry product and September’s mostly the premium one. Price per unit falls, and every rep did their job. The only way to see it is units by product, and that report needs the unit on the line item.

Returns, credit notes and tax are a separate subject ( [bookings vs billings vs revenue](https://salesbond.app/blog/bookings-vs-billings-vs-revenue-pipedrive/)). For the volume question, the booked amount on the closed-won deal is enough.

## A three-number monthly line for the owner’s report

The line we recommend is one row per month: three figures and a fourth derived one.

`October: 52 deals won · 110 units · 171,000 · avg deal 3,290 (Sep: 40 · 95 · 180,000 · 4,500)`

Deal count and amount come from the closed-won filter for the month. HubSpot’s custom report builder, for one, gives “the number of associated deals” as a typical measure and lets you pick the aggregation for a field ( [HubSpot: custom report builder](https://knowledge.hubspot.com/reports/create-reports-with-the-custom-report-builder)). Units are the sum of line item quantity across the same deals. If your CRM report can’t sum quantity across deals, export the month’s line items to a sheet. Most teams skip this step because the amount tile already looks like an answer.

Keep the previous month in brackets on the same row. An owner reads it in order: did we win more, did we ship more, did we earn more? Where the answers disagree, the sections above say what to open next. The [dashboard tiles and fields](https://salesbond.app/blog/crm-dashboard-owner-head-of-sales-tiles-and-fields/) piece fits around this line and [activity metrics for a small team](https://salesbond.app/blog/sales-activity-metrics-small-team/) covers the inputs that feed it.

A disclosure, since we’re at the reporting question: we build SalesBond, a sales management layer on top of the CRM a team already uses; we started with Pipedrive. It works with Pipedrive, HubSpot, Salesforce, Zoho CRM, Microsoft Dynamics 365, Freshsales, Close, monday CRM, Copper, Zendesk Sell, Nutshell, Insightly, Attio, Bitrix24 and Kommo (amoCRM), and its free CRM audit reads the last 30 days of the CRM and sends a PDF report with the main findings and what to fix. The unit rule is still yours to write. To see what your closed-won data says this month, [check your CRM with SalesBond](https://salesbond.app/).
