How to Write a Simple Case Study in Under an Hour
Case studies sit on the "someday" list of almost every small business, forever, because they feel like a big production. 💖 They don't have to be. The businesses that actually publish them tend to use a boring, repeatable structure rather than trying to write a feature article every single time.
What most businesses get wrong
The biggest trap is waiting for the "perfect" result before starting, which means it never happens, because perfect never quite arrives. The second is trying to write it like a magazine piece, with a narrative arc and a clever opening line, which turns a twenty-minute task into something that sits half-finished in a drafts folder for months. The third, and most common, is describing the work in detail and then glossing over the actual outcome with something vague like "the client was really happy with it," which tells a reader nothing concrete at all.
The SAR formula + 6 prompts
Situation (2-3 sentences): What was happening before you got involved? What was the specific problem?
Action (3-5 sentences or bullets): What did you actually do — the key steps, the timeframe, the one thing that mattered most?
Result (2-3 sentences, ideally with one number or one direct quote): What's different now?
Answer these six prompts, in order, and the draft writes itself:
- What was happening before we started?
- What made them come to us, specifically?
- What were the two or three things we actually did?
- What was the biggest obstacle we solved along the way?
- What's different now? (a number, if you have one)
- What would they say to someone considering us? (one short quote)
How to actually get it done in under an hour
- Pick one result-rich client — don't hold out for a mythical "perfect" one, pick whichever recent project has a clear before and after.
- Send the six prompts as a quick email or ask them on a short call — most clients answer in a few sentences each.
- Draft Situation, Action, Result in that exact order, plainly, without trying to be clever about it.
- Add one real number or quote if you have it — this is what makes it feel true rather than generic.
- Publish it without overworking the design. A clean, simple layout beats a half-finished, highly designed one that never ships.
Mistakes to avoid
- Writing heavily in the third person about your own team instead of the client's experience
- Describing the process in detail and skipping the actual result
- Making it long — case studies work better short and skimmable, not exhaustive
- Publishing a client's name or details without checking they're happy to be identified
- Leaving out any sense of the "before," so the "after" has nothing to contrast against
Frequently asked questions
What if I don't have hard numbers to use?
A specific qualitative change still works — less time spent on something, fewer back-and-forth emails, a faster turnaround. Numbers help, but vagueness is the real problem, not the absence of a statistic.
Do I need the client's permission to publish it?
Yes, always, before publishing anything identifying — a quick "mind if we write this up?" message is usually all it takes, and it protects the relationship as much as it protects you.
How long should a case study actually be?
Short is fine. A few hundred words with a clear Situation-Action-Result structure often performs better than a long narrative piece, because most people skim rather than read every line.
Can I write one without interviewing the client directly?
You can draft it from your own project notes and emails, but it's noticeably weaker without the client's own words somewhere in it — even a short line lifted from a thank-you email is usually enough to carry it.
Keep reading 🤍
I help Gold Coast and Brisbane businesses grow with branding, websites and marketing that actually works.
Work with me ✦