0
Case study structure from a customer success story
⁂auto-checked, 23 hours oldAauraNovice
The prompt
Turn the raw customer story below into a proper case study. I have the facts but not a compelling structure yet.
Customer background: customer_background
What problem they had before us: before_state
What we did / how they used the product: implementation_details
Results (be specific with any numbers given, don't round generously): results_data
Any direct quotes available: available_quotes
Structure it as:
1. A specific, non-generic headline stating the actual result (a number or concrete outcome, not 'How [Customer] succeeded with [Product]').
2. Situation: the before-state written specifically enough that a reader in a similar situation recognizes themselves, not generic 'they needed a better solution.'
3. What changed: focus on the customer's actions and decisions, not a product feature list, this should read as their story, we're supporting cast.
4. Results: present the actual numbers given, don't inflate or round in our favor; if a number is modest, present it honestly rather than padding with adjectives.
5. One section addressing what almost went wrong or what they were skeptical about before starting, real case studies that admit friction are more credible than frictionless success narratives.
Flag anywhere you had to infer rather than use a stated fact, so I can verify before publishing.
Where it has been run
| Model | Version | People | Broke | Auto | Last |
|---|---|---|---|---|---|
| Claude | Haiku 4.5 | 0 | 0 | 1/1 | 23 hours ago |
Example output
Headline: '32% fewer support tickets in 90 days, no new headcount' (using your actual provided number, not rounded up). Situation section opens with the specific before-state, a 3-person support team fielding the same 5 questions repeatedly, specific enough for a reader in that exact spot to recognize it. What-changed section centers the customer's decision to restructure their help docs before adding our tool, framing them as the protagonist rather than opening with our feature list. Results section presents the 32% figure plainly alongside the secondary metric (response time), without additional unverified superlatives added. Skepticism section includes the customer's stated initial hesitation about migration effort, using their actual quote, adding credibility rather than a frictionless narrative. Flagged: the exact timeline (90 days) was inferred from two dates you gave me, not explicitly stated as '90 days' by the customer, recommend confirming before publishing.
0 comments
Sign in to comment or report what this prompt did for you.
Sign inNo comments yet. Run the prompt and report what you got.