home / skills / wesleysmits / agent-skills / case-study-creator

case-study-creator skill

/.agent/skills/case-study-creator

This skill crafts compelling case studies with measurable results, turning client success into reusable narratives for sales, marketing, and thought leadership.

npx playbooks add skill wesleysmits/agent-skills --skill case-study-creator

Review the files below or copy the command above to add this skill to your agents.

Files (1)
SKILL.md
11.4 KB
---
name: creating-case-studies
description: Writes compelling customer success stories with measurable results. Use when the user asks about case studies, success stories, customer stories, client wins, testimonials, or proof of results.
---

# Case Study Creator

## When to use this skill

- User asks to write a case study
- User needs customer success stories
- User wants to document client results
- User mentions social proof content
- User needs portfolio pieces

## Workflow

- [ ] Gather client and project details
- [ ] Identify challenge and solution
- [ ] Quantify results and outcomes
- [ ] Structure the narrative
- [ ] Write the full case study
- [ ] Create summary versions

## Instructions

### Step 1: Gather Case Study Inputs

**Required information:**

| Field                | Purpose                      |
| -------------------- | ---------------------------- |
| Client name/industry | Context and relatability     |
| Challenge/problem    | Reader identification        |
| Solution provided    | Your value proposition       |
| Results achieved     | Proof and credibility        |
| Timeline             | Scope understanding          |
| Quote from client    | Social proof                 |
| Visuals available    | Before/after, charts, photos |

**Questions to ask:**

```markdown
1. What problem was the client facing before working with you?
2. What made this problem urgent or painful?
3. What solution did you provide?
4. What specific results did the client achieve?
5. How long did the project take?
6. Do you have a testimonial quote from the client?
7. Can you share before/after visuals or data?
```

### Step 2: Case Study Formats

| Format       | Length            | Use Case                     |
| ------------ | ----------------- | ---------------------------- |
| One-pager    | 300-500 words     | Sales handouts, quick reads  |
| Standard     | 800-1,200 words   | Website, blog posts          |
| Long-form    | 1,500-3,000 words | Whitepapers, gated content   |
| Video script | 2-5 minutes       | YouTube, sales presentations |
| Slide deck   | 8-12 slides       | Presentations, pitches       |

### Step 3: The Classic Case Study Structure

**Problem → Solution → Results (PSR)**

```markdown
## [Compelling headline with key result]

### The Challenge

[What problem did the client face?]
[Why was this problem urgent?]
[What had they tried before?]

### The Solution

[What approach did you take?]
[What specific services/products were used?]
[How did you implement the solution?]

### The Results

[Quantified outcomes]
[Before vs after comparison]
[Unexpected benefits]

### Client Quote

"[Testimonial]" — [Name], [Title], [Company]

### Key Takeaways

- [Takeaway 1]
- [Takeaway 2]
- [Takeaway 3]
```

### Step 4: Headline Formulas

**Result-focused headlines:**

| Formula                                | Example                                        |
| -------------------------------------- | ---------------------------------------------- |
| How [Client] [Achieved Result]         | "How Acme Corp Increased Sales 47% in 90 Days" |
| [Client] + [Result] + [Timeframe]      | "TechStart: From 0 to 10K Users in 6 Weeks"    |
| From [Before] to [After]               | "From Manual Chaos to Automated Excellence"    |
| [Number]% [Improvement] for [Industry] | "312% ROI for E-commerce Retailer"             |
| [Client] [Overcomes Challenge]         | "How a Local Bakery Conquered Online Ordering" |

**Headline power words:**

- Achieved, transformed, unlocked, boosted
- Doubled, tripled, skyrocketed, slashed
- Secret, breakthrough, proven, guaranteed

### Step 5: Writing the Challenge Section

**Structure:**

```markdown
### The Challenge

[Company name] is a [brief description] serving [target market].

Before working with us, they struggled with:

- [Pain point 1 with specific detail]
- [Pain point 2 with specific detail]
- [Pain point 3 with specific detail]

**The breaking point:** [What made them seek a solution now?]

"[Quote about the frustration]" — [Client name]

Previous attempts to solve this included [what they tried],
but [why it didn't work].
```

**Example:**

