Customer story builder

Take raw customer inputs — interview transcripts, survey responses, Slack quotes, support tickets, review excerpts — and generate a structured case study draft with problem/solution/result narrative, pull-quotes, metric callouts, and multi-format outputs (full case study, one-pager, social proof snippet, sales deck slide).

How to use it

  1. Hit Copy SKILL.md — or use the Claude Code line below to get every file.
  2. Claude: ⋯ → Download .md, then Customize → Skills → Add → Upload skill.
    ChatGPT: make a Project and paste it into Instructions.
    Neither? Paste it at the top of a new chat — it works for that chat.
  3. Describe your job in plain words. The AI follows the skill from there.
Claude Code — installs the whole folder, not just SKILL.md
npx degit gooseworks-ai/goose-skills/skills/content/composites/customer-story-builder#main ~/.claude/skills/customer-story-builder

For one project only, change the path to .claude/skills/customer-story-builder. This skill also uses case-study-full.md, one-pager.md, social-snippets.md, slide-content.md, raw-inputs.md — copying SKILL.md alone won't be enough. See the folder on GitHub.

Not working?
  • Check which app you pasted it into — the steps above name the right one.
  • Some skills need the paid tier of Claude or ChatGPT.
Step-by-step guide with screenshots · Ask in the forum

Paste into Claude, ChatGPT or Cursor.

Show the full text242 lines
customer-story-builder/SKILL.md242 lines6.9 KBpushed 96d agoRawView on GitHub

Customer Story Builder

Turn raw customer signal into a polished case study — plus every derivative format you need. One input (messy transcript or quote), all outputs (case study, one-pager, social snippet, deck slide).

Core principle: The best customer stories already exist in your support tickets, Slack channels, and call recordings. You just need to extract and structure them.

When to Use

  • "Turn this customer interview into a case study"
  • "We have a great Slack quote from [customer] — help me build a story around it"
  • "Write a case study for [customer]"
  • "I need social proof assets from [customer win]"
  • "Package this customer result for the sales team"

Phase 0: Intake

Customer Context

  1. Customer name — Can we use their name publicly? (Named vs. anonymous)
  2. Company description — Industry, size, stage (1 sentence)
  3. Customer role/title — Who's the champion?
  4. How long have they been a customer?

Raw Input (provide any/all)

  1. Interview transcript — Full or partial transcript from a customer call
  2. Slack/email quotes — Specific messages where they praised the product
  3. Survey responses — NPS comments, CSAT feedback
  4. Support ticket excerpts — Before/after of a problem solved
  5. Review excerpts — G2, Capterra, Trustpilot quotes
  6. Metrics — Any numbers: time saved, revenue impact, efficiency gains, before/after

Story Angle

  1. Primary use case — What were they using the product for?
  2. Key transformation — What changed? (The "before → after" in one sentence)
  3. Output formats needed — Full case study, one-pager, social snippet, sales slide, or all?

Phase 1: Extract Story Elements

From the raw inputs, identify and extract:

The Problem (Before)

  • What was the customer's situation before using the product?
  • What specific pain were they experiencing?
  • What had they tried before? (Manual process, competitor, nothing)
  • How bad was it? (Quantify if possible — hours wasted, money lost, deals missed)

The Decision (Why You)

  • Why did they choose your product?
  • What alternatives did they consider?
  • What was the deciding factor?

The Solution (How)

  • Which specific features/capabilities did they use?
  • How did they implement it? (Timeline, effort)
  • Any surprising use cases or creative applications?

The Result (After)

  • Hard metrics — numbers, percentages, time saved, revenue gained
  • Soft outcomes — confidence, team morale, process improvements
  • Before/after comparison — the transformation in concrete terms

Best Quotes

Pull the 3-5 strongest verbatim quotes from the raw input:

  • Hero quote — the single most powerful statement (for headlines)
  • Problem quote — describes the pain vividly
  • Result quote — describes the outcome with specificity
  • Recommendation quote — would they recommend? Why?

Phase 2: Generate Story Outputs

Output 1: Full Case Study (800-1200 words)

# [Headline: Outcome-driven, not product-driven]
*[Subhead: Customer name + one-line result]*

---

## About [Customer]

[2-3 sentences: company, industry, size, what they do]

## The Challenge

[2-3 paragraphs: What was the problem? Why did it matter? What had they tried?]

> "[Problem quote]"
> — [Name], [Title] at [Company]

## Why [Your Product]

[1-2 paragraphs: How did they find you? What made them choose you?]

## The Solution

[2-3 paragraphs: How did they use the product? Which capabilities mattered most?]

> "[Solution/experience quote]"

## The Results

[Results summary with metric callouts]

### Key Metrics
- **[Metric 1]:** [Number + context]
- **[Metric 2]:** [Number + context]
- **[Metric 3]:** [Number + context]

> "[Result quote]"

## What's Next

