How to write a case study a business owner will actually read

A case study a business owner will read has five short sections on one page: the problem in the owner's own words, what you built described as what it does for the business, what changed with one honest number, what you learned, and proof the reader can check. It uses no invented results, names the systems involved, and ends with what you'd do next. Written this way it takes an hour and does more for your next client than a list of tools ever will.

Why do most builder case studies go unread?

They are written for other builders. They open with the stack, describe the architecture, and bury the outcome. A business owner reading them learns that you know Make and OpenAI, and nothing about whether you can solve their problem. Reverse the order: outcome first, systems last, and the same project becomes persuasive.

The second failure is inflation. Owners have read "increased efficiency by 300%" enough times to distrust every number. One modest, verifiable figure beats three impressive ones.

Section 1: the problem, in the owner's words

Two to four sentences. Quote the owner if you can: "We were answering website leads the next morning; by then half of them had booked somewhere else." Include what the problem cost, in time or money, only if the owner told you. Do not diagnose; describe.

Section 2: what we built, as what it does

Three to five bullets, each an action the business now sees happening, not a component:

• Every website form entry gets a WhatsApp reply within a minute, in the clinic's tone.
• The lead is created in the CRM with the source and the two answers they gave.
• Anything mentioning pain or an emergency goes straight to the front desk's phone.

Then one screenshot of the workflow with the tools named in the caption. The screenshot is what makes it real; a wall of text without one reads like a proposal.

Section 3: what changed, with one number

State the measurement, the before, the after, and the period. "First reply time, measured from the CRM timestamps: 9 hours on average in the two weeks before, under 1 minute in the two weeks after. No-shows unchanged; that's the next project." If the number is small, say it. If the client reported it and you didn't measure it yourself, write "reported by the client". If there's no number yet, write what you're measuring and from when.

Section 4: what we learned

The section builders skip, and the one owners trust most. Two or three sentences on what surprised you, what broke, and what you'd do differently: "The form sent duplicates on refresh; we added de-duplication on phone number in week two." This tells the reader you have seen a real project through, not just built one.

Section 5: proof the reader can check

Attach what you can: a 60-second screen recording of the automation running on a test lead, a screenshot of the CRM entry it created, the workflow screenshot from section 2, and a one-sentence quote from the owner with their permission and how they'd like to be named. Label anything anonymised. On AgeBridge, attach these as evidence on the project; they are what moves a project from "described" to proven.

The words to avoid

• "Cutting-edge", "seamless", "revolutionary": they add nothing and cost trust.
• Percentages without a base, a period and a source.
• Tool names in the headline. They belong in the caption.
• "Client was thrilled" without a quote.

A template you can copy

Note Title: the outcome in the owner's words · Problem (3 sentences) · What we built (3–5 bullets + screenshot) · What changed (measurement, before, after, period, who measured) · What we learned (2–3 sentences) · Proof (recording, screenshots, quote, permission) · Next step.

Best fit and not a good fit

Best fit: any finished pilot or project, even a small one, especially your first. Not a good fit: a build that never ran on real data. Run it for a week first; a case study about a demo is a demo.

What to do this week

Take your most recent project and write the five sections in an hour. Send the "what changed" paragraph to the client to confirm the number, then publish it on your profile with the screenshot attached.