```markdown
### The Challenge

GreenLeaf Organics is a sustainable food company serving
health-conscious consumers across the Netherlands.

Before working with us, they struggled with:

- A website that took 8+ seconds to load on mobile
- Cart abandonment rates of 73%
- Zero organic traffic despite quality products

**The breaking point:** A Black Friday sale crashed their site,
costing them an estimated €50,000 in lost sales.

"We knew our products were great, but our website was driving
customers away before they could even see them." — Maria, Founder

They had tried hiring freelancers twice before, but both times
ended with incomplete projects and wasted budgets.
```

### Step 6: Writing the Solution Section

**Structure:**

```markdown
### The Solution

After analyzing [client]'s situation, we developed a
[timeframe] plan focused on:

**Phase 1: [Name] ([Duration])**
[What you did and why]

**Phase 2: [Name] ([Duration])**
[What you did and why]

**Phase 3: [Name] ([Duration])**
[What you did and why]

Key elements of our approach included:

- [Specific tactic/tool/method 1]
- [Specific tactic/tool/method 2]
- [Specific tactic/tool/method 3]
```

**Show your process:**

| Element       | Description                    |
| ------------- | ------------------------------ |
| Discovery     | How you understood their needs |
| Strategy      | Your unique approach           |
| Execution     | Specific actions taken         |
| Tools used    | Technologies or methods        |
| Collaboration | How you worked together        |

### Step 7: Writing the Results Section

**Quantify everything:**

```markdown
### The Results

Within [timeframe], [client] achieved:

| Metric     | Before  | After   | Improvement |
| ---------- | ------- | ------- | ----------- |
| [Metric 1] | [Value] | [Value] | [+X%]       |
| [Metric 2] | [Value] | [Value] | [+X%]       |
| [Metric 3] | [Value] | [Value] | [+X%]       |

**Headline result:** [Most impressive outcome in one sentence]

Beyond the numbers, [client] also experienced:

- [Qualitative benefit 1]
- [Qualitative benefit 2]
- [Unexpected positive outcome]
```

**Result categories:**

| Type         | Examples                                             |
| ------------ | ---------------------------------------------------- |
| Revenue      | Sales increase, average order value, conversion rate |
| Efficiency   | Time saved, cost reduction, productivity gains       |
| Growth       | New customers, market expansion, user acquisition    |
| Performance  | Speed, uptime, error reduction                       |
| Satisfaction | NPS score, reviews, retention rate                   |

### Step 8: Client Quotes

**Quote types:**

| Type           | Use For                               |
| -------------- | ------------------------------------- |
| Problem quote  | Challenge section - their frustration |
| Process quote  | Solution section - working together   |
| Result quote   | Results section - their success       |
| Recommendation | Closing - endorsement                 |

**Strong quote formula:**

```
[Specific result] + [Emotional impact] + [Recommendation]
```

**Examples:**

```markdown
"Our conversion rate jumped from 2% to 6.8%. For the first time,
I actually look forward to checking our analytics. I'd recommend
[Company] to any e-commerce business serious about growth."
— Sarah Chen, CEO, TechGear Pro

"What impressed me most wasn't just the results—it was how easy
they made the whole process. We went from chaos to clarity in
just six weeks."
— Michael Torres, Marketing Director, Acme Corp
```

### Step 9: Visual Elements

**Include where possible:**

| Visual                   | Purpose                |
| ------------------------ | ---------------------- |
| Before/after screenshots | Visual proof of change |
| Results chart            | Data visualization     |
| Client logo              | Brand recognition      |
| Client photo             | Human connection       |
| Process diagram          | Show methodology       |
| Timeline graphic         | Project scope          |

**Chart formatting:**

```markdown
### Traffic Growth Over 6 Months

[Bar chart showing month-over-month growth]

Month 1: 1,200 visitors
Month 2: 2,400 visitors (+100%)
Month 3: 4,100 visitors (+71%)
Month 4: 7,800 visitors (+90%)
Month 5: 12,500 visitors (+60%)
Month 6: 18,200 visitors (+46%)
```

### Step 10: Call to Action

**Case study CTAs:**

```markdown
### Ready for Similar Results?

[Button: Schedule a Free Consultation]

or

### Your Turn

If you're facing similar challenges with [problem area],
we'd love to help. Book a free 30-minute strategy call
to discuss your goals.

[Button: Book Your Call]

or

### Download the Full Case Study

Get the complete case study with all the details,
including the exact strategies we used.

[Button: Download PDF]
```

### Step 11: Summary Versions

**One-paragraph summary (for emails/social):**

