How to Write a SaaS Case Study When You Only Have Two Customers

Most founders know a case study would help them sell. A real customer story, a concrete result, a before and after. It is the kind of content that does work in sales conversations, on the homepage, and in cold outreach.

But they wait. They tell themselves they need more customers first. Ten at least. Maybe twenty. Something that feels like enough to be worth writing about.

So they wait. And while they wait, they keep selling without proof. And selling without proof is harder than it needs to be.

Here is the thing: you do not need ten customers to write a case study. You need one good story.

Why Waiting Is Costing You More Than You Think

Every week you spend selling without a case study is a week where the person you are talking to has to take your word for it.

You are asking them to trust that your product does what you say it does, that it works for someone like them, and that the outcome you are promising is real. That is a lot to ask from a stranger.

A case study does not do the selling for you. But it changes the dynamic of the conversation. Instead of "we believe this will work for you," you get to say "here is what happened when someone in your exact situation used it." That is a completely different kind of credibility.

Even one case study, from one real customer, with one honest result, moves conversations forward faster than any amount of polished positioning copy.

What a Case Study Actually Needs to Do

A case study has one job: help a potential customer see themselves in someone else's experience.

That is it. It does not need to be long. It does not need professional photography or a PDF download. It does not need to show a dramatic percentage improvement with a perfect before and after chart.

It needs to describe a specific person in a specific situation, what they were struggling with before they found your product, what changed when they started using it, and what things look like now.

If a potential customer reads that and thinks "that sounds like me," the case study worked.

How to Get the Story Out of One Customer

The hardest part for most founders is not writing the case study. It is getting the information they need from the customer to write it well.

The right way to do this is a short conversation, not a form, not an email survey. A twenty minute call where you ask five specific questions.

What were you trying to solve when you first came across us? What had you tried before and why did those things not work? What made you decide to try our product? What specifically changed after you started using it? And what would you say to someone in the same situation who is thinking about trying it?

Those five questions give you everything. The before. The decision moment. The after. And a closing quote you can use almost word for word.

Record the call. Transcribe it. The best lines in your case study will come directly from what the customer said, in their own words, not from how you would describe the outcome yourself.

The Structure That Makes a Short Case Study Work

A case study that is four hundred words and well structured will outperform one that is two thousand words and unfocused.

Here is the structure that works for early-stage SaaS:

Start with one sentence describing who this customer is. Their role, their company type, their situation. Make it specific enough that a similar reader immediately recognises someone like them.

Then describe the problem they had before. Not a generic version of the problem. The specific way it showed up in their day-to-day. The more concrete this is, the more real it feels.

Then describe what changed when they started using the product. What did they do differently? What became easier? What stopped being a problem?

Then close with one quote from the customer in their own words. Something that captures the shift in a way they would actually say it.

That is the whole thing. Four sections. Four hundred words. Done.

When Your Customer Does Not Want to Be Named

This comes up more than founders expect, especially in early days when customers are happy to give feedback but do not want their name on a public page.

That is fine. You have options.

You can write the case study with a description of the customer type instead of the company name. "A solo founder running a B2B SaaS with under ten customers" is often more relatable to your ICP than a company name they have never heard of anyway.

You can use initials if the customer is comfortable with that. Or you can ask if they are comfortable with the story being shared privately in sales conversations even if not published publicly.

A case study used in one-on-one outreach does not need to be public to be effective. The question to ask your customer is not "can I publish this?" but "can I share this story with other founders in similar situations?" Most people say yes to the second question even when they hesitate on the first.

Where to Use It Once You Have It

The mistake founders make with case studies is writing them and then posting them in a blog section nobody visits.

Use it everywhere.

Put a one-paragraph version on your homepage in the section just above the pricing. Drop it into cold outreach as a two-sentence version with a link. Share it in conversations when someone asks "has this worked for anyone else?" Use it in your LinkedIn posts as a short before and after story.

The case study is not a content piece. It is a sales asset. Treat it like one.

Some founders use structured research and content planning workflows to map out what proof assets they need and where those assets will get used before they create anything. Tools like Infinall.ai help founders plan that kind of content layer so each piece of proof content gets created with a specific use in mind rather than sitting in a blog archive nobody reads.

What to Create First If Your Customer Gave You One Sentence

Sometimes your customer is happy but does not have much to say. They give you one line: "It saved me a lot of time" or "It made the whole thing easier."

Work with that.

Ask one follow-up question: "What specifically used to take a long time that does not anymore?" or "What was the hardest part before you started using it?"

That one follow-up almost always opens up a real story. People are not naturally analytical about their own experience. They need a prompt to go deeper. Your job is to ask the right prompt, listen carefully, and then write the story that was always there underneath the surface.

FAQ

Can I write a SaaS case study with only one customer?
Yes. One customer with a clear story, a specific before and after, and a direct quote is more than enough to create a useful case study. The goal is not volume. It is specificity. One very specific story will do more work than five vague ones.

What should a B2B SaaS case study include?
Who the customer is and their situation. What problem they had before. What changed when they started using the product. One quote from the customer in their own words. That is the minimum. Length does not matter. Specificity does.

How do I get a customer to agree to a case study?
Ask them informally in a conversation rather than sending a formal request. Frame it as sharing their story to help other founders in similar situations. Most happy customers say yes when the ask feels small and the purpose feels reasonable.

What if my customer wants to stay anonymous in my case study?
Describe them by role and company type instead of name. "A solo founder running a B2B SaaS tool" is often more relatable to your target reader than a company name they do not recognise. You can also ask whether they are comfortable with the story being shared privately in sales conversations even if not published publicly.

How long should a SaaS case study be?
Four hundred to six hundred words is usually enough. Three to four focused sections covering the customer, the problem, the outcome, and a quote. Longer is not better. A tight well-structured story that a potential customer can read in two minutes will get read. A long one usually will not.