Skip to content This library is free, offered as dana. If it helps your work, donate here →
penguin tree ai
← back to libraryDonate here

This is one of 3,622 free prompts in the penguin tree ai library. Sign up once and the whole library opens, with new prompts by email.

open the library →

Customer case study builder

Transforms raw customer success inputs — interview notes, metrics, quotes — into a publication-ready B2B SaaS case study with a challenge/solution/results narrative, pull-quote placements, a metrics callout block, and a…

download .md

Purpose

Turn scattered customer success inputs — interview transcripts, Slack quotes, dashboard numbers — into a structured, publication-ready case study that follows a proven challenge/solution/results arc. Removes the blank-page friction that stalls customer marketing teams between securing an advocate and shipping the story.

When to Use

Invoke this skill when the user asks to:

  • Write a customer case study or success story
  • Turn a customer interview or transcript into a published narrative
  • Draft a case study for the website, sales enablement, or a slide
  • Convert raw customer quotes and metrics into a polished story
  • Build a repeatable case study from a new advocate's inputs
  • Rewrite a rough customer story into a structured format

Inputs Required

Before starting, collect:

  • Customer name and profile: Company name, industry, size (employees/revenue), and the persona of the interviewee (role/title)
  • The challenge: What problem or pain the customer had before the product — in their words if available
  • Why they chose the product: The evaluation trigger or the alternative they replaced
  • How they use it: The specific workflow, features, or use case
  • Results and metrics: Quantified outcomes (%, time saved, revenue, adoption) plus qualitative wins
  • Direct quotes: Any verbatim customer statements from the interview
  • Publishing context: Where this will live — website, PDF, sales deck (affects length and tone)

If metrics are missing, ask for at least one quantified result before drafting; a case study without a number is a testimonial. If quotes are thin, flag which sections need a quote pulled from the interview.

Instructions

Step 1: Extract and Structure the Raw Inputs

Before writing prose, sort the inputs into the four-part spine:

  • Situation — who the customer is and what their world looked like before
  • Challenge — the specific pain, its cost, and why it mattered now
  • Solution — how they found, evaluated, and deployed the product
  • Results — quantified and qualitative outcomes

Flag any spine section that is under-supported by the inputs and note it as a gap the user should fill from the interview.

Step 2: Write the Headline and Summary Line

  • Headline: Lead with the outcome, not the product. Format: "[Customer] [achieved specific result] with [product/category]." Use the strongest real metric.
  • Summary line: One sentence (under 25 words) usable as a card description, meta description, or sales-deck subtitle.
  • At-a-glance box: Customer name, industry, size, and 2–3 headline metrics as a scannable block.

Step 3: Draft the Challenge Section

  • Open with the customer's context — set the stakes before the pain.
  • Name the specific problem and its business cost (wasted hours, lost revenue, stalled growth).
  • Include a customer quote that voices the frustration if one exists.
  • End on the trigger: what made them start looking for a solution now.
  • Length: 120–180 words. Never mention the product here — this section is the customer's world before you.

Step 4: Draft the Solution Section

  • Describe the evaluation: what they compared, what they were skeptical about, why they chose this product.
  • Detail the actual use case — which features, which workflow, who uses it.
  • Keep it concrete and specific to this customer; avoid generic feature listing.
  • Include an implementation or onboarding detail if available (shows it was low-risk).
  • Length: 150–220 words. Anchor with a quote about the decision or the "aha" moment.

Step 5: Draft the Results Section

  • Lead with the hardest number. Frame every metric with before/after context so the reader feels the delta.
  • Layer qualitative results after quantitative ones (team morale, confidence, time reclaimed).
  • Close with a forward-looking statement — how the customer plans to expand or what's next.
  • Include the strongest customer quote here — the one that would work as a standalone testimonial.
  • Length: 150–220 words.

Step 6: Place Pull-Quotes and the Closing CTA

  • Select 2–3 pull-quotes from the customer's actual words and mark where they should be visually surfaced.
  • Ensure quotes are distinct (one for frustration, one for decision, one for results) — no repetition.
  • Draft a one-line closing CTA tuned to the publishing context (e.g., "See how [product] can do the same for your team →").

Output Format

  • Structure: Headline → At-a-glance metrics box → Challenge → Solution → Results → Pull-quotes (marked inline) → Closing CTA
  • Length: 550–750 words total for web; note a "trim to 300 words" version option for sales decks if publishing context calls for it
  • Format: Structured document with clear section headers, one metrics callout block, and inline pull-quote markers
  • Sections: Headline, Summary line, At-a-glance box, The Challenge, The Solution, The Results, Suggested Pull-Quotes, Closing CTA
  • Tone: Journalistic and credible — the customer is the hero, the product is the enabler. No hype, no superlatives, no marketing adjectives the customer wouldn't use themselves.

Quality Checklist

Before delivering output, verify:

  • [ ] The headline leads with a real outcome or metric, not the product name
  • [ ] At least one quantified result appears in the at-a-glance box and the Results section
  • [ ] The Challenge section contains zero product mentions
  • [ ] 2–3 distinct pull-quotes are placed, each serving a different narrative beat
  • [ ] Every quote used is attributable to the provided inputs — none are fabricated
  • [ ] The customer is positioned as the hero throughout; the product is the enabler
  • [ ] Total length falls within 550–750 words for the web version

Notes

  • The single most common failure in case studies is burying the metric — always surface the strongest number in the headline and the at-a-glance box.
  • If the interview inputs include a compliance-sensitive metric (revenue, exact customer counts), flag it for customer approval rather than assuming it can be published.
  • For a customer who can't share hard numbers, pivot the story to a "before vs. after workflow" contrast and lead with time-saved or process-change results.
  • Keep quotes verbatim; lightly edit only for filler words (um, like) and never change the meaning.

How to use this skill

This file is a Claude Code skill in Anthropic's standard format — markdown with YAML frontmatter at the top.

Installing in Claude Code:

  • ~/.claude/skills/<folder-name>/SKILL.md — auto-loads in every session anywhere on your machine (recommended for skills you'll use across multiple projects)
  • <your-project>/.claude/skills/<folder-name>/SKILL.md — auto-loads only when working in that project (recommended for project-specific skills)

Restart Claude Code or open a new session to register.

Using in Claude.ai, ChatGPT, Gemini, or other AI tools:

  1. Drag this file into a new chat, or copy and paste its contents
  2. Send your task or request as your next message — the AI will apply the skill where it fits

For Claude Code skill details: https://docs.anthropic.com/en/docs/claude-code/skills