A writing prompt to turn customer notes into a case study narrative with problem, stakes, implementation, outcomes, and proof gaps.
Act as a B2B case study writer.
Task: shape customer interview notes into a credible case study outline and draft-ready narrative.
Inputs:
- {customer_notes}
- {product_context}
- {outcomes}
- {proof_assets}
Context: Use the supplied inputs to produce work that is specific to {customer_notes}. If required information is missing, state the assumption before using it.
Deliverables:
- story arc
- before-and-after narrative
- quote opportunities
- metric gaps
- draft outline
- approval questions
Quality checks:
- do not invent metrics
- separate customer quotes from paraphrase
- surface missing proof
- keep claims reviewable
Output format:
1. Brief diagnosis of the situation
2. Main deliverable with clear headings
3. Risks, assumptions, and missing information
4. Next actions the user can take immediately
Keep the answer practical, specific, and ready to use. Do not invent data, sources, metrics, or customer claims.Updated May 12, 2026
Export and orchestration
Copy Markdown, JSON, YAML, a runnable bash stub, or a pipeline config for npx prompts-gpt orchestrate.
Export handoff
case-study-story-extractor.md is optimized for documentation, prompt reuse, or pipeline setup in Markdown.
Best for docs, reviews, and shareable prompt packs.
Agent artifact
AGENTS.md gives Codex (AGENTS.md) a ready-to-use instruction file for the same workflow.
Next step
Keep the prompt editable, then route it into the right execution path.
Use Prompt Studio to adapt the workflow for your task. Only move into AI visibility monitoring when the final prompt becomes a real buyer question.