Prepare a Customer Renewal Review Pack

A renewal review should help the customer decide what to do next. A slide deck full of activity charts can show that people used the service without explaining whether it delivered the outcome the customer wanted. A success story that ignores unresolved issues creates an equally weak basis for the decision.

Prepare a concise renewal pack that connects the agreed goals, available evidence, customer feedback, open issues and proposed next-term scope. Explain where the evidence is incomplete. Give the customer a clear decision and the information needed to make it.

This guide provides a planning and document workflow, not a formula for guaranteeing renewal. The worked example is illustrative. Use actual account evidence in a real pack and never invent adoption, savings, satisfaction or business results to make the review look stronger.

1. Start with the decision and agreement

Identify what the customer needs to decide: continue the current service, change scope, resolve a problem before renewal or end the relationship. Review the applicable agreement and the organization's renewal process with the responsible commercial team. Do not guess notice periods or contractual obligations.

Salesforce's customer-success guidance encourages beginning renewal conversations before the term ends. Build your preparation around the actual customer decision process rather than treating renewal as a last-minute pricing email. Salesforce Trailhead: Make Customers for Life

Ask who participates in the review and what evidence each person needs. The sponsor may focus on outcomes, the operational owner on usability, finance on the proposed scope and IT on ongoing dependencies. Keep the pack coherent while making those perspectives visible.

Record the intended review period and the next step. A renewal pack covering “this year” is ambiguous if the customer expects a contract-term comparison. State the dates or periods clearly and keep the same basis throughout the documents.

2. Revisit the original goals

Collect the goals agreed during sales and onboarding, together with any later approved changes. Do not substitute whatever result is easiest to chart. If the original goal was to reduce a particular review bottleneck, a count of uploaded files does not by itself demonstrate that improvement.

The rows are illustrative categories rather than claimed results. In the actual pack, use the customer's specific task and measure. Preserve changes in goals so the reader can distinguish an abandoned objective from an unmet one.

If nobody defined measurable goals, say so. Use the review to establish a clearer basis for the next term instead of inventing a historical success criterion.

3. Build an evidence register before charts

For each proposed metric, record its source, period, definition, coverage and limitations. Identify who can verify it. This makes it harder for a persuasive chart to outrun the underlying record.

Keep units and periods consistent. Do not compare a full quarter with an incomplete month without stating the difference. Exclude test or irrelevant activity where the source reliably allows it, and describe the filtering rather than pretending the raw count is an outcome.

Use only data you are authorized to disclose. Aggregate or limit personal information appropriately for the review audience. A customer review should not expose another customer's activity or private employee details simply because the analytics export includes them.

4. Distinguish activity from outcomes

Usage is useful evidence, but its meaning depends on the task. A high count can represent successful adoption, repeated attempts to complete a difficult workflow or activity unrelated to the goal. Ask the customer to interpret it alongside the process evidence.

Avoid converting product activity into money saved without a defensible method and stated assumptions. If the customer has measured a benefit, show its source and calculation. If you propose an estimate for discussion, label it clearly as an estimate and let the customer challenge the inputs.

Separate directly observed results from interpretations. “The activity export records use by the specified team during the review period” is narrower than “the product transformed the department.” The second statement needs evidence that the first alone cannot provide.

Keep uncertain findings visible. Explain what the data can establish, what it cannot establish and what additional evidence would help. A truthful limitation makes the review useful; it does not require burying the metric or adding a dramatic claim to compensate.

5. Use an illustrative renewal review

Consider an illustrative customer that bought a service to organize a recurring document review. The available records show that the team used the shared workspace during the term, but there is no reliable pre-purchase timing baseline. Two workflow issues remain open.

The pack reports the supported activity with its period and definition. It does not claim a percentage improvement or financial saving. A feedback section records the operational owner's view of what became easier and what still causes friction, clearly attributed as customer feedback rather than an objective measurement.

The open-issue table names the two problems, their current states and responsible owners. The proposed next-term plan includes clarifying the workflow and establishing a consistent baseline for future review. Any requested feature remains a request unless approved through the relevant process.

The customer can now evaluate continued use with a realistic account of the evidence. The pack does not guarantee renewal, conceal the missing baseline or claim that the proposed improvement plan is a contractual commitment.

6. Put unresolved issues in the main story

A renewal pack should not require the customer to search an appendix for the problem that matters most to it. Include significant unresolved issues alongside the outcomes and usage, with an accurate state and an accountable next step.

For each issue, record what the customer reports, what has been verified, what remains uncertain and who owns the response. Avoid marking an issue resolved solely because an internal ticket closed. Ask for customer confirmation when that is needed to establish the outcome.

