Open your pre-renewal value realization recap with this: 'Here's what you asked us to change, what the records show we've changed, and what still needs a decision.' Rebuild the client's starting position from evidence, then let them check the result. Arrange the conversation before their contract decision window, with time to address gaps.
Don't ask the client to remember the environment you inherited. Bring the record. My view is that the recap should make your contribution understandable to someone who wasn't there at onboarding, without claiming credit for every improvement in the business.
Work Back From the Actual Decision Date
Book the discussion while the client still has a meaningful choice. Check the agreement's renewal date and any non-renewal notice deadline separately. Then allow time for the evidence review and the work needed to answer an unresolved concern.
On a podcast, Dan Mallard recommends tracking both dates so account managers can identify problems before the client's decision window. His example uses an advance-notice arrangement; the host notes that other MSPs use different agreements. Use your client's actual terms rather than borrowing a universal countdown.
Say this when inviting the decision-maker: 'I'd like us to check the results against the starting position before we discuss the next agreement. We'll also cover anything you think hasn't improved.' Tell them which decision needs their involvement and when it must be made.
Don't present the recap as a special favor earned by renewing early. It explains work already delivered and the decisions ahead. Keep the commercial offer clear enough to evaluate separately.
Rebuild the Before Without Inventing It
Use the onboarding assessment and the client's original priorities to establish the starting point. Add dated service or project records where they answer a specific question. A recollection can guide your search, but it shouldn't quietly become a verified baseline.
Ask the service lead to check the proposed recap before it goes to the client. Erick Simpson describes checking with the desk before a client visit to discover issues that might need attention first. That's his operating approach; I'd use it to keep the renewal discussion from arriving unaware of an unresolved problem.
What if you can't find the original baseline? Say, 'We don't have a reliable before measure for that claim, so I haven't put a savings figure against it.' Then show the completed work and the current result you can substantiate.
That answer is stronger than reconstructing a convenient number. You can show that a tested recovery procedure now exists without claiming a particular outage was prevented. Keep the date and limits of the test beside the result.
Build a Record the Client Can Check
Connect each selected improvement to the reason it mattered to this client. Keep a distinction between the work completed and the outcome established. Installation records prove an installation; they don't by themselves prove a business process became faster.
| Part of the Recap | What You Record | What You Say |
|---|---|---|
| Starting Position | A dated observation and the client priority it affected | This is the issue recorded when we agreed the work. |
| Delivered Work | The change and its completion or acceptance record | This is what we implemented and when it was accepted. |
| Current Evidence | A current test or comparable measure, with its limits | This is what we can verify now. |
| Client Confirmation | The decision-maker’s view of the effect on their work | Does this match what your team is experiencing? |
| Remaining Decision | The unresolved gap, recommended next action, and responsible person | This part still needs a decision; it is not a completed result. |
For a hypothetical example, suppose the onboarding record showed no documented recovery procedure for a business application. The completed work is the procedure and an agreed test. The recap should describe the test result and remaining limits, then ask whether it covers the business's current need.
Don't convert that into a claim that you've saved the client from a disaster. If you have no reliable downtime or financial comparison, leave those claims out. The result can be useful without an invented dollar value.
Use the Conversation to Find the Gap
Send the short recap before the meeting so the decision-maker can check it with colleagues. In the discussion, use the evidence to invite a correction. Reading a service report aloud doesn't tell you whether the client considers the original problem resolved.
We recorded this as a priority when we started. This is the change we've completed, and this is the result we've checked. What still gets in your team's way?
If the client names an unresolved problem, put it into the action record with an owner and an agreed next update. Don't bury it beneath the next success slide. A technically completed change may still leave a workflow awkward for the people using it.
If they say, 'We haven't seen much value,' reply: 'Which part hasn't matched what you expected? Let's compare that with the agreed outcome and decide what needs fixing.' Ask for the specific case before defending the whole contract.
I don't buy generic advice to remind customers how much they need you. In an MSP renewal, a long list of closed tickets can mean you've worked hard while the same business problem remains. Show the relevant result and hear the client's view of it.
Keep the Renewal and Price Clear
State what the continuing monthly fee includes and what sits outside it. The model calls for a flat monthly fee with plain scope boundaries. A recap of past work shouldn't blur a new project into the recurring agreement.
The model's annual price step is 5%, written into the contract and communicated ahead of time. Apply the actual agreement and authorized notice process. Don't make the value recap a surprise condition for a previously agreed annual change.
The recap shows the work delivered under the current agreement. Separately, here's the proposed continuing scope and its price. This recommended project has its own scope and quote.
If the client asks for a lower recurring price, say: 'Let's check the service and scope you're comparing before changing the fee.' The model doesn't discount monthly recurring revenue to win a client. Don't promise the same commitment at a lower fee just to finish the renewal conversation.
Leave With a Checked Record
In practitioner renewal advice, Erick Simpson recommends discussing delivered value and future needs with a roadmap rather than only presenting an agreement. Rich Freeman adds that listening and addressing problems should continue through the year. Treat that as their recommended practice, not evidence that a recap guarantees renewal.
The model's 95% annual retention is a planning assumption. It doesn't tell you the chance this client will renew, and a signed renewal won't prove the recap caused it. Keep the client's stated reasons and unresolved concerns with the account record.
Finish by confirming the corrections to the recap and the next decision with its owner. Send a version the client can share internally. Before you use it in the renewal proposal, remove any result you can't substantiate and resolve any disagreement you've left looking like an agreed success.
mspoutpost.com/articles/value-realization-before-an-msp-contract-renewal
Written by Natalie Brandt
MSP Outpost publishes information, not legal, financial, insurance, tax or compliance advice, and reading it creates no professional relationship. For decisions about your business, talk to a qualified professional.