A case study is a short, honest story of how you helped a specific client solve a specific problem. To write one that wins clients, choose a project with a clear outcome, get the client's permission, tell it in a simple structure (context, challenge, approach, solution, results, lessons), use only verified and approved numbers, add a real quote, and put it where prospects will actually see it.
Key takeaways
- Case studies persuade because they show proof in a situation your prospect recognises, not claims about yourself.
- Pick projects that match the clients you want more of, not just your biggest or newest.
- Always get client approval, and use only figures that are verified and approved. Never invent or inflate results.
- A simple structure, written plainly, beats an elaborate design.
- A case study only works if it is distributed: on your site, in proposals and in sales conversations.
Why case studies persuade
Buyers of services and software worry about risk. They wonder whether you can handle a business like theirs, whether you deliver on time, and what working with you is actually like. A good case study answers those worries with a real story. It helps a prospect picture themselves in the client's position, which is more convincing than generic promises.
It also helps your own team. Writing the story forces you to articulate what you really did, what worked and what you would do differently, which sharpens your sales conversations and delivery process. For B2B companies, case studies also give you proof to share on social channels; our guide to social media marketing for B2B tech companies shows how to put them to work.
Choosing the right project
Not every project makes a good case study. Look for:
- A clear problem that your target customers also have.
- A defined approach you can describe without revealing confidential detail.
- An outcome that can be described honestly, even if it is modest.
- A client who is happy, communicative and willing to take part.
- A project that matches the work you want to win next.
A modest but honest result in a relevant industry often persuades more than a spectacular one in an unrelated context. Our use cases section shows the kind of scenario-style summaries we mean.
Getting permission and approval
This step protects both sides. Ask early, ideally at the start of the project or at its successful close, rather than months later.
- Agree what you may share: the client's name and logo, screenshots, figures, quotes and photos.
- Confirm who at the client signs off, which may include legal, communications or the leadership team.
- Share the draft for approval before publishing, and keep the written agreement.
- Check any contractual confidentiality terms.
- Give the client a way to withdraw or update later.
If a client prefers not to be named, you can still write an anonymised version, covered below.
The structure of a case study
A reliable structure keeps readers oriented and lets them skim.
1. Client and context
Introduce who the client is: their industry, size in general terms and what they do. Give just enough background for the reader to relate.
2. The challenge
Describe the problem in the client's words and from their point of view: what was not working, what it cost them in time, effort or missed opportunity, and why it mattered now. Be specific and human.
3. The approach
Explain how you went about it: how you scoped the work, what options you considered, why you chose one, and who was involved. This shows your thinking, which is what a buyer is really evaluating.
4. The solution
Describe what you built or delivered: the features, process or system, in plain language. Use screenshots or diagrams where they clarify, and avoid jargon.
5. The results
Report what changed, using facts you can support. If there are numbers, they must be verified with the client, approved for publication and described accurately: what was measured, over what period and how. Never invent or inflate a figure, and do not round up. If you do not have hard numbers, describe the outcome qualitatively and honestly: a faster process, fewer manual steps, a launch completed on schedule, a team that now works from one system. Readers trust honesty far more than perfection.
6. Lessons and next steps
End with what you learned, what the client plans next and what the reader can take away. Admitting a challenge, such as a scope change that was handled well, adds credibility.
Quotes and visuals
A direct quote from the client, approved by them, adds a human voice. Ask open questions such as "What was the situation before we started?" and "What has changed since?", then use their words, lightly edited for clarity with their consent. Do not write a quote and ask them to sign it unless it truly reflects their view.
Visuals help scanning: a before and after screenshot, a simple diagram of the system, a photo of the team or a short timeline. Make sure you have the rights to show everything, and blur or remove private data.
Formats: page, PDF and video
- Web page: the best default. It is easy to find, share and update, and it can help your site be discovered.
- PDF: useful for sales conversations, proposals and email attachments. Keep it to one or two pages.
- Video: a short client interview can be powerful, if the client is comfortable and audio quality is good. Add captions and a transcript.
- Short summary: a few lines for use in a proposal, deck or social post.
Start with the page and repurpose from there.
Anonymised case studies
When a client cannot be named, describe them generically, such as "a mid-sized regional distributor", and be careful that details do not identify them accidentally. Say clearly that the case study is anonymised, and be even more careful with figures, since readers cannot check them. Anonymised versions are still useful if they are specific about the problem and approach.
SEO for case study pages
As far as is publicly documented, search engines reward pages that are useful and clearly written for people. Give each case study a descriptive title that mentions the industry and problem, a clear heading structure, a summary near the top and internal links to related services and products. Keep a hub page that lists all your case studies, and link to them from relevant service pages. Our guide to on-page SEO covers the basics. Prospective clients often search for terms like "[industry] software case study", so the industry name matters.
Distribution and sales enablement
A case study sitting unseen in a menu does little.
- Link it from relevant service, product and industry pages.
- Share it with your sales team and teach them which story fits which prospect.
- Attach or link it in proposals and follow-up emails.
- Share extracts on social media and in newsletters.
- Ask the client to share it with their own network if they are comfortable.
- Revisit and update it as the project evolves.
Template outlines
Full case study outline
- Headline that names the client type and the outcome
- At a glance: client, industry, services used, timeframe
- The challenge
- Our approach
- The solution
- Results, with verified and approved figures only
- Client quote
- Lessons and what comes next
- A calm call to action
One-page sales version
- Client and problem in two sentences
- What was done in three bullet points
- Outcome in two sentences
- Quote
- Contact details
Common mistakes
- Writing about yourself instead of the client's problem.
- Publishing without approval, or with figures the client has not confirmed.
- Inventing, inflating or cherry-picking numbers.
- Using jargon the prospect would not use.
- Hiding in a long wall of text with no headings or visuals.
- Never updating or sharing the finished piece.
- Writing only about the biggest clients and ignoring those most like your future ones.
A worked example
Imagine a small software company that built an online booking system for a regional clinic group. The team asks the client for permission at project close, and agrees that the clinic's name, a screenshot and one quote may be used. The case study explains the problem of phone-only appointment booking, the options considered, what was built and how the staff now work. It reports the outcomes in the clinic's own cautious words, and only includes a figure after the clinic checked its records and approved it. The page is linked from the services page, attached to proposals and used in a sales call with a similar clinic.
FAQ
What should a case study include?
Include the client and context, the challenge, your approach, the solution, the results and lessons learned, plus a client quote and relevant visuals. Keep it honest and easy to skim.
How long should a case study be?
Long enough to tell the story clearly and no longer. Many work well as a web page with short sections, plus a one-page summary for sales use.
What if the client will not let me use their name?
Write an anonymised version that describes the client generically, say clearly that it is anonymised, and avoid any detail that could identify them. You can also ask whether they would approve a named version later.
Can I use numbers I cannot fully verify?
No. Use only figures that you and the client have verified and approved, and explain what they measure. If you lack reliable numbers, describe the outcome in qualitative terms instead.
Related reading
- B2B Content Marketing Strategy: From Plan to Measurement
- Link Building for Business Websites: Ethical Methods
- Website Copywriting That Converts: A Practical Guide
Next steps
List your last five projects and score each against the criteria above. Choose one, contact the client for permission and an interview, and draft it using the outline. Then publish it on your site and put it in front of your next prospect. If you would like help presenting your work on a site that converts, contact us.
