A No-Hype Take on Problem Interviews (AI SaaS)
Most posts about AI SaaS problem interviews oversell them. Thirty minutes of conversation will not reveal product-market fit. Here is the honest version.
What They Actually Do
Give you grounded vocabulary, recurring trust-boundary patterns, and disconfirmations of assumptions you walked in with. That is most of the value. They deliver warranted confidence at best, not certainty.
What They Do Not Do
They do not validate that someone will pay for AI. People who say they will adopt AI tools routinely do not. They do not predict whether your model will produce trusted output - that is a product execution question. They do not eliminate the build.
The Realistic Best Case
Run ten to fifteen interviews. Learn the trust boundary. Roadmap is narrower than it was. The product you ship is more likely to land than the one you would have shipped without the calls. Better odds, not certainty.
The Realistic Worst Case
Run ten interviews. Patterns are noisy because the audience filter was wrong. Spend two weeks rerunning against a tighter filter. The build is now a month later than originally planned. That month is the cost of doing it right - smaller than the cost of building the wrong thing for three months.
When They Disappoint
The most common disappointment for AI SaaS teams is that the patterns are kind of obvious. The trust boundary the customer described matches your intuition. The vocabulary matches what you would have written.
It usually was not wasted. The shift from intuition to twelve specific quotes is sturdier than gut feel. It also surfaces the one or two things you did not intuit - usually the most valuable findings of the round.
Where the Hype Is Wrong
Problem interviews do not unlock product-market fit. They do not replace gut judgment. They do not solve the model selection problem. They do not validate AI capability. They narrow your error bars on the customer-side variables. They do nothing for the others.
An AI SaaS team with great interview practice can still pick the wrong moment, the wrong model, or the wrong distribution and lose.
The Honest Recommendation
Run them anyway. They materially raise your odds, they cost less than skipping them, and they produce skills that compound across the rest of your career building AI products. Do not expect magic. Do expect to know more about your customer than you did.