One-Customer Proof Story

What it does

/case-study is a Cursor slash command. Type it in chat to run a saved workflow: One-Customer Proof Story.

Writes a case study from a real customer. Marks [NEEDS QUOTE] instead of inventing proof.

Before, after, real quote. No fiction. Unlike a skill, a command is something you invoke on purpose. The agent does not decide to run /case-study for you.

Why it exists

Founders retype the same multi-step prompt until it rots. /case-study exists so the pipeline, all 4 steps of it, is a file in .cursor/commands, versioned with the repo.

It ships in the Marketing Kit. It is wired to the Customer Proof Marketer (customer-marketer) and Direct Response Copywriter (copywriter) agents. Required skills: Customer Case Study Narrative; Win/Loss Analysis & Churn Diagnostics.

When to use it

• Use when you have a happy user or an approved quote.
• Use /case-study when you want that pipeline, not a freeform chat. If you only need one step, use a narrower command or a single agent.
• Start a new chat. Do not run this command in a thread that just touched production SQL.

When not to use it

• Do not run /case-study as a substitute for reading the diff. The command produces files; you still gate them.
• Do not chain it into a 40-turn chat. Fresh context is part of the design.
• Do not run it if you have not filled CURSOR.md. The pipeline will invent a stack.

Example workflow

1. customer-marketer gathers quote source
2. Write before/after + pull quote
3. Note where it runs (landing, PH, sales)
4. Auto-save docs/marketing/case-studies/<slug>.md

Example usage

Type this in Cursor chat: /case-study Acme went from spreadsheet to weekly close, use their email quote

The command file tells the session which agents to adopt and which skills to read. You should see phase headers, not a single dump of code.

If a phase fails its gate, stop. Do not add 'just continue'.

Example output

• Expected artifact: docs/marketing/case-studies/....md

Best practices

• Keep the prompt specific. /case-study Acme went from spreadsheet to weekly close, use their email quote is the shape: object, constraint, and outcome.
• Let the listed agents work in order: customer-marketer → copywriter.
• Save outputs in the repo. Chat-only answers evaporate.
• Marketing commands write to docs/marketing/ so the next command can read positioning before it writes a landing page.

Common mistakes

• Typing /case-study with no object ('do the thing'). The pipeline will guess.
• Re-running the command in the same chat after a failed gate instead of fixing the failing file.
• Editing the command file to skip review so it 'goes faster'.
• Skipping the Customer Case Study Narrative skill that the command depends on.