A CV says I know n8n and Claude Code. A proof page says 2–4 h → 0 h. So I built one — five real wins, each with a number you can check.
Portfolios and LinkedIn profiles list what you touched — frameworks, languages, projects. An employer or a client reads that and still can't see the one thing they're buying: the delta. Did anything actually get faster, cheaper, or safer? By how much? Most pages never say.
I borrowed Nate Herk's three-part structure and made it the spine of the whole page. Every case answers the same three things, in order: the thinking constraint that was blocking progress, the KPI that measures the change (a real number, before → after), and the AI system that removed it. Constraint and KPI first — the build is the proof, not the pitch.
Every case on the page is a system shown in an earlier episode — so the number isn't a claim, it's a link. Publishing: a 2–4 h manual build → 0 h (the nightly engine). Research: a 20-minute watch → 3 minutes (the /watch skill, which caught income claims inflated 4×). Infrastructure: scraping → 1 command (the AI front door). Observability: silent context deaths → 0 (the fuel gauge). And the in-house consultant role: inbound ↑.
Four cases carry hard before/after numbers pulled straight from shipped episodes. The fifth — the in-house consultant case — is inbound ↑, a direction not a metric, and it's marked that way on purpose. A proof page that fakes one number loses all five.
The proof page is live on the site, in the main nav, next to the episodes. Tap any image to enlarge it and read the exact prompt that drew it.




No bullet list of skills. Five constraints, five numbers, five systems — and one button that says hire the operator. For the Q3 search, this is the link I send instead of a resume.
Why I stopped sending a CV and started sending a link that shows the delta.
The framework is free: pick one constraint, name the KPI, link the build. Everything on the Cases page is open — view the source, copy the structure, swap in your own numbers.
/cases → for each win: the constraint blocking me, the KPI before→after, the system that moved it. Never list a number I can't link.
No GitHub needed — it's a single page. Comment PROOF on the post and the bot DMs you the framework breakdown.
Two clients sent unsolicited quotes about working with me. Next: turning real testimonials into social proof — raw words vs. cleaned, and where the line is.