.png)
Problem Market Fit - Validating Real, Urgent Pain
Not All Problems Are Created Equal
Now that you have Founder Market Fit, you understand your market and can access the right customers. The next step is to validate whether the problem you believe exists matters and whether it is important enough for someone to pay to solve.
This is where Problem Market Fit comes in, and it is also where many otherwise strong startups lose momentum. A founder can have deep market knowledge and still focus on the wrong problem. The pain may exist, but it may not be urgent. The people experiencing it may not have the budget. Or the person who controls spending may not even recognise the problem as something worth solving.
Problem Market Fit requires two clear validations. First, the problem must be genuinely painful and urgent for a specific persona. Second, that persona must have the authority and budget to invest in a solution.
The Multi-Persona Reality
One of the most common mistakes founders make is assuming that the person who experiences the problem is the same person who pays for the solution. In reality, these are often completely different stakeholders.
In enterprise environments, multiple personas are typically involved in a single buying decision:
1. The End User
This is the person who deals with the problem every day. They feel the pain most directly and may strongly want a solution, but they usually do not control the budget.
2. The Economic Buyer
This is the individual or team responsible for approving spend. They may not use the product themselves or fully understand the day-to-day problem, but without their approval, no purchase moves forward.
3. The Influencer
This is someone who shapes the decision through expertise or internal credibility. They do not have final authority, but their opinion can significantly impact the outcome.
4. The Champion
This is the internal advocate who actively pushes your solution forward. They help navigate internal processes and keep momentum alive. Without a champion, progress often slows or stops entirely.
For Problem Market Fit, the goal is to identify the persona that both feels the problem most acutely and has the authority and budget to act. In most cases, this is not the end user, and recognising that distinction is critical.
The CodeMonk.ai Story: Persona Mismatch
When I was building CodeMonk.ai, I initially focused on engineering leaders as my core user. They immediately saw the value. The product helped them move faster, reduce time spent on hiring, and improve outcomes. The response was positive and the problem felt validated.
But there was a gap. Engineering leaders did not control the budget for recruitment software. That responsibility sat with recruiting managers and talent acquisition leaders.
The problem was not just about who used the product. It was about who decided to pay for it.
And more importantly, the problems themselves were different. Engineering leaders cared about team efficiency, speed, and quality of hires. Recruiters were focused on entirely different challenges such as managing multiple systems, maintaining employer branding, ensuring compliance, optimising cost per hire, and supporting hiring across the entire organisation, not just engineering.
This forced a fundamental shift. The value proposition had to be reframed to align with the priorities of the economic buyer, not just the convenience of the end user.
That was a hard but important lesson. Problem Market Fit is not only about whether a problem exists. It is about whether the person experiencing that problem is the same person who has the authority and budget to solve it.
Validating Problem Market Fit
Here are the specific questions you need to answer:
The Persona Selection Framework
Not all personas deliver equal value, especially in the early stages. You need a clear way to prioritise where to focus first. Use the following framework to evaluate each persona:
1. Pain Level
How strongly does this persona experience the problem?
Score this from 1 to 10 based on urgency and impact on their day-to-day work.
2. Budget Access
Does this persona control the budget or have meaningful influence over spending decisions?
Score this from 1 to 10 based on their ability to approve or shape purchases.
3. Ease of Access
Can you reach this persona easily through your existing network or credibility?
Score this from 1 to 10 based on how quickly you can engage and get responses.
4. Market Size
How many potential customers exist within this persona group?
Score this from 1 to 10 based on overall reach and scale.
Prioritise personas that score high on pain, budget, and ease of access.
At the early stage, total market size is less important than speed of learning and ability to convert.
Red Flags: When You Don’t Have Problem Market Fit
Watch for these warning signs early, as they often indicate a lack of true Problem Market Fit:
- People acknowledge that the problem exists but rarely raise it on their own. This usually means it is not urgent enough to drive action
- The person experiencing the pain has no budget authority and limited influence over spending decisions. This points to the wrong persona being targeted
- Prospects continue investing time and money into existing workarounds. This suggests the current state is tolerable and not compelling enough to change
- Multiple stakeholders are required to approve a decision, but their priorities are misaligned. This often results in stalled or failed deals
- You are discovering the problem only through customer conversations. This signals a lack of prior market understanding and weak Founder Market Fit
I encountered each of these challenges firsthand while scaling CodeMonk.ai, and they highlighted how critical it is to validate the right problem with the right persona early.
Problem Market Fit for AI-Native Products
AI-native products introduce a unique layer of complexity to Problem Market Fit. In many cases, the problem you are solving did not exist in the same form before, or the capability of AI reshapes how the problem is defined altogether.
For AI-native products, you need to evaluate the problem differently and focus on a few key areas:
- What high-value workflows are still manual and heavily dependent on human effort. These are often the strongest opportunities for AI-driven efficiency
- Which personas are directly responsible for these workflows and carry the cost of inefficiency, typically in the form of time, effort, or expensive talent
- Whether you can clearly quantify the value created by the solution, especially in terms of time saved and how that translates into measurable business impact
- Whether the solution can be easily replicated using existing foundational models, since customers may choose to build internally if the barrier to entry is low
Understanding these factors requires strong domain context and a clear view of how work is currently done. Without that, it is easy to build AI features that look impressive but fail to deliver meaningful value in real-world workflows.
What Comes Next
Once you have validated Problem Market Fit, when you have clearly identified a persona that feels the pain urgently and has the budget to act, you can move to the next stage: Message Market Fit.
In Part 3, we will focus on one of the most challenging aspects of early-stage product development: communicating the problem and solution in a way that genuinely resonates with your target persona. This is where many founders struggle, and mistakes at this stage often lead to months of misalignment, weak traction, and wasted effort.
Key Takeaways
- Not all personas carry equal weight. Focus on the one that combines strong pain, clear budget access, and ease of reach
- The person experiencing the problem is often different from the one making the purchase decision
- Urgency is critical. A problem that exists but can be tolerated rarely leads to action
- Budget authority is essential. Validate the economic buyer, not just the end user
- For AI products, clearly quantify time saved and cost impact. ROI becomes your strongest lever
Have you identified a persona with high pain and real budget? If not, that is the priority before you move forward
