Open a plumber's website and scroll to the reviews. You'll find three lines of italic text next to a row of stars: "Great service, fast and professional, highly recommend!" That's not a case study. That's a testimonial dressed up to look like proof, and most visitors register the difference even if they can't name it.
Here's the problem with the way most service businesses handle "social proof": it's vague on purpose. Nobody wants to name the client, the price, or what actually went wrong, so the write-up shrinks down to a generic compliment anyone could have written about anyone. It doesn't persuade. It just fills space.
This article gives you a case study template built for service businesses (plumbers, HVAC companies, dentists, salons, contractors, anyone who sells a job rather than a subscription), plus two worked examples and a straight answer on where to put them.
Why case studies convert better than testimonials
A testimonial is an opinion. "They were great" tells a reader nothing about whether the business can handle their specific problem. A case study has a beginning, a middle, and a checkable end: a homeowner had a specific issue, you did specific things about it, and something specific changed. That structure does work a testimonial can't.
The industry data backs this up. Among B2B marketers, 75% already use case studies or customer stories as a content format, rated the second most effective format overall, just behind video and ahead of blog posts, ebooks, and data sheets.
Buyers lean on this kind of proof more than ever before they pick up the phone. 90% of people search online before choosing a local business, and most of them read reviews as part of that search. Nielsen Norman Group's research on website trust and credibility found something worth knowing: people liked seeing testimonials and case studies on a company's own site, but regarded them "with a healthy dose of skepticism." They wondered if the stories were even true, since of course a business only posts the good ones.
That skepticism is exactly what a real case study defeats. Vague praise triggers the "of course they'd say that" reaction. Specific detail (a name, a date, a part number, a photo) doesn't, because it's harder to fake and easier to check. Testimonials aren't worthless (a video or written testimonial still works as a quick trust signal), but a case study is what actually moves someone from "maybe" to "call them."
The case study template that actually works
Skip the fancy structure. Three parts, in this order, every time:
| Part | What goes here | Typical length |
|---|---|---|
| 1. The problem | The specific situation before you got involved — what was broken, costing money, or embarrassing. Named, dated, concrete. | 2–3 sentences |
| 2. What you did | The actual steps you took, in plain language. Not "we optimized their approach" — what you diagnosed, built, replaced, or fixed. | 3–5 sentences |
| 3. The result | A specific outcome the reader can picture or verify — a number, a timeframe, a direct quote, a before-and-after photo. | 1–2 sentences + proof |
The problem is where most write-ups go soft. "A customer needed help with their plumbing" isn't a problem, it's a category. "A homeowner in Lakewood had a water heater fail on a Sunday night, no hot water for a family of five" is a problem. Put a person in it, and put a stake in it: money, time, comfort, safety.
What you did is where you get to be boring on purpose. Resist the urge to sound impressive. List the actual steps: what you inspected, what you found, what parts you used, how long it took. The mundane detail is what makes it believable. A case study that sounds like a sales pitch reads like one.
The result is the payoff, and it needs to be checkable. A number is the strongest version ("replaced same-day, back to hot water in under three hours"), but if you don't have a clean number, a specific quote or a photo works almost as well. What doesn't work: "the customer was thrilled." That's a testimonial wearing a case study's clothes.
Write the result sentence first, then work backward. If you can't write a specific, checkable result in one sentence, you don't have enough material for a case study yet. You have a testimonial. Go get the detail before you publish.
Two worked examples
The two examples below are illustrative composites, invented for this article to show the template in action. They aren't real clients, and no business should be inferred from them.
Example: Harbor Line HVAC (illustrative, not a real business)
The problem: A homeowner's furnace died on the coldest night of the year, two young kids in the house, temperature dropping into the teens. Their previous contractor didn't pick up. They found Harbor Line through a Google search at 11 PM.
What we did: Dispatched a technician within 40 minutes. Diagnosed a cracked heat exchanger, a safety issue, and explained the carbon monoxide risk in plain terms before recommending replacement over repair. Installed a new unit the next morning with a loaner space heater dropped off that night.
The result: Heat restored within 14 hours of the first call, with a written safety explanation the homeowner could hand to their insurance company. That's the kind of specific timeline a one-off emergency call needs to turn into a repeat customer for the annual tune-up.
Example: Bluebell Family Dental (illustrative, not a real business)
The problem: A new patient needed a crown but had put off calling for months, worried about cost and unsure what insurance would cover. Their old provider's site had no pricing information and a contact form that never got a reply.
What we did: Built a same-day-answer policy into intake: patients get a real cost range over the phone before they book, plus a plain-language breakdown of typical crown coverage. The patient booked a consultation the same day they called, three months after first considering it.
The result: Treatment completed within two weeks of first contact. The patient later ranked "not having to guess about cost" as more valuable than the polish of the office itself. That's the actual friction removed, and the kind of outcome a case study can be built around.
Notice what both share: a named scenario, a specific action, an outcome you could double-check. Works for a two-person plumbing outfit or a multi-chair dental practice, same template either way.
Where to put case studies on your site
Case studies do the most work in three places, and you don't need more than that.
- A dedicated case studies or "our work" page linked from the main nav, for someone who's already interested and wants to get convinced.
- Service pages, one relevant case study embedded per page. Someone reading about water heater repair should see a water heater case study, not a generic testimonial carousel.
- Right above your contact form, on whichever page gets the most traffic. It's the last thing someone reads before deciding whether to fill out the form or pick up the phone, and a specific story beats a generic "why choose us" list every time.
Don't scatter one case study across five pages hoping it does double duty everywhere. Match it to the page's topic. A roofing case study about storm damage belongs on the storm damage service page, not buried on the homepage where it competes with everything else you do.
Want case studies built into your site, not bolted on?
RankLoft builds the story structure into your site from day one — service pages, proof, and a contact form that actually gets used.
Get a free site audit →Common mistakes to avoid
Trust in generic proof is eroding. In the most recent Local Consumer Review Survey, 75% of consumers say they're concerned about running into fake reviews, and nearly half won't consider a business with a thin review history. Vague, unverifiable praise is exactly what that skepticism targets.
With that context, here's where service businesses keep going wrong:
- No proof attached. No photo, no number, no name (even a first name or "a homeowner in [city]"). Without one verifiable detail, it reads the same as a testimonial.
- Using stock photos instead of the real job. A generic wrench photo undercuts the whole point. If you don't have real photos yet, start taking them; even a phone photo of the actual work beats stock. (Here's how to get better ones with what you already have: simple DIY business photography that doesn't look amateur.)
- Writing it like a brag sheet. "Our expert team delivered exceptional results" is a testimonial in disguise. Say what you actually did, step by step.
- Never updating them. A case study from 2019 reads as evidence you haven't had a win since. Add one every time you finish a job worth telling.
- Hiding them behind a PDF download. Buyers won't fill out a form to read proof before they trust you. Publish it directly on the page.
Most of these mistakes come from treating the case study as a formality instead of a sales tool. It's worth the extra ten minutes to get a real quote, a real number, and a real photo. That's the difference between a page nobody reads and the page that actually turns a visitor into a booked job.
Sources
- Content Marketing Institute — B2B Content Marketing Trends Research 2025
- HubSpot — 16 Important Ways to Use Case Studies in Your Marketing
- Nielsen Norman Group — Trustworthiness in Web Design: 4 Credibility Factors
- Nielsen Norman Group — Trust and Credibility: Ecommerce UX Report
- BrightLocal — Local Consumer Review Survey
Frequently asked questions
How many case studies does a service business website need?
Three to five is plenty for most local service businesses — one per major service line or common objection. More than that and visitors stop reading. A handful done well beats a library of generic ones.
What's the difference between a case study and a testimonial?
A testimonial is a quote about how great you are. A case study is a story with a specific problem, what you did about it, and a result someone can check — a timeline, a before-and-after photo, a number. Testimonials are opinions; case studies are evidence.
Do I need a client's permission to publish their case study?
Yes, always get written sign-off before naming a client or using their photos — a quick email confirming what you'll publish is enough. If someone doesn't want their name used, anonymize the write-up (a homeowner in your city) and keep the specifics that make it credible.
Can a case study work without exact numbers?
It can, but it's weaker. If you don't have a hard number, use a specific detail instead — the exact problem, the parts used, the timeline, a direct quote about what changed. Specificity is what makes it believable, and a number is just the easiest kind of specific.
