I use a four-type problem framework in almost every early-stage product conversation I have. It's not complicated, but getting it right is one of the highest-leverage diagnostic moves a founder or product leader can make. Because the type of problem you're solving determines how hard it is to sell, how fast you can grow, and whether you should be building at all.
The four types
Active problems — the customer is aware of the problem, it's painful, and they're actively looking for a solution right now. They have urgency. They have budget. They will pay whatever it takes to make it stop. This is the one you want. If you find out early that you're solving an active problem, that's a huge signal to keep going. Don't overthink it — go build.
Passive problems — the customer knows the problem exists, but it's not urgent or costly enough to do anything about. The "cost of doing nothing" feels low. They'll live with it. They might even complain about it — but when it comes time to spend money or change behavior to fix it, they won't. This is a trap. A lot of founders get excited because customers validate the problem in discovery conversations, then wonder why nobody buys. It's because validation and purchasing intent are not the same thing. If your problem is passive, you need to pivot.
Latent problems — the customer doesn't even know they have the problem yet. It exists, it may be costing them real money or quality, but it's not on their radar. These can absolutely be worth building for — but with eyes open. The sales cycle is longer because you have to do two jobs: first educate the prospect that the problem exists and matters, then sell them on your solution. Your job isn't just to close deals; it's to move buyers from unaware to convinced as quickly and cheaply as possible. If you can crack that education loop, you can own a category. If you can't, you'll burn runway trying.
Vision problems — the customer knows they have the problem and already has a clear picture of the solution in their head. They're not looking for help figuring it out — they're shopping for someone to execute their spec. These look like opportunities but usually aren't. You're competing purely on execution and price, there's no strategic moat, and you're at the mercy of whatever the customer thinks the solution should be rather than what would actually work. If you find yourself in this position, it's worth asking hard questions about whether there's a real business here or just a project.
What to do with this information
The point of the framework isn't to categorize problems for its own sake. It's to force an honest conversation early — before you've hired a team, built a product, or committed to a direction.
"Figuring out what problem type you're solving is one of the most important things you can do before you build anything."
If you have an active problem: great, keep going, move fast. The risk here is competition, not demand — so focus on why your solution is meaningfully better, not just whether the problem exists.
If you have a passive problem: stop. Seriously reconsider. Passion for the problem space is not enough. The graveyard of well-built products that solved passive problems is enormous. People do not change their habits or spend real money on things that aren't urgent.
If you have a latent problem: proceed, but build your go-to-market around education first. Your content, your sales conversations, your positioning — all of it needs to start by making the invisible visible. Help your buyer see the problem clearly before you ask them to buy the solution.
If you have a vision problem: be cautious. Ask whether the customer's vision of the solution is actually right. Sometimes it is, and you can execute it well. More often, the customer thinks they know what they need, but the real problem underneath is different — and a product built to their spec will solve the wrong thing.
The hardest part
Most founders find out they have a passive or vision problem after they've already built something. Customer discovery conversations are full of false positives — people are polite, they validate your idea, they say "we'd definitely use that." That's not a committed yes. That's a confirmation yes at best, a counterfeit yes at worst.
The discipline is asking questions that give people a genuine chance to say no — and watching what they actually do, not just what they say. Do they have budget allocated? Are they solving this problem some other way right now? What's the cost if they don't fix it this year?
The answers tell you what type of problem you're actually dealing with. And that tells you almost everything about what to do next.
