Turn one customer story into a full case study that doesn't read like an ad
A case study that sounds like marketing convinces nobody who's actually skeptical.
- Use it for
- Anyone turning a happy customer into a written case study.
Case studies frequently read as thin marketing dressed up with a customer's logo — vague outcomes ("saw significant improvement"), no real texture about the actual problem, and a resolution that arrives too smoothly to be believable. Skeptical readers, who are exactly the audience a case study needs to convince, recognize this pattern instantly and discount it. A case study that actually persuades includes the messy middle — what didn't work first, what the real struggle was — because that's what makes the eventual result credible.
This prompt builds the case study around specific, checkable details instead of smoothed-over marketing beats.
When not to use this
If you don't have access to real specifics — actual numbers, direct quotes, a concrete before/after — this isn't the right prompt yet; get a real interview with the customer first. Manufacturing specificity you don't have is worse than an honest, general case study.
Did this work?
A skeptical reader in the target audience would find at least one specific, checkable detail that makes the story feel real rather than like marketing copy with a customer's name attached.
Tested on claude-opus-5. Evidence status is draft; it moves to battle-tested only on recorded runs, never by hand.