# How to Write a SaaS Case Study (Even With 5 Customers) > How to write a SaaS case study with only a handful of customers: who to pick, an ask email, a 30-minute interview script, real numbers, approval and structure. - Canonical: https://zeroraised.com/blog/how-to-write-a-saas-case-study - Published: 2026-11-07T11:30:00Z - Author: ZeroRaised Team (https://zeroraised.com/blog/authors/zeroraised) - Publisher: ZeroRaised (https://zeroraised.com/) - Section: Growth - Tags: marketing, sales, saas, customers **Short answer:** To write a SaaS case study, pick one customer with a clear before and after, ask them for a 30-minute interview, confirm the numbers with them (and with your own product data, if they allow it), then write it in a fixed structure: outcome headline, snapshot, problem, alternatives tried, solution, results, quote and call to action. Get written approval before you publish. You can do all of this with five customers. Most of this guide is our own process and advice. The public examples we link were checked on 7 Nov 2026. We left out buyer-survey statistics because we could not verify a primary source today. ## TL;DR - **Pick for clarity, not fame.** The best first case study is the customer whose problem and result you can explain in one sentence. - **Ask small.** One short email: 30 minutes, you write the draft, they approve it, and saying no is fine. - **Interview, do not survey.** A recorded call with open questions gets the detail and the language a form never will. - **Use real numbers only.** Their estimate, your product data with permission, or no number at all. Never round up. - **Write to a template, publish in three sizes.** A page, an email paragraph and a one-liner for your pricing page. **Disclosure:** ZeroRaised publishes this guide and is a launch site for bootstrapped products. We have no commercial relationship with Stripe or Intercom, whose public case studies we link as format examples. Nothing here is legal advice. ## Case study vs testimonial: why bother A testimonial is a sentence. A case study is the story behind it. If you have not collected short quotes yet, start with our guide on [how to get testimonials and reviews for your SaaS](https://zeroraised.com/blog/how-to-get-testimonials-and-reviews-for-your-saas), which covers asking for and displaying them. A case study answers what a careful buyer asks before paying: is this for someone like me, what did they try before, and what actually changed? Our read: with few customers, one honest, specific story does more than a page of five-star quotes. ## Step 1: Pick the right customer With 3 to 10 customers you do not have many options, which makes this easier. Score each customer quickly against these questions: | Question | Why it matters | |---|---| | Can you state their result in one sentence? | If you cannot, the reader will not either | | Do they look like the buyers you want more of? | A case study attracts people similar to its subject | | Did they switch from something (spreadsheet, rival, agency)? | "Alternatives tried" is, in our view, the most persuasive section | | Have they used the product long enough to see a change? | A week-old account has opinions, not results | | Do they like you, and can they say yes? | Some companies forbid naming vendors; ask early | Pick the customer with the most "yes" answers, not the one with the largest logo. If nobody passes yet, keep collecting testimonials and come back in a month. Our [founder-led sales strategy](https://zeroraised.com/blog/founder-led-sales-strategy) guide covers the conversations that produce good candidates. ## Step 2: Send the ask (email template) Keep the request short, specific and easy to decline. Send it from your own address, not a no-reply tool. > **Subject:** Could I write up how you use [Product]? > > Hi [Name], > > You have been using [Product] for [time period] and you mentioned [specific thing they said or did, e.g. "you no longer chase invoices by hand"]. I would love to write a short customer story about that. > > What it involves: > - A 30-minute call at a time that suits you (I will record it only if you are happy with that) > - I write the draft, you review it, and nothing goes live until you approve it > - You choose whether to use your name, your company name and your logo, or keep it anonymous > > As a thank you, [optional: a link back to your site / a free month / early access to X]. > > If it is not a good time, or your company does not allow this, no problem at all, and it changes nothing about your account. > > Thanks, > [Your name] The specific detail shows you are not mass-mailing, the approval promise removes the main fear, and the explicit "no problem" lets busy people decline without awkwardness. ## Step 3: Run a 30-minute interview Record the call (with permission) and transcribe it so you can quote exactly. Ask, then stay quiet. **Warm-up (3 minutes)** 1. What does your company do, and what is your role? 2. How big is the team that uses [Product]? **Before (8 minutes)** 3. Before [Product], how did you handle [the job]? 4. What was frustrating about that? Can you give me a specific example? 5. What did it cost you, in time, money, errors or stress? 6. What made you start looking for something better at that moment? **Alternatives (5 minutes)** 7. What else did you try or consider? 8. Why did those not work for you? 9. Why did you pick [Product] in the end? Was anything holding you back? **After (9 minutes)** 10. Walk me through how you use [Product] now, step by step. 11. What changed after you started? What is easier, faster or no longer a problem? 12. How do you know? Is there a number you track, even a rough one? 13. Was there a moment you realised it was working? 14. What still is not perfect? (This keeps the story honest and often gives you a roadmap item.) **Wrap-up (5 minutes)** 15. If a friend in your role asked whether to use [Product], what would you tell them? 16. Is there anything I did not ask that you think matters? 17. Is it OK if I follow up with one or two questions while writing? Question 15 usually produces your pull quote; question 12, your numbers. ## Step 4: Get real before and after numbers You have three honest sources of numbers. 1. **The customer's own figures.** "We used to spend about a day each month on reconciliation, now it takes an hour." Quote it as their estimate, in their words. 2. **Your product analytics, with permission.** You can often see what the customer cannot easily measure, such as projects created or how usage grew since signup. Publish none of it without asking: list the exact figures and date range in a follow-up email and let them remove anything. Check this fits your privacy policy and any data processing agreement with them. 3. **No number.** A clear qualitative change ("we stopped losing leads between the form and the CRM") is better than a made-up percentage. Our rule: give every number a time period, use the customer's baseline, and never turn "about half the time" into "52% faster". ## Step 5: Consent and approval Use a written checklist (general advice, not legal advice): - [ ] They agreed to the interview and, separately, to the recording. - [ ] They chose how they are named: full name and company, first name and role only, or anonymous ("a five-person design agency"). - [ ] They approved the use of their logo, if you want one. Some companies have brand rules, so ask. - [ ] They saw and approved the final text, every quote and every number, in writing (an email reply is fine). - [ ] They know where it will appear: website, emails, social posts, launch pages. - [ ] They know they can ask you to take it down later, and you will. Send the draft with quotes and numbers highlighted so they can check them quickly. ## Step 6: Write it with this fill-in structure Copy this skeleton and fill in the brackets. **Headline with the outcome.** "[Customer] [achieved result] with [Product]". Lead with the change, not with your product name. **Snapshot box.** Customer, industry, team size, previously used, features used, key result in one line. **The problem.** Two or three paragraphs on how things worked before and why it hurt, using a specific example from the interview. **Alternatives tried.** What they tried first and why it fell short. Be fair to competitors; just state what did not fit. **The solution.** How they set up and use your product now, in concrete steps. Mention any friction in switching honestly. **Results.** The before and after, with time periods. Use the customer's numbers, your approved data, or a clear qualitative change. **Quote.** One strong pull quote, in their exact words, with name and role (or anonymised description). **CTA.** One next step for a reader in the same situation: start a trial, book a call, or read a related guide. Public examples follow the same shape. Stripe's [Easy Bathrooms story](https://stripe.com/gb/customers/easy-bathrooms) opens with an outcome headline and a row of stat blocks, then runs Challenge, Solution and Results sections, with a named customer quote. Intercom's [Birdie Care story](https://www.intercom.com/customers/birdie-care) uses an "At a glance" snapshot, then challenge, solution and "Key results" sections. You do not need their design budget, only their structure. ## Step 7: Choose the format and length | Format | Length (our suggestion) | Best for | Effort | |---|---|---|---| | Web page | 600 to 1,200 words | SEO, linking from sales emails and pricing page | Low | | One-page PDF | About 300 words plus snapshot | Buyers who forward to a manager | Low, once the page exists | | Short video | 1 to 3 minutes | Social posts, launch pages | Higher: needs a willing, camera-comfortable customer | | Email paragraph | 50 to 100 words | Sales follow-ups, onboarding | Very low | | Pricing page one-liner | One sentence plus name | Reducing doubt at the moment of purchase | Very low | Start with the web page. Everything else is a cut-down version of it. ## Step 8: Use it everywhere Put it where people hesitate: - **Pricing page.** One line and a link next to the plan the customer uses, close to the buy button where doubt peaks. - **Sales and follow-up emails.** Paste the 50 to 100 word version when a prospect matches the customer's profile. - **Launch posts.** A real customer story beats a feature list. Our [free marketing channels for bootstrapped makers](https://zeroraised.com/blog/free-marketing-channels-for-bootstrapped-makers) guide lists places to share it. - **Onboarding and social.** Show new users how someone like them got value, and turn the quote and the before and after into a couple of posts. ## Worked example outline (illustrative only) The example below is **fictional**, invented to show the structure. It contains no real data; brackets show where real, approved figures would go. **Product:** "Tally Desk", an imaginary invoicing tool for small agencies. **Customer:** "North Lane Studio", an imaginary four-person design agency. **Headline:** "How North Lane Studio stopped chasing late invoices by hand" **Snapshot:** - Customer: North Lane Studio (fictional), design agency, 4 people - Previously used: a spreadsheet plus manual email reminders - Uses: automated reminders, client portal - Key result: [customer-approved result, e.g. their own estimate of hours saved per month] **Problem:** Invoices lived in a spreadsheet and reminders went out when someone remembered. [Specific example from the interview.] **Alternatives tried:** A general accounting tool (too complex for a four-person team) and a calendar reminder system (easy to ignore). **Solution:** Imported open invoices, set reminder rules per client, turned on the client portal. Note honestly: setup took longer than expected because of [detail from interview]. **Results:** [Customer's own before and after, with time period.] [Any product data the customer approved, with date range.] If neither exists, a qualitative change: "The founder no longer keeps a list of who owes what." **Quote:** [Exact words from interview question 15, approved by the customer.] **CTA:** "Running a small agency? Start a free trial and import your open invoices in [time]." In the real version, every bracket gets filled with something the customer said or approved, or the line comes out. ## Frequently asked questions ### Can I write a case study with only a few customers? Yes. With 3 to 10 customers you are looking for one with a specific, believable change, such as hours saved, a tool replaced or a process that now works. Small numbers told honestly are more persuasive than big claims nobody can check. If no customer has results yet, wait a few weeks and collect testimonials in the meantime. ### How long should a SaaS case study be? Our suggestion is 600 to 1,200 words for a web page, plus a 50 to 100 word summary you can paste into emails and a one-line version for your pricing page. Long enough to show the problem and the change, short enough to read in a few minutes. ### Do I need the customer's permission to publish a case study? Yes. Get written approval of the final text, the quote, any numbers, and the use of their name and logo. If you want to include figures from your own product analytics about their account, ask first and show them exactly what will be published. This is general advice, not legal advice. ### What questions should I ask in a case study interview? Ask about life before your product, what they tried first, why they chose you, what changed after, how they measure that change, and what they would tell a peer. Ask for specifics and examples, then let them talk. The full 30-minute script is in this guide. ### What is the difference between a case study and a testimonial? A testimonial is a short quote. A case study is a full story: who the customer is, the problem, what they tried, how they use your product and what changed, with a quote inside it. Testimonials are quick to collect; a case study takes an interview and an approval round but answers far more buyer questions. ## Put your story in front of buyers ZeroRaised is a launch directory for products built without institutional VC. Once you have a customer story worth telling, [submit your product](https://zeroraised.com/submit) for free and link the case study from your listing. For more practical growth guides for bootstrapped founders, [join the ZeroRaised newsletter](https://zeroraised.com/newsletter). ## Sources - [Stripe customer stories](https://stripe.com/customers), last checked 7 Nov 2026 - [Stripe: Easy Bathrooms customer story](https://stripe.com/gb/customers/easy-bathrooms), last checked 7 Nov 2026 - [Intercom customer stories](https://www.intercom.com/customers), last checked 7 Nov 2026 - [Intercom: Birdie Care customer story](https://www.intercom.com/customers/birdie-care), last checked 7 Nov 2026 ## Frequently asked questions ### Can I write a case study with only a few customers? Yes. With 3 to 10 customers you are looking for one with a specific, believable change, such as hours saved, a tool replaced or a process that now works. Small numbers told honestly are more persuasive than big claims nobody can check. If no customer has results yet, wait a few weeks and collect testimonials in the meantime. ### How long should a SaaS case study be? Our suggestion is 600 to 1,200 words for a web page, plus a 50 to 100 word summary you can paste into emails and a one-line version for your pricing page. Long enough to show the problem and the change, short enough to read in a few minutes. ### Do I need the customer's permission to publish a case study? Yes. Get written approval of the final text, the quote, any numbers, and the use of their name and logo. If you want to include figures from your own product analytics about their account, ask first and show them exactly what will be published. This is general advice, not legal advice. ### What questions should I ask in a case study interview? Ask about life before your product, what they tried first, why they chose you, what changed after, how they measure that change, and what they would tell a peer. Ask for specifics and examples, then let them talk. The full 30-minute script is in this guide. ### What is the difference between a case study and a testimonial? A testimonial is a short quote. A case study is a full story: who the customer is, the problem, what they tried, how they use your product and what changed, with a quote inside it. Testimonials are quick to collect; a case study takes an interview and an approval round but answers far more buyer questions.