Skip to content
Faisal Mahmud TusherDigital marketing, SEO & analytics
with Faisal Tusher

Content Marketing › Content Production

Writing a Customer Case Study

How to write a customer case study people believe: choose the story, get written permission, interview the customer, check results, approve and keep it current.
Tutorialintermediate13 min readUpdated

What makes a case study believable

A case study is Social Proof in its most detailed form. It borrows its force from the reader's belief that a real customer, in a situation like theirs, had this problem and got this result. The trust and proof guide places case studies among the proof elements that show a claimed outcome has happened for someone like the visitor, and names the way they fail: figures without context or consent. The sales content and training guide describes what a good one contains: the named customer, their situation before, why they chose, what changed after, quotes from the people involved, and results that are specific where the customer allows and verified.

Each of those elements can strengthen the story or quietly undermine it.

ElementWhat makes it believableWhat undermines it
The customerNamed, or described specifically with their agreement"A leading company" with nothing a reader could check
The situationA starting point the reader recognises as their ownA generic problem anyone might have
The decisionThe alternatives considered and the reason for the choiceA straight line from problem to product
The changeWhat is different now, in the customer's termsAdjectives in place of outcomes
The resultsFigures with a period, a measure and a record behind themRound numbers with no source
The quotesThe customer's own words, approved by themLines polished or written for the customer
The relationshipAny thank-you or incentive disclosed beside the storyA discount or fee the reader never hears about

The structure that makes the story recognisable comes from jobs to be done: the customer was in a situation, trying to make progress, and something stood in the way. Told as a list of features the customer used, a case study reads as a brochure with a logo on it. Told as the situation, the decision and the change, it lets a reader at the consideration stage of the Funnel see their own problem and judge whether the same route would work for them.

Three neighbouring jobs sit elsewhere. Where testimonials and results are placed on a landing page is covered in the trust and proof guide. Organising a library of stories that sales representatives can find is covered in the sales content guide. And proof for business buying committees belongs to the business-to-business section: the business-to-business content guide covers content for those buyers, and the customer references and advocacy guide covers running a reference pool, matching references to deals and recruiting advocates. This tutorial is the writing of one case study.

Before you start

  • A brief. The content brief tutorial produces the reader, the stage, the question the story answers and the call to action it leads to. A case study without a brief tends to celebrate whichever customer was happiest last month.
  • A shortlist from the people who know the customers. Account managers, support staff, installers and project leads know who had the problem the reader has, and who is pleased enough to say so.
  • A permission letter or form, agreed with whoever advises the business on legal matters. This tutorial lists what it usually covers; it does not supply the wording.
  • Records to check results against. Job sheets, project logs, invoices, product usage data, or the customer's own reports if they will share them.
  • An interview set-up. Recording with the customer's agreement and a transcript; the customer interviews tutorial covers consent, recording and questions about real past behaviour.
  • An owner and a review date. Someone keeps the story current after it is published and removes it if the customer withdraws.

The steps

