1. Ask For Testimonial
Start with a short 1 to 3 sentence testimonial ask. It is the easiest proof request to approve.
Reusable sales proof page
Turn completed work into proof without adding friction.
This page handles the proof layer after a sprint is complete: testimonial asks, case-study permission, anonymous proof options, and what is safe to reuse in future sales.
- 1 testimonial path
- 1 case-study path
- 1 anonymous proof option
Proof Path
Use the smallest proof request that still helps the next close.
2. Ask For Case Study Permission
If they are comfortable, ask whether the sprint can be described as a short case study.
Open Case Study Board3. Offer Anonymous Version
If naming is sensitive, offer a brandless version focused on the bottleneck, the fix, and the result.
4. Ask For One Referral
Once proof exists, ask for one relevant introduction while the result is still fresh and easy to describe.
Open Case ConverterReady-To-Send Lines
Keep proof asks short and low-friction.
Testimonial Ask
If you are happy with the outcome, a short 1 to 3 sentence testimonial would help. Even a brief note on the bottleneck and result is enough.
Case Study Ask
If useful, I can describe this as a short case study without sharing anything sensitive. Mostly the starting bottleneck, what changed, and the outcome.
Anonymous Option
If public naming is a problem, I can keep it anonymous and just reference the type of team, the bottleneck, and the result.
Reusable Proof
What usually matters most in future sales.
Starting Bottleneck
What specific friction existed before the sprint started.
What Changed
What was actually shipped or tightened during the sprint.
Open Delivery Proof PackCommercial Result
Faster responses, clearer handoff, fewer missed opportunities, or another concrete operational win.