.png)
Frameworks, core principles and top case studies for SaaS pricing, learnt and refined over 28+ years of SaaS-monetization experience.
Thank you! Your submission has been received!
Oops! Something went wrong while submitting the form.
What Is the Real ROI of Locking in Multi Year Customers
Multi-year contracts have become a familiar answer to an uncomfortable SaaS question: how can a company make revenue more predictable without slowing growth? The usual logic is simple. Give a customer a discount, secure several years of revenue, reduce renewal risk, and improve the forecast.
That logic is incomplete. A multi-year signature can create committed revenue, but it can also lock in a weak price, conceal poor adoption, and postpone a hard renewal conversation rather than eliminate it. The stakes are high because the concession often lasts longer than the sales leader who approved it. Our view is direct: multi-year contracts create real ROI when they fund an adoption-and-expansion plan and when the discount is smaller than the renewal risk and pricing flexibility the vendor gives away. They destroy ROI when used as a quarter-end device to turn an unproven customer into a discounted backlog number.
A signed three-year agreement answers one question well: what revenue is contractually committed? It does not answer the more important question: did the company improve the expected lifetime gross profit of the account?
The distinction matters because revenue recognition and cash collection do not convert a poor deal into a good one. Salesforce’s fiscal 2026 filing, for example, reported $72.4 billion in remaining performance obligations as of January 31, 2026, including $37.3 billion due after the next 12 months. Salesforce also cautioned that this measure is affected by contract duration, renewal timing, currency, and other factors.
ServiceNow makes the same point more plainly. As of December 31, 2025, 54% of its $28.2 billion in remaining performance obligations sat beyond the next 12 months. Yet its filing also states that remaining performance obligations are contracted revenue, not a prediction of future growth.
The real ROI calculation has five parts:
- Incremental gross profit from avoiding churn before the next renewal.
- Cash-flow benefit from earlier invoicing or prepayment.
- Lower selling and procurement effort at fewer renewal events.
- Expansion earned because the customer has time to adopt more use cases.
- Less the discount, price caps, support burden, and lost ability to reprice.
The contract form determines which of those benefits are available. A three-year term billed annually is fundamentally different from a three-year prepayment, even if both produce the same total contract value.
Exhibit 1: Longer terms create different kinds of economic value
For operators, the implication is straightforward: a multi-year deal should be measured against the economics of the annual alternative, not against the comfort of a larger booking.
Multi-year contracts are strongest when the product becomes more valuable after deployment. Core systems often fit that pattern because the buyer must configure workflows, integrate data, train users, and change operating habits before value becomes visible.
Workday is a useful reference point. In its fiscal 2026 10-K, filed March 6, 2026, Workday said its subscription contracts are generally noncancelable and “generally three years or longer.” It reported $28.1 billion of subscription backlog as of January 31, 2026, with $15.8 billion expected to be recognized during the following 24 months. A three-year structure makes sense for a product where the implementation, operating change, and value realization often extend well beyond the first quarter.
Monetizely’s 5-Step Pricing Framework helps explain why. The sequence begins with business goals and customer segments, then moves to packaging, the pricing metric, price points, and operationalization. The order matters. A term is part of the package offered to a particular buyer, not a substitute for knowing who that buyer is, what they value, how usage should be charged, or whether billing and customer success can support the promise. As developed more fully in Monetizing Agentic AI, the framework places terms after the company has identified its goal and segment, but before it has declared victory on price.
That sequence exposes a common sales mistake. A company sells a three-year deal to a customer whose usage is still uncertain, then labels the contract “retention.” In reality, the company has traded away price before it knows whether the buyer will adopt.
A better test asks whether the customer can reach a clear value milestone before the first renewal would otherwise occur. The scorecard below turns that question into an operating decision.
Exhibit 2: A three-year term should be earned through account evidence
| Account condition | 0 points | 1 point | 2 points |
|---|---|---|---|
| Time to first measurable value | More than 12 months | 4-12 months | Within 90 days |
| Deployment readiness | Data, sponsor, or workflow still unclear | Some dependencies remain | Clear owner, data access, and launch plan |
| Adoption breadth | One team is experimenting | One function is active | Multiple teams or use cases are planned |
| Expansion path | No identified next purchase | General interest in add-ons | Named users, modules, or volume triggers |
| Cost predictability | Usage or service cost is unknown | Some volatility | Stable unit economics and clear limits |
| Total score | Recommended commercial posture |
|---|---|
| 8-10 | Offer a three-year agreement with disciplined discount limits |
| 5-7 | Keep the primary commitment at one year while creating a priced expansion path |
| 0-4 | Do not use term length to solve an adoption problem |
The table makes the core point: length should follow evidence of customer value. It should not be offered merely because the buyer asks for a discount or the quarter needs bookings.
The arithmetic behind multi-year ROI is more demanding than most deal desks admit. A vendor should not compare three years of contracted revenue with one year of current ARR. It should compare the discounted present value of the multi-year offer with the expected value of annual renewals.
Consider a $100,000 annual subscription. Under annual terms, assume an 85% renewal probability after year one and again after year two. Under a three-year agreement, assume the vendor gives a 10% discount, reducing annual revenue to $90,000. Using a 10% discount rate, the three-year contract is worth more because it removes enough churn risk to offset the concession.
Exhibit 3: A three-year commitment can create value even with a discount
| Measure | Annual renewable contract | Three-year agreement |
|---|---|---|
| Year 1 revenue | $100,000 | $90,000 |
| Expected Year 2 revenue | $85,000 | $90,000 |
| Expected Year 3 revenue | $72,250 | $90,000 |
| Nominal three-year revenue | $257,250 | $270,000 |
| Net present value at 10% | $236,983 | $246,198 |
| Incremental value from the three-year term | $9,215 |
At an 85% annual renewal probability, the vendor can give a 10% discount and still create $9,215 of incremental revenue value before considering differences in support cost, sales commissions, or expansion.
The result changes sharply as retention improves. If a customer is already highly likely to renew, the vendor is not buying much additional certainty. It is mostly giving the buyer a cheaper price.
Exhibit 4: Better renewal odds justify smaller multi-year discounts
| Expected annual renewal probability | Maximum three-year discount that breaks even |
|---|---|
| 75% | 21.5% |
| 85% | 13.4% |
| 90% | 9.1% |
| 95% | 4.6% |
The message is counterintuitive but important: the best customers often deserve the smallest term discounts because they would probably renew anyway.
Price growth makes the constraint tighter. If the annual alternative includes a 3% price increase, the break-even discount at an 85% renewal probability falls from 13.4% to 11.2%. A vendor that grants a flat three-year rate is giving away more than a discount. It is also giving the customer an option on future prices.
Public SaaS pricing pages show that mature vendors separate commitment from deep discounting. Slack’s published pricing, accessed September 8, 2026, lists Pro at $8.75 per user per month when paid monthly and $7.25 when paid annually, a 17.1% annual-payment reduction. Business+ is listed at $18 monthly and $15 annually, a 16.7% reduction.
Atlassian takes a more restrained approach to longer commitments. Its cloud licensing page states that annual subscriptions may be quoted for 12 or 24 months, while a 24-month purchase is double the annual price. Annual cloud pricing is lower than monthly pricing, but the company does not present a further 24-month list-price reduction simply for extending the term.
Those examples reveal a practical design principle. Annual prepayment can merit a published discount because it reduces payment friction and improves cash collection. A second or third contractual year should not automatically earn an additional concession. The stronger exchange is usually rate protection, implementation support, added flexibility to reassign seats, or a pre-priced expansion schedule.
Salesforce’s fiscal 2026 10-K reinforces why. It states that multi-year subscription agreements billed annually can produce a high unbilled remaining-performance-obligation balance early in the contract, but that balance runs down toward renewal. The filing also notes that a low balance can signal an impending renewal without predicting whether renewal will occur. The term creates visibility. It does not remove the need to build customer value before the next decision point.
The strongest terms preserve expansion while preventing capacity waste
The central danger in multi-year contracting is not that customers leave. It is that customers stay but stop growing because the original package was oversized, underused, or priced too cheaply to expand.
A well-designed agreement therefore commits the customer to the core product while preserving room for the account to grow. For a workforce platform, the core may be a minimum employee population with a defined annual true-up. For a workflow platform, it may be a committed set of products plus pre-priced additional business units. For a collaboration tool, it may be a one-year seat commitment with simple monthly additions rather than a speculative three-year seat count.
ServiceNow’s 2025 filing illustrates the operating reality behind that approach. The company says it generally invoices subscription customers annually in advance, its contracts are generally noncancelable, and its sales commissions on initial and expansion contracts are amortized over a five-year benefit period. The lesson is not that every SaaS company should copy ServiceNow’s terms. Rather, it is that the commercial, finance, and customer-success systems must all support the long-term promise.
Exhibit 5: Contract architecture should follow the customer’s adoption pattern
| Customer situation | Primary commitment | Pricing posture | Why it creates ROI |
|---|---|---|---|
| Core system with a 12-18 month deployment | Three-year subscription, annual invoicing | Small discount or rate protection with scheduled increases | Gives the vendor time to secure adoption and makes implementation investment rational |
| Proven platform expanding across functions | Three-year core agreement | Pre-priced add-ons and clear volume bands | Captures future usage without reopening the entire price book |
| Collaboration product tied to changing headcount | One-year seat commitment | Annual-payment discount; flexible additions | Limits capacity waste while preserving low-friction growth |
| New product with unproven business value | One-year agreement | Price the pilot or initial use case cleanly | Keeps the vendor from discounting before value is demonstrated |
| Usage-sensitive product with uneven demand | Annual committed spend | Defined overage rates and usage limits | Protects margin while giving the buyer a predictable budget |
The architecture is decisive: use a multi-year commitment for the durable core of customer value, not for speculative capacity, unproven modules, or variable demand that the buyer cannot forecast.
A company with 80% of its revenue under multi-year contracts can still have weak economics if those contracts carry excessive discounts, flat prices, or thin adoption. Equally, a company with more annual agreements can have excellent economics if it has strong renewals, regular price improvement, and fast expansion.
Monetizely’s position is that the portfolio should be managed around expected gross-profit value, not multi-year booking volume. Every three-year agreement should clear a financial hurdle that accounts for the account’s renewal likelihood, the discount, the cost to serve, and the value of keeping future price and package choices open.
Operators should act on that position in five ways:
Set a company-wide hurdle rate for multi-year deals. Require each segment to show the maximum discount that still beats the annual-renewal alternative.
Track realized value after signing. Report adoption, gross margin, expansion, and price realization at months 6, 12, and 24 alongside bookings.
Give customer success a formal role in term approval. A three-year deal without a credible adoption plan should not qualify as a strategic win.
Evaluate sales compensation on durable account value. Reward gross-profit retention and expansion, not only total contract value booked in the current quarter.
Use multi-year mix as a strategic portfolio measure. Increase it in segments where deployment and adoption require time; resist it in segments where value appears quickly and price flexibility is more valuable.
Assumptions: The modeled figures use a $100,000 starting annual contract value, flat annual pricing unless stated otherwise, 75%-95% annual renewal probabilities, annual invoicing, and a 10% discount rate. The model excludes taxes, implementation revenue, financing fees, changes in gross margin, and expansion revenue.
Footnotes
- https://www.amazon.com/Monetizing-Agentic-AI-Handbook-Transformation/dp/B0H7Z13VKJ/
- Salesforce, Form 10-K for the fiscal year ended January 31, 2026, filed March 2, 2026. (d18rn0p25nwr6d.cloudfront.net)
- Workday, Form 10-K for the fiscal year ended January 31, 2026, filed March 6, 2026. (sec.gov)
- ServiceNow, Form 10-K for the fiscal year ended December 31, 2025, filed January 29, 2026. (sec.gov)
- Slack and Atlassian, official pricing and cloud licensing pages, accessed September 8, 2026. (atlassian.com)