The Promise Gap: Improving Renewal Rates with Documented Value
The Promise Gap: Improving Renewal Rates with Documented Value

Dan Sixsmith explains why adoption alone cannot secure renewals, and how documented business outcomes close the promise gap.
Share
Based on a session at FRONTIER by Planhat, on 10 November 2026.
If your 10 largest customers were up for renewal tomorrow, could you prove that your software delivered the business outcomes you promised them?
Most B2B software companies can tell customers how often their products are used, which features have been adopted and how engagement has changed. Far fewer can quantify the revenue generated, costs reduced or operational improvements achieved through that usage. Yet those are the outcomes that justified the original purchase, and they’re what customers ultimately need to defend their investment.
The distance between what a software company promises during the sale and what it can prove it delivered is the promise gap. Closing it requires a change in how sales and customer success operate, with business outcomes documented from the beginning and measured throughout the relationship.
The distance between what a software company promises during the sale and what it can prove it delivered is the promise gap.”
“
Based on a session at FRONTIER by Planhat, on 10 November 2026.
If your 10 largest customers were up for renewal tomorrow, could you prove that your software delivered the business outcomes you promised them?
Most B2B software companies can tell customers how often their products are used, which features have been adopted and how engagement has changed. Far fewer can quantify the revenue generated, costs reduced or operational improvements achieved through that usage. Yet those are the outcomes that justified the original purchase, and they’re what customers ultimately need to defend their investment.
The distance between what a software company promises during the sale and what it can prove it delivered is the promise gap. Closing it requires a change in how sales and customer success operate, with business outcomes documented from the beginning and measured throughout the relationship.
The distance between what a software company promises during the sale and what it can prove it delivered is the promise gap.”
“
Based on a session at FRONTIER by Planhat, on 10 November 2026.
If your 10 largest customers were up for renewal tomorrow, could you prove that your software delivered the business outcomes you promised them?
Most B2B software companies can tell customers how often their products are used, which features have been adopted and how engagement has changed. Far fewer can quantify the revenue generated, costs reduced or operational improvements achieved through that usage. Yet those are the outcomes that justified the original purchase, and they’re what customers ultimately need to defend their investment.
The distance between what a software company promises during the sale and what it can prove it delivered is the promise gap. Closing it requires a change in how sales and customer success operate, with business outcomes documented from the beginning and measured throughout the relationship.
“The distance between what a software company promises during the sale and what it can prove it delivered is the promise gap.”
From the consumption gap to the promise gap
In the era of perpetual licenses, customers purchased software upfront. Vendors had limited financial dependence on what happened after the transaction.
SaaS changed that relationship. Renewals made ongoing adoption essential to revenue retention. Customer success emerged to address the consumption gap, helping customers implement and use software effectively. Companies tracked logins, feature adoption and usage because customers who weren’t using the product had little reason to renew.
Now AI is changing how customers evaluate their software investments. When technology can automate substantial amounts of work, the question increasingly becomes what the business accomplished rather than how much software it consumed. A customer might achieve high adoption without realizing the financial or operational improvements that motivated the purchase.
Adoption doesn’t equal value. Usage doesn’t prove that the promised outcome has been achieved.
Software companies need to become promise keepers.”
“
From the consumption gap to the promise gap
In the era of perpetual licenses, customers purchased software upfront. Vendors had limited financial dependence on what happened after the transaction.
SaaS changed that relationship. Renewals made ongoing adoption essential to revenue retention. Customer success emerged to address the consumption gap, helping customers implement and use software effectively. Companies tracked logins, feature adoption and usage because customers who weren’t using the product had little reason to renew.
Now AI is changing how customers evaluate their software investments. When technology can automate substantial amounts of work, the question increasingly becomes what the business accomplished rather than how much software it consumed. A customer might achieve high adoption without realizing the financial or operational improvements that motivated the purchase.
Adoption doesn’t equal value. Usage doesn’t prove that the promised outcome has been achieved.
Software companies need to become promise keepers.”
“
From the consumption gap to the promise gap
In the era of perpetual licenses, customers purchased software upfront. Vendors had limited financial dependence on what happened after the transaction.
SaaS changed that relationship. Renewals made ongoing adoption essential to revenue retention. Customer success emerged to address the consumption gap, helping customers implement and use software effectively. Companies tracked logins, feature adoption and usage because customers who weren’t using the product had little reason to renew.
Now AI is changing how customers evaluate their software investments. When technology can automate substantial amounts of work, the question increasingly becomes what the business accomplished rather than how much software it consumed. A customer might achieve high adoption without realizing the financial or operational improvements that motivated the purchase.
Adoption doesn’t equal value. Usage doesn’t prove that the promised outcome has been achieved.
“Software companies need to become promise keepers.”
Why the promise gap persists
The problem usually begins before the contract is signed. Sales teams promise improvements in revenue, efficiency or cost reduction, but often fail to document the customer’s starting position or the KPIs that will demonstrate success. Business cases may be created late in the sales cycle to justify a purchase, while the underlying assumptions remain in spreadsheets or individual conversations.
When the account moves into customer success, those objectives are frequently lost. The CSM receives information about the product purchased and the implementation required, but little evidence of the financial outcomes the customer expects. Measuring improvement becomes difficult because nobody established the baseline against which it should be assessed.
Prospects struggle to justify purchases framed around features rather than financial outcomes. At renewal, commercial teams must reconstruct the business case, while internal champions lack the evidence to defend the investment when a CFO questions it.
Why the promise gap persists
The problem usually begins before the contract is signed. Sales teams promise improvements in revenue, efficiency or cost reduction, but often fail to document the customer’s starting position or the KPIs that will demonstrate success. Business cases may be created late in the sales cycle to justify a purchase, while the underlying assumptions remain in spreadsheets or individual conversations.
When the account moves into customer success, those objectives are frequently lost. The CSM receives information about the product purchased and the implementation required, but little evidence of the financial outcomes the customer expects. Measuring improvement becomes difficult because nobody established the baseline against which it should be assessed.
Prospects struggle to justify purchases framed around features rather than financial outcomes. At renewal, commercial teams must reconstruct the business case, while internal champions lack the evidence to defend the investment when a CFO questions it.
Why the promise gap persists
The problem usually begins before the contract is signed. Sales teams promise improvements in revenue, efficiency or cost reduction, but often fail to document the customer’s starting position or the KPIs that will demonstrate success. Business cases may be created late in the sales cycle to justify a purchase, while the underlying assumptions remain in spreadsheets or individual conversations.
When the account moves into customer success, those objectives are frequently lost. The CSM receives information about the product purchased and the implementation required, but little evidence of the financial outcomes the customer expects. Measuring improvement becomes difficult because nobody established the baseline against which it should be assessed.
Prospects struggle to justify purchases framed around features rather than financial outcomes. At renewal, commercial teams must reconstruct the business case, while internal champions lack the evidence to defend the investment when a CFO questions it.
Build a shared record of customer outcomes
Closing the promise gap starts with establishing a shared understanding of value. During the sales process, the vendor and customer should agree on the outcomes they want to achieve, define the KPIs that represent those outcomes and document the customer’s baseline performance.
Those measurements must remain accessible throughout implementation, adoption and renewal. Rather than rebuilding the business case during each commercial conversation, teams should work from a common record of the customer’s objectives, assumptions and progress. This also allows the customer to participate in defining and validating the value achieved.
At Ecosystems, we’ve found that collaboration is closely associated with stronger sales performance. Across the customer engagements we’ve studied, win rates have shown a stronger relationship with the degree of customer collaboration than with the size of the projected ROI. When customers participate in developing the business case, they’re better positioned to understand, validate and take ownership of the expected outcome.
After the sale, success plans should remain a living record of customer objectives and progress. Product telemetry and operational data should contribute wherever possible.
Build a shared record of customer outcomes
Closing the promise gap starts with establishing a shared understanding of value. During the sales process, the vendor and customer should agree on the outcomes they want to achieve, define the KPIs that represent those outcomes and document the customer’s baseline performance.
Those measurements must remain accessible throughout implementation, adoption and renewal. Rather than rebuilding the business case during each commercial conversation, teams should work from a common record of the customer’s objectives, assumptions and progress. This also allows the customer to participate in defining and validating the value achieved.
At Ecosystems, we’ve found that collaboration is closely associated with stronger sales performance. Across the customer engagements we’ve studied, win rates have shown a stronger relationship with the degree of customer collaboration than with the size of the projected ROI. When customers participate in developing the business case, they’re better positioned to understand, validate and take ownership of the expected outcome.
After the sale, success plans should remain a living record of customer objectives and progress. Product telemetry and operational data should contribute wherever possible.
Build a shared record of customer outcomes
Closing the promise gap starts with establishing a shared understanding of value. During the sales process, the vendor and customer should agree on the outcomes they want to achieve, define the KPIs that represent those outcomes and document the customer’s baseline performance.
Those measurements must remain accessible throughout implementation, adoption and renewal. Rather than rebuilding the business case during each commercial conversation, teams should work from a common record of the customer’s objectives, assumptions and progress. This also allows the customer to participate in defining and validating the value achieved.
At Ecosystems, we’ve found that collaboration is closely associated with stronger sales performance. Across the customer engagements we’ve studied, win rates have shown a stronger relationship with the degree of customer collaboration than with the size of the projected ROI. When customers participate in developing the business case, they’re better positioned to understand, validate and take ownership of the expected outcome.
After the sale, success plans should remain a living record of customer objectives and progress. Product telemetry and operational data should contribute wherever possible.
What Cisco ThousandEyes learned from a customer that churned
The company had a major customer that was actively using its product but nevertheless decided to churn. At the time, much of the sales process focused on features and capabilities, while business cases were created separately in spreadsheets, often late in the deal. Customer success didn’t consistently inherit the objectives and assumptions that had informed the original purchase.
The loss prompted ThousandEyes to change its approach. Working with Ecosystems, the company standardized its value-selling process around repeatable use cases and introduced more consistent methods for creating business cases. It also established a mandate to carry those business cases into customer success, so that quarterly and executive business reviews could assess the outcomes originally agreed with customers.
Enablement and specialist deal assistance helped teams conduct value conversations. ThousandEyes reported substantially improved win rates in the first three quarters of fiscal 2026, although no specific percentage was shared.
What Cisco ThousandEyes learned from a customer that churned
The company had a major customer that was actively using its product but nevertheless decided to churn. At the time, much of the sales process focused on features and capabilities, while business cases were created separately in spreadsheets, often late in the deal. Customer success didn’t consistently inherit the objectives and assumptions that had informed the original purchase.
The loss prompted ThousandEyes to change its approach. Working with Ecosystems, the company standardized its value-selling process around repeatable use cases and introduced more consistent methods for creating business cases. It also established a mandate to carry those business cases into customer success, so that quarterly and executive business reviews could assess the outcomes originally agreed with customers.
Enablement and specialist deal assistance helped teams conduct value conversations. ThousandEyes reported substantially improved win rates in the first three quarters of fiscal 2026, although no specific percentage was shared.
What Cisco ThousandEyes learned from a customer that churned
The company had a major customer that was actively using its product but nevertheless decided to churn. At the time, much of the sales process focused on features and capabilities, while business cases were created separately in spreadsheets, often late in the deal. Customer success didn’t consistently inherit the objectives and assumptions that had informed the original purchase.
The loss prompted ThousandEyes to change its approach. Working with Ecosystems, the company standardized its value-selling process around repeatable use cases and introduced more consistent methods for creating business cases. It also established a mandate to carry those business cases into customer success, so that quarterly and executive business reviews could assess the outcomes originally agreed with customers.
Enablement and specialist deal assistance helped teams conduct value conversations. ThousandEyes reported substantially improved win rates in the first three quarters of fiscal 2026, although no specific percentage was shared.
Customer success needs stronger commercial skills
Moving toward outcome-based relationships changes what customer success teams are expected to do. CSMs need to understand financial metrics, conduct discovery, manage relationships across multiple stakeholders and identify the business objectives behind product usage. They also need to support expansion conversations and help customers justify continued investment.
These responsibilities require capabilities traditionally associated with consultative selling. An employee skilled at resolving support issues and encouraging adoption won’t automatically be prepared to discuss revenue growth, cost savings or return on investment with senior executives.
Organizations need structured enablement in value discovery, measurement and commercial conversations. Specialist value teams can support difficult engagements, while managers inspect the quality of those conversations and keep outcomes central to account planning.
Customer success needs stronger commercial skills
Moving toward outcome-based relationships changes what customer success teams are expected to do. CSMs need to understand financial metrics, conduct discovery, manage relationships across multiple stakeholders and identify the business objectives behind product usage. They also need to support expansion conversations and help customers justify continued investment.
These responsibilities require capabilities traditionally associated with consultative selling. An employee skilled at resolving support issues and encouraging adoption won’t automatically be prepared to discuss revenue growth, cost savings or return on investment with senior executives.
Organizations need structured enablement in value discovery, measurement and commercial conversations. Specialist value teams can support difficult engagements, while managers inspect the quality of those conversations and keep outcomes central to account planning.
Customer success needs stronger commercial skills
Moving toward outcome-based relationships changes what customer success teams are expected to do. CSMs need to understand financial metrics, conduct discovery, manage relationships across multiple stakeholders and identify the business objectives behind product usage. They also need to support expansion conversations and help customers justify continued investment.
These responsibilities require capabilities traditionally associated with consultative selling. An employee skilled at resolving support issues and encouraging adoption won’t automatically be prepared to discuss revenue growth, cost savings or return on investment with senior executives.
Organizations need structured enablement in value discovery, measurement and commercial conversations. Specialist value teams can support difficult engagements, while managers inspect the quality of those conversations and keep outcomes central to account planning.
Start with one customer and two KPIs
Building an outcome-focused organization doesn’t require a comprehensive measurement framework from the beginning. Start with one customer and identify two meaningful KPIs that reflect the business results they want to achieve. Establish the baseline, agree on the desired improvement and measure progress through both pre-sales and post-sales activities.
From there, develop repeatable value frameworks for common use cases, using standardized assumptions, templates and benchmarks where appropriate. Integrate those measurements into ongoing success plans and train commercial teams to discuss the results with customers. As the approach becomes established, extend it across the portfolio while maintaining the ability to adapt to individual customer objectives.
Software companies need to become promise keepers. When they can demonstrate that they delivered what they promised, renewal becomes a continuation of proven value rather than another attempt to justify the original purchase.
Start with one customer and two KPIs
Building an outcome-focused organization doesn’t require a comprehensive measurement framework from the beginning. Start with one customer and identify two meaningful KPIs that reflect the business results they want to achieve. Establish the baseline, agree on the desired improvement and measure progress through both pre-sales and post-sales activities.
From there, develop repeatable value frameworks for common use cases, using standardized assumptions, templates and benchmarks where appropriate. Integrate those measurements into ongoing success plans and train commercial teams to discuss the results with customers. As the approach becomes established, extend it across the portfolio while maintaining the ability to adapt to individual customer objectives.
Software companies need to become promise keepers. When they can demonstrate that they delivered what they promised, renewal becomes a continuation of proven value rather than another attempt to justify the original purchase.
Start with one customer and two KPIs
Building an outcome-focused organization doesn’t require a comprehensive measurement framework from the beginning. Start with one customer and identify two meaningful KPIs that reflect the business results they want to achieve. Establish the baseline, agree on the desired improvement and measure progress through both pre-sales and post-sales activities.
From there, develop repeatable value frameworks for common use cases, using standardized assumptions, templates and benchmarks where appropriate. Integrate those measurements into ongoing success plans and train commercial teams to discuss the results with customers. As the approach becomes established, extend it across the portfolio while maintaining the ability to adapt to individual customer objectives.
Software companies need to become promise keepers. When they can demonstrate that they delivered what they promised, renewal becomes a continuation of proven value rather than another attempt to justify the original purchase.
The Archive
[
Discover All
]
[
Through the Lens
]
[
Talking Planhat
]
[
Expert Advice
]
[
In Perspective
]
[
In Conversation
]
Load more
The Archive
[
Discover All
]
[
Through the Lens
]
[
Talking Planhat
]
[
Expert Advice
]
[
In Perspective
]
[
In Conversation
]
Load more
The Archive
[
Discover All
]
[
Through the Lens
]
[
Talking Planhat
]
[
Expert Advice
]
[
In Perspective
]
[
In Conversation
]
Load more

Don't miss a beat.

Don't miss a beat.








