Reference
Annual Contract Value Definition
Learn the governed definition of Annual Contract Value, including ACV variants, booked value, first-year value, annualization rules, and ClariLayer Drift Risk.
Metric 12 of 16
Recurring revenue
Annual Contract Value
Annual Contract Value measures the annualized value of a customer contract or opportunity, after deciding how recurring, non-recurring, ramped, multi-year, and discounted amounts are treated.
Governed formula
contract value normalized to one annual period using the governed value basis
- State whether ACV is per contract, per account, per opportunity, or averaged across a population.
- Keep ACV separate from ARR unless both use the same recurring value and active-state rules.
Booked ACV
Uses signed opportunity or contract value normalized to one annual period.
Useful for sales bookings, but it can diverge from live recurring revenue after activation.
First-year ACV
Uses the value expected in the first contract year, including governed ramps or discounts.
Useful for implementation and planning, but it should not be mixed with steady-state annualized value.
Average ACV
Averages annualized contract values across a governed customer or deal population.
Useful for segment strategy, but outlier and population filters need to be visible.
Decisions to lock
Does ACV include only recurring subscription value or also services, usage, and one-time fees?
The metric may be used like ARR even when non-recurring amounts are included.
How are multi-year contracts, ramps, discounts, and future starts normalized?
Different normalization rules change both sales productivity and customer-value views.
Is ACV reported per contract, per account, per opportunity, or as an average?
The grain determines whether renewals, expansions, and multiple contracts are combined or separated.
Validation questions
- Can each ACV amount be traced back to a signed contract, opportunity, or approved quote?
- Are services, usage, discounts, ramps, and multi-year terms classified before annualization?
- Do ACV and ARR reconcile only where their governed inclusion rules intentionally match?
Common drift traps
- Opportunity amount is reused as ACV even though it includes services or usage that ARR excludes.
- A ramped deal is annualized from steady-state value while first-year planning uses discounted value.
- Multiple contracts under one account are averaged in one report and summed in another without a grain label.
Source-system boundary
Contract value spine
CRM, Contracts, Billing platform, Data warehouse
The governed definition should state value basis, contract grain, recurring filters, ramp handling, and discount treatment.
Context-layer proof
ClariLayer's context layer should bind ACV to value basis, contract grain, recurring inclusion rule, and annualization method so sales and finance agents do not substitute opportunity amount for governed contract value.
- Governed signals
- value basis, contract grain, recurring inclusion rule, annualization method
- Review cadence
- Review after quote, contract, packaging, discounting, or sales-process changes.
ClariLayer Drift Risk
ACV is high risk because it sits between sales bookings and recurring revenue, where opportunity, quote, contract, and billing values often differ.
Ambiguity
5/5ACV can mean booked value, first-year value, average contract value, recurring-only value, or total contract annualization.
Source-system dependency
5/5The metric depends on CRM opportunities, quotes, contracts, billing records, discounts, and warehouse normalization.
Time-window sensitivity
4/5Contract start dates, ramps, renewals, amendments, and close dates can shift ACV between periods.
Governance need
5/5ACV drives sales productivity and financial planning, so value basis and grain need explicit approval.
AI-agent risk
An AI agent can compare ACV with ARR or ARPA incorrectly if contract grain, recurring inclusion, and annualization rules are not attached to the value.