Deployed Works Guide
For providersHow To Write Proof For Capability Review
Show the problem, what you did, what changed and what evidence you are allowed to share.
Audience
For providers
Providers, independent providers, consultants, fractional leaders, AI specialists and small specialist teams
Time
2 minute read
Outcome
Show the problem, what you did, what changed and what evidence you are allowed to share.
Share this guide
PDF guide
Share this guide with your team.
Download the PDF for meetings or offline use. The web guide has the latest version.
Related guides
Guide summary
What this guide helps you do
Who it is for
Best fit readers
- A provider with useful work experience but weak case studies.
The problem
Proof matters more than a skills list.
Proof is evidence that you can solve a problem like the buyer's problem. Buyers need enough confidence that you understand this kind of work, have handled similar constraints, can explain your approach, know what success looks like and can work responsibly with their team.
Proof categories
Connect problem, process, outcome, constraints and trust.
Problem proof
Shows you understand the buyer's type of problem.
Process proof
Shows how you diagnose, design, build, integrate, document or hand over.
Outcome proof
Shows what improved.
Constraint proof
Shows you can work with messy data, legacy tools, small teams, compliance, urgency or unclear scope.
Trust proof
Shows references, testimonials, repeat clients, permissioned logos, verification as a trust signal or responsible handling of sensitive details.
Proof Ladder
Move proof from claim to buyer confidence.
Use the ladder to turn vague experience into evidence buyers can evaluate while reviewing a capability profile.
Level 1
Skills list
Weakest on its own. It says what tools or categories you know, but not whether you have solved a relevant problem.
Level 2
Work example
Shows something you did. Useful when you can name the work, context and your contribution clearly.
Level 3
Before / after
Shows what changed. This helps buyers understand the practical value of your deployed capability.
Level 4
Metric or outcome
Shows measurable or concrete value, such as reduced manual checks, faster reporting or clearer handover.
Level 5
Case study or reference
Strongest when relevant. Gives buyers confidence through permissioned detail, testimonial, repeat work or reference.
You do not need level 5 proof for every profile. Move proof up the ladder where you can, and explain proof gaps honestly when you cannot.
Example
Before and after examples
Weak: “Experienced in automation and AI workflows. ” Better: “Mapped and automated a manual onboarding workflow for a B2B SaaS team using HubSpot, form intake and Slack handoff.
Template
Simple proof structure
Buyer or context: Problem: Constraints: What I / we did: Tools or systems involved: Outcome:
Common mistakes
Avoid these traps
- Listing tools without outcomes.
- Using vague adjectives.
- Relying only on logos.
Checklist
Ready to publish when
- I have named the problem.
- I have described the context.
- I have explained what I did.
- I have included constraints where relevant.
FAQ
Questions this guide usually raises
How do I write proof when client details are confidential?
Use company type, sector, size or stage, problem category, permitted systems, before/after detail and allowed metrics. Do not name clients without permission or expose sensitive data.
What if I do not have polished case studies?
Write one short proof note from a past project, use internal or project examples where allowed, describe relevant open-source or self-initiated work, include diagnostic or process proof, use testimonials or references, and explain proof gaps honestly.
Take it with you
Share this guide with your team.
Download the PDF for meetings or offline use. The web guide has the latest version.
Share this guide
Use the canonical page link. No social scripts or tracking widgets are loaded.
Use the guide
Make your capability easier to trust.
Create a profile that shows what you can deploy, what problems you solve and what proof buyers can use.
Read the companion blog post