Case Studies and Customer Proof SKILL.md

This is the exact file agents read, including the credit header and licence notice. Save it as case-studies-customer-proof/SKILL.md.

---
name: case-studies-customer-proof
description: "Build a customer proof programme: proof gaps mapped by segment, use case and competitor, candidate selection, interviews that capture measurable results, case studies with the customer as hero, quotes, videos, reviews and references, approvals and anonymised fallbacks, formats for website, decks, ads and sales, and yearly maintenance. Use whenever someone asks for case studies, customer stories, testimonials, customer proof, reference programmes, review collection, social proof for sales or why prospects want peers like them."
license: CC-BY-4.0
metadata:
  author: Afeez Adebayo
  author_url: https://afeezadebayo.com
  author_linkedin: https://www.linkedin.com/in/afeez-adebayo/
  author_x: https://x.com/za_icon
  source: https://afeezadebayo.com/skills-md/marketing/product-marketing/case-studies-customer-proof/
  category: marketing
  subcategory: product-marketing
  version: "1.0.0"
  created: "2026-10-10"
  updated: "2026-10-10"
---

# Case Studies and Customer Proof

Buyers trust other customers more than they trust vendors. Case studies, testimonials, reviews, references and customer videos turn claims into evidence, and they are often the deciding factor late in a deal. Yet many case studies are bland: a logo, a quote that could apply to any product and no numbers. Others take months to produce and then sit unused.

This skill builds a customer proof programme: identifying the right customers, interviewing them, writing case studies with real results, collecting reviews and references, getting approvals and making proof easy for sales and marketing to use.

## Operating principles
1. **Specific beats impressive.** A clear before-and-after with numbers persuades more than a famous logo with vague praise.
2. **Match proof to buyers.** Prospects want stories from companies like theirs, with their problem.
3. **Tell the customer's story, not yours.** The customer is the hero; the product is the tool.
4. **Make it easy to say yes.** Short interviews, drafts written for them, clear approval steps.
5. **Distribute widely.** Proof belongs on the website, in decks, emails, ads and sales conversations.

## Types of proof
| Type | Best for | Effort |
|---|---|---|
| Written case study | Depth for evaluation stages | Medium |
| Short customer quote | Website, ads, decks | Low |
| Video testimonial | Emotional connection, events | High |
| Review site reviews (G2, Capterra, Trustpilot, app stores) | Third-party credibility, search | Low to medium |
| Reference calls | Late-stage enterprise deals | Low per call, relationship cost |
| Data stories (aggregate results) | Broad claims with evidence | Medium |
| Logos | Recognition | Low, but needs permission |

## Case study structure
| Section | Content |
|---|---|
| Headline | The result, in numbers if possible |
| Customer snapshot | Industry, size, region, use case |
| Challenge | What wasn't working and what it cost |
| Why they chose you | Alternatives considered, deciding factors |
| Solution | How they used the product, in their words |
| Results | Measurable outcomes, with time frames |
| Quote | One strong, specific quote from a named person |
| What's next | Expansion, future plans |

## When to use, and when not to
Use it when sales lacks proof for a segment, before launches, when entering new markets, when review site presence is weak and when building a reference programme.

Don't use it for general customer research (`customer-research-interviews`) or for paid social creative testing (the Performance Marketing skills), though both use customer stories.

## Inputs to ask for, in one message
1. Target segments and use cases needing proof.
2. Candidate customers (high satisfaction, measurable results, expansion).
3. Existing case studies, quotes and review profiles.
4. Legal or approval requirements on both sides.
5. Where proof will be used (website, sales, ads, events).

## Workflow

### Step 1. Map proof gaps
By segment, use case, company size and competitor; prioritise gaps that hurt deals most.

### Step 2. Find candidates
High NPS, strong usage, expansion, measurable results; ask customer success and sales for introductions.

### Step 3. Request participation
Explain what's involved, the benefits to them (visibility, backlinks, thought leadership) and the approval process.

### Step 4. Interview
30 to 45 minutes covering the challenge, alternatives, decision, rollout and measurable results; ask for numbers and permission to use them.

### Step 5. Write the draft
In the customer's voice, using the structure above; keep it short and specific.

### Step 6. Approve
Share with the customer contact and their marketing or legal team; agree on what can be named and published.

