A finished site and a happy client prove nothing. A number the client measured, and an honest account of the brief, do.
A case study is the most read page on a studio's website and usually the least honest. It shows the finished thing, says the client was delighted, and stops.
We rewrote all of ours last year around one question: what would a buyer need to know to trust this?
A number the client measured
Every case study now ends with three results. The rule is that the client measured them, on their own tools, and agreed to the wording.
That rule removes a lot. "Improved engagement" does not survive it. "Demo requests rose by 46 percent in the quarter after launch" does.
What we were asked to do
A case study that opens with the solution hides the interesting part. We start with the brief in the client's own terms, including what was wrong with the old site.
- The brief, in two paragraphs.
- What we made, as three things you can point at.
- How it went, including how long it really took.
A logo wall says who paid you. A number says what they got.
What did not work
This is the part we are still learning to write. On the Sightglass project, the first explanation of the product went through eleven versions on paper. Saying so makes the final version more believable, not less.
A reader can tell when a story has had its difficulties removed.