```markdown
[Client] came to us with [problem]. In [timeframe], we [solution],
resulting in [key result 1] and [key result 2]. "[Short quote]"
— [Client name]. Read the full story: [link]
```

**LinkedIn post version:**

```markdown
🎯 Case Study: How [Client] achieved [result]

The challenge:
→ [Problem 1]
→ [Problem 2]

Our approach:
→ [Solution 1]
→ [Solution 2]

The results:
✅ [Result 1]
✅ [Result 2]
✅ [Result 3]

"[Short quote]" — [Name, Title]

Full case study in comments 👇
```

**Email teaser:**

```markdown
Subject: How [Client] [achieved result] (case study)

Hi [Name],

Quick case study for you:

[Client] was struggling with [problem].

After working together for [timeframe], they achieved:
• [Result 1]
• [Result 2]
• [Result 3]

→ Read the full story: [link]

[Sign-off]
```

## Output Format

```markdown
## Case Study: [Client Name]

**Industry:** [Industry]
**Challenge:** [One-line summary]
**Result:** [Key metric improvement]
**Timeline:** [Project duration]

---

### Full Case Study

[Complete case study following PSR structure]

---

### Summary Versions

**One-paragraph:**
[Short summary]

**LinkedIn post:**
[Social media version]

**Email teaser:**
[Email version]

---

### Suggested Visuals

1. [Visual 1 description]
2. [Visual 2 description]
3. [Visual 3 description]
```

## Validation

Before completing:

- [ ] Challenge clearly defined with specific pain points
- [ ] Solution explains what was done and why
- [ ] Results include at least 2-3 quantified metrics
- [ ] Before/after comparison included
- [ ] Client quote obtained or placeholder noted
- [ ] Timeline specified
- [ ] CTA included
- [ ] Summary versions provided

## Error Handling

- **No metrics available**: Use qualitative results (time saved, stress reduced, goals achieved) and estimate where possible.
- **Client won't be named**: Use "A leading [industry] company" or create anonymized version.
- **No quote available**: Write placeholder and request from client, or paraphrase feedback.
- **Weak results**: Focus on process improvements, lessons learned, or foundation laid for future success.
- **Confidential details**: Omit sensitive specifics; focus on percentages over absolute numbers.

## Resources

- [Case Study Buddy](https://casestudybuddy.com/) - Templates and examples
- [Canva Case Study Templates](https://www.canva.com/) - Visual design
- [SlideBean](https://slidebean.com/) - Pitch deck templates
- [Hemingway Editor](https://hemingwayapp.com/) - Readability check

Overview

This skill writes compelling customer success stories that highlight measurable results and clear outcomes. It turns raw client data into structured case studies, one-pagers, slide decks, or social summaries suitable for sales, marketing, and PR. Use it to create proof-of-result content that drives trust and conversion.

How this skill works

I gather key inputs—client context, challenge, solution, timeline, metrics, and quotes—and use a Problem→Solution→Results structure to craft readable narratives. The skill quantifies outcomes, produces headline options, and creates summary variations (LinkedIn post, email teaser, one-pager). Visual suggestions, CTAs, and validation checks are included to ensure the case study is complete and actionable.

When to use it

  • When a user asks to write a case study or success story
  • To convert client results into sales collateral or website content
  • When preparing portfolio pieces, pitch decks, or whitepapers
  • To create short social posts or email teasers from a full case study
  • When you need structured, measurable proof for marketing or sales

Best practices

  • Collect specific inputs up front: metrics, timeline, client quote, and visuals
  • Use the Problem→Solution→Results (PSR) structure for clarity and flow
  • Quantify outcomes wherever possible and show before/after comparisons
  • Pick a format and length that matches the channel (one-pager, standard, long-form, video script)
  • Include a clear CTA and at least one client testimonial or a noted placeholder

Example use cases

  • Create a one-page case study for a sales meeting showing conversion lift and ROI
  • Draft a website case study (800–1,200 words) with charts and a client quote
  • Write a LinkedIn post and email teaser from an existing full case study
  • Produce a slide-deck outline (8–12 slides) for a pitch that highlights timeline and metrics
  • Generate a video script (2–5 minutes) summarizing the challenge, approach, and headline result

FAQ

What if the client won’t share exact numbers?

Use percentages, relative improvements, or qualitative outcomes; note estimates and anonymize the client if required.

Which case study length should I choose?

Match the audience: one-pager for sales, standard (800–1,200 words) for websites, long-form for gated content or deep dives; create summary versions for social.