Prompt library
Draft a case study from messy notes
Every-number-needs-a-baseline is what separates evidence from marketing gas, and the [NEED] markers turn missing data into a follow-up list instead of silent invention. Including one real friction point is a credibility device readers consistently reward.
Last reviewed July 17, 2026
The prompt
Draft a customer case study from the notes below.
Notes: {{notes}}
Structure:
1. Headline: the customer's result in their numbers, not our product name.
2. Context: who they are, the constraint that made the problem hard for them specifically. 3-4 sentences.
3. Before: the old workflow, its cost in time or money, and the moment they decided to change. Use their quotes where the notes contain them.
4. After: the new workflow step by step, then the results with baseline, new value, and time window for every number.
5. One real limitation or adjustment they made; a case study with no friction reads as fiction.
6. Pull quote suggestion: the strongest verbatim sentence from the notes.
Rules: never invent quotes or numbers. Where the notes lack a number the structure needs, insert [NEED: metric] so I can chase it.Run in idaptOpens a new chat with the prompt prefilled. Nothing sends until you press send.
Fill in the variables
| Variable | What it is | Example |
|---|---|---|
| {{notes}} | Call transcripts, emails, metrics: everything you have | [paste interview notes, metrics, and email snippets] |