Why most renewals fail before they begin
Most renewal conversations fail for a reason that has nothing to do with the product. They fail because the customer and the vendor never agreed on what was supposed to happen.
The customer believes they bought outcome A. The vendor believes they delivered scope B. Both are partially right. Neither is fully aligned. Twelve months later, the renewal conversation is a debate about who misunderstood whom, and the relationship collapses under the weight of unspoken assumptions.
The fix is a two-page document, signed by both sides, in the first 30 days. The book calls it the expectations document. It is not a project plan. It is not a Statement of Work. It is a two-page alignment tool that prevents 80% of renewal disputes.
What goes in the expectations document
The expectations document has five sections. Each section is one paragraph. The whole document fits on two pages.
The first section is what was promised. Not what your proposal said. What the customer heard during the sales conversation. This is the section that requires the most discipline, because it forces the vendor to write down, in the customer's language, what was actually said — including the parts that were oversold in the heat of the deal.
The second section is what was not promised. Every feature, every outcome, every timeline that the customer might expect but that was not actually part of the deal. This section is uncomfortable to write. It is also the section that prevents 80% of the disputes.
The third section is success criteria. What does the customer need to see, in their own business metrics, to consider this engagement successful? Not your metrics. Theirs. The CFO's metrics, not the project manager's.
The fourth section is scope of the relationship. Who is in scope (the people who will use the product), who is out of scope (the people who were discussed but not included), and what happens when scope changes.
The fifth section is the renewal conversation. When will it happen, who will initiate it, what information will be required, and what is the expected outcome. Writing the renewal conversation into the expectations document sounds premature. It is the single most effective way to make the renewal a continuation, not a renegotiation.
What does not go in the document
Three things do not go in the expectations document.
Legal language does not go in. The contract has the legal language. The expectations document is operational, not legal. Mixing the two creates a document nobody reads.
Internal project tasks do not go in. The implementation plan is internal. The expectations document is shared with the customer. Internal tasks that the customer does not care about belong in the project plan, not in the alignment document.
Aspirations do not go in. The expectations document is what will happen, not what we hope will happen. Aspirations create disappointment. Commitments create trust.
How to use the document at renewal
The expectations document is the foundation of the renewal conversation. When renewal time comes, the first slide is the document, signed by both sides, 11 months earlier. The conversation becomes: did we deliver what we agreed to deliver? If yes, the renewal is a continuation. If no, the conversation is about the gap, not the renewal.
This is the difference between a renewal and a rescue. A renewal is a continuation. A rescue is a project. The expectations document turns rescues into renewals by making the gap visible early, when there is still time to close it.
Frequently asked questions
What is the difference between an expectations document and a Statement of Work?
The Statement of Work is a legal document that describes what will be delivered. The expectations document is an operational document that describes what was understood. The SOW protects the vendor legally. The expectations document protects the relationship operationally.
How long should the expectations document be?
Two pages, maximum. If it is longer than two pages, the customer will not read it. The point of the document is alignment, not legal protection. Anything longer belongs in an appendix that is referenced, not read.
Who writes the expectations document?
The delivery lead writes the first draft, based on the deal story from the handoff. The customer reviews and edits. Both sign. The act of co-authoring the document is what creates alignment — not the document itself, but the conversation that produces it.
What if the customer refuses to sign the expectations document?
Then you have learned something important on day 30: the customer does not want to be aligned. The renewal risk on that account is high. Adjust the rest of the engagement accordingly: shorter check-ins, more written confirmation, and a 60-day pre-renewal conversation instead of a 30-day one.
How often should the expectations document be updated?
It should be reviewed, not updated, at the 90-day mark. The document is a baseline. Changes are exceptions, not the rule. If the document is being updated every month, it has become a project plan, not an alignment tool.
Conclusion
The expectations document is a two-page alignment tool that prevents 80% of renewal disputes. It is co-authored in the first 30 days, signed by both sides, and used as the foundation of the renewal conversation 11 months later. The companies that use it do not have fewer problems. They have earlier conversations about their problems — which is the only place problems are cheap to solve.
The next chapter covers the onboarding plan: how to design the first 90 days so that the customer experiences the value they bought, in the timeframe they expected.
Buy the full book on the store | USD 5
About the author: Reginaldo Osnildo is a journalist, professor, and author of works on sales, technology, and communication strategies. His work connects academic research, practical business experience, and storytelling to deliver clear, didactic, and applicable knowledge.
Photo by Ketut Subiyanto on Pexels.
Comments