# Case Study Writing > A case study is a published narrative of one customer's outcome with a vendor's product or approach. It is the highest-conversion content asset in B2B marketing because it does the one thing prospects Parent: [Writing and Documentation](https://llms-explorer.com/tree/writing-and-documentation/) · 11 facets · 47 facts · page: https://llms-explorer.com/tree/case-study-writing/ ## Overview - A case study is a published narrative of one customer's outcome with a vendor's product or approach. It is the highest-conversion content asset in B2B marketing because it does the one thing prospects most need: prove that a buyer like them succeeded with this solution. — [source](https://llms-explorer.com/sources/mdb-context-hub/case-study-writing/#overview) - The defining traits of a case study: — [source](https://llms-explorer.com/sources/mdb-context-hub/case-study-writing/#overview) - Specific, named (or carefully anonymized) customer — [source](https://llms-explorer.com/sources/mdb-context-hub/case-study-writing/#overview) - Concrete before/after with quantified outcomes — [source](https://llms-explorer.com/sources/mdb-context-hub/case-study-writing/#overview) - At least one direct quote from a named customer stakeholder — [source](https://llms-explorer.com/sources/mdb-context-hub/case-study-writing/#overview) - A clear narrative arc: Challenge → Solution → Result — [source](https://llms-explorer.com/sources/mdb-context-hub/case-study-writing/#overview) - Customer approval in writing before publication — [source](https://llms-explorer.com/sources/mdb-context-hub/case-study-writing/#overview) - A non-marketing tone - the customer is the protagonist, not the vendor — [source](https://llms-explorer.com/sources/mdb-context-hub/case-study-writing/#overview) ## 1. Challenge / Solution / Result — the BLUF for customer stories - Front-load the result. Place the hero metric in the title or subtitle, and again in the first paragraph. — [source](https://llms-explorer.com/sources/mdb-context-hub/case-study-writing/#1-challenge-solution-result-the-bluf-for-customer-stories) ## 2. Anonymization decisions - Name the customer when: Written marketing approval is signed; customer is referenceable; naming helps, not hurts. — [source](https://llms-explorer.com/sources/mdb-context-hub/case-study-writing/#2-anonymization-decisions) - Anonymize when: Regulated industry; sensitive admission; customer in quiet period. — [source](https://llms-explorer.com/sources/mdb-context-hub/case-study-writing/#2-anonymization-decisions) - Anonymization patterns: — [source](https://llms-explorer.com/sources/mdb-context-hub/case-study-writing/#2-anonymization-decisions) - "A Fortune 500 financial-services firm headquartered in the U.S. Northeast" - High trust — [source](https://llms-explorer.com/sources/mdb-context-hub/case-study-writing/#2-anonymization-decisions) - "A large healthcare provider" - Low trust — [source](https://llms-explorer.com/sources/mdb-context-hub/case-study-writing/#2-anonymization-decisions) ## 3. The "X% improvement" claim hygiene - Specific baseline: "down from 4.2 hours to 12 minutes" beats "much faster" — [source](https://llms-explorer.com/sources/mdb-context-hub/case-study-writing/#3-the-x-improvement-claim-hygiene) - Specific time window: "in the first 90 days" beats "over time" — [source](https://llms-explorer.com/sources/mdb-context-hub/case-study-writing/#3-the-x-improvement-claim-hygiene) - Specific scope: "across 1,200 trades per day" — [source](https://llms-explorer.com/sources/mdb-context-hub/case-study-writing/#3-the-x-improvement-claim-hygiene) - Verifiable source: the customer signed off on this number — [source](https://llms-explorer.com/sources/mdb-context-hub/case-study-writing/#3-the-x-improvement-claim-hygiene) ## 4. Quote integration - Attributed to a named individual with a title — [source](https://llms-explorer.com/sources/mdb-context-hub/case-study-writing/#4-quote-integration) - Sounds like a human said it (not vendor-speak) — [source](https://llms-explorer.com/sources/mdb-context-hub/case-study-writing/#4-quote-integration) - Specific, not generic ("we cut our deploy time in half" beats "Acme has been a great partner") — [source](https://llms-explorer.com/sources/mdb-context-hub/case-study-writing/#4-quote-integration) - Bad quote: "Acme is a true partner who has helped us leverage our data to drive transformational outcomes." — [source](https://llms-explorer.com/sources/mdb-context-hub/case-study-writing/#4-quote-integration) - Good quote: "We used to spend two full days every month reconciling reports. Now it's a 20-minute job for one person." - Sarah Chen, Director of Engineering — [source](https://llms-explorer.com/sources/mdb-context-hub/case-study-writing/#4-quote-integration) ## 7. The written approval workflow - Customer success identifies a candidate — [source](https://llms-explorer.com/sources/mdb-context-hub/case-study-writing/#7-the-written-approval-workflow) - Verbal pre-approval from a customer executive — [source](https://llms-explorer.com/sources/mdb-context-hub/case-study-writing/#7-the-written-approval-workflow) - Draft 1 to the customer — [source](https://llms-explorer.com/sources/mdb-context-hub/case-study-writing/#7-the-written-approval-workflow) - Customer Legal and PR review — [source](https://llms-explorer.com/sources/mdb-context-hub/case-study-writing/#7-the-written-approval-workflow) - Final draft + approval signature — [source](https://llms-explorer.com/sources/mdb-context-hub/case-study-writing/#7-the-written-approval-workflow) - Renewal (annually if case study remains live) — [source](https://llms-explorer.com/sources/mdb-context-hub/case-study-writing/#7-the-written-approval-workflow) ## 8. Tone calibration: the customer is the hero - Vendor-as-hero (anti-pattern): > "Acme's revolutionary platform transformed BigCo's operations, delivering 73% productivity gains." — [source](https://llms-explorer.com/sources/mdb-context-hub/case-study-writing/#8-tone-calibration-the-customer-is-the-hero) - Customer-as-hero (correct): > "BigCo's engineering team cut deploy time from 4 hours to 22 minutes by replacing their legacy CI system." — [source](https://llms-explorer.com/sources/mdb-context-hub/case-study-writing/#8-tone-calibration-the-customer-is-the-hero) ## Where this helps - Producing the highest-conversion B2B marketing asset — a case study — built around a named or carefully anonymized customer outcome rather than a generic testimonial. — [source](https://llms-explorer.com/tree/case-study-writing/) *(AI-suggested, synthesized from this pack's existing facts — not extracted from a source document.)* - A prospective customer is evaluating a vendor claim and needs a specific, credible before-and-after number, such as “down from 4.2 hours to 12 minutes,” instead of vague language like “much faster.” — [source](https://llms-explorer.com/tree/case-study-writing/) *(AI-suggested, synthesized from this pack's existing facts — not extracted from a source document.)* - A customer is in a regulated industry, made a sensitive admission, or is in a quiet period, and the anonymization patterns show how to still publish the story without naming the account. — [source](https://llms-explorer.com/tree/case-study-writing/) *(AI-suggested, synthesized from this pack's existing facts — not extracted from a source document.)* - Managing the approval workflow for a customer story and needing a clear path from candidate identification through verbal pre-approval to a signed draft. — [source](https://llms-explorer.com/tree/case-study-writing/) *(AI-suggested, synthesized from this pack's existing facts — not extracted from a source document.)* ## How to apply this - Front-load the result: put the hero metric in the title or subtitle and restate it in the first paragraph, rather than building up to it at the end. — [source](https://llms-explorer.com/tree/case-study-writing/) *(AI-suggested, synthesized from this pack's existing facts — not extracted from a source document.)* - Apply improvement-claim hygiene — pair every percentage with a specific baseline, a specific time window, and a specific scope, instead of a bare number. — [source](https://llms-explorer.com/tree/case-study-writing/) *(AI-suggested, synthesized from this pack's existing facts — not extracted from a source document.)* - Integrate quotes attributed to a named individual with a title that sound like something a real person actually said, and are specific rather than generic vendor-speak. — [source](https://llms-explorer.com/tree/case-study-writing/) *(AI-suggested, synthesized from this pack's existing facts — not extracted from a source document.)* - Write with the customer as the hero of the narrative — “BigCo's engineering team cut deploy time from 4 hours to 22 minutes” — rather than the vendor as hero. — [source](https://llms-explorer.com/tree/case-study-writing/) *(AI-suggested, synthesized from this pack's existing facts — not extracted from a source document.)* ## Antipatterns - Framing the vendor as the hero of the story instead of the customer, which reads as vendor-speak rather than evidence. — [source](https://llms-explorer.com/tree/case-study-writing/) *(AI-suggested, synthesized from this pack's existing facts — not extracted from a source document.)* - Publishing a percentage improvement with no baseline, time window, or scope attached, which reads as unverifiable marketing rather than a credible claim. — [source](https://llms-explorer.com/tree/case-study-writing/) *(AI-suggested, synthesized from this pack's existing facts — not extracted from a source document.)* - Skipping written customer approval and relying on a verbal go-ahead alone, which leaves the publisher exposed if the customer's position changes later. — [source](https://llms-explorer.com/tree/case-study-writing/) *(AI-suggested, synthesized from this pack's existing facts — not extracted from a source document.)* - Using a generic, unattributed quote instead of one attributed to a named individual with a title and a specific detail. — [source](https://llms-explorer.com/tree/case-study-writing/) *(AI-suggested, synthesized from this pack's existing facts — not extracted from a source document.)* ## Limitations - A case study depends entirely on customer cooperation — willingness to be named, to sit for a quote, and to sign off on the final draft — which makes the pipeline slower and less predictable than other content formats. — [source](https://llms-explorer.com/tree/case-study-writing/) *(AI-suggested, synthesized from this pack's existing facts — not extracted from a source document.)* - Anonymization protects a customer in a regulated industry or quiet period, but it also weakens the story's credibility relative to a named, referenceable account. — [source](https://llms-explorer.com/tree/case-study-writing/) *(AI-suggested, synthesized from this pack's existing facts — not extracted from a source document.)* - Numbers sourced from a customer are only as reliable as what the customer reported; a case study writer isn't independently auditing the metric, just presenting it with proper hygiene. — [source](https://llms-explorer.com/tree/case-study-writing/) *(AI-suggested, synthesized from this pack's existing facts — not extracted from a source document.)* - The written approval workflow, from candidate identification through verbal pre-approval to draft and customer review, takes real calendar time across multiple stakeholders, so a case study can't be produced on a rushed deadline. — [source](https://llms-explorer.com/tree/case-study-writing/) *(AI-suggested, synthesized from this pack's existing facts — not extracted from a source document.)* ## Context files - [Case Study Writing](https://llms-explorer.com/downloads/sources/mdb-context-hub/case-study-writing.md)