Case Study Builder

Most case studies fail in the same way: they describe the process instead of dramatizing the transformation. The reader doesn't care what you did — they care whether you can solve their problem. Every sentence has to help the reader see themselves in the story. The Case Study Builder enforces the SCSR-T framework: Situation, Challenge, Solution, Results, Testimonial, in that order, because that order mirrors how a prospect actually evaluates whether to hire you.

The Solution section is where most case studies go wrong, so the skill is opinionated here. It's insight-led, not process-led. "The audit revealed something surprising..." reads as expertise. "First we did an audit, then we analysed the data, then we redesigned..." reads as a paint-by-numbers timeline. The Solution is also kept deliberately shorter than the Challenge plus Results combined — because prospects care more about the problem and the outcome than the middle.

It won't fabricate. If you don't have the baseline, it writes "Achieved [result]" and inserts [NEED: starting baseline for comparison] so you know exactly what to fill in. If you don't have a testimonial yet, it generates a client-friendly quote prompt engineered to elicit specific, quotable responses — not generic "they were great to work with" sentences. If you ask it to inflate the results, it refuses cleanly and reframes modest numbers with context instead: "A 5% revenue increase on a $2M base is $100K annually." Let the math do the work.

Output comes in the length that matches the use case — 800 words for web, 1200 for downloadable PDF, 300-400 for proposal inserts, 100-150 for portfolio thumbnails. There's an anonymisation mode that strips the client name while keeping the self-identification triggers (industry, size, role) and all the metrics — because numbers stay credible even without a brand attached.