ACV vs. ARR for Usage-Based SaaS Contracts
Usage-based pricing collapses ACV because contracts lack committed minimums at signature.

ACV and ARR describe the same underlying economics at two different levels of resolution, and they only agree with each other under a narrow set of conditions. ACV is calculated as Total Contract Value minus one-time fees, divided by contract years. It is a per-deal number, annualized so that contracts of different lengths can be compared on equal footing. ARR is the company-wide sum of every active ACV at a given point in time. ACV is the building block; ARR is the building constructed from it, and the two operate at different levels of granularity. A finance team needs to understand how each one is built before trusting either.
The distinction matters because ACV is measured at the moment a single contract is signed, while ARR is a portfolio aggregate measured at a moment in time across the entire customer base. One is a bookings metric tied to a specific negotiation. The other is a state metric that describes the business as a whole. Neither TCV nor MRR does the job ACV and ARR do in an annual-contract business, and conflating them with ACV or ARR is where early mistakes tend to start.
Under one specific configuration, ACV and ARR collapse into the same number. That configuration requires the contract to run exactly one year, the price to be flat for the duration, and no ramp structure that changes the price in later periods. A three-year deal with no one-time fees and a flat annual price still nests cleanly: its ACV matches its annual contribution to ARR exactly, year over year, because nothing about the price changes and nothing needs to be estimated. This is the environment ACV and ARR were built for, a world of fixed-term, seat-based, annual contracts where the price on the contract is the revenue the business can count on. The three conditions, fixed term, flat price, no one-time fees, are what hold that agreement together. Removing any one of them causes the two metrics to separate before usage-based pricing ever enters the picture.
Multi-year discounts and ramp structures strain the ACV-ARR relationship before any usage variability appears

The divergence between ACV and ARR is not a usage-based pricing invention. It appears in ordinary multi-year subscription deals, long before any contract ties price to consumption. That gap between the two numbers flows directly into forecast error, and it compounds each time a similar deal closes.
That gap multiplies across a pipeline of similar deals, so a forecast built on CRM-reported ACV starts to describe a business that does not exist in its recognized revenue.
Ramp contracts introduce a second version of the same problem. A ramp structure prices Year 1 lower than later years, so the ACV you calculate at signature reflects a discounted entry price, but the long-run ACV reflects the escalated rate the customer eventually pays. Averaging the two naively obscures the actual shape of revenue the business will realize, masking a slow ramp as a flat, predictable line.
The incentive structure built on top of these numbers makes the distortion worse. Most high-performing SaaS organizations have corrected for this by compensating on first-year ACV or first-year ARR instead, aligning rep behavior with revenue the company can actually recognize on the books. A related distortion comes from one-time fees folded into the subscription line: in one documented due-diligence scenario, implementation fees and custom development work embedded inside the subscription line reduced the reconcilable ARR figure materially. That revenue earned no software multiple, because it was services revenue wearing a recurring-revenue costume. Conflating TCV with ACV, quoting a three-year total as if it were the annual figure, remains one of the most common mistakes in early-stage SaaS reporting. If discounting and ramp structures alone can produce gaps this large inside fixed-price contracts, consumption variability does not introduce a new problem so much as turn an occasional reporting error into a structural feature of the business.
Usage-Based Pricing and the ACV Calculation at Signature
Usage-based pricing does something multi-year discounts and ramps do not: it removes the number ACV is supposed to measure before the ink on the contract dries. Without a committed minimum, a company has no ACV at signature, only a probabilistic estimate based on consumption forecasts that may or may not materialize. What used to be an edge case, a handful of consumption-priced contracts tucked into an otherwise seat-based book of business, is now a mainstream structure across SaaS, with AI products accelerating its adoption. Deloitte's 2026 TMT forecast shows seat-based revenue sliding as a share of total SaaS income, because vendors now tie price to tokens consumed, workflows executed, or outcomes delivered, not to named users.
GitHub's move of Copilot to usage-based billing on June 1, 2026 shows why flat pricing became untenable for a product with this much variance in how it gets used. Averaging those two users into a single flat price either overcharges the light user or loses money on the heavy one, and a single ACV figure for either customer becomes a fiction the moment usage starts to diverge from the forecast.
Intercom's Fin product prices at $0.99 per successful resolution, charging only for the fraction of conversations it resolves and absorbing the cost of the ones it does not. The ACV of any given Fin customer is unknowable at the point of signature, because it depends entirely on a resolution rate that varies by customer and by conversation.
Salesforce's Agentforce pricing shows the same uncertainty built into a menu of options rather than a single model: a credit-based path, a flat per-conversation rate, a per-user monthly subscription, a lower-cost user license paired with separate credits, and a bundled edition priced higher per user. The credit and per-conversation paths produce no deterministic ACV at signing, because the final bill depends on how many credits or conversations the customer actually consumes. A gross margin problem makes the stakes higher than a reporting inconvenience: traditional SaaS gross margins compress toward a meaningfully lower level for AI-native businesses, because every API call carries a scaling inference cost. The revenue-per-unit calculation becomes unstable because the cost side of the ledger is no longer fixed. This is not a calculation problem that better spreadsheet discipline can fix. ACV itself becomes an ambiguous term the moment a contract has no floor to anchor it.
The ACV-ARR gap compounding when usage revenue is folded into ARR without a committed-revenue qualifier
Folding unconstrained usage revenue into ARR without qualifying it overstates the contractually committed base of the business, misleads anyone running a valuation off that number, and creates reconciliation failures the moment an investor asks for the underlying contracts. The remainder consisted of implementation fees and consumption revenue that had been folded into the subscription line, inflating a number that was supposed to represent dependable, recurring revenue.
Snowflake offers a public-market illustration of how seriously this distinction is taken at scale. Snowflake does not formally define ARR in its filings, a deliberate choice that reflects how its consumption-based revenue model makes the word "recurring" genuinely contestable. Most private SaaS companies cannot replicate it without explicit alignment with their investors on what the number means and does not mean.
Investors tend to do the separation themselves when a company does not do it first. Buyers in due diligence typically split committed recurring revenue from variable consumption revenue, and they weight the consumption piece more heavily for volatility and downside risk. ARR that includes consumption revenue without disclosing it is ARR that gets discounted once the buyer finds the mix. The multiple applied to committed ARR is not the multiple applied to a consumption run-rate, and treating the two as interchangeable inflates the implied value of the business on paper.
There is a blind spot sitting inside the growth numbers themselves. If a finance team tracks only new-logo ACV, it measures less than half of the actual growth story, because the expansion engine driving the rest of it runs on usage patterns that UBP makes inherently variable. In minimum-commit-plus-overage structures, the annualized usage figure embedded in ARR can overlap with the committed minimum already counted elsewhere, producing double-counted ARR that sits quietly on the books until a diligence process or an audit surfaces it.
The two ACV figures every usage-based contract now requires
The resolution to this ambiguity is definitional before it is procedural. Usage-based contracts require finance teams to maintain two separate ACV figures, committed and realized, and they need a usage run-rate tracked adjacent to ARR rather than folded inside it.
Committed ACV is the contractual minimum a customer owes regardless of consumption. It is the only portion of the relationship that belongs in ARR under a strict, renewable-commitment definition, because it is the only portion the company can count on independent of how the customer behaves. Realized ACV is what the customer actually spends, a figure that can exceed committed ACV or, in a zero-minimum contract, replace it. Realized ACV reflects true account economics, but it carries no forward contractual guarantee, so it cannot stand in for ARR without misrepresenting how durable that revenue is.
Tracking only one of the two figures distorts the picture in a predictable direction. Neither figure is sufficient on its own, so both need to sit side by side in the same reporting package. A third figure, usage run-rate, the annualized version of trailing usage revenue, should be tracked and labeled explicitly as a non-contractual indicator of current customer behavior, never folded into ARR without disclosure.
The clean-nesting rule from fixed-price contracts depends on contract certainty at signature, and that certainty disappears the moment even a modest committed minimum gets layered with usage overages. Hybrid structures like this are increasingly common across AI and SaaS pricing, so billing platforms such as Flexprice, built to model both committed and consumption charges on a single engine, have become a practical requirement if you want to keep ACV and ARR definitions consistent across a contract portfolio rather than reconciled by hand after the fact. Reporting only mean ACV across a usage-priced customer base hides skewed distributions, where a handful of high-consumption accounts pull the average up while most customers sit near the committed floor. That pattern describes a risk profile concentrated in a few accounts rather than a growth signal spread across the base. The boundary rule that resolves most investor concerns is narrow and specific: ARR should include only revenue tied to renewable contractual commitments, and usage run-rate should stand beside it as a complementary signal of business momentum, never as a component of the ARR stack itself.

