PlaybookPrompts

Turn a customer win into a tight one-pager

Sales & Outreach case-studysales-enablementcontent

Reps close deals, then never capture the story in a usable format. This prompt converts raw notes from a customer conversation into a one-page case study your prospect can read in under two minutes.

Prompt
You are a B2B content writer who specializes in sales enablement. Convert the raw customer win notes below into a one-page case study formatted for sales use — not marketing fluff.

Structure it exactly as follows:
1. **Headline** (one line, lead with the measurable outcome, not the company name)
2. **The situation** (2-3 sentences: who the customer is, what problem they had before us, what it was costing them)
3. **Why they chose us** (2-3 sentences: what tipped the decision — be specific, avoid vague praise)
4. **What we did** (3-4 bullet points: concrete actions or features used, written from the customer's perspective)
5. **The result** (lead with numbers; if the customer gave ranges not exact figures, use ranges and note that)
6. **One direct quote** (pull or lightly polish from the notes; mark it clearly if you polished it)
7. **Best-fit signal** (one sentence describing which prospects this story will resonate with most)

Raw notes from customer conversation: {{CUSTOMER_NOTES}}
Customer company size and industry: {{CUSTOMER_PROFILE}}
Our product / solution used: {{PRODUCT_USED}}

If the notes lack a quantified result, write a placeholder and flag it — do not invent metrics.
Variables to fill in
  • {{CUSTOMER_NOTES}}
  • {{CUSTOMER_PROFILE}}
  • {{PRODUCT_USED}}

How to use this prompt

  1. Copy the prompt above (Copy button on the top-right).
  2. Replace each {{VAR}} with your own value. Variables: {{CUSTOMER_NOTES}}{{CUSTOMER_PROFILE}}{{PRODUCT_USED}}.
  3. Paste it into one of the recommended tools below.
  4. Iterate: tighten constraints in the prompt if the output is generic.

Why this prompt is structured this way

The prompt is split into explicit steps because LLMs do better when the path is named, not implied. Each variable forces specificity at the input layer — vague inputs get vague outputs.

Heads up: some of the links on this page are affiliate links — meaning we may earn a commission if you sign up after clicking, at no extra cost to you. We only recommend tools we'd put on our own stack. You can see our full affiliate disclosure here.

Pair this prompt with a tool

The PlaybookPrompts weekly

One short email per week. The five sharpest prompts we found, one tool worth your attention, one anti-pattern to avoid. Unsubscribe in one click.

Newsletter signup is not configured. Set PUBLIC_NEWSLETTER_USERNAME in the build env.