Match the evidence to the question
A buyer worried about setup needs a realistic implementation explanation. A buyer unsure about quality may need a close view of the deliverable. A buyer evaluating expertise may need a case study explaining the problem, decisions and work performed.
More numbers are not automatically stronger proof. Confidential financial figures, overlapping dashboard snapshots or unexplained percentages can create both disclosure risk and interpretation problems.
Select an evidence format
| Buyer question | Useful evidence |
|---|---|
| Does the product do this? | An accurate demonstration or specification. |
| What will I receive? | A clear preview and inclusion list. |
| Can this person execute? | A case study describing scope, process and supported outcomes. |
| Is the experience credible? | Authorized customer feedback with relevant context. |
Build a publishable proof asset
- Write the exact claim the evidence is meant to support.
- Confirm authorization to publish the material and any identifiers.
- State the scope, period or conditions needed to interpret it.
- Remove private details while preserving the meaning of the evidence.
- Avoid implying that a single result is a prediction for every buyer.
When permission is incomplete, describe the work and decision process without publishing protected figures. A thoughtful qualitative case study can still demonstrate expertise.
Worked example: replace a sensitive revenue detail
Illustrative example: a software project cannot disclose its recurring revenue. The case can still explain the acquisition challenge, onboarding work, measurement questions and collaboration. A visual journey can show how the approach connected acquisition to activation without inventing conversion rates.
If some public milestone is available, identify where it comes from and what it represents. Do not fill missing periods with made-up growth curves merely to make the case look more impressive.
Make evidence easy to inspect
Provide readable captions, clear labels and access to the original where appropriate. Smaller dashboard previews can keep a page comfortable to read, while an enlarged view preserves inspection. Keep the underlying image unchanged unless an authorized redaction is required.
Are logos enough to prove results?
No. Logos can identify context when their use is appropriate, but they do not establish the scope or outcome of the work.
Should every case study contain revenue?
No. Product adoption, process improvements, delivery artifacts and the reasoning behind decisions can be meaningful when honestly described.
Put this into practice
Audit your strongest claim and its supporting asset. Add the missing scope information, remove unsupported implications and confirm that publication does not reveal confidential data.
Related foundation: Paid social creative testing: a framework for useful learning. How these guides are prepared.
Ayoub Mouhachtt
Growth & performance marketing. Explore the portfolio and working background.
Related portfolio work: Etsy & Shopify. The worked examples in this guide are illustrative and are separate from the portfolio’s project evidence.