Contract economics

Builds directly on the previous lesson's three mechanisms. Where that lesson explained why the pricing ceiling and the multi-year term exist, this one works the actual numbers those forces produce — annual contract value, sales-cycle length, and how the two move together.

---

#Annual Contract Value, by segment

The industry shorthand for "how much is this deal worth per year" is Annual Contract Value (ACV) — total contract value divided by its term length. Benchmarks aggregated across SaaS operating-benchmark research (OpenView-style investor benchmarking, and multiple independent SaaS-finance advisory sources) consistently converge on roughly the same bands:

[Directional] — this is a convergent pattern across multiple independent SaaS-benchmarking sources, not one disclosed census; treat the specific dollar boundaries as illustrative bands, not exact cutoffs. Individual enterprise deals routinely run into seven figures a year in regulated, high-headcount, or mission-critical categories — the bands above describe the median shape of the market, not its ceiling.

#Sales-cycle length tracks contract value, closely and predictably

The same benchmark research shows sales-cycle length rising in step with ACV, which is exactly what the buying-committee mechanism in the previous lesson predicts — more stakeholders and more review stages take more time to align:

• Under $5,000 ACV: roughly 2–4 weeks
• $15,000–$50,000 ACV: roughly 6–13 weeks
• $100,000+ ACV: roughly 4–7 months
• $250,000+ ACV: 6–12 months or longer

[Directional] — same sourcing basis as the ACV table above; the direction (cycle length rises with contract value) is extremely well corroborated across sources, the specific week counts are benchmark aggregation, not a single authoritative study.

#Why this isn't a bad trade — the economics of "slow but sticky"

A 6-to-12-month sales cycle sounds like a straightforward cost against a fast-closing self-serve alternative, and considered alone, it is: it means real cash spent on sales and marketing before a dollar of revenue lands, and a genuinely long runway requirement (Module 5 works this in actual dollars). What it buys in return, following directly from the switching-cost mechanism in the previous lesson, is retention a self-serve product structurally cannot match — once an enterprise buyer has been through this process once, migrated data in, and built internal process around the tool, the cost of repeating that process with a competitor is exactly the asset-specificity gap that made the original sale slow. The multi-year contract term isn't incidental to this — it's usually the vendor formalizing, in the contract itself, the switching-cost relationship that already exists structurally, in exchange for a price concession (Module 3 covers the actual negotiation mechanics of that trade).

#What a working unit-economics picture has to include

A realistic view of whether an enterprise motion pencils out has to hold three figures at once, not just contract value in isolation:

1. Customer acquisition cost (CAC), inflated by the long sales cycle above — a 6-to-9-month cycle means sales and marketing cost accrues for most of a year before the contract signs, not the weeks a self-serve motion assumes.
2. Gross retention, which should be meaningfully higher than a self-serve product's, if the switching-cost mechanism is real — a business plan that assumes enterprise-grade churn without enterprise-grade retention hasn't actually captured the mechanism it's relying on to justify the CAC.
3. Net revenue expansion — enterprise accounts that work well are frequently expanded (more seats, more modules, a wider mandate) rather than simply renewed, which is often where an enterprise motion's economics actually clear, not in the first-year contract value alone.

None of these three numbers is safely assumed from outside — Module 5's capital lesson is explicit about what it costs to survive the CAC-heavy early period before retention and expansion have had time to prove out.