ASC 606 treatment of usage variability and audit-ready revenue schedules for UBP contracts
The committed-versus-realized distinction is not only a management-reporting preference. ASC 606 requires finance teams to estimate, constrain, and update variable consideration every reporting period, and most billing systems are not architecturally built to support that discipline once a contract's price depends on usage.
Three contract structures carry three different recognition treatments, and billing systems tend to blur the differences between them. A minimum-commit-plus-overage contract does not qualify for that expedient: the minimum has to be recognized ratably over the contract term, while the overage counts as variable consideration that has to be estimated and constrained under the standard. Prepaid credits create a third pattern entirely, generating deferred revenue that can only be recognized as the customer actually consumes the credits, and this is the case that billing systems mishandle most often, since a credit purchase looks like revenue at the moment of sale when it is, in fact, a liability until consumed.
Mid-term contract modifications expose a further gap. The actual ASC 606 schedule usually gets built in a spreadsheet that references the billing system's output rather than one the billing system produces on its own, a workaround rather than a system of record.
What hybrid pricing structures do to both metrics
Hybrid pricing, a committed minimum layered with usage overages, is now the dominant structure finance teams building in 2026 actually have to account for, and it forces ACV and ARR to be defined separately for each layer of the contract rather than as a single blended number. Committed ACV covers the minimum; realized ACV covers the minimum plus whatever overage the customer actually generates. A single blended ACV figure flattens that distinction and reintroduces the exact ambiguity the committed-realized split was built to remove.
Net revenue retention faces the same pressure. NRR is traditionally built from changes in ARR across a cohort over time, expansions, contractions, and churn measured against a known starting base. When part of a customer's revenue is a fixed commitment and part is consumption that moves with usage, a retention metric calculated only off the committed layer understates genuine account growth, because it never captures the overage revenue expanding alongside it. The accurate approach tracks both: a retention metric on committed ACV as the conservative, contractually guaranteed floor, and a second retention metric on total realized revenue as the indicator of actual account momentum, reported side by side rather than collapsed into one number.
A ramp contract layered with usage overages worsens the mismatch between the contract's stated price and its recognized revenue described earlier in the piece, because Year 1 pricing, the escalated long-run rate, and a variable consumption component are now all moving independently inside the same contract. If finance teams manage that combination, they need billing logic that can model each year's consumption separately and recalculate recognized ARR as actual usage data arrives, turning what was once a forecasting error into a number precise enough to trust. That is the standard ACV and ARR were held to under fixed-price contracts, and it remains the standard worth rebuilding for hybrid ones.


