By Laura Leiva, Fractional Managing Editor
The short answer: a strong SaaS case study is a 600 to 1,200 word customer story built on a real interview. It shows who the customer is, the problem they had, why they chose you, how rollout went and what changed, in numbers and in the customer's own words. Write it so a prospect in the same industry sees themselves in it, and so your sales team can send it the same day.
Most SaaS case studies don't do that. They read like a feature list with a logo on top, and sales stops sending them. Here's how to write one that gets used, from an editor who has written and edited customer stories for software companies that serve hotels, restaurants, beauty brands and clinics.
What should a SaaS case study include?
Every case study needs the same core parts:
A results headline. Lead with the outcome, not the product: "How a 12-property hotel group cut guest response time in half."
A snapshot box. Customer, industry, size, product used and two or three headline results, for readers who skim.
The challenge. What was broken before, in the customer's words, and what it cost them.
Why they chose you. What else they considered and what tipped the decision. This is the part prospects care about most.
Rollout. How long it took, who was involved, what surprised them. It answers "Will this be painful for us?"
Results. Specific numbers where possible, plus the softer wins people actually notice.
A strong quote. One line a salesperson would want to read aloud.
A next step. A demo, a related case study or a contact link.
How do you choose the right customer?
The best case study customer isn't always your biggest logo. Look for a customer who:
Looks like the prospects you want more of, in industry, size and role
Had a clear before and after, ideally with numbers
Has a champion who's willing to talk for 30 to 45 minutes
Can get approval to be named (check this first, not last)
Uses the product in a way that shows off what makes you different
Ask your customer success and sales teams. They know who's happy, who's measurable and which story prospects keep asking for.
What questions should you ask in the customer interview?
A 30 to 45 minute call is enough. Record it (with permission) so you can quote accurately. These 15 questions cover everything you need:
Before
What does your team do, and what's your role in it?
What were you using before, or how were you handling this?
What wasn't working? Can you give me a specific example?
What was that costing you, in time, money, stress or customers?
What made you decide it was time to change?
The decision
What other options did you look at?
What made you choose us?
Did you have any doubts going in?
Rollout
How long did it take to get up and running?
Who on your team was involved, and how did they take to it?
Was anything easier or harder than you expected?
Results
What's different now, day to day?
Can you put a number on it: hours saved, revenue, bookings, response time, retention?
What would you tell someone in your role who's considering us?
If we went away tomorrow, what would you miss most?
Questions 14 and 15 are where the best quotes usually come from.
How should you structure the story?
Keep it simple and in this order:
Headline with the result
Snapshot box: customer, industry, size, product, top results
The challenge (2 to 3 short paragraphs)
Why they chose you (1 to 2 paragraphs)
Rollout (1 paragraph)
Results (a short list of numbers, then a paragraph on what changed day to day)
Pull quote
Next step
Write it like a short feature story: the customer is the hero, and your product is the tool that helped. If the reader has to wade through two paragraphs about your company before meeting the customer, start over.
What if the customer doesn't have hard numbers?
Many don't, and that's fine. Ask for estimates ("roughly how many hours a week?"), before-and-after comparisons ("what used to take a day now takes an hour") or proof points they do track, like review scores, no-show rates or ticket volume. Check any number with the customer before publishing. A specific, honest estimate beats a vague claim.
How do you get customer approval without stalling?
Approval is where most case studies die. To keep it moving:
Confirm the customer can be named before the interview.
Send the draft with a clear deadline and a short list of what to check (facts, numbers, quotes).
Ask one person to approve, not a committee.
Offer an anonymized version ("a 40-location restaurant group") as a fallback.
How long should a SaaS case study be?
600 to 1,200 words for the full web version. Then reuse it: a one-page PDF for sales, a single slide for decks, a short LinkedIn post and a 2 to 3 sentence snippet for your website and emails. One interview should give you five assets.
Writing case studies for vertical SaaS
If your software serves hotels, restaurants, salons, med spas or other operators, generic SaaS case study advice only gets you halfway. A few things change:
Your customers are operators, not marketers. They think in covers, occupancy, no-shows and front-desk hours, not "productivity." Use their words.
Interview the person who feels the change. The champion who bought the software matters, but the GM, chef or practice manager who uses it every day gives you the best details.
Show the guest or client side. Prospects want to know what changed for the people walking through the door: faster check-in, fewer missed bookings, better reviews.
Mind the claims in regulated fields. In medical aesthetics and healthcare-adjacent software, avoid treatment or results claims, never include patient details, and have the customer approve every number.
Make it local and specific. "A 34-room inn in Asheville" is more convincing to another inn owner than "a hospitality brand."
Example outline (illustrative)
Headline: How a four-location restaurant group cut no-shows by 30% with online deposits
Snapshot: restaurant group, four locations, reservation and deposit software, 30% fewer no-shows in three months
Challenge: Friday and Saturday no-shows left prime tables empty; staff spent hours confirming bookings by phone
Why they chose it: deposits for large parties, simple setup and texts guests actually answered
Rollout: live at all four locations in two weeks; hosts trained in one shift
Results: fewer no-shows, fewer confirmation calls, steadier weekend revenue
Quote: "We stopped guessing how many tables we'd actually fill on a Saturday."
Mistakes to avoid
Leading with your company instead of the customer
Listing every feature instead of telling one story
Polishing quotes until they sound like marketing
Skipping "why they chose you," the part prospects care about most
Waiting until the draft is done to ask for approval
Frequently asked questions
How many case studies does a SaaS company need?
Start with three: one for each of your main customer types or industries. Add more as you enter new markets.
Should SaaS case studies be gated?
Usually not. Case studies work best when prospects and sales can share them freely. Save gating for white papers and research. (Read Case Study vs. White Paper for when to use each.)
Who should interview the customer?
Someone outside the sales relationship, ideally a writer or editor. Customers speak more candidly to a neutral interviewer.
Can AI write a SaaS case study?
AI can help transcribe and outline, but the value of a case study is the real interview, specific details and quotes, which AI can't invent. Use it to speed up the work, not to replace the conversation.
Need case studies your sales team will use?
I'm Laura Leiva, a journalism-trained editor and fractional managing editor with 15 years of experience. I interview customers and write case studies for SaaS and tech companies, especially software that serves hospitality, restaurants, beauty, aesthetics and wellness.
If you have happy customers whose stories never got written, tell me what you're working on.