---
name: customer-case-study
description: Turns a customer interview and outcome evidence into a fact-checked case study with approved-looking quotes, short and long versions, and a clear evidence trail. Use for customer stories, reference marketing, success stories, testimonial drafts, or proof-point development.
license: Apache-2.0
metadata:
  adlass.categories: "marketing-content/content-production, marketing-content/product-marketing"
  adlass.industries: ""
  adlass.tags: "case-study, customer-story, testimonials, quotes, proof-points, interview"
  adlass.adaptation: "reference-doc"
  adlass.source: "original"
  adlass.version: "1"
---

# Customer case study

## Purpose

Create a credible customer story that connects an initial problem, chosen approach, implementation, and measured outcome without overstating evidence.

## Scope

The skill covers interview analysis, narrative structure, outcome evidence, quotes, sensitive details, short and long versions, and a review draft.

**Excluded:** requesting approval, inventing metrics, making legal claims, and publishing the story.

## Data basis

- Interview transcript supplied as an input.
- Customer context, outcome data, permissions and template in scope.
- Product facts and brand guide in scope.

## Result

A long case study, quote bank, and approval-ready review draft.

## Quality criteria

- Every material fact and quote cites the transcript or evidence source.
- Outcomes include measurement basis, period and limitations.
- Inferences are labelled and sensitive details are identified.
- Short and long versions do not contradict one another.

## Instructions

Use the customer's language where accurate, but do not turn an opinion into a result. Prefer specific before/after evidence and explain the comparison basis. Never imply that one customer's result is typical. Preserve uncertainty and mark every detail that needs customer or legal confirmation.

## Adapt before use

- Add the case-study template and customer approval rules.
- Define approved metrics, attribution language and disclosure requirements.
- Add product facts and brand guidance.
- Define redaction rules for names, figures and sensitive details.
- Keep source facts, analysis, recommendations, and unresolved questions visibly separate.
- Preserve stable document, section, page, sentence, URL, or row identifiers in every finding.
- Record assumptions about audience, channel, period, approval status, and data coverage.
- Treat missing guidance as an adaptation gap rather than inventing a company rule.
- Prefer a precise, bounded recommendation over a broad generic rewrite.
- Use supplied terminology consistently across the document, sheet, and any derivative copy.
- Do not infer performance, customer behavior, product capability, or market response from wording alone.
- Make every unresolved issue actionable by naming the missing decision, evidence, owner, or source.
- Keep factual claims traceable even when the final copy is concise.
- Recheck that counts, names, dates, and identifiers match across all outputs.
- Mark hypotheses as hypotheses and preserve competing explanations when evidence is mixed.
- Use the stated acceptance criteria as the final completeness check.