case-study-writer

name

case-study-writer

description

Write evidence-backed customer stories and case studies that show challenge, solution, implementation, and measurable outcomes in a credible narrative. Use when the work is about customer success stories, B2B case studies, proof-driven marketing narratives, reference stories, or sales-enablement stories based on real results. Do not use for fictional storytelling, press releases, or generic blog posts.

Case Study Writer

Turn customer proof into a story buyers trust.

This skill is for writing case studies that demonstrate real outcomes without sounding like ad copy. Strong case studies make the customer credible, the problem concrete, the intervention understandable, and the results measurable enough to persuade skeptical readers.

Scope

Use this skill for:

• B2B customer success stories
• website, PDF, deck, or sales-enablement case studies
• challenge-solution-results narratives
• customer reference stories for specific industries or use cases
• interview-based or data-backed proof storytelling
• adapting one case study into multiple audience or channel variants

Do not use this skill for

Do not use this skill for:

• fictional success stories or invented testimonials
• press releases, product launch copy, or opinion articles
• broad thought-leadership pieces with no customer narrative
• legal approval of claims or regulated marketing signoff
• stories with no verifiable evidence, quotes, or outcomes

Inputs to gather

Before writing, identify:

• target audience and intended use of the case study
• customer profile, context, and consent constraints
• original challenge, stakes, and why change was needed
• solution delivered and what was distinctive about the approach
• implementation timeline, obstacles, and adoption realities
• measurable outcomes, timeframe, and proof sources
• approved quotes, naming rules, and sensitive details to omit

If evidence is thin, do not fake authority. Recommend a lighter proof format or call out where claims need validation.

Output expectations

Return outputs such as:

• full case study draft
• short customer story for web or sales use
• interview-to-case-study synthesis
• headline, summary, and pull-quote options
• proof-point table supporting claims
• channel-specific adaptation plan for site, deck, or email use

Working method

1. Start with the proof, not the prose

Identify the strongest evidence first:

• concrete business outcome
• operational improvement
• timeline change
• cost or revenue impact
• quote that reveals decision logic

Build the story around what can be defended.

2. Frame the customer situation clearly

Readers need enough context to recognize relevance. Clarify:

• who the customer is
• what environment they operate in
• what challenge they faced
• what was at risk if nothing changed

Avoid hiding the problem behind flattering brand language.

3. Explain the solution in buyer language

Describe what was done and why it mattered. Include:

• approach or deployment model
• differentiators that affected the outcome
• obstacles or complexity handled during rollout
• what the customer actually changed in behavior or process

Do not turn the middle of the story into a feature dump.

4. Make outcomes measurable and attributable

Use specifics wherever possible:

• percentage change
• time saved
• throughput increase
• error reduction
• revenue, pipeline, or cost impact
• user adoption or satisfaction movement

State timeframe and attribution limits so the story stays credible.

5. Preserve the customer's voice

Use quotes to add judgment, emotion, or credibility, not filler praise. Good quotes explain:

• why the old approach failed
• why the solution was chosen
• what changed operationally
• why the result mattered

A case study feels real when the customer sounds like a person, not a marketing committee.

6. Match the structure to the channel

For most formats, a strong shape is:

• headline with outcome or transformation
• customer context
• challenge
• solution or approach
• results
• quote and takeaway

Compress or expand depending on whether the output is a landing page, one-pager, deck slide, or email asset.

Heuristics

Prefer:

• evidence before adjectives
• customer-centered storytelling
• specific outcomes with timeframe and context
• tension, stakes, and implementation reality
• quotes that reveal real experience or decision logic

Avoid:

• invented claims, quotes, or metrics
• feature-led stories that bury the business problem
• vague result language like "improved efficiency" with no numbers
• over-polished copy that erases credibility
• making the vendor the hero instead of the customer

Review lenses

When evaluating case-study writing, check:

• Is the audience clear and is the story relevant to them?
• Are challenge, solution, and results easy to follow?
• Are the proof points specific, attributable, and believable?
• Does the customer remain the protagonist?
• Are quotes useful rather than ornamental?
• Could a skeptical buyer repeat the core result without confusion?

Adjacent skill boundaries

• copywriter: broader persuasive marketing copy beyond customer proof stories
• blog-writer: general article writing without customer-story structure
• press-release-writer: announcement format instead of evidence narrative
• ghostwriter: voice-led writing for attributed experts rather than proof assets
• content-writer: broader content production where case-study discipline is not central

Quality bar

A strong result should:

• earn trust with evidence and restraint
• tell a complete challenge-to-outcome story
• show why the result mattered to the customer
• include proof points a sales team can reuse confidently
• sound polished without sounding fabricated

References to use

Use prompt.md for response structure and stance. Use examples/README.md for output shapes. Use guides/qa-checklist.md before finalizing. Use meta/skill.json for metadata and boundaries.