Validation & Discovery
Problem-Solution Fit
Problem-Solution Fit is the point where you have confirmed that a real, painful problem exists for a specific group of people and that your proposed solution actually relieves it for them. It comes before Product-Market Fit and is validated through customer conversations and small tests, not by shipping a polished product.
Also known as: problem solution fit, PSF, problem/solution fit
Why it matters
Most failed startups build something nobody wanted, and the cause is skipping Problem-Solution Fit. It is the cheapest checkpoint you have: a few weeks of interviews and a smoke test cost almost nothing compared to months of engineering toward a guess. Reaching it tells you the problem is worth solving and that your angle on it resonates, which is the green light to actually build an MVP. If you cannot get there, no amount of features, design polish, or paid ads will save the idea, and the honest move is to pivot the problem or the segment. The trap is that Problem-Solution Fit feels soft and unquantified, so founders rationalize their way past it and start coding. Treat it as a build-or-kill gate: clear evidence of pain plus credible evidence your solution removes that pain, or you do not proceed.
Worked example
A founder thinks small law firms waste hours on intake paperwork. She runs 15 Mom Test interviews and finds 11 firms describe the same pain and 7 already pay an assistant or clunky tool to handle it. She mocks up a one-page intake flow, shows it to those 7, and 5 say they would switch and 3 pre-pay a $50 deposit for early access. That mix of consistent pain plus paid intent signals Problem-Solution Fit, so she builds the MVP.
Common mistakes
- Confirming the problem but never testing whether your specific solution removes it. Validated pain with an unwanted fix is not Problem-Solution Fit.
- Treating polite enthusiasm as evidence. 'That sounds useful' is worthless; look for behavior like switching, pre-orders, or time and money already spent on the problem.
- Confusing it with Product-Market Fit. Problem-Solution Fit is qualitative and pre-build; Product-Market Fit shows up later as retention, organic pull, and a repeatable growth loop.
Frequently asked questions
What is a good signal of Problem-Solution Fit?
The strongest signals are behavioral, not verbal. Look for people who already hack together a workaround, pay for an inferior tool, or commit something real like a pre-order, a deposit, or a calendar slot to switch. When several prospects in the same segment describe the same pain in their own words and react to your solution by trying to act, you have it.
Problem-Solution Fit vs Product-Market Fit, what is the difference?
Problem-Solution Fit comes first and is mostly qualitative: you have proven a painful problem exists and that your proposed solution credibly relieves it, usually through interviews and small tests before building. Product-Market Fit comes after launch and is measured by retention, organic growth, and demand you struggle to keep up with. You can have Problem-Solution Fit and still miss Product-Market Fit if the market is too small or your delivery is wrong.
How do you validate Problem-Solution Fit without building the product?
Run 10 to 20 customer discovery interviews focused on past behavior, not opinions, then test demand with a low-cost artifact like a smoke test landing page, a fake-door button, or a concierge MVP you run by hand. Watch for sign-ups, pre-payments, or willingness to do real work to get access. None of these require a finished product, and they fail cheap if the idea is wrong.
How many customer interviews do I need to reach Problem-Solution Fit?
There is no magic number, but most founders start seeing clear patterns around 10 to 20 interviews within one tight segment. If the same pain and language keep repeating and you are not learning anything new, you have likely saturated that segment. If answers are all over the place after 20, your target customer is probably too broad or the problem is not acute enough.
Can you have Problem-Solution Fit and still fail?
Yes. Problem-Solution Fit only proves the problem is real and your solution fits it for a few people. You can still fail if the market is too small to be a business, the cost to acquire customers exceeds their value, or you cannot deliver the solution profitably. It is a necessary gate, not a guarantee, which is why unit economics and market size matter next.
Is Problem-Solution Fit the same as a painkiller versus vitamin test?
They overlap but are not identical. The painkiller-versus-vitamin lens asks whether the problem is acute enough that people will pay to make it stop, which is the problem half of the equation. Problem-Solution Fit adds the second half: that your specific solution actually relieves that pain for them. A painkiller-level problem with the wrong cure still fails the fit test.
Related terms
More in Validation & Discovery
Stop reading definitions. Pressure-test your idea.
Knowing the terms is the easy part. Olune runs your actual idea against live Reddit signals, competitor data, and real search demand, then gives you an honest GO / NO-GO verdict in about eight minutes. Free, no card.
Last updated 2026-06-09 · Back to the glossary