[1 paragraph: Future plans, expansion, what they're excited about]

---

**Industry:** [X] | **Company size:** [X] | **Use case:** [X] | **Product:** [X]

Output 2: One-Pager (Sales Leave-Behind)

# [Customer Name]: [Headline Result]

**Challenge:** [2 sentences]
**Solution:** [2 sentences — what they use and how]
**Results:**
- [Metric 1]
- [Metric 2]
- [Metric 3]

> "[Hero quote]"
> — [Name], [Title]

[CTA: Learn more / Request a demo]

Output 3: Social Proof Snippets

For website testimonial section:

"[Short, punchy quote — max 2 sentences]"
— [Name], [Title] at [Company]
[Result: X% improvement in Y]

For LinkedIn post:

[Customer Name] just shared their results:

→ [Metric 1]
→ [Metric 2]
→ [Metric 3]

"[Quote]"

Here's their story: [link]

For cold email insert:

[Company in their industry] saw [key metric] after switching to [Product].

"[Short quote about the result]" — [Name], [Title]

Output 4: Sales Deck Slide Content

Slide title: "[Customer] — [Key Result]"

Left side:
- Challenge: [1 line]
- Solution: [1 line]
- Result: [1 line with metric]

Right side:
> "[Hero quote]"
— [Name], [Title]

[Customer logo]

Output 5: Metric Callout Cards

For website or marketing collateral:

[BIG NUMBER]
[Label — e.g., "hours saved per week"]
— [Customer Name]

Generate 2-3 of these from the strongest metrics.

Phase 3: Story Quality Check

Before finalizing, verify:

  • Specificity — Are results concrete, not vague? ("3x pipeline" > "improved results")
  • Credibility — Is the customer named? Is the metric believable?
  • Relevance — Does this story match your ICP? Will prospects see themselves?
  • Permission — Flag if customer approval is needed before publishing
  • Freshness — Are the results recent? (>12 months old = less impactful)

Phase 4: Output

Save all assets to clients/<client-name>/product-marketing/customer-stories/[customer-slug]/:

  • case-study-full.md — Complete case study
  • one-pager.md — Sales leave-behind
  • social-snippets.md — All social proof formats
  • slide-content.md — Deck slide content
  • raw-inputs.md — Original source material (for reference)

Cost

Component Cost
All story generation Free (LLM reasoning)
Total Free

Tools Required

None. Pure reasoning skill. Takes raw text input and produces structured outputs.

Trigger Phrases

  • "Turn this transcript into a case study"
  • "Build a customer story for [customer]"
  • "Package [customer]'s results as social proof"
  • "Run customer story builder for [customer]"
1---
2name: customer-story-builder
3description: >
4 Take raw customer inputs — interview transcripts, survey responses, Slack quotes,
5 support tickets, review excerpts — and generate a structured case study draft with
6 problem/solution/result narrative, pull-quotes, metric callouts, and multi-format
7 outputs (full case study, one-pager, social proof snippet, sales deck slide).
8 Pure reasoning skill. Use when a product marketing team has customer signal but no
9 time to write the story.
10tags: [content]
11---
12 
13# Customer Story Builder
14 
15Turn raw customer signal into a polished case study — plus every derivative format you need. One input (messy transcript or quote), all outputs (case study, one-pager, social snippet, deck slide).
16 
17**Core principle:** The best customer stories already exist in your support tickets, Slack channels, and call recordings. You just need to extract and structure them.
18 
19## When to Use
20 
21- "Turn this customer interview into a case study"
22- "We have a great Slack quote from [customer] — help me build a story around it"
23- "Write a case study for [customer]"
24- "I need social proof assets from [customer win]"
25- "Package this customer result for the sales team"
26 
27## Phase 0: Intake
28 
29### Customer Context
301. **Customer name** — Can we use their name publicly? (Named vs. anonymous)
312. **Company description** — Industry, size, stage (1 sentence)
323. **Customer role/title** — Who's the champion?
334. **How long have they been a customer?**
34 
35### Raw Input (provide any/all)
365. **Interview transcript** — Full or partial transcript from a customer call
376. **Slack/email quotes** — Specific messages where they praised the product
387. **Survey responses** — NPS comments, CSAT feedback
398. **Support ticket excerpts** — Before/after of a problem solved
409. **Review excerpts** — G2, Capterra, Trustpilot quotes
4110. **Metrics** — Any numbers: time saved, revenue impact, efficiency gains, before/after
42 
43### Story Angle
4411. **Primary use case** — What were they using the product for?
4512. **Key transformation** — What changed? (The "before → after" in one sentence)
4613. **Output formats needed** — Full case study, one-pager, social snippet, sales slide, or all?
47 
48## Phase 1: Extract Story Elements
49 
50From the raw inputs, identify and extract:
51 
52### The Problem (Before)
53- What was the customer's situation before using the product?
54- What specific pain were they experiencing?
55- What had they tried before? (Manual process, competitor, nothing)
56- How bad was it? (Quantify if possible — hours wasted, money lost, deals missed)
57 
58### The Decision (Why You)
59- Why did they choose your product?
60- What alternatives did they consider?
61- What was the deciding factor?
62 
63### The Solution (How)
64- Which specific features/capabilities did they use?
65- How did they implement it? (Timeline, effort)
66- Any surprising use cases or creative applications?
67 
68### The Result (After)
69- **Hard metrics** — numbers, percentages, time saved, revenue gained
70- **Soft outcomes** — confidence, team morale, process improvements
71- **Before/after comparison** — the transformation in concrete terms
72 
73### Best Quotes
74Pull the 3-5 strongest verbatim quotes from the raw input:
75- **Hero quote** — the single most powerful statement (for headlines)
76- **Problem quote** — describes the pain vividly
77- **Result quote** — describes the outcome with specificity
78- **Recommendation quote** — would they recommend? Why?
79 
80## Phase 2: Generate Story Outputs
81 
82### Output 1: Full Case Study (800-1200 words)
83 
84```markdown
85# [Headline: Outcome-driven, not product-driven]
86*[Subhead: Customer name + one-line result]*
87 
88---
89 
90## About [Customer]
91 
92[2-3 sentences: company, industry, size, what they do]
93 
94## The Challenge
95 
96[2-3 paragraphs: What was the problem? Why did it matter? What had they tried?]
97 
98> "[Problem quote]"
99> — [Name], [Title] at [Company]
100 
101## Why [Your Product]
102 
103[1-2 paragraphs: How did they find you? What made them choose you?]
104 
105## The Solution
106 
107[2-3 paragraphs: How did they use the product? Which capabilities mattered most?]
108 
109> "[Solution/experience quote]"
110 
111## The Results
112 
113[Results summary with metric callouts]
114 
115### Key Metrics
116- **[Metric 1]:** [Number + context]
117- **[Metric 2]:** [Number + context]
118- **[Metric 3]:** [Number + context]
119 
120> "[Result quote]"
121 
122## What's Next
123 
124[1 paragraph: Future plans, expansion, what they're excited about]
125 
126---
127 
128**Industry:** [X] | **Company size:** [X] | **Use case:** [X] | **Product:** [X]
129```
130 
131### Output 2: One-Pager (Sales Leave-Behind)
132 
133```markdown
134# [Customer Name]: [Headline Result]
135 
136**Challenge:** [2 sentences]
137**Solution:** [2 sentences — what they use and how]
138**Results:**
139- [Metric 1]
140- [Metric 2]
141- [Metric 3]
142 
143> "[Hero quote]"
144> — [Name], [Title]
145 
146[CTA: Learn more / Request a demo]
147```
148 
149### Output 3: Social Proof Snippets
150 
151**For website testimonial section:**
152```
153"[Short, punchy quote — max 2 sentences]"
154— [Name], [Title] at [Company]
155[Result: X% improvement in Y]
156```
157 
158**For LinkedIn post:**
159```
160[Customer Name] just shared their results:
161 
162→ [Metric 1]
163→ [Metric 2]
164→ [Metric 3]
165 
166"[Quote]"
167 
168Here's their story: [link]
169```
170 
171**For cold email insert:**
172```
173[Company in their industry] saw [key metric] after switching to [Product].
174 
175"[Short quote about the result]" — [Name], [Title]
176```
177 
178### Output 4: Sales Deck Slide Content
179 
180```
181Slide title: "[Customer] — [Key Result]"
182 
183Left side:
184- Challenge: [1 line]
185- Solution: [1 line]
186- Result: [1 line with metric]
187 
188Right side:
189> "[Hero quote]"
190— [Name], [Title]
191 
192[Customer logo]
193```
194 
195### Output 5: Metric Callout Cards
196 
197For website or marketing collateral:
198```
199[BIG NUMBER]
200[Label — e.g., "hours saved per week"]
201— [Customer Name]
202```
203 
204Generate 2-3 of these from the strongest metrics.
205 
206## Phase 3: Story Quality Check
207 
208Before finalizing, verify:
209 
210- [ ] **Specificity** — Are results concrete, not vague? ("3x pipeline" > "improved results")
211- [ ] **Credibility** — Is the customer named? Is the metric believable?
212- [ ] **Relevance** — Does this story match your ICP? Will prospects see themselves?
213- [ ] **Permission** — Flag if customer approval is needed before publishing
214- [ ] **Freshness** — Are the results recent? (>12 months old = less impactful)
215 
216## Phase 4: Output
217 
218Save all assets to `clients/<client-name>/product-marketing/customer-stories/[customer-slug]/`:
219- `case-study-full.md` — Complete case study
220- `one-pager.md` — Sales leave-behind
221- `social-snippets.md` — All social proof formats
222- `slide-content.md` — Deck slide content
223- `raw-inputs.md` — Original source material (for reference)
224 
225## Cost
226 
227| Component | Cost |
228|-----------|------|
229| All story generation | Free (LLM reasoning) |
230| **Total** | **Free** |
231 
232## Tools Required
233 
234None. Pure reasoning skill. Takes raw text input and produces structured outputs.
235 
236## Trigger Phrases
237 
238- "Turn this transcript into a case study"
239- "Build a customer story for [customer]"
240- "Package [customer]'s results as social proof"
241- "Run customer story builder for [customer]"
242 

Discussion

Alternatives

Also in Proposals & decks