6 Oct 26 
Most case studies are bland brag pieces nobody reads. Here is how to write one as a sales asset, with real structure and numbers that answer a buyer objection.
CRO
A while back I spent the better part of a week building what I thought was a beautiful case study. Polished layout, a hero image of the client’s new homepage, a tidy paragraph about our process, a logo wall underneath for good measure. We put it live, shared it around, and waited. It generated exactly zero enquiries. Not one person wrote in because of it. I kept it up for months before admitting the obvious: I had written a brag piece, not a sales asset. It flattered us and told a prospect nothing they could use to make a decision.
Why most case studies quietly fail
The default case study reads like an awards submission. It leads with the agency, lists deliverables, and treats the result as an afterthought squeezed into the last line. Nobody outside your office cares that you ran three rounds of wireframes. The prospect reading it is not grading your effort, they are sitting with a problem of their own and silently asking whether you have solved anything like it before. A case study that never names a problem they recognise gives them nothing to grab onto, so they skim and leave.
The fix starts with a shift in how you think about the thing. A case study is not a diary entry about a project you finished. It is a sales asset, and like every sales asset it should be tied to a specific objection a buyer carries into the room. “Will this actually move revenue, or is it just prettier?” “Do they understand a business like mine?” Before I write a line now, I decide which doubt this particular study exists to dissolve. One study, one objection. If it tries to answer everything, it answers nothing.
The structure that actually works
The shape I keep coming back to is simple and it mirrors how a buyer actually reasons. Open with the client’s situation and what was at stake, in their words and from their side of the table. A founder was pouring money into ads but the landing page converted at a rate that made the whole channel unprofitable, and the runway was getting short. That is a stakes sentence, and it is the part most case studies skip entirely.
Then explain what you did and, more importantly, why. Not a feature list, a reasoning trail. We rebuilt the page around a single objection buyers kept raising, moved the proof up so it was seen before the ask, and cut three competing calls to action down to one. The why signals judgement, and judgement is what people are really buying. After that comes the result with real numbers, stated plainly, including the baseline so the number means something. A jump from a two percent to a, say, three percent conversion rate is a fifty percent lift, but only if you show both figures. Close with a quote from the client that sounds like a human being said it, because a sentence in their voice carries more weight than three in yours.
A lot of the decisions inside this structure are the same ones I write about elsewhere, like where social proof sits on the page and how the messaging hierarchy orders what a reader meets first. A case study is just that logic applied to your own selling.
Specific, credible, and easy to skim
Vague case studies die on the word “significantly.” Significantly more leads, substantially better engagement. These phrases exist to hide the fact that there is no number, and buyers read them as a tell. Specificity is credibility. A precise, modest number beats a vague, grand one, and the honest admission of a trade-off, that something took two months longer than planned, makes the whole thing more believable, not less. The same instinct that makes trust badges and security signals work on a checkout page works here: concrete detail lowers the reader’s guard.
Then make it skimmable, because almost nobody reads top to bottom. A clear problem line, the result in a size you cannot miss, the quote pulled out, subheads that tell the story on their own. And put it where the doubt actually surfaces. The study that answers a pricing objection belongs near your pricing, not buried in a portfolio archive nobody visits.
Getting results and permission you can use
None of this works without raw material, and the time to secure it is before the project ends, not six months after when everyone has moved on. I agree up front that we will measure outcomes and ask for a short testimonial at the close, while the relief of a problem solved is still fresh. For numbers a client cannot share publicly, a percentage change without absolute figures usually clears legal, and a named person at a vaguely described company still beats an anonymous quote.
Pick one real project, aim it at one real objection, show the before and the after with honest numbers, and let your client do the closing in their own words. That single page will out-earn the prettiest portfolio you have ever built.