Glossary
What Is Problem-Solution Fit?
Updated · Team Fonda
Short answer
Problem-solution fit is the point where you have evidence that a specific group of people has a real, painful problem and that your proposed solution is something they want. You reach it before you build the full product, mostly by talking to customers and testing whether they will commit time or money.
Key takeaways
- It answers two questions: is the problem real, and do people want this way of solving it?
- The evidence comes from customer conversations and small commitments, not from opinions or compliments.
- It comes before product-market fit. You can reach it with no product at all.
- If you cannot find it, change the problem, the customer or the solution before you spend money building.
What problem-solution fit means in plain words
Many new businesses start with a solution: an app, a service, a product. Problem-solution fit turns that around. You first prove that a clear group of people has a problem they care about, and then that the thing you plan to offer is a solution they would choose over what they do today.
It is the first of two milestones. The second is product-market fit, which asks whether a real product keeps enough customers coming back to build a business. Problem-solution fit is cheaper to test because it needs conversations and simple mock-ups, not finished software or stock.
How to tell if you have it
There is no formula. You judge it from evidence gathered during customer discovery. Look for these signs, in rising order of strength:
- People describe the problem without being led. In a customer interview they bring it up themselves and can tell you the last time it happened.
- They already spend something on it. Money, hours or a clumsy workaround such as a spreadsheet. A problem nobody is trying to solve is usually not painful enough.
- Your solution makes sense to them quickly. After a short description or a prototype, they can say back what it does and why it beats their workaround.
- They commit. A pre-order, a deposit, a signed letter of intent, a place on a waitlist with a real email, or an introduction to a colleague with the same problem.
A simple test
Compliments are not evidence. Count only what people did in the past and what they are willing to give up now: time, money or reputation.
A worked example
This is an illustration, not data. Say you want to build a tool for private music teachers that offers a cancelled lesson slot to other students and bills for late cancellations. You interview 15 teachers.
| What you checked | Result | What it tells you |
|---|---|---|
| Raised last-minute cancellations as a problem unprompted | 11 of 15 | The problem is real for this group |
| Already use a workaround (a written cancellation policy, a group chat to fill slots) | 8 of 15 | It hurts enough to act on |
| Understood your solution from a one-page mock-up | 9 of 15 | The solution is clear |
| Paid a $20 deposit for early access | 5 of 15 | Some will pay before it exists |
Example numbers only. There is no universal pass mark.
Five deposits from fifteen conversations is a strong early signal for a small paid tool. If the same interviews had produced eleven people who agreed it was annoying and nobody willing to pay, you would have a real problem without a solution people want, and the right move would be to rethink the solution or the customer.
Why it matters for a first-time founder
You meet this term right after you pick an idea and before you plan or build. Being wrong costs less here than at any later point. Changing your mind after ten conversations costs a few evenings. Changing it after six months of building costs your savings.
Once you have it, the next steps become clearer: you know who to build for, which features matter for the MVP and what to write in a business plan. Fonda's Validate phase follows this order. You look at the market and the key risks, talk to real customers, and then get a Verdict of go, refine or pivot with reasons. If you want a quick outside view first, the free roast my idea tool points out the weak spots in an idea.
Common mistakes
- Asking friends and family. They want to be kind. Talk to strangers who match your target customer.
- Pitching instead of listening. If you describe your idea first, people react to the idea. Ask about their problem first.
- Treating "I would use that" as proof. Future promises are cheap. Ask what they did last time the problem came up.
- Defining the customer too widely. "Small businesses" is not a group you can interview. "Private music teachers with more than twenty weekly students" is.
- Stopping at the problem. A real problem with a solution nobody wants is only half of the fit.
Frequently asked questions
What is the difference between problem-solution fit and product-market fit?
Problem-solution fit shows that people have the problem and want your proposed solution, usually before the product exists. Product-market fit shows that a real product is being bought, used and kept by enough customers to grow a business. The first is tested with interviews and mock-ups, the second with usage and revenue.
How many customer interviews do I need to reach problem-solution fit?
There is no set number. Keep going until the answers start to repeat and you can predict what the next person will say. A well-defined customer group shows patterns sooner than a mixed one, so narrow the group if the answers stay scattered.
Can I reach problem-solution fit without building anything?
Yes. A sketch, a landing page, a slide or a manual version of the service is enough to test whether people want the solution. Building comes after, once you know what is worth building.
What should I do if I cannot find problem-solution fit?
Change one thing at a time. Try a narrower customer group, a different problem the same people mentioned, or a different solution to the same problem. If several rounds still produce no commitment, it is usually cheaper to move to another idea.