---
name: case-study-from-interview-notes
description: Drafts a customer story from interview notes and approved facts. Use when marketing has notes or a transcript, the customer's permission status and approved results. Never invents numbers or quotes, and flags what needs customer approval.
---

# Customer story from interview notes

## When to use
Use this skill when a marketing, sales or customer success person has spoken to a customer and wants a first draft of a customer story. It suits website pages, PDFs, LinkedIn posts and sales decks. Do not use it to create a story without an interview, or to publish anything without the customer's approval.

## What to ask for
Ask the user for each item below. If an item is missing, ask for it before drafting.
- Customer business name, contact person and job title.
- Permission status: whether the customer agreed to be named and to share results, and whether final approval is still pending.
- A short description of the customer's business and size.
- What the user's company supplied to the customer.
- The interview notes or transcript, in any state.
- The results the customer has approved, with the approved wording.
- Where the story will be used, who will read it and the target length.

If the user has no approved results yet, continue without any figures and say so.

## Steps
1. Read the notes and sort them into four groups: facts the customer stated, figures, opinions or feelings, and vague or uncertain remarks.
2. Check the permission status. If naming the customer is not clearly allowed, use a placeholder for the name and say why.
3. Outline three parts: the problem as the customer experienced it, what was done together, and the result.
4. Write the draft from the outline. Use only facts found in the notes, the background and the approved results. Keep the user's company role factual and modest. Do not add linking sentences that state a benefit, such as 'this helps the team'.
5. Write the Summary and The result only from the approved results, in the approved wording.
6. Handle numbers strictly. Treat words such as 'twice' or 'about a month' as figures. Use only the approved figures, worded as approved. Any other figure goes on the approval list and stays out of the story.
7. Handle quotes strictly. Never write a quote. Create three to five quote slots. Where the notes hold the customer's exact words, show them in quotation marks and label them as verbatim from notes and needing approval. Otherwise write a placeholder naming the topic.
8. Treat incidents the customer described as their account. Use them only in quote slots or flag them for approval.
9. Mark each assumption in the text as an assumption.
10. Build the approval list, the gaps list and the left-out list. Then go through the draft line by line and add any name, job title, description, figure, incident or quote that is missing from the approval list.

## Output format
Return the following, in this order:

```text
Headline
Summary (two sentences)
The problem
What we did together
The result
Quote placeholders

Needs customer approval: every name, job title, description, figure, incident, claim and quote in the draft
Gaps: questions to ask the customer
Left out: material from the notes not used, and why
```

Use short sentences and short paragraphs. Keep close to the target length given by the user, and state the approximate word count at the end.

## Quality check
Before giving the answer, confirm each of these.
- Every figure in the story appears in the approved results with the same wording.
- The Summary and The result add nothing beyond the approved results.
- There are no invented quotes, and every quotation mark is attached to words from the notes.
- Every sentence can be traced to the notes, the background or the approved results.
- The approval list covers every name, job title, description, figure, incident, claim and quote in the draft.
- Assumptions are marked and none is stated as fact.
- The customer is named only if permission allows it.
- There are no claims such as best, leading or first, and no hype words.
- The length is close to the target.

## Watch-outs
- Verbal agreement is not final approval. Remind the user to get written approval of the finished text before publishing.
- Notes can hold personal or commercial details the story does not need. Leave them out and remind the user to follow their data protection rules.
- Do not imply the user's company caused a result unless the customer said so and approved it.
- Do not name the customer's own buyers, staff or suppliers without confirmation.
- If the notes are thin, say so and ask for more detail. A short accurate draft is better than a full one with guesses.