The order matters most at the start. Permission comes before the interview, and agreement on what can be named and measured comes before the questions, because a story drafted first and cleared afterwards is the story most likely to be refused or watered down at the last moment.

  1. Choose a customer whose situation a buyer will recognise

    The best story is rarely the biggest customer or the most impressive result. It is the customer whose starting point matches the reader in the brief, described as the Buyer Persona describes them: the same kind of problem, the same constraints, the same worries. Ask the people who know your customers which ones fit, then ask whether the result was typical or exceptional. The influencer contracts and disclosure guide records that claims should not imply results that are not typical, and an exceptional outcome presented as the normal one misleads in the same way. If the best story is exceptional, say so in the story. Approach customers when they are pleased: the trust and proof guide advises asking at the moment of satisfaction, after delivery, a result or a renewal.

  2. Ask for permission in writing before the interview

    Before anyone books an interview, write to the customer explaining what the story is for, where it will appear, roughly what it will cover and that they will approve the final wording before anything is published. Ask for their agreement in writing, from someone entitled to give it: for a household, the people who will be named; for an organisation, someone with authority to agree on its behalf, who may not be your day-to-day contact. The trust and proof guide advises getting written permission to use a customer's name and words and keeping a record of it, and notes for customer logos that many contracts require permission, so check what your agreement with the customer says. The permission covers what may be named, the formats and channels, how long the story may run and how the customer can withdraw. Treat this as general practice and ask your adviser about the wording.

  3. Agree what can be named and measured

    Settle the limits before the questions. Will the customer be named, or described? Which people may be named, and with which roles? May you use photographs, a logo, a location? Which results may be published, and which must stay private? Some customers allow their name but no figures; others allow figures but not their name. Record each answer in the permission file. Do not push for a figure the customer will not publish, and do not plan to ask again at approval in the hope that they relent. If you are offering anything for taking part, such as a discount, a fee, a gift or early access, say so now, say that it does not depend on what they say, and say that it will be disclosed beside the story.

  4. Interview for the before, the decision and the after

    Run the interview in three parts. The before: what the situation was, what triggered the search for help, what they had already tried and what the problem was costing them in their own terms. The decision: which alternatives they considered, what worried them, why they chose you and what nearly stopped them. The after: what is different now, what surprised them and what is still not perfect. Ask about specific moments rather than general impressions, such as "what happened the week before you called us?", and when they mention a change, ask how they know and where it is recorded. The customer interviews tutorial covers the technique of asking about real past behaviour. Talk separately to the colleague who delivered the work for the facts of the job, using the subject-matter expert interview method, so the customer's time goes on their experience.

  5. Check every result against a record

    For every figure in the story, write down what exactly was measured, over what period, compared with what and from which record. Use the business's own records, such as job sheets, project logs or usage data, or the customer's records if they choose to share them. A figure that cannot be traced to a record is cut, or becomes a change described in the customer's own words and attributed to them. The guide to AI claims and consumer protection makes the point for outcome claims generally: if a claim describes typical results, the evidence has to show they are typical, not just possible. Keep the record of each check in the same file as the permission, so that anyone asked about a figure later can show where it came from.

  6. Draft in the customer's order of events

    Draft in the order the customer lived it: the situation, the trigger, the alternatives, the decision, what happened, the result and what comes next. Open with the situation the reader will recognise, not with the product or the business. The headline names the customer's situation and the change, so a reader scanning a list of stories can find the one that matches theirs. The product appears where the customer met it, described as they experienced it. Keep the hesitations and the parts that did not go perfectly; a story with no friction reads as advertising copy, and a candid detail is often the line readers remember. End with the call to action the brief set, matched to the reader's stage.

  7. Keep quotes in the customer's words

    Every quotation comes from the recording or the transcript. The trust and proof guide sets the rule: edit for length, never for meaning, and never write a testimonial for a customer to approve, because the words should be theirs. The AI claims guide adds that AI may help around the edges, for example in sorting genuine quotes by topic, but cannot supply the words, and that polishing a real customer's words changes what they said. Where a spoken sentence is muddled, quote a shorter part of it, paraphrase outside quotation marks with attribution, or ask the customer in the approval step whether they would like to put it differently in their own words.

  8. Send the draft for the customer's approval and record it

    Send the complete draft: the headline, every quotation, every figure, the photographs and captions, the disclosure line and the list of places it will appear. Ask for approval in writing and record who approved which version and when. Changes made after approval, however small, go back for approval again. If the customer asks to remove a figure or a sentence, remove it; the story is published with their consent or not at all. Where the customer's organisation has its own review process, allow for it in the timetable rather than chasing.

  9. Publish with any disclosure and a date

    If the customer received anything for taking part, disclose it beside the story, where a reader meets it, not in a footer or a general policy page. The section below sets out what the site's guides record from the FTC's and the ASA's guidance. Show the publication date and the period the results cover, so that a reader in a later year can judge whether the story still describes the business. Link the story from the pages where its reader is deciding, such as the relevant service or product page, as the trust and proof guide recommends for proof placed beside the decision it supports.

  10. Cut derivatives within the permission and set a review date

    A case study is a source asset: quote cards, a short video, a sales slide, a newsletter summary, a post. Cut only the formats and channels the permission covers. The repurposing guide warns that a quote or image cleared for the original is not cleared for every format. For where each derivative goes, the distribution channels guide suggests customer stories travel through sales enablement, the newsletter and partners' channels, and notes that communities read them as advertising. The sales content guide adds that sales teams must be able to find the story by the attributes buyers share. An awards entry that names the customer is one more use to clear, and the guide to writing an industry awards entry asks for the customer's written approval of exactly what the entry will state. Finally, set a review date. At each review, check that the results still hold, the customer is still a customer and still happy to be named, the product details are current and the permission period has not ended. If the customer withdraws, take down the story and every derivative.

Permission, incentives and disclosure

This section describes general practice and what the site's guides record from regulators' guidance. It is educational, not legal advice, and the rules differ by market and change over time; the regulator's own guidance and your adviser are the authorities.

Permission is a record, not a conversation. Keep it in one file per story, with these items:

ItemWhat to record
Who gave permissionName, role, and the basis on which they can agree for the household or organisation
What may be namedThe customer, the people and their roles, location detail, photographs, logos
What may be measuredEach published figure, its period, its measure and the record it was checked against
Formats and channelsThe website, sales material, social cut-downs, video, events, any paid placement
How longThe period the story may run and what happens when it ends
How to withdrawWhom the customer tells and how quickly the story and its derivatives come down
Any incentiveWhat was offered for taking part, when, and how it is disclosed
ApprovalWho approved which version of the draft, and when

