When do you have enough evidence for a customer case study?
You have the beginnings of a case study when a real person or account has used the product for a specific task and you can explain what happened. A well-known customer logo is optional. A clear starting point, the actual workflow, the support involved, and a result the reader can evaluate matter more than a dramatic headline.
Begin with the question a prospective customer is trying to answer. An independent tutor considering a scheduler might want to know whether it handles an appointment across time zones. A story about that workflow can be useful even before you have evidence of time savings or increased bookings. Our trust guide covers the public facts a new product can show alongside the story.
Collect the evidence before writing the success headline
Create a small evidence brief with the participant’s role, starting process, product version, task, observation period, assistance, result, and source of each claim. Keep the private source material separate from the public draft. A statement copied from a founder’s memory should not silently become a measured customer outcome.
GOV.UK’s research-recording guidance recommends recording observations and handling notes and recordings within the agreed permissions. For a public customer story, separately agree which name, quotation, screenshots, and results may appear and where. Permission to participate in a product test should not be treated as blanket permission to publish the participant’s identity.
What should you ask the customer?
Ask them to reconstruct a recent occasion: what triggered the task, how they handled it before, what they tried in the app, where help was needed, and what they did with the result. Invite corrections to your account. A customer saying the product feels easier provides a different kind of evidence from a timestamp showing a completed operation.
Avoid asking for a superlative quotation and then inventing the supporting story around it. The customer-interview guide helps keep questions specific. Useful follow-ups include what did you use the next time, which step still happens elsewhere, and what would make this unsuitable for another team? Those answers give a buyer practical boundaries as well as benefits.
Turn an appealing claim into an accurate result
The table below is an entirely fictional editing exercise for a scheduling app. No customer session or time-saving study was conducted. It shows how the strength of a sentence should follow the strength of its evidence. A more limited statement can be more useful because the reader can understand exactly what was established.
For a before-and-after comparison, record comparable tasks, inputs, people, timing, and assistance. Explain differences that affect interpretation. A faster second attempt may reflect familiarity or an easier task. If you cannot establish a comparable baseline, describe the observed result and leave the savings claim out.
| Available evidence | Overstated interpretation | More accurate account |
|---|---|---|
| One tutor completed a sample booking with maker assistance | Tutors can onboard independently | One assisted trial reached the sample booking result |
| The customer recalls less calendar coordination | The app cuts scheduling time by half | The customer reported less coordination; elapsed savings were not measured |
| A confirmation displayed the expected time zone | Time-zone errors are eliminated | The recorded example displayed the expected zone under the stated setup |
| A customer requested another trial | The product has proven long-term retention | The customer agreed to another trial; later use remains to be observed |
How should you structure the finished page?
Lead with a concise account of the person, task, and supported result. Then explain the starting process, why the product was considered, what the customer actually did, the evidence, and the remaining limitations. Include dates or a version boundary when the behavior may change. A reader should be able to distinguish the customer’s experience from your general product description.
Use a small screenshot, sample output, or approved quotation where it adds information. A focused product demonstration can show the relevant step, while the case study explains its context in the customer’s work. The product-led content guide helps connect that explanation to an appropriate next task.
Can you publish an anonymous case study?
An anonymous account can be useful when the person agrees to publication but their identity cannot be shared. Say what has been withheld and retain enough context to explain the workflow. Check that a screenshot, location, client name, or unusual project detail does not accidentally identify them. Do not imply that anonymity makes a claim independently verified.
If you have no real customer evidence, publish a labeled fictional walkthrough or a demonstration of your own test account. Those formats can explain a capability. They should not be presented as a customer result, populated with invented testimonials, or attached to an organization’s logo without an appropriate basis. Keep the kind of evidence visible in the title or opening explanation.
How does a case study support discovery and sales?
Use a descriptive title around the actual workflow and link the page from the relevant use case, product description, and buying conversation. Make the main explanation available as text, including the conditions behind any important number. A quotation embedded only in an image is harder for a reader to inspect or reuse accurately.
A case study supports evaluation; it does not guarantee a ranking, AI citation, or sale. During a founder-led sales conversation, offer the story when the customer’s task is relevant. Explain differences between the published case and the buyer’s situation instead of promising that everyone will receive the same result.
Review the story after publication
Ask the participant to check the draft facts and the agreed quotation before publication. Record the approved version, publication locations, source references, and a contact for corrections. Later, review the story when the workflow, offer, or supported integration changes. Preserve useful context without leaving obsolete instructions presented as current behavior.
The downloadable evidence brief keeps the claim, source, permission status, and limitations together. If you want to make a broader measured claim, use the original-research guide to design that work. A thoughtful customer account is valuable because it explains a real experience clearly, not because it disguises a small sample as a universal result.