Average Contract Value
Average annualized contract value across new-customer deals signed during the period (ACV). Defines where the company plays on the SaaS deal-size spectrum and dictates the operating model — high-ACV businesses tolerate longer sales cycles and direct sales motions; low-ACV businesses must run product-led or inside-sales motions to keep CAC payback short. Common pitfall: blending new and expansion ACV obscures the new-logo deal-size trend that boards actually want to see. Anchored to KBCM/Sapphire SaaS Survey 2024 §Average Contract Value for cross-company benchmarking. — Sales KPI anchored to KBCM/Sapphire SaaS Survey 2024 (15th Annual).
Rogue ID: sales.avg_contract_value
Type: Currency
Domain: Sales
Definition
Average annualized contract value across new-customer deals signed during the period (ACV). Defines where the company plays on the SaaS deal-size spectrum and dictates the operating model — high-ACV businesses tolerate longer sales cycles and direct sales motions; low-ACV businesses must run product-led or inside-sales motions to keep CAC payback short. Common pitfall: blending new and expansion ACV obscures the new-logo deal-size trend that boards actually want to see. Anchored to KBCM/Sapphire SaaS Survey 2024 §Average Contract Value for cross-company benchmarking.
Formula
Average Contract Value = New Business ARR / New Customers Added (for the same period). For multi-year contracts, use the annualized ACV (TCV / contract term in years), not Total Contract Value (TCV). Restrict to new-logo deals to keep the trend interpretable; track Expansion ACV separately if material.Why it matters
Sets the cost ceiling for the sales motion — at $5k ACV the company cannot afford a field sales team; at $250k ACV inside sales alone usually leaves money on the table. The board uses ACV trend to validate up-market or down-market strategy bets.
How to interpret
Per KBCM/Sapphire SaaS Survey 2024 §Average Contract Value, segmentation bands: SMB ≤ $5k, Mid-Market $5k–$50k, Enterprise > $50k (often $100k+ for true enterprise). ACV doubling over four quarters is a clear up-market motion — make sure CAC and sales-cycle changes are reflected in plan. Flat ACV with rising volume = scaling the existing motion; rising ACV with flat volume = a deliberate up-market bet that needs explicit board buy-in.
Calculation policy
How an AI agent should compute this KPI from messy company data. Free-text rules consumed at reasoning time — not a deterministic DSL. The most common ways to get this wrong are listed under Common miscomputations.
Inclusion rules
- Numerator:
sales.new_business(annualized new-logo ARR for the period). - Denominator:
sales.new_customers_added(count of new logos in the same period, using the same logo unit). - Result is annualized — for multi-year contracts use annualized contract value, not TCV.
Exclusion rules
- Expansion ARR in the numerator — that produces Expansion ACV, a different metric. Track separately if material.
- Existing customers in the denominator — same reason.
- Pilots / unpaid trials.
Required inputs
- New Business ARR for the period.
- New Customers Added for the period (matching logo unit and same period).
Data-source priority
- Same CRM source as
sales.new_businessandsales.new_customers_added— they must come from the same record set.
Edge cases
- Single very large enterprise deal: pulls ACV up dramatically. Surface alongside median deal size to spot when one mega-deal is masking the underlying distribution.
- Mid-period logo-unit change: ACV becomes meaningless across the boundary. Keep methodology pinned and back-cast on change.
- Multi-year contracts with ramp pricing: use Year 1 annualized value for the numerator (matches the New Business ARR convention).
Validation checks
- ACV = New Business ARR / New Customers Added — recompute and verify against any pre-computed value.
- ACV should sit within the segmentation band consistent with the company's ICP (SMB ≤ $5k, Mid-market $5k-50k, Enterprise > $50k). Out-of-band ACV signals up- or down-market drift worth a narrative line.
Common miscomputations
- Including expansion ARR in the numerator — produces a "blended ACV" that boards mis-read as new-logo ACV.
- Counting customers (denominator) using a different logo unit than ARR (numerator) — e.g. counting billing entities for revenue but parent accounts for logos — produces nonsense.
- Using TCV instead of annualized ACV — overstates by the contract term (e.g. a 3-year deal looks 3x as large).
- Reporting a single-deal-pulled ACV without flagging the outlier — leadership reads it as motion improvement when it's one good deal.
- Computing ACV from median deal size when ACV should use the arithmetic mean — these are different metrics (
sales.median_deal_sizeexists for the median).
Related KPIs
sales.new_businesssales.new_customers_addedsales.median_deal_sizesales.average_deal_sizesales.avg_sales_cycle_dayssales.cac
Source
KBCM/Sapphire SaaS Survey 2024 (15th Annual) · section: Average Contract Value — published 2024-09-01.
Why does this cite KBCM/Sapphire SaaS Survey 2024 (15th Annual)? Read the ontology methodology for the published vs editorial tier system, attribution rules, and dispute process.
Industry benchmark
A reference distribution sourced from KBCM/Sapphire SaaS Survey 2024 (15th Annual) (2024):
| Percentile | Value |
|---|---|
| 25th | 25000$ |
| Median | 62000$ |
| 75th | 100000$ |
Higher is better.
Stage relevance
| Company stage | Priority |
|---|---|
| Series A | Core |
| Series B | Core |
| Series C+ | Core |
| Public | Core |
Suggested for stages: Series A, Series B, Series C+, Public.
Default owning functions
- Sales
Machine-readable
- This KPI as JSON:
/api/ontology/sales/avg_contract_value.json - All Sales KPIs:
/api/ontology/sales.json - Full catalog:
/api/ontology/index.json
Average Deal Size
Mean dollar value across active pipeline opportunities (Pipeline Value / Pipeline Deal Count). Distinct from sales.avg_contract_value (ACV) which measures closed-won deals — average_deal_size is forward-looking pipeline-shape, ACV is realized output. Common pitfall: a few oversized deals materially skew the average — always inspect median_deal_size alongside; a large gap between average and median signals a few mega-deals that drive most of the projected number, which concentrates pipeline risk. — Sales KPI, I'mBoard-authored (editorial tier).
Average Sales Cycle (Days)
Average number of days from opportunity creation to closed-won status — measured only on won deals (lost deals are tracked separately). The motion-velocity metric — directly determines how much pipeline coverage is needed, how quickly investment in new reps pays back, and how feedback loops on packaging or pricing experiments compound. Common pitfall: blending segment cycles (SMB and Enterprise often differ 5–10×) into a single average hides material trend signals — segment-cut the metric where deal-volume permits. — Sales KPI, I'mBoard-authored (editorial tier).