# Average contract value > Understand average contract value in SaaS marketing: a plain-language definition, a worked example, common mistakes and practical next steps. Source: https://saas-marketing.net/glossary/average-contract-value/ Topic: SaaS Metrics and Analytics Type: glossary Published: 2026-09-17 Last updated: 2026-09-17 Publisher: SaaS Marketing (saas-marketing.net) License: CC BY 4.0. Quote or republish with attribution and a link to https://saas-marketing.net/glossary/average-contract-value/ ## Short answer Average contract value is the average value of contracts under a stated policy, often normalized to one year for recurring software agreements. State whether one-time fees and variable usage are included. ## Key takeaways - Define the treatment of contract length, discounts and services. Segment the average when a few enterprise contracts dominate the result. - Confusing total contract value with annual value can double the apparent size of a multiyear deal. - Use the definition consistently across your marketing, product and sales discussions. --- This concept sits within [saas metrics](/saas-metrics/). Use the definition above to align terminology before comparing reports or planning work. ## A SaaS example A two-year subscription worth $24,000 has $12,000 annualized contract value before any separately treated setup fee. This is an illustrative scenario, not a reported result from a customer study. The point is to show the meaning of the term and the decision it affects. ## The mistake to avoid Confusing total contract value with annual value can double the apparent size of a multiyear deal. ## Put the definition to work Define the treatment of contract length, discounts and services. Segment the average when a few enterprise contracts dominate the result. When adding the term to a brief or dashboard, write down the scope and the evidence the team will use. Assign an owner for the definition so it does not change quietly between reporting periods. If two teams use the same label differently, resolve that difference before combining their numbers or handing work between them. ## Related reading - [How to Calculate CAC for SaaS](/guides/how-to-calculate-cac-for-saas/) - [CAC Payback Period](/guides/cac-payback-period/) - [How to Reduce CAC Payback Period](/playbooks/reduce-cac-payback-period/) - [LTV to CAC Ratio](/guides/ltv-cac-ratio/) Browse the [full glossary](/glossary/) for adjacent definitions and the [resource library](/resources/) for working materials. {/* expanded-practice-2026-09 */} ## Apply average contract value in a working review Start by explaining the term without repeating its label. Then point to an observable example and a counterexample. If it is a metric, write the unit, numerator, denominator and time window. If it is a role, process or strategy, identify the responsibility or decision that distinguishes it from adjacent terms. This prevents a shared word from concealing different operating assumptions. For this topic, involve the metric owner and the source-system owner and work from metric dictionary, source records and cohort definition. The relevant unit is a consistent account, user, event or revenue cohort. State the question the review should resolve before choosing a chart, an asset or a tool. If participants disagree about the unit or scope, resolve that disagreement before combining their evidence. ### Evidence to prepare Write the numerator, denominator, unit, period, source and exclusions before interpreting the number. Separate observed data from assumptions and forecasts. A metric can be calculated correctly while still answering the wrong business question. | Review field | What to record | | --- | --- | | Topic | Average contract value | | Decision | The specific action this explanation should help you choose | | Working evidence | metric dictionary, source records and cohort definition | | Unit and scope | a consistent account, user, event or revenue cohort | | Responsible people | metric owner and the source-system owner | | Remaining uncertainty | The missing fact that could change the decision | ### Two situations that can change the interpretation #### When a benchmark compares unlike businesses An enterprise sales-led payback observation may be a poor direct target for a self-serve product with a different cost structure. Use this check: Inspect the benchmark's sample, period, metric definition and distribution. A median from one population is not a universal operating standard. The [focused diagnostic guide](/guides/benchmark-comparison-has-mismatched-populations/) provides the correction process and a working evidence sheet. #### When pipeline coverage includes weak opportunities An opportunity with no buyer-confirmed next step should not be treated like a deal whose approval process is actively underway. Use this check: Review stage criteria, close timing and qualification evidence for included opportunities. A ratio is not a forecast without assumptions about conversion and timing. The [focused diagnostic guide](/guides/pipeline-coverage-uses-unqualified-opportunities/) provides the correction process and a working evidence sheet. ### Record the decision and the limit Twenty activated accounts divided by eighty eligible accounts is 25%. Dividing the same twenty accounts by two hundred individual signups produces 10%, but it mixes units. Both inputs can be real while the second ratio is unsuitable for an account-activation claim. Keep the conclusion beside the evidence that supports it. Record what the team will do, who owns the next action and which event or date will trigger a review. If the underlying definition, audience or product behavior changes, revisit the conclusion rather than assuming the old result still applies. A clear limit is useful information; it tells the next reader where additional investigation is required. Use the [complete topic collection](/topics/saas-metrics/) for related methods and the [category field guides](/industries/) when the product's buying situation or implementation requirements change how the method should be applied. ## Frequently asked questions ### What does average contract value mean? Average contract value is the average value of contracts under a stated policy, often normalized to one year for recurring software agreements. State whether one-time fees and variable usage are included. ### What is an example of average contract value? Illustrative example: A two-year subscription worth $24,000 has $12,000 annualized contract value before any separately treated setup fee. ### What mistake should teams avoid with average contract value? Confusing total contract value with annual value can double the apparent size of a multiyear deal. ### How should a SaaS team apply this concept? Define the treatment of contract length, discounts and services. Segment the average when a few enterprise contracts dominate the result.