The Product Readiness Gap
Why companies need more than product-market fit before scaling development.
Product-market fit matters because it gives a company evidence that a product is solving a meaningful problem for a market. Customers are using it, there are signs of demand, and the business has begun to understand where value is being created.
But product-market fit mainly tells us something about what has worked to get the company here. It does not automatically answer what the company should invest in next.
A company can have real customers, genuine traction and clear evidence of market need, and still carry significant uncertainty about:
- what to build next
- which problem deserves priority
- which part of the workflow should change
- whether a proposed solution will actually improve the experience
- whether customers will adopt it
- whether the next investment is sufficiently supported by evidence
Growth introduces new assumptions
The evidence that supported one product decision does not automatically support the next.
As a product develops, new decisions introduce new uncertainties: a new feature, a different market, a redesign, an AI capability, a change to an important workflow or a larger investment in the next version of the product.
Existing evidence remains valuable. Customer behaviour, product data, previous research, commercial performance and what a team has learned from operating the product should all inform what happens next. But some of the assumptions behind the next investment will be new.
This is becoming particularly interesting as AI changes the speed at which product ideas can be explored and expressed. Teams can move from an idea to something that looks and feels credible remarkably quickly. Concepts can be generated, prototypes produced and possible directions explored with much less effort than before.
That is a genuine advantage. But the speed at which an idea can be expressed does not remove the need to establish whether the assumptions behind it are true.
As investment grows, those decisions may also need to stand up beyond the immediate product team. Founders, boards, investors and other stakeholders may reasonably ask why one opportunity deserves priority over another, what evidence supports it, and what remains uncertain.
The gap
The Product Readiness gap sits in the space between two sentences.
Somewhere between belief and build sits a useful question:
What evidence actually supports this particular investment?
Belief is not the problem. Companies need conviction to make decisions, and momentum matters. The gap appears when assumptions begin to be treated as established facts, or when confidence in an idea becomes the main justification for investing in it.
Closing that gap does not necessarily require a lengthy research programme. It starts by being clear about which assumptions the investment depends on, what evidence already exists, and where the remaining uncertainty could materially affect the decision.
Sometimes the existing evidence will be enough. Sometimes it will reveal something important that still needs to be investigated with customers, users or within the real context in which the product has to work.
The point is to understand that before committing further time, money and development capacity rather than discovering it afterwards.
Four questions
A Product Readiness conversation can begin with four fairly simple questions.
What has genuinely been established through existing research, observed behaviour, product data, tested propositions, customer feedback or commercial signals?
And where are we still relying primarily on judgement or belief?
Every product plan contains assumptions. That is normal.
The important question is which assumptions the proposed investment actually depends on, particularly where the consequences of being wrong could materially change the decision.
Not every uncertainty needs a research project.
Which of the things we do not yet know could materially change the decision if they turned out to be different from what we currently believe?
Those are usually the uncertainties worth prioritising.
The outcome does not always have to be build or don’t build.
The evidence might support proceeding with the proposed investment. It might suggest refining part of the proposition first. It might point towards a different approach. Or it may show that an important uncertainty needs to be resolved before making a larger commitment.
In Product Readiness terms, those outcomes are:
The important part is that the recommendation follows from what has been learned rather than being decided in advance.
Not a gate
Product Readiness is not intended to create another approval process between a team and its ability to build.
Nor does every decision require the same depth of investigation.
The amount and strength of evidence needed should be proportionate to the uncertainty, the consequences of being wrong and the investment being considered. A small, easily reversible product decision is different from committing significant budget and development capacity to a new proposition, market or capability.
The purpose is not to build less.
It is to make clearer decisions about where to invest next, what evidence supports that decision, and what remains genuinely uncertain.