Testimonials and Case Studies Are Not the Same Thing
Most homeowners cannot see a pool leak. They may only know the pool is losing water, the water bill has gone up, the autofill runs constantly, or the pool service company noticed something unusual. They have no way to evaluate leak detection equipment or field technique. What they can evaluate is trust -- and trust comes from proof.
A Testimonial
Tells people that a customer had a positive experience. "They found the leak quickly and explained everything clearly." Useful -- but it does not show the process that earned the result.
A Case Study
Shows the problem, the inspection sequence, what was tested, what the evidence showed, and what the next step was. It proves the company has a real process behind the result.
Both matter. A testimonial reduces hesitation. A case study builds conviction. Together they show that the company does reliable, documented work -- not just that someone was happy once.
What a Strong Pool Leak Case Study Includes
Case Study Elements
- The customer's concern and how they described it
- Water-loss history -- how much, how long, what triggered the call
- Pool type and age
- Visible symptoms at arrival
- What areas were inspected
- What tests were performed and why
- What was confirmed with evidence
- What was suspected but not confirmed
- What could not be tested or accessed
- Photos or short video clips when available and permitted
- The repair recommendation
- Verification visit or follow-up result when applicable
This should not read like a marketing brochure. It should read like a clear field summary. The most credible case studies include honest limitations -- what was not found, what was inaccessible, what remains suspected rather than confirmed. That honesty makes the confirmed findings more believable.
Where to Use Testimonials and Case Studies
Once you have clean, permission-approved testimonials and case studies, they can work in multiple places simultaneously. Put them on your website service pages and city pages. Add them to your Google Business Profile as posts. Use them in newsletters sent to past customers, referral partners, and builders. Share short versions on YouTube, Instagram, and TikTok as educational content. Include a sample case study in your capability packet when approaching builders or property managers. Reference specific case studies in sales conversations when a prospect describes a similar problem.
A case study library organized by leak type -- skimmer, return fitting, light niche, main drain, structural crack -- gives you a specific piece of proof to reference no matter what a customer describes.
The FTC requires that testimonials and endorsements be honest, not misleading, and that any material connection or incentive be clearly disclosed. Fake reviews, AI-generated consumer reviews, and paid reviews that are not disclosed are a significant compliance risk. Use real customer feedback only and follow platform rules on review solicitation.
The H.U.N.T.E.R. Method Gives Every Case Study a Structure
Instead of random job photos with a caption, each case study can follow the inspection method -- which shows the thinking behind the result, not just the result itself.
What did the customer report? Water loss per day? Duration? Prior repairs? This is the opening of every good case study.
Pool type, age, plumbing layout, equipment. Context that explains why the inspection went the direction it did.
Which areas were most likely based on symptoms? Showing this reasoning proves the company has a method -- not just tools.
What test was used and why? Dye test, pressure test, acoustic -- explain the choice in plain language.
The evidence. Photos, video, test results, measurements. This is the core of the case study -- what the work actually produced.
What happened next? Repair referral, follow-up inspection, verification visit. Close the case study with a clear outcome.
The best marketing I ever did was a clean report with photos. The builder read it, understood it, and called me for the next three jobs before I sent a single email. That is what documentation does -- it sells the next job while you are still on the current one.
A lot of companies collect reviews and call it marketing. Reviews matter. But a case study that walks through the customer's concern, the inspection sequence, the evidence, and the recommendation does something a five-star review cannot do on its own. It shows that the company thinks through the problem. That is harder to fake and harder to ignore.
One rule I keep: never say "confirmed" when the finding was only suspected. If the case study inflates the certainty of the result and a builder or repair contractor checks the work, you lose the relationship. Write what the evidence actually showed. The honesty is the credibility.
Beginner vs. Advanced
Starting Out
- Take clear before-and-after photos on every job
- Write a short job summary after each inspection
- Ask for an honest review at the end of every job
- Get customer permission before using any photos or details
- Start with 3-5 strong cases before publishing
Building the Library
- Organize case studies by leak type, pool type, and city
- Publish on service pages, city pages, and GBP posts
- Use short video case studies for YouTube Shorts and Reels
- Include sample cases in builder capability packets
- Reference specific cases in sales conversations
Common Mistakes
- Posting customer photos without explicit permission
- Showing addresses, license plates, faces of children, or private property details
- Using fake, staged, or AI-generated reviews
- Making every case sound like a perfect success -- include honest limitations
- Writing "confirmed" when the finding was only suspected
- Posting close-up defect photos with no explanation of what the viewer is seeing
- Treating reviews as a substitute for documented case studies
- Hiding no-leak-found jobs -- a documented no-leak-found result is legitimate proof
- Letting the case study library go stale -- keep adding new ones quarterly
Frequently Asked Questions
Should I publish no-leak-found case studies?
Yes. A documented no-leak-found result with photos, test notes, and a clear explanation of what was inspected is legitimate proof of process. It shows the customer what a thorough inspection looks like even when no leak is confirmed -- and it helps set realistic expectations for future customers with similar concerns.
How many case studies do I need before it makes a difference?
Start publishing with three to five strong examples. Quality matters more than quantity early on. A few honest, well-documented cases are more credible than twenty thin ones. Add more over time and organize them by type so visitors can find the one most relevant to their situation.
Can I use case studies in sales conversations with builders?
Yes -- this is one of the most effective uses. When a builder or property manager describes a situation, being able to say "we had something similar here -- here is how we documented it" is far more convincing than a general sales pitch. Keep two or three printed or digital examples in your capability packet.
Do I need to tell customers I am going to use their job as a case study?
Yes. Always get explicit permission before using any customer-specific information, photos, or details in any public marketing. Some customers prefer full privacy. Others are happy to be included. Ask clearly before publishing anything.
Build Proof Worth Showing
The H.U.N.T.E.R. Method course gives you the documented field process that turns every inspection into a credible case study -- not just another job.
View Courses at Stan Store Use the Free Report App