SaaS Customer Discovery & Problem Validation for AI Startups

Stop Building Features. Start Collecting Receipts.

Last year I spent six months building a SaaS product with polished UI, solid architecture, and clean code. I launched it to 12 signups. Zero paying users. I shut it down shortly after.

The postmortem was brutal but clear: I built something nobody needed. I fell in love with the solution before verifying the problem existed. Most founder advice says to talk to users, validate your idea, and get feedback. But feedback is cheap. People will tell you your idea is great, that they'd totally use it, that they'd pay for it, and then they won't.

The gap between what people say and what people do is where startups die. I needed a filter that separated enthusiasm from commitment. Here is the filter I am using now. It is not finished, but it is already better than anything I had before.

The Receipt Question: When Did It Last Hurt?

Instead of asking "Would you want this automated?", I ask: "Walk me through the last time this actually hurt you."

This is not about usefulness. It is about a specific cost. A specific moment. A specific workaround they used instead of your future product. If they cannot anchor it to a specific incident, the signal is weak no matter how enthusiastic the answer sounds.

The Cost Question: What Stays Broken?

"What stays broken if this never gets fixed?"

This separates complaints from costs. A recurring annoyance is a complaint. A recurring annoyance with a broken process and a willingness to change is a wedge. One is noise. The other is a market.

The Switch Question: Would You Switch Tomorrow?

"Would you switch tomorrow?" But with one caveat: the answer only counts if it attaches to a dated incident.

"When this broke last month, I spent two hours on it" counts.

"Yes, I would probably switch" does not.

If the switch answer cannot attach to a specific memory, it is still a wish describing itself as a decision.

Pass or Fail is Not Enough

Twenty conversations where five produce dated incidents and fifteen produce adjectives is a different market than the reverse. The filter gets sharper when you track two things:

• Did one vivid story appear? (pass/fail)
• How often does the same kind of costly incident repeat? (the ratio)

A founder with one dramatic anecdote and a shrug on frequency is a different signal from a boring incident that happens every week. Both count as receipts. Only one of them is a market.

One Story is a Blog Post. Repetition is a Business.

"How many times this month?"

This is the whole filter. One dramatic story is a blog post. The same boring incident every week is a business. You do not just need the story. You need the calendar.

"When did it last hurt?" gets the receipt. "How many times this month?" tells you if it is a market or an anecdote.

The Outside Check: Public Postmortems

There is an outside check that helps too. Looking at public postmortems of stalled products reveals the same split over and over. The ones that moved had a current cost someone was already paying, whether that was a workaround, a bad process, or time wasted every week. The ones that stalled had enthusiasm but no calendar. No recurring cost. No real wedge.

How This Changes Your SaaS Validation Process

If you are doing Customer Discovery the old way, stop. Asking "Would you use this?" or "What features do you want?" is Product-Market Fit cosplay. Real validation comes from finding people who are already paying a cost for a broken process.

Your SaaS idea is not validated until you can name the person, the specific incident, the frequency, and the workaround they currently use instead of your solution. Until then, you are not building a business. You are building a portfolio piece.

Use the Right Tools for the Right Stage

At the discovery stage, tools like Craigslist, Reddit, and Facebook Groups are goldmines for finding people who are actively complaining about problems. You are not looking for users. You are looking for victims of the exact problem you think you are solving.

Once you have receipts from 10 to 15 conversations, move to tools like Fiverr or Upwork to test if people will pay for a manual version of your solution. This is the bridge between enthusiasm and commitment. If they will not pay you $50 on Fiverr, they will not pay you $50 per month for SaaS.

Only after manual validation should you think about building. Use Gumroad to sell access to a landing page or waitlist. If people do not convert there, do not build the product. Find a better problem first.

The Calendar Test

Every SaaS founder should run their idea through the calendar test:

• Can you name the last specific time this problem hurt someone?
• Can you attach a date to that incident?
• Can you quantify how many times per month it repeats?

If you cannot answer all three, you are not ready for Product-Market Fit. You are still in the ideation phase. Go back to Customer Discovery.

Entrepreneurship is not about building what you think is cool. It is about finding a pain so consistent and so costly that people will pay to make it stop. The best SaaS products are not born from "Wouldn't this be useful?" They are born from "This happens every damn week and I am tired of it."

Build your product only after someone tells you the story of how your solution would have saved them time, money, or stress on a specific Tuesday in March. Until then, keep collecting receipts.