Distinguish a workaround from a permanent solution. Explain any limitations of the workaround and the conditions under which it is useful. Do not convert a proposed engineering investigation into a promised release date.

Where an issue has commercial implications, route the proposed response to the responsible team. The review coordinator should not invent credits, new service terms or feature commitments to improve the tone of the meeting. Capture the authorized decision and update the appropriate record when it is made.

7. Present clear next-term options

Keep proposed options understandable. State the service scope, responsibilities, dependencies and decision required for each. Use approved current commercial information rather than copying figures from an older proposal.

These are planning categories, not universal contract options. Include only choices your organization can actually offer and the agreement permits. If a choice depends on approval, label it pending rather than making it look immediately available.

Relate the options to the customer's evidence and goals. Do not add unrelated upsell material merely because the review is a commercial opportunity. A proposed expansion should answer a demonstrated task and explain the additional responsibility it creates.

8. Build a readable review pack

Use a short reading order: decision summary, agreed goals, evidence, unresolved issues and options. Place detailed exports or supporting references after the main narrative. The customer should understand the decision without inspecting every raw record.

Create charts only when they clarify a valid comparison. Label the period, source and unit directly. If there is no defensible comparison, a simple evidence table is better than a dramatic trend line. Avoid decorative dashboards that imply precision the underlying data does not provide.

Make the pack suitable for internal forwarding. Include context so a finance or procurement reviewer can understand it without hearing the original meeting. Use approved customer-specific documents and the appropriate recipient boundary.

Test readability in the actual shared format. Check chart labels, table wrapping and reference destinations. If the pack contains restricted commercial or operational material, verify access through the intended reviewer path. Do not claim that secure hosting prevents every retained copy or quotation.

9. Record the review and follow-up decisions

During the review, ask the customer to confirm or challenge the interpretation of the evidence. Record disagreements explicitly. A meeting is not successful merely because nobody interrupted the slides.

Capture the actual decision, outstanding approvals and next owners. If the customer needs an internal review, identify what additional information it requires and when the parties intend to reconnect. Keep that timing distinct from contractual deadlines, which the responsible commercial team must verify.

Update the pack only through a clear revision process. If a metric or claim was corrected, preserve the change and communicate it to the affected audience. Avoid silently modifying a shared review after the customer used it in its internal decision.

After renewal, transfer the agreed next-term goals and unresolved responsibilities into the operating plan. If the relationship ends, follow the approved access, data and transition process. Do not treat renewal confirmation as evidence that every prior issue was resolved or every proposed initiative was approved.

10. Renewal-pack verification checklist

Before releasing the review, confirm:

• The customer decision and review audience are identified.
• Relevant commercial requirements were checked by their owner.
• The review period is explicit and consistent.
• Original goals and approved changes are traceable.
• Metrics have defined sources, units and coverage.
• Activity is not mislabeled as business value.
• Estimates are distinguished from observed results.
• Customer feedback is attributed accurately.
• Significant unresolved issues remain visible.
• Proposed options use approved scope and terms.
• Charts and tables are readable in the shared copy.
• Recipients can open the required evidence.
• Follow-up actions have named owners.

Keep an internal record of the approved pack and the customer's response. Use that record to improve the next review rather than recycling the same slides with a new date. The best renewal pack makes uncertainty and progress understandable enough for the customer to make a considered decision.

Frequently asked questions

What if we have no reliable baseline?+

State that limitation. Use supported activity and attributed customer feedback without inventing a before-and-after result. Agree a practical measurement method for the next review where useful.

Should unresolved issues appear in the renewal pack?+

Yes, when they matter to the decision. Explain their state, evidence and next owner accurately rather than hiding them behind positive usage charts.

Can usage alone prove ROI?+

No. An ROI claim needs a defensible method and inputs. Usage can support the review but does not automatically establish financial benefit.

Before you share

A strong renewal review makes the evidence, limits and next choices easy to understand. Use the customer's real goals, disclose unresolved issues and finish with an accountable decision process.

Parent guide

• What Belongs in a Digital Sales Room?

Related articles

• Build a Buyer Business Case With Evidence

• Share an ROI Calculator Buyers Can Check

• Hand Off Sales Documents to Customer Success

Sources and editorial disclosure

Primary documentation reviewed October 11, 2026. Examples, templates and checklists are illustrative editorial recommendations unless explicitly identified otherwise. Product settings and entitlements may change.

• Salesforce Trailhead: Make Customers for Life

VDR Directory is published by the SendNow team. Product references are limited to documented capabilities; this guide does not report a signed-in product demonstration or a completed customer project. Stock photos illustrate the surrounding workflow and do not prove feature behavior. No ranking, revenue, compliance or legal outcome is guaranteed.