How to Tell a Nice-to-Have Problem from a Have-to-Have Problem
The cleanest way I know to sort problems is this: would a customer fire you if you went away?
"Have to have" products sit in the critical path of something important, whether that is revenue, operations, compliance, or customer retention. When they break or disappear, something significant breaks with them.
"Nice to have" products sit at the edge. Useful, appreciated, but the business does not stop if they are gone.
Would a customer fire you if you went away? That is the question that sorts problems worth solving from ones that are merely interesting.
This is not a judgment about quality or value. Plenty of "nice to have" businesses are profitable. But they are harder to sell, have higher churn, and are usually the first budget line cut when things get tight. If you are building a "nice to have," you need to know that going in and price accordingly.
What Real Customer Pain Sounds Like in a Conversation
When you are talking to a potential customer and the problem is genuinely urgent, they do not need much prompting. They interrupt. They bring up examples before you can ask for them. They tell you what they tried that did not work. They want to know your timeline.
When the problem is mild, you feel it in the tempo of the conversation. They are engaged, polite, they think it is interesting. But they are not leaning in. They do not have a specific instance of the problem ready to surface. They will say things like "it would be helpful" or "we have thought about something like that."
"Helpful" and "we have thought about that" are not the language of urgency. When someone has a real problem, they talk about it the way people talk about things that are already costing them something. Listen for that difference.
Why You Should Validate the Pain Before the Solution
Most founders validate their solution. They build a prototype, show it around, and get feedback on the features. What they skip is validating whether the pain is real and frequent enough to drive purchase behavior.
Ask potential customers this: how much time or money does this problem cost you today?
If they cannot answer specifically, if it is "hard to say" or "not that much, honestly," that is the answer. The problem is not hurting enough.
You can have a technically superior product solving a problem that is not urgent enough to create a real business. That is a worse outcome than a mediocre product solving an urgent problem, because at least the second one has customers.
The goal is not to find a perfect product. It is to find one that is painful enough that solving it is worth something to the people who have it. That threshold, more than almost anything else, determines whether you have a business. It is also the foundation of everything covered in Evaluate Your Idea.