### Step 7. Produce formats
Full case study, one-page PDF, short quotes, social posts, a slide for the deck, a video clip if possible.

### Step 8. Distribute
Website pages by industry and use case, sales library, emails, ads, review site responses.

### Step 9. Maintain
Update results annually; retire stories from customers who have left.

## Interview questions
```
1. What was happening before you started looking?
2. What did that cost you (time, money, risk)?
3. What alternatives did you consider, and why did you choose us?
4. How did rollout go? What surprised you?
5. What has changed since? Can you share numbers?
6. What would you tell a peer considering us?
```

## Request email (template)
```
Subject: Would you share your [result] story?
Hi [name],
Your team's results with [product] (for example [result]) would really help other [industry] teams facing the same problem. Would you join a 30-minute call? We'll write the draft, you approve every word, and we can include a link to [company] and a short bio for you.
[name], [role]
```

## Proof library structure
| Field | Example |
|---|---|
| Customer | Acme Distribution |
| Segment and size | Distribution, 200 employees |
| Use case | Warehouse picking accuracy |
| Competitor replaced | Spreadsheets and legacy WMS |
| Headline result | Picking errors down 38% in four months |
| Formats | Case study, quote, slide, video clip |
| Approved uses | Website, sales, ads |
| Review date | October 2027 |
Tagging proof this way lets sellers find the right story for each deal in seconds.

Ask for reviews and quotes at moments of success, such as a renewal, a milestone or a strong NPS response.

## Proof metrics
Track case study views in deals, proposals that include proof, review volume and rating trends, reference requests fulfilled and win rates in segments where new proof was added.

Thank customers publicly when stories go live and share the results with them, which makes future requests easier.

## Edge cases and judgement calls
| Situation | What to do |
|---|---|
| Customer can't be named | Anonymised story with industry and size, plus specific results |
| No hard numbers | Use time saved, process changes and specific quotes; ask what they measure |
| Approval takes months | Offer anonymised versions first; keep drafts short |
| Regulated industries | Expect legal review; avoid sensitive data |
| Review sites | Ask satisfied customers at happy moments; never pay for or fake reviews |

## Handoffs to related skills
- Customer interviews: `customer-research-interviews`
- Messaging proof: `messaging-framework`
- Sales use: `sales-enablement`
- Switch stories for battlecards: `competitive-intelligence`
- Launch proof: `product-launch`
- AI search citations from reviews: the AEO & GEO `ai-citation-earning` skill

## Worked example
A logistics software company had eight case studies, all from large enterprises, while most pipeline came from mid-sized distributors. Sales said prospects asked for peers. The programme mapped gaps, recruited six mid-sized distributor customers through customer success, ran 40-minute interviews and produced short case studies with headline results such as "cut picking errors by 38% in four months", plus deck slides and quotes. Proof pages by industry went live and sales added them to proposals. Mid-market win rates improved, and two stories were reused in ads with strong click-through.

## Output format
```
# Customer proof plan: <company>, <date>
## Proof gap map (segments, use cases, competitors)
## Candidate customers and outreach
## Interview guide
## Case study drafts and formats
## Approval tracker
## Distribution plan
## Maintenance schedule
```

## Common mistakes
- Case studies with no numbers.
- Stories that make the vendor the hero.
- Proof from the wrong segment.
- Long approval cycles with no anonymised fallback.
- Case studies buried on one website page.

## Questions to ask before you produce
- Which segments and use cases lack proof in deals today?
- Which customers have measurable results and would speak?
- Where will each story be used?

## Self-check before you answer
- Are gaps mapped to deals?
- Does each story have specific, approved results?
- Is the customer the hero?
- Is distribution planned beyond the website?

## Further reading
- Product Marketing Alliance on case studies: https://www.productmarketingalliance.com/
- G2 review collection guidance: https://sell.g2.com/

---
Created by Afeez Adebayo, Marketing, SEO & Growth Expert
Website: https://afeezadebayo.com
LinkedIn: https://www.linkedin.com/in/afeez-adebayo/
X: https://x.com/za_icon
Source: https://afeezadebayo.com/skills-md/marketing/product-marketing/case-studies-customer-proof/

Licence: CC BY 4.0 (https://creativecommons.org/licenses/by/4.0/). You may copy, share and adapt this skill, including for commercial use, as long as you credit Afeez Adebayo and link to the source URL above. Keep this notice in any copy or adapted version.