Agency Case Study Machine

The reason most agencies don't have case studies isn't laziness — it's that the standard format is "we did SEO and traffic went up." Nobody clicks on that. Nobody shares that. Nobody opens a proposal because of that. The skill enforces the format that actually converts: result-led headline, the client as hero, you as guide, hard numbers with context, and the strategic insight that explains why your approach was the right one for this situation.

It runs a structured extraction first. The setup (who, where, what's broken), the problem (what was at stake, what they'd already tried), the work (what you did and the reasoning behind it, including pivots), and the results (quantitative first, then qualitative, then a client quote if you have one). If the user says "just write something," the skill pushes back — generic case studies don't convert, specificity is the entire mechanism.

The HERO arc structures every output: Hook (the most relatable problem or most impressive result, one sentence), Environment (who the client is, enough to be credible without being boring), Resolution (what you did and why that approach was right for this situation — strategic thinking, not just tactics), Outcome (numbers first, then forward-looking statement). Three formats come out simultaneously: full version for the website (500-800 words), short version for social and email (150 words), and one-liner for proposals and decks.

NDA clients still get usable case studies — anonymised descriptors ("Series B healthtech"), results-led headlines, and numbers that don't need permission to publish. Modest results get reframed around the strategic insight ("how we identified the real bottleneck") rather than the percentage. And every case study ends with a distribution plan, because writing it once and using it everywhere is the entire point — three formats, five channels, all from one project worth of data.