Make a Case Study From the Customer Call You Already Had
You already have the proof. It is sitting in a job you finished in March and never wrote down, and it would answer the exact question your next customer is about to ask.
Quick answer
A case study is one job told as a story: what was wrong, what you did, what changed.
Numbers help but they are not the point. The recognisable situation is the point.
Twenty minutes on the phone with the customer gives you more usable material than an hour of writing from memory.
One good one beats six vague ones, and most businesses need three in total, not thirty.
Every business owner has had the conversation where a prospect is almost convinced and then asks, politely, whether you have done this before for somebody like them. The honest answer is usually yes, many times. The useful answer is a specific story, and most of us do not have one ready.
That gap is what a case study closes. Not a brochure, not a testimonial, a short account of one real job that somebody in the same position can recognise themselves in.
Why the Vague Version Does Not Work
Most attempts read like this. We worked with a client in the construction sector to improve their processes and deliver significant efficiencies.
Nobody believes it, because nobody can picture it. There is no customer, no problem, no before and no after. It could describe anything, which means it describes nothing.
The fix is almost uncomfortable in how specific it has to be. What kind of business, how big, what was actually going wrong, what it was costing them, what you did first, what happened. Specific is what makes it credible.
What a Case Study Is Actually For
Not for impressing people who already like you. For answering the one question that stops a sale.
Every business has two or three of these. Will this work for a business my size. Will it disrupt my team while it is happening. Have you dealt with the awkward part of my situation, the old system, the difficult supplier, the seasonal rush.
Pick the job that answers the question you get asked most, and write that one first. A case study that answers no particular question is an article about yourself.
The Shape That Works
Four parts, in order, and it fits on one page.
The situation. Who they are and what their week looked like before. Enough detail that the right reader thinks, that is us.
What was going wrong. The specific problem, not the general theme. Quotes were taking four days. Half the enquiries were never followed up. Two people were doing the same work twice.
What you did. The actual steps, in order. This is where most people get vague to protect their methods, and it is the part that builds trust. Nobody can copy your business by reading one page.
What changed. The result, with a number if you have one, and the honest version of how long it took.
Then one line about what you would do differently next time. It costs you nothing and it is the line that makes the rest believable.
Get the Material From the Customer, Not From Memory
The best case studies come out of a twenty minute phone call with the customer, recorded with their permission.
Ask four questions. What was the situation before you called us. What had you already tried. What was the part you were most worried about. What is different now. Then stop talking and let them answer in their own words.
Two things come out of that call that you would never write yourself. Their description of the problem, which is almost always better than yours, and the detail they cared about that you had forgotten was difficult.
Ask about permission at the start, and ask what they are comfortable sharing. Some customers are happy to be named, some will agree to the story but not the name, and a case study about an unnamed engineering firm with forty staff still works.
Turning the Call Into the Page
The written version is the part that stalls, because a recording is not a document and most of us do not want to sit and type it out.
A lab in IdeoLab is a canvas where your source material and the work you produce from it sit side by side as cards. You can bring in a recording, a document or a web page and have it available to the chat you are working in. So the call with the customer, the original proposal and the notes from the job can all be in front of the same conversation, and the first draft of the case study comes from what was actually said rather than from what you can remember three months later.
The work you then do is editing, which is faster and far more accurate than writing from memory. And the customer's own phrasing survives into the final page, which is the thing that makes the reader believe it.
If this is the job that never gets started, the trial covers the whole system for a week: https://ideolab.ai/TrialBuild
Once the page exists, the same material gives you the short version for a proposal, the paragraph for an email, and the quote for your site, which is why one careful call is worth more than a morning of writing. If the shots from that job are sitting unused too, more marketing from the shots you have covers what to do with them.
Numbers, and What to Do Without Them
A number makes a case study land harder. Forty percent fewer missed calls. Four days down to one. Twelve hours a week back.
But many good jobs do not produce a clean number, and inventing one is the fastest way to lose the trust you were trying to build.
When you do not have a number, use a before and after that a reader can picture. They were checking three systems every morning and now they check one. Enquiries that arrived at the weekend used to wait until Monday. That is concrete without being fabricated, and it is better than a percentage nobody can verify.
Where It Goes Once It Exists
A case study filed in a folder has done nothing. It needs to be where the question gets asked.
Three places cover most of it. On your site, near the service it relates to rather than on a separate page nobody visits. In your proposals, as a short paragraph with a link. And in the follow up email after a first conversation, because that is the moment the prospect is describing you to somebody else.
If the page it sits beside is doing the selling, it is worth checking that page is built for it, which is what getting one live before your next promotion goes through.
Start With the Job You Keep Mentioning
There is one you already bring up in conversations because it explains what you do better than your own description does. That is the first case study, and the customer will probably say yes if you ask.
Call them, record it, keep it to one page, and put it where the question is asked.
Start your free 7 day trial of IdeoLab →
Most people start on the trial, which is full Agency access for seven days. If you already know which plan fits, you can start on one directly. Starter is $39 a month with 2,500 credits for one person, and Agency is $99 a month with 10,000 credits for a team.
Questions Owners Ask About Case Studies
How long should one be?
One page, around five hundred words. Long enough for the story, short enough that a prospect reads it on their phone while deciding whether to call you back.
What if the customer will not be named?
Write it anyway and describe them by type and size. A named customer is stronger, but a specific story from an unnamed one beats a vague story from a named one.
How many do I need?
Three is usually enough, each answering a different objection. More than that and they stop being read. A library of thirty is a sign of effort, not of persuasion.
Can I write one about a job that went imperfectly?
Yes, and those often work best, as long as the ending is honest. A case study that admits a delay and explains how it was handled answers a fear that a flawless one leaves untouched.
Should I ask the customer to approve it?
Always, before it goes anywhere. Send the draft, invite corrections, and keep the approval in writing. It takes a day and removes every awkward conversation that could follow.
How often should they be updated?
Check them once a year. Prices, names and job titles go stale, and a case study that mentions something you no longer offer does more harm than good.