Boards grade sales teams on ACV when comparing deal productivity, on TCV when comparing total booked value, and on ARR when comparing company run-rate. The three answer different questions.
ACV, or annual contract value, is a signed deal's total value normalized to one year. If a customer signs a three-year contract for 300,000, the ACV is 100,000. ACV is the metric sales teams use to compare deals of different lengths on an apples-to-apples basis. It is distinct from TCV, which is the full multi-year value, and from ARR, which is the recurring run-rate across the whole customer base at a point in time.
ACV answers five questions a well-run sales org asks every quarter: how big is a typical deal, is deal size growing, which segments carry which ACV, how long are the contracts underneath those deals, and how does ACV compare to the recurring ARR run-rate. Six quick angles cover it.
ACV equals the total committed value of the contract divided by the contract length in years. A one-year 60,000 deal has an ACV of 60,000. A three-year 240,000 deal has an ACV of 80,000. A multi-year deal with ramped pricing (year one at 50,000, year two at 100,000, year three at 150,000) still gets normalized by averaging the three years or using year one depending on the finance team's convention.
Without normalization, a rep who closes a three-year 300,000 deal looks like they outperformed a rep who closed a one-year 150,000 deal twice. ACV flattens the comparison: both close at 100,000 and 150,000 respectively. ACV is how boards grade rep productivity when contract lengths vary across the team.
TCV, or total contract value, is the full committed value across every year of the deal, including ramps and any committed services. ACV is TCV divided by the contract length. A five-year 1,000,000 deal has a TCV of 1,000,000 and an ACV of 200,000. Finance reports TCV on the booking. Sales reports ACV on the comparison.
ARR, or annual recurring revenue, is the sum of annualized recurring revenue across every active customer at a point in time. ACV is the annualized value of a single deal when it is signed. Many deals of varying ACV add up to the company's ARR. ACV is a sales metric. ARR is a finance and board metric.
Most teams calculate ACV using recurring software fees plus committed usage. One-time services, implementation fees, and professional services are typically excluded because they do not repeat. The exclusion matters for deals where services are a big line item. A 300,000 TCV with 90,000 of implementation lands at 70,000 ACV, not 100,000, if the services are stripped out.
A healthy SaaS org tracks ACV by segment because segments move at different ACV baselines. Enterprise ACV lives in the six to seven figures. Mid-market lives in the mid-five figures. SMB lives under 15,000. Mixing them hides the real signal, which is which segment is growing and which is softening on deal size quarter over quarter.
ACV reads like a one-line formula and gets complicated the moment ramps, discounts, and services enter the deal. These six examples match how a controller would normalize each one. Rules of thumb here beat improvising on the spot during a board slide review.
A customer signs for one year at 60,000. ACV is 60,000. TCV is 60,000. ARR added to the company run-rate is 60,000. Everything matches because the deal is one year with no ramps and no services. This is the clean case most teams start their reports with before layering in the harder examples.
A customer signs three years at 80,000 per year. TCV is 240,000. ACV is 80,000. ARR added is 80,000. The deal is three times a one-year 80,000 deal from a run-rate perspective. The sales rep gets credited with 80,000 of ACV even though the company has 240,000 of booked future revenue in hand.
A customer signs three years with ramped pricing: 50,000 year one, 100,000 year two, 150,000 year three. TCV is 300,000. The common ACV conventions are averaging to 100,000, or using year one at 50,000, or using the ending run-rate at 150,000. Pick a convention and apply it consistently. The CFO cares more about consistency than which rule.
A one-year 120,000 subscription with a 30,000 one-time implementation fee has a TCV of 150,000 but an ACV of 120,000. The services do not repeat, so finance strips them from the ACV calculation. The sales rep gets credit for 120,000 of ACV and 150,000 of TCV. Confusing the two inflates ACV by 25 percent and breaks the comparison with pure-subscription deals.
A customer signs a 100,000 annual commitment with usage over commit billed at list. ACV books at the commit, 100,000, because that is what the customer signed for. If the customer consumes 140,000 in year one, finance may recognize 140,000 of revenue but the next renewal ACV still starts at the committed baseline until the customer resigns at a higher commit.
ACV always uses net price, not list. A deal with a 100,000 list and a 25 percent discount lands at 75,000 ACV, not 100,000. Reporting ACV at list is a common forecast-inflation mistake junior teams make. The CRM should capture both the list price and the net price on the opportunity so the discount percentage shows up on every deal review.
ACV is not a vanity metric. It drives comp plans, segment coverage, forecasting, and investor pitches. Six places where the ACV number quietly steers a sales org every quarter and the mistake teams make when they ignore it.
A rep's quota is usually built from a target ACV multiplied by a target deal count. A 1,200,000 quota at 100,000 ACV means twelve deals a year. At 50,000 ACV, that is 24 deals. If management expects twelve but the pipeline is averaging 50,000, the rep is set up to miss. Comp plans should match actual ACV, not aspirational ACV.
A sales org splits segments by expected ACV. Enterprise reps work accounts expected to produce 100,000+ ACV. Mid-market reps work 25,000 to 100,000. SMB reps or self-serve covers under 25,000. Mixing an SMB account into an enterprise rep's book burns rep capacity on a deal size that cannot carry the overhead.
Pipeline coverage math uses ACV. A rep with a 1,200,000 quota, a 100,000 average ACV, and a 25 percent win rate needs 4,800,000 of pipeline to make the number. The rep with the same quota but a 50,000 ACV needs the same 4,800,000 of pipeline distributed across twice as many deals, which is a different coverage conversation.
When a mid-market rep forecasts a 500,000 deal and their segment average ACV is 60,000, the forecast is either a career-maker outlier or a story that is going to collapse under scrutiny. ACV distribution gives the manager the sanity check. Deals that live three standard deviations outside the segment average need a different conversation than deals inside the band.
Investors read ACV growth as a signal of segment maturity. Rising ACV means the company is winning bigger customers, selling bigger packages, or landing more use cases per customer. Flat or declining ACV with growing deal count can look like a shift down-market, which boards will want explained. ACV is a slide in almost every Series B through Series D update.
Mature teams split starting ACV (what landed on day one) from net ACV (where the customer is 12 months in after upsells and cross-sells). A 60,000 start that lands at 90,000 after one year has a net expansion rate of 150 percent on that account. That motion funds growth without new logos and is one of the highest-ROI things an existing book of business can produce.
Strkr captures TCV, contract length, discounts, and services on every opportunity, and derives ACV automatically on every deal, segment, and quarter. Pipeline and forecast views ship with ACV baked in. Start a workspace in minutes or walk the full platform.
ACV stands for annual contract value. It is the normalized annual value of a signed customer contract, calculated by dividing the total committed value of the contract by the contract length in years. ACV lets sales teams compare deals of different lengths on an apples-to-apples basis and is the standard metric used in SaaS comp plans, quota setting, and segment design.
ACV equals total contract value divided by the contract length in years. A one-year 60,000 contract has an ACV of 60,000. A three-year 300,000 contract has an ACV of 100,000. Finance teams usually exclude one-time services and implementation fees from the ACV calculation because those do not recur. For ramped multi-year deals, teams either average the ramp or use year one, applied consistently.
TCV, or total contract value, is the full committed value across the entire length of the deal. ACV is TCV divided by the contract length in years. A three-year 300,000 deal has a TCV of 300,000 and an ACV of 100,000. Finance reports TCV on the booking because that is the total future revenue committed. Sales reports ACV on productivity comparisons because it normalizes for deal length.
ACV is the annualized value of a single deal when it is signed. ARR, or annual recurring revenue, is the sum of annualized recurring revenue across every active customer at a point in time. ACV is a per-deal sales metric. ARR is a company-wide finance and board metric. Many deals of varying ACV add up to the company's ARR, and ARR shifts every day as new deals land, customers expand, and others churn.
There is no single good ACV because segment and category drive the baseline. SMB SaaS lives at 2,000 to 15,000 ACV. Mid-market lives at 15,000 to 100,000. Enterprise lives at 100,000+ with named accounts commonly in the 250,000 to 1,000,000 ACV range. The question is less about absolute ACV and more about whether ACV is growing, whether the sales motion matches the ACV, and whether the segment economics work at the current ACV.
The common convention is no. Services and implementation fees are one-time, so they do not recur, which breaks the apples-to-apples normalization ACV is designed to deliver. A 120,000 subscription with a 30,000 implementation fee has a TCV of 150,000 but an ACV of 120,000. Some teams report a services-included and a services-excluded ACV side by side when services are a strategic revenue line. Consistency across every deal matters more than the specific rule.
A sales rep's quota is typically built from an expected ACV multiplied by an expected deal count. A rep with a 1,200,000 quota at 100,000 expected ACV is being asked for twelve deals a year. The comp plan assumptions should match reality. If management expects 100,000 ACV but the pipeline is averaging 50,000, the rep is set up to miss on deal count. Ramped reps often have lower ACV expectations in their first two quarters to account for the smaller deals that close early.
Strkr captures the deal's TCV, contract length, services line, and discount percentage on every opportunity. ACV is calculated as a derived field so every deal, segment, rep, and quarter rolls up cleanly without manual spreadsheet math. Strkr AI flags deals where the proposed ACV sits more than two standard deviations outside the segment average so forecast reviews catch outlier deals early. Reporting ships with ACV by segment, by rep, and by cohort as a default view.
No sales call, no migration consultant, no four-month implementation. Enter your card, get 14 days of the full Pro tier, cancel any time before day 14 with zero charge. Spin up a workspace, import your CSV, and have something useful before lunch.