Incentives are common and are not a problem in themselves; hiding them is. The reviews and social proof guide sets out, from the FTC's business guidance, that endorsements from people with a material connection to the business must say so, and that incentives cannot be conditional on sentiment. The influencer contracts guide records that the FTC's endorsement guidance treats a free product or other benefit as a material connection, and that its published questions and answers expect material connections to be disclosed clearly and conspicuously. For a case study, that means a customer who received a discount, a fee, a gift or early access for taking part has that disclosed beside the story, and the thank-you never depends on what they say or on their approving a flattering draft.

The UK advertising codes administered by the ASA require marketing to be obviously identifiable as such, as the media and publishing guide records. A case study on the business's own site is plainly the business's own marketing. The question arises when the story runs somewhere readers might take it for independent editorial, such as a paid placement in a trade publication or a partner's newsletter, where it needs to be recognisable as advertising where the reader meets it.

What the sources this site cites do not settle, this tutorial does not either: the exact wording of a permission or a disclosure, rights in photographs and recordings, and any market-specific rule. Those are questions for your adviser and the regulator's own guidance.

A kitchen fitter's customer story (illustrative)

Illustrative example — not a real result

Grainlatch Kitchens writes a family's refit story

Grainlatch Kitchens, an invented kitchen fitter, wants a story for homeowners who dread living through a refit. Its lead installer suggests a family of four whose galley kitchen was refitted while they stayed in the house. Before any interview, the office sends a one-page permission letter: the story will appear on the website and as three short social cut-downs for 24 months, the family can withdraw by emailing the office, and they will approve the final wording. Both parents sign. They agree to first names and photographs of the kitchen but decline to give a surname or street. Grainlatch offers a voucher for its accessories range as thanks, before the interview and whatever the family says. The 40-minute interview covers the before (a previous refit elsewhere that left them without a sink for a fortnight), the decision (Grainlatch kept a temporary sink and hob working throughout) and the after. The family remembers the fit as "about a week"; the job sheet shows 9 working days, so the story says 9. One quote is shortened, not reworded. The family asks for a sentence about the old cupboards to be removed, and approves the second draft by email, which the office files with the version number. A line under the story discloses the voucher, and the review date is set for 12 months.

Common mistakes

  • Choosing the biggest name instead of the recognisable situation. A famous logo with an unfamiliar problem persuades fewer readers than an ordinary customer with theirs.
  • Interviewing before permission. The story gets drafted, then refused or cut to nothing at approval.
  • Results without a record. A figure nobody can trace is a claim the business cannot support.
  • Writing or polishing the quotes. Words written for a customer to approve are not the customer's words.
  • A product brochure with a customer's name on it. Tell the customer's situation, decision and change, not the feature list.
  • Approval with no record. "They said it was fine on the phone" is not a record of which version was approved.
  • An undisclosed thank-you. A discount, fee or gift for taking part is disclosed beside the story.
  • Derivatives beyond the permission. A quote cleared for the website is not cleared for a paid advert.
  • An exceptional result presented as typical. Say when a story is exceptional.
  • No review date. The customer leaves, the product changes, and the story keeps telling readers otherwise.

Frequently asked questions

Do I need the customer's permission to publish a case study?

Treat written permission as the starting point, obtained before the interview from someone entitled to give it, and covering what may be named, the formats and channels, how long the story may run and how the customer can withdraw. The trust and proof guide on this site advises getting written permission to use a customer's name and words and keeping a record of it, and your contract with the customer may say something about naming them too. This is general practice, not legal advice; ask your adviser about the wording of the permission itself.

Can we give customers something for taking part in a case study?

Many businesses thank customers with a discount, a gift or early access. The reviews guide on this site sets out, from the FTC's business guidance, that endorsements from people with a material connection to a business must say so, and the influencer guide records that the FTC's endorsement guidance treats a free product or other benefit as a material connection to disclose clearly. So disclose the thank-you beside the story, and never make it depend on what the customer says or on their approving a flattering version. This is educational, not legal advice.

Can a case study be anonymous?

Yes, if the customer prefers not to be named, but describe the customer specifically enough that a reader recognises the situation, and say that the name is withheld at the customer's request. An anonymous story carries less weight than a named one, so everything else has to be checkable: the results still come from a record and the quotes are still the customer's own words, approved by them. Never fill the gaps with invented detail, and never present a composite of several customers as one.

Terms used on this page

Frameworks

Where this page is used

Also related

Sources

  1. FTC Endorsement Guides: What People Are Asking — Federal Trade Commission
  2. FTC business guidance — Federal Trade Commission
  3. Advertising Standards Authority — ASA

Related