How to write a case study that actually wins clients
Most case studies on agency and service business websites are unreadable. They describe the project from the supplier's point of view, list the technologies used, and end with a sentence saying the client was satisfied. A good case study does something different: it lets a prospective client recognise their own situation and see, step by step, that you have solved it before.
Why case studies outperform testimonials
A testimonial is an opinion. A case study is evidence. Both help, but they do different work, and the second one is what closes a deal that has been sitting undecided for weeks.
The reason is specificity. A quote saying the team was professional and delivered on time could have been written about anyone. A page showing that a wholesaler with eleven hundred products moved off a failing platform without losing their rankings could only have been written about you.
Case studies also answer objections before they are raised. Every buyer has a private worry, usually about cost overruns, disruption to their existing business, or ending up locked in. A case study that describes how those things went is more persuasive than any reassurance you offer directly.
There is a sales benefit that has nothing to do with your website. Case studies become the attachments you send during a pitch, the slides in a proposal, and the answer to the question about whether you have done this in our industry before.
And there is a search benefit. A case study about a bakery in Tartu naturally contains the words a bakery owner in Tartu would type, and those long specific searches convert far better than generic ones.
The structure that works
Use the same five part shape every time. Consistency makes them faster to write and easier for a reader who is comparing three of them.
- The client in one paragraph: what they do, how big they are, what market they serve. Enough for a stranger to judge whether this resembles their own business.
- The problem, in the client's words if possible. Not the technical diagnosis, but the thing that was actually hurting: enquiries had dried up, the shop was losing orders at checkout, staff spent six hours a week retyping data.
- What you did, in plain language and in order. Include the decisions, not only the deliverables, because the decisions are what a reader is buying.
- The result, with numbers wherever you have them and a timeframe attached.
- What happened next, which is the part almost everyone omits. A sentence about the ongoing relationship or the follow up project tells the reader that the result held.
Keep the whole thing between six hundred and a thousand words. A case study is not a portfolio of your writing, and the people who read them are usually skimming with a specific question in mind.
Getting the numbers
Numbers are what separate a case study from an anecdote, and most service businesses have more of them available than they think.
The strongest numbers are commercial: enquiries per month, orders, average order value, revenue, cost saved, hours saved. These are the ones a buyer converts into their own situation.
Second best are the leading indicators: organic traffic, conversion rate, load time, positions for a set of keywords, support tickets. They are easier to obtain and still meaningful if you connect them to the commercial effect.
Always give a baseline and a period. A figure showing enquiries rising from nine to twenty three per month over four months means something. A figure claiming a rise of one hundred and fifty percent, with no starting point, means nothing and reads as marketing.
Be honest about attribution. If the client also started advertising during the same period, say so. Buyers are more sceptical than flattering claims assume, and an acknowledged limitation makes the rest of the page more credible, not less.
Collect the baseline before the project starts. This is the single most practical habit in this article: a screenshot of the analytics and the current numbers taken during kickoff turns into your case study a year later, and reconstructing it afterwards is usually impossible.
When the client will not let you publish
This happens constantly, particularly with larger clients and anyone in a competitive niche, and it is not a reason to give up on the format.
Ask properly. Explain what you want to publish, offer to send the draft for approval, and make the request at the moment of success rather than months later. Approval rates are far higher when the project has just finished well.
If the name is the problem, anonymise it. A regional wholesaler with forty staff conveys almost everything a reader needs, and the case study still works.
If the numbers are the problem, use ranges or relative figures. Enquiries roughly doubled within a quarter is weaker than the exact figures but far stronger than nothing.
If publication is refused entirely, write it anyway and keep it internal. An unpublished case study is still the document you send under NDA during a pitch, and it is still the thing that makes your proposals concrete.
Put the permission question in your contract. A short clause allowing you to name the client and describe the work, with a right of review, removes this whole negotiation from every future project.
Where to publish and how to reuse it
Give each case study its own page with its own address. A single portfolio page holding twelve projects ranks for nothing and lets a reader compare nothing.
Link from the relevant service page to the two or three case studies that match it. This is the highest converting internal link on most service websites, because the reader is already interested and looking for proof.
Add a short outcome summary near the top, so the person who reads only the first screen still leaves with the result.
Include real images: the finished work, the interface, the before and after. Stock photography on a case study page actively damages credibility.
Reuse each one in at least three other places: a section in your proposal template, a post on whichever social channel your clients actually use, and a paragraph in your newsletter. The writing is the expensive part, and it is already done.
Aim for a realistic rhythm. Four solid case studies a year, one per quarter, covering different services and different client sizes, beats a plan to publish monthly that stops after two.
FAQ
How many case studies does a small service business need?+
Between four and eight is the point where the format starts doing its job properly, because the reader needs to find one that resembles their own situation and a single example rarely matches. Aim for coverage rather than volume: different services, different client sizes and ideally different industries, so that whoever lands on the page sees themselves in at least one of them. Beyond about a dozen the returns flatten quickly, and your effort is better spent keeping the existing ones current and adding a follow up result to the older ones than producing more.
What if the project did not produce impressive numbers?+
Publish it anyway if the outcome was genuinely useful, because not every valuable project shows up as a dramatic percentage, and buyers are more suspicious of a page where every result is spectacular than one with a mix. A migration that changed nothing visible but removed a security risk and cut hosting costs is a legitimate story, as is a rebuild that kept traffic flat while halving the time staff spent updating the site. What you should not do is stretch a weak number into a strong looking claim, since anyone capable of hiring you can also do arithmetic, and a single inflated figure casts doubt over every other page you have written.
Should a case study be written by us or by the client?+
Write it yourself, because you know the sequence of decisions and you can structure it for a reader who is deciding whether to hire you, but build it around the client's own words wherever you can get them. A fifteen minute recorded call after the project ends, asking what the situation was before, what worried them about starting and what changed since, gives you the quotes that make the page believable and takes almost no effort from them. Then send the draft for approval, which is both a courtesy and the thing that makes permission easy to obtain, and let the client correct only the facts about their business rather than rewriting the whole piece.