You finished a job that went well. The customer was happy, the work was clean, and the result was something you would love a future customer to see. Then you open your own website and it says "quality work" and "trusted by local clients," the same words every competitor uses. A case study for service business owners fixes that gap by showing one real job instead of describing your standards. The worry underneath is rarely the writing. It is whether you can prove the work without stretching the result, exposing the customer or making them uncomfortable. All of that is manageable, and you can start with three lines and one email to the customer. A short page built from one real job beats a long one built from adjectives.
Key Takeaways
Write the problem, the work and the outcome of one recent job. If you cannot write them specifically, pick another job.
Get written, project-specific permission before you publish the customer's name, quote, photos or results. The FTC treats a customer's words in your marketing as an endorsement.
Describe the result as this customer's outcome, with a time period. "Results may vary" alone does not fix an unusual result, per the FTC.
What goes into a short case study for a service business?
A short case study shows one real customer's situation, the problem they faced, what you did, and what changed afterward. Add a specific result when you can support it, a customer quote only with permission, and real project evidence such as photos or screenshots. Publish it on your website and link it to the service it shows.
HubSpot's case study guide lists a title, client profile, challenge, solution, results, visuals, quotes and a call to action. The Content Marketing Institute centers on the client, their needs, your solution, the results and a testimonial quote. Put together for a contractor, agency or consultant, the parts look like this:
| Part | What to write | Example of a specific line |
|---|---|---|
| Customer | Their type of business or home, and why a future customer would relate | A two-person dental office with one front desk |
| Problem | The before-state, not a general service description | Patients waited on hold because the phone line dropped calls |
| Objective | What the customer needed to change | Stop losing booking calls |
| Work | The decisions, steps, scope and timeframe | Rerouted the line and tested it over two weeks |
| Result | A measured outcome, or a plain observable change | The front desk stopped logging missed calls |
| Customer words | An approved quote, attributed to them | One or two sentences they signed off on |
| Proof | Real photos, screenshots or documents | A photo of the finished work |
| Next step | A link to the matching service and a way to reach you | A link to the service page |
The example lines above are only a demonstration of how specific each part should be. Use your own job and your own records. A made-up customer or a quote that never happened has no place on the page.
How do you pick the job and write the three lines?
Choose one recent job with a clear difference between before and after. Then write three lines:
- Problem: What was wrong, slow, costly, confusing or risky before the work?
- Work: What did you diagnose, build, repair, redesign, install or change?
- Outcome: What changed afterward, when was it measured, and what backs that up?
Next, list the customer material you already have: a quote, a photo, a screenshot, permission to name the business, permission to show the work. If you cannot write the three lines specifically, choose another job or gather more facts before drafting. Hoffman Marketing Communications recommends getting customer permission and using real customer photography, which fits this order: facts first, then permission, then copy.
Do not start by designing a polished page. A real problem, a defined piece of work and an outcome you can back up matter more than layout. A short web page can be more useful than a long download if it makes the problem, the work and the result easy to see.
What permission do you need before publishing a customer's name, quote or photos?
Get written, project-specific permission before you publish the customer's name, company, identifying details, photographs, screenshots, quote or results. A verbal yes is easy to forget and hard to prove later, so ask in a message the customer can reply to. A good request names:
- where the material may appear, such as your website, email or social posts
- which items you want to use: name, logo, quote, photos, results
- whether you may edit for length or grammar
- whether the customer may approve the final version
- whether they can withdraw permission before it goes live
The FTC's Endorsement Guides questions and answers explain why this is more than courtesy. The June 2023 Endorsement Guides define an endorsement as an advertising message likely to reflect another person's opinions, beliefs, findings or experiences. A customer quote inside a case study fits that definition. The endorsement must reflect the endorser's genuine experience, and it cannot claim something you could not legally claim yourself. If the customer has a material connection to you, such as a payment, a job, a family tie or something of value, and the audience would not expect it, it must be disclosed.
Permission and truthful advertising are two separate questions. Permission controls whether you may use the customer's identity, words, images and project details. FTC rules control whether the finished marketing is truthful, supported and properly disclosed. A customer saying yes does not make every claim on the page acceptable.
Privacy rules, publicity rights and contract terms can differ by state and by the customer's industry. If a contract has a confidentiality clause, or the work touches regulated information, have a lawyer review your release before you publish anything that identifies the customer.
Who owns the photos you want to use?
Two different questions hide inside "can I use this photo?" The first is whether the person or property pictured agrees to appear. The second is who owns the copyright. The U.S. Copyright Office's photography guide says the person who took a photograph generally owns it, and others need permission to use it.
In practice, that means photos you took yourself of your own work are yours to use, subject to the customer's permission to show their property or their face. A photo the customer took, or a photo of their finished space that a photographer shot, belongs to that photographer unless they give you rights. Add a line to your permission request that covers each photo you plan to use and who took it. The same goes for a logo. Do not copy a customer's logo from their website without being told you may.
A real project photo does not have to look like a studio shoot. A clear image of the actual work is more useful to a future customer than a staged one.
How do you describe results without overpromising?
Describe the result as this customer's documented outcome, with the time period, the starting point, where the data came from and any conditions that applied. A line such as "During the first three months after launch, the customer reported fewer support calls" claims only what happened. "Our process reduces support calls" turns one job into a promise.
That distinction matters because of how the FTC reads testimonials. Per the FTC's advertising FAQs for small business, a testimonial that shows an unusual result can imply that other customers can expect the same, and "Results may vary" on its own is not enough. You have two ways to stay on the right side of that: back up the claim that the result is typical, or clearly state what customers can generally expect or how limited the featured experience was. The FTC's talk on myths and half-truths about deceptive advertising covers the same ground.
You do not need a dramatic percentage. If the outcome is qualitative, name the change you can observe without inventing a number: fewer repeated questions, a shorter process, a repaired failure, a project finished within a tight constraint, a clearly different appearance. Publishing several similar success stories also does not prove the result is typical. Each story still needs its own support.
Where should the case study live on your website?
Give each substantial case study its own page, reachable through a central section such as Case Studies, Work or Results. Link that index page to each story, and link each story to the service page that matches the work. A PDF buried in a download folder, or a gallery with no text, does not do the job. A crawlable page with a clear heading and real text can be found, read and sent to a prospect.
Use link text that names the destination, such as "content marketing services" or "website redesign services," rather than "learn more." Link to the customer's own website only if they agree and only if the link helps the reader. Match each link to the work you actually did. A case study about a website rebuild should link to your web design service, not to every service you sell.
Google's AI features guidance says an indexed page that is eligible to appear as a search snippet is eligible for AI features, and that no special schema is required. A case-study index helps people and search engines find your stories, and it does not guarantee rankings or citations. So, build the page for the reader who is comparing you to another provider, and treat search visibility as a side effect.
If you also collect customer clips, see video testimonials for a small business.
What usually goes wrong, and how long does each fix take?
These are the weak spots to check, in the order they tend to do damage. The order is a practical risk list, not a measured ranking. The time ranges are rough planning figures that depend on whether you already have records and permission.
| Problem | What fixes it | Rough time |
|---|---|---|
| Vague problem and generic service description | Interview yourself or review project records | 30 to 60 minutes |
| Result with no baseline or period | Find the starting point, measurement window and data source | 1 to 3 hours if records exist |
| No written permission | Request approval and record the allowed uses | Minutes to several weeks, depending on the customer |
| Quote edited past its meaning | Send the exact draft back for approval | 30 to 90 minutes |
| No evidence behind the story | Gather reports, screenshots, invoices or photos | 1 to 4 hours |
| Story hidden in a PDF or gallery | Create a crawlable page, an index entry and links | Several hours to a day |
| No link to the matching service | Add one relevant service link and one next action | 15 to 30 minutes |
| Self-praise instead of customer story | Rewrite around the customer, the problem and the result | 1 to 3 hours |
The first five items damage trust or create compliance risk. The last three make the page harder to use and to find. If you have to pick where to spend time, fix the first five before touching design.
What can you stop worrying about?
You can stop worrying that every case study needs a spectacular revenue number, a studio photo shoot, a long PDF or a customer who writes a glowing quote. A specific operational improvement is useful: fewer repeated questions, a shorter process, a repaired failure, a project finished within a tight constraint.
You can also drop the idea that a story has to be anonymous to be safe. An anonymous version is allowed when the customer does not want to be named, as long as the page does not identify them and every claim is accurate and supportable. If the customer declines altogether, you can still publish a project description using only information you own and can support, as long as it does not identify the customer or imply an endorsement they never gave.
Keep taking permission, evidence, privacy, photo ownership and claim accuracy seriously. Those matter more than decoration.
When does it make sense to hire help?
You can do the first ten-minute check yourself, and you should. Pick the job, write the three lines, list the materials, and send the permission request. If that goes smoothly, a short page built from your own notes may be all you need.
Outside help starts to pay off when you have several possible projects and scattered evidence, a customer who needs a careful approval process, sensitive information, results that are hard to state, or a website that does not turn the finished story into a useful page. A writer or agency can interview you, separate facts from claims, record permission, keep the customer's meaning intact, structure the page for scanning, connect it to the right service and keep it accurate as it ages. The value is less friction and less risk. It is never a stronger result than your records support, and a vendor who promises one is selling something the evidence will not back.
Is your case study ready to publish?
Pick an answer to begin.
1. What should you write first, before designing any page?
2. A customer says yes by phone to being featured. What should you do next?
3. Your customer's result was unusually strong. How should you word it?
Frequently Asked Questions About case study for service business
What is a case study for a service business?
A short account of one real customer's problem, the work you did and what changed afterward. It can include an approved quote and real project photos.
Does a case study need exact numbers?
No. Numbers help when you can support them. A specific operational change, such as fewer repeated questions or a shorter process, can be reported without a figure.
Do I need the customer's permission?
Get written permission before you use the customer's name, quote, images, logo, identifying details or confidential results. Spell out where each item will appear.
Is a case study the same as a testimonial?
No. A testimonial is the customer's endorsement or experience. A case study adds the background, the work you did and the outcome. A customer quote inside a case study can still count as an endorsement under FTC guidance.
Can I publish an anonymous case study?
Yes, if the page does not identify the customer and every claim is accurate and supportable.
Can I just add "results may vary"?
No. Per the FTC, that phrase alone does not fix a testimonial that shows an unusual result. Support the claim that the result is typical, or clearly state what customers can generally expect.
Moving Forward
A case study for a service business is one real job told in a form a future customer can use: the problem, the work, the result, the customer's approved words and real proof. Start with three lines. Get written permission. Word the result as this customer's outcome with a time period. Put the page where it can be found and link it to the service it shows. None of this needs a big number or a designer.
Done well, one finished story becomes a page you can send to a prospect who asks whether you have done something like this before, and it stands in for a paragraph of claims you would otherwise have to defend. You can add more stories one job at a time, each with its own permission and its own records.
If you want help turning a finished job into a page, Web Leveling can interview you, sort the facts from the claims, handle the permission steps and place the story on a page tied to the right service. Our content marketing work covers written project stories like this one. If your records are thin or the result will not hold up as a claim, we will say so and help you write the version that does. We work with small and medium businesses across the country and overseas. Contact us about your case study and bring one job you want to show.
Terms
Case study words in this post
Tap a term to see what it means.
Case study. A short written account of one customer's problem, the work done and the result.
Testimonial. A customer's statement about their experience, used in your marketing.
Endorsement. Under the FTC's Endorsement Guides, an advertising message likely to reflect someone's opinions, findings or experiences.
Material connection. A payment, job, family tie or other thing of value between you and the person endorsing you.
Baseline. The starting numbers or condition before the work began.
Release. A signed permission that says what a customer allows you to use and where.
