1. What Was The Leak?
State the original bottleneck in plain language so the result has a clear reference point.
Post-delivery asset page
Turn finished work into a client-ready summary and a reusable proof pack.
This page compresses delivery into the parts that matter after the sprint: what shipped, what changed, what the client can approve quickly, and what can later be reused in proof and sales.
- 4 parts in the proof pack
- 1 approval summary
- 1 proof reuse path
Pack Shape
Every delivery proof pack should answer these four questions.
2. What Shipped?
List the delivered assets only: the flow, the structure, the SOP, the page, or the handoff component that was actually completed.
3. What Changed?
Explain the visible shift: clearer next step, faster response path, stronger confidence, or cleaner owner handoff.
4. What Can Be Reused?
Note what is safe to turn into proof, case-study framing, or referral support after approval.
Client Summary
Use a short delivery note instead of a messy handoff message.
What Shipped
Delivered:
one tightened follow-up path
one cleaner intake summary structure
one owner-facing SOP
What Improved
The path from interest to next action is clearer, easier to explain, and easier for the owner to run consistently.
What Happens Next
Review the shipped assets, confirm any light revisions, and then approve the final handoff and remaining balance.
Open Client RecoveryProof Reuse
Move from delivery to reusable proof without rebuilding the story.
Case Study Base
Use the same before-shipped-after structure as the base for the case study or testimonial request.
Open Case ConverterTestimonial Ask
Ask for a short result-based testimonial while the shipped work is still fresh and easy to describe.
Open Proof BoardReferral Support
Reuse the same concise summary as the forwardable explanation when asking for one relevant intro.
Open Referral Board