Deployed Works Guide
How To Write Proof That Actually Gets You Shortlisted
Turn past work into evidence buyers can use when reviewing your capability profile.
Audience
Providers, freelancers, consultants, fractional leaders, AI specialists and small specialist teams
Time
9 minutes
Outcome
Buyer-readable proof that strengthens a capability profile
Share this guide
PDF guide
Download and share with your friends and colleagues.
Use the PDF version to rewrite your proof, case studies or portfolio notes before updating your capability profile. The web guide remains the canonical 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.
- A freelancer or consultant turning past projects into clearer proof notes.
- A fractional leader who needs to show evidence without exposing confidential details.
- An AI, automation, product or engineering specialist improving a capability profile.
- A small specialist team that wants buyers to understand relevance, not just credentials.
The problem
Proof matters more than a skills list.
Proof is not a brag sheet. Proof is evidence that you can solve a problem like the buyer's problem. A buyer does not need your entire career history. They need enough confidence to believe 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. Skills lists tell buyers what tools or categories you know; proof shows whether you have used that capability to solve a relevant problem.
Proof categories
Connect problem, process, outcome, constraints and trust.
Problem proof
Shows you understand the buyer's type of problem. Name the workflow, decision, risk, bottleneck or business pressure you helped with so the buyer can recognise relevance quickly.
Process proof
Shows how you diagnose, design, build, integrate, document or hand over. Buyers want to know how you work, not only what tools you list.
Outcome proof
Shows what improved. This can be a metric, reduced manual work, clearer ownership, a shipped tool, a cleaner handoff or a better decision process.
Constraint proof
Shows you can work with messy data, legacy tools, small teams, compliance, urgency or unclear scope. Constraints often matter more than polished case-study language.
Trust proof
Shows references, testimonials, repeat clients, permissioned logos, verification as a trust signal or responsible handling of sensitive details. Trust proof supports the conversation, but it does not replace work evidence.
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 role 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. Reduced repeated manual checks and created clearer ownership between sales, ops and CS.” Weak: “Worked with startups on product strategy.” Better: “Helped a seed-stage B2B SaaS founder turn a vague product roadmap into a 6-week MVP delivery plan, including feature cuts, engineering sequence and investor demo priorities.” Weak: “Built internal tools.” Better: “Built an internal reporting tool that replaced weekly spreadsheet exports and gave the sales team a live pipeline view from CRM data.”
Template
Simple proof structure
Buyer or context: Problem: Constraints: What I / we did: Tools or systems involved: Outcome: What this proves: What I / we would do differently next time: Anonymised proof structure: - Company type - Sector - Size or stage - Problem category - Systems or tools, if allowed - Before and after - Permitted metrics - Anonymised quote, if available
Common mistakes
Avoid these traps
- Listing tools without outcomes.
- Using vague adjectives.
- Relying only on logos.
- Hiding all detail because of confidentiality.
- Writing case studies that are too long.
- Claiming impact without evidence.
- Forgetting buyer relevance.
- Overstating results.
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.
- I have included a before/after or outcome.
- I have protected sensitive details.
- I have explained why this proof matters to future buyers.
- I have not confused verification with proof of skill.
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.
Does verification prove skill?
No. Verification is optional, charged at a one-off £1.25 at cost through Stripe Identity, and does not guarantee skill, suitability or performance. It is a trust signal, not proof of capability.
What is the best proof format?
Use a short structure buyers can scan: context, problem, constraints, what you did, tools or systems, outcome, what it proves and why it is relevant to future buyers.
Take it with you
Download and share with your friends and colleagues.
Use the PDF version to rewrite your proof, case studies or portfolio notes before updating your capability profile. The web guide remains the canonical 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