Average Deal Size vs Average Selling Price

What is the difference between average deal size and average selling price?

Average deal size is what a whole contract is worth. Average selling price is what one unit of your product goes for. In a business selling a single product on annual terms the two numbers converge. In a business selling bundles or multi-year terms they diverge badly, and the gap gets loaded straight into the revenue plan.

Average deal size is a sales metric. It describes the size of the transactions the team is closing and feeds capacity planning, quota setting, and coverage math. Average selling price is a pricing and product metric. It describes what the market pays for a unit and feeds packaging decisions and discount policy.

The failure mode is specific. Someone computes average deal size from total contract value, then uses it in an annual revenue model. The plan now assumes three years of revenue lands in twelve months.

How do you calculate average deal size?

Divide the total value of closed-won deals in a period by the count of those deals. Forty deals worth $2.4 million combined gives a $60,000 average deal size.

The value definition decides everything. Annual contract value counts one year of the subscription. Total contract value counts the full term. A business with a meaningful share of three-year contracts will show an average deal size on a TCV basis that runs two to three times the ACV version, and both are correct answers to different questions.

Pick ACV for anything that touches an annual plan. Reserve TCV for questions about total customer commitment and cash. Then enforce the choice in the reporting query so nobody has to remember it.

How do you calculate average selling price?

Divide total revenue from a product by the number of units sold. The unit definition varies by business model. A per-seat product uses seats. A platform with modules uses product lines. A tiered subscription uses subscriptions.

The point of ASP is comparability across time and across customers. It answers whether the market is paying more or less for the same thing, which is a question average deal size cannot answer because deal size moves with bundle composition. A rising average deal size next to a falling ASP means you are selling more units at worse prices, and only the second half of that sentence is a pricing problem.

How do the two compare side by side?

Deal size measures transactions. Average selling price measures price. The division is clean once stated. A change in one does not imply a change in the other, and reading them as interchangeable is how packaging problems get mistaken for sales problems.

Why does pipeline average deal size overstate what you close?

Because most deals close for less than the amount sitting in the CRM. Amounts get entered early, based on the largest configuration discussed, and nobody revises them downward while the deal is open. The correction happens at close, all at once.

The gap is often large. A pipeline carrying an $80,000 average deal size against a $40,000 closed-won average is running at half the value it reports. Every metric built on pipeline amounts inherits that error, including pipeline coverage. Coverage of 4x on inflated amounts is functionally 2x, and the ratio will never disclose it.

Market conditions widen the gap further. When a new competitor enters and creates pricing pressure, average deal size falls before anyone updates the pipeline assumptions that were set in the annual plan.

Which number belongs in the forecast?

Closed-won average deal size on an ACV basis, segmented by deal size band and by source. A blended company average assumes the mix stays constant, and the mix is the first thing that moves when a market shifts.

Segmenting matters because the segments behave differently. Large deals take longer, convert at lower rates, and discount more. Applying one average across them produces a revenue forecast that is wrong in a direction determined by whichever way the mix happens to tilt that quarter.

Average selling price stays out of the forecast entirely. It is a diagnostic for why average deal size moved, not an input to the revenue number.

What distorts both metrics?

Outliers distort the mean. One $900,000 contract in a quarter of $45,000 deals will lift the average enough to make the next quota cycle unrealistic. Report the median alongside the mean and use the median for anything involving rep capacity.

Mixed definitions distort trends. If Q1 was computed on TCV and Q2 on ACV because two different analysts built the reports, the resulting decline is an artifact. This happens more often than teams admit, and it is worth auditing before anyone acts on a trend line.

Seasonality distorts period comparisons. Q2 and Q4 usually run stronger than Q1 and Q3, and the third month of a quarter runs stronger than the first two. Comparing an average deal size in the first month of Q1 against the last month of Q4 measures the calendar rather than the business.

How should you report them together?

Put four numbers on the same view: pipeline average deal size, closed-won average deal size, the gap between them, and ASP for the core product. The gap is the most actionable of the four, because it tells you how much of your reported pipeline value is real.

Then trend all four by quarter. A stable ASP with a falling closed-won average deal size means customers are buying fewer units, which is a land-and-expand question. A stable deal size with a falling ASP means you are discounting to hold the number, which shows up in gross margin two quarters later and in any sales forecast built on last year's price assumptions.