The Case Study Format Most Founders Get Backwards
Write a case study that starts with the client's specific mess, real numbers and real frustration, and spend about half its length there before the result. Readers only trust a result they can measure against a concrete starting point, and prospects recognize themselves in the problem, not the happy ending.
Most founder-written case studies open with the result and spend most of the page on the happy ending. Revenue up. Client thrilled. Everyone wins.
That's backwards. The case studies that build trust spend real time on the mess before the fix, because that's the part a skeptical reader needs to see before they'll believe the result.
Before you ask for money, know you're ready.
Your number, your terms, your system to find investors and your answers. One checklist, built by a founder who has been on both sides of the table.
SEND ME THE CHECKLIST →Why should a case study start with the problem?
A case study that jumps straight to "revenue grew forty percent" reads like marketing copy. The reader has no way to judge whether the change was meaningful, because they never saw where it started.
Detail the starting mess, the exact numbers, the exact frustration, and the result finally has something concrete to be measured against.
It does something subtler too. A reader stuck in a similar mess right now recognizes their own situation in your starting point. That connection is stronger than any polished success story, and it's the moment they start thinking, "that's me."
How do you write a case study that builds trust?
Use four beats, in this order. Each one needs a concrete detail a reader could double-check if they wanted to.
| Beat | What goes in it | Share of length |
|---|---|---|
| 1. The starting mess | Real numbers, the real bottleneck, the client's own words about the frustration | About half |
| 2. The decision | The specific call or intervention that changed something | Short |
| 3. The mechanism | Why that change worked, in plain terms | Short |
| 4. The result | Real numbers again, never "significant improvement" | Short |
The mechanism is the beat most founders skip, and it's the one that turns a story into proof. Without it, the result looks like luck.
The objection: "Won't dwelling on the client's problems feel unflattering?"
The pushback: won't a detailed messy starting point feel exposing to the client, especially when they review it before it goes live?
Most clients, asked directly, are comfortable with an honest before-and-after when it's framed as their smart decision to fix the problem, not a judgment on where they were. The mess is the setup for their win.
Get explicit approval on the specific details before you publish. That handles the concern head-on instead of stripping out the detail that makes the story work. If a number is sensitive, ask to use a range or a percentage rather than cutting it.
Find out what an investor will ask before they ask it.
The Raise Readiness Checklist walks you through everything you need before you ask for money.
GET THE FREE CHECKLIST →Two hypothetical case studies, same result
Consider two hypothetical founders describing a similar outcome.
The first opens with "we helped a client increase revenue by thirty-five percent," then moves into generic language about strategy and execution. It blends in with every other vague claim readers have already scrolled past.
The second opens with the client's starting numbers, the exact operational bottleneck behind them and the client's own words about the frustration at the time. Then it walks through the fix and the resulting numbers. That's the version prospects quote back on sales calls as the reason they reached out.
Same result. Only one of them sells.
Where do the best case study details come from?
From the calls, not from memory. The client's own words about their frustration are usually sitting in a recording or your notes from the first conversation, and that's also where your best content idea is sitting.
Once it's written, don't bury it. A strong case study belongs near the story of why you do this work, which is why your About page does more selling than your sales page. And if spending half the page on a mess feels uncomfortable, that's a good sign; the content nobody wants to publish is usually the content that works.
What to do this week
Take your next case study, or rewrite your best existing one, so at least half its length covers the specific starting mess before the result. The result convinces people who already believe you. The mess convinces everyone else.
Key takeaways
- Spend about half of every case study on the specific starting mess.
- Use four beats: the mess, the decision, the mechanism, the result.
- Get the client's approval on details instead of cutting the details.
Frequently asked questions
What should a case study include?
Four beats: the specific starting situation with real numbers, the decision that changed something, the mechanism for why it worked, and the result with real numbers. Each beat needs a concrete detail a reader could check.
How long should the problem section of a case study be?
About half the case study. The starting mess is what gives the result meaning and what lets a prospect recognize their own situation, so it deserves more space than the happy ending.
How do I get a client to approve a detailed case study?
Frame the messy starting point as the setup for their smart decision to fix it, then send the draft for explicit approval. If a number is sensitive, offer a range or a percentage instead of removing it.
Mike Nathan
Founder & CEO, Impero Ventures · Founding Partner, Exit 156 Capital
20+ companies. $170M revenue. $55M raised. 3 exits. 2 VC funds. 1M+ YouTube subscribers.
He doesn't just pitch investors. He founded two venture capital funds.
More about Mike →Got a real business and never raised?
The Raise Academy takes founders from frustrated and floundering to fundable and raising. Four weeks with Mike Nathan. Investor-ready, GUARANTEED.
The guarantee covers getting you investor-ready. No one can guarantee a raise.