No pharmacy in a neighbourhood doesn’t mean the neighbourhood needs one. How to tell an indicator worth testing from demand you can build on.
The most expensive mistake in small projects is treating an early indicator as an established fact. “There is no café in this neighbourhood” may be true, but it does not tell you whether residents want one, or why nobody opened one before you.
What is an early gap?
It is an observation from public data: fewer businesses than expected relative to population, a recurring complaint in reviews, or a service people ask about that nobody offers. An early gap is a hypothesis. Its value is that it directs verification, not that it replaces it.
When does demand become proven?
When someone pays. Pre-orders, real orders from a temporary spot, contracts with first customers, or measured uptake of a trial product. Everything before that is an indicator, however convincing.
Why a gap can be a trap
Sometimes the gap exists for a reason: rent too high for the activity, a regulation that blocks licensing, or a buying habit that sends residents elsewhere. Verifying why the gap exists matters more than verifying that it exists.
We present the gap as a hypothesis and tell you what must hold for it to become demand.
Have an idea built on a gap you noticed? Test it before you commit.
Test my project before I invest