Find opportunity, spotted.
Also called: Problem spotting · Opportunity framing · Gap analysis · Pain discovery
Spotting a real, frequent, painful problem that people would pay to solve, and framing it as an opportunity before you commit to any idea.
Start with a problem worth solving, not a product you fancy building. A good opportunity is real, frequent, painful, and addressable. Qualify it on those four tests first. Solution-first thinking is the most common way a project wastes a year before anyone asks whether the problem was real.
What finding an opportunity is
An opportunity is a problem worth solving, not a product worth building. The two get confused constantly. “A heated proofing box” is a product. “Serious home bakers keep binning overnight proves because their kitchens are too cold” is an opportunity. The first is a guess at a solution; the second is the gap that might justify one. Find the gap first, and the product becomes a question you can answer rather than a bet you have already placed.
The discipline here is to stay on the problem long enough to qualify it. Most founders skip straight to the thing they want to make, then spend months engineering a solution to a problem they never checked was real. Finding the opportunity is the cheapest stage in the whole framework and the one that decides whether the other nine are worth running at all.
The four tests of a real opportunity
- Real. The problem exists outside your own head. You can point to people who have it, not a hunch that they might.
- Frequent. It happens often enough to register as a pain, not once a year. A problem people meet weekly is worth more than one they meet once.
- Painful. Solving it is worth money, time, or relief. A mild annoyance is not an opportunity; people tolerate those for free.
- Addressable. You can actually reach the people who have it, and a product could plausibly fix it within your means.
Qualifying the proofing-box opportunity
Before there was a box, a price, or a single line of CAD, there was a problem being watched. Here is the opportunity scan that ran on it, so you can see what a qualified opportunity looks like rather than a generic template.
Notice the scan never names a solution. It pins a problem and tests it from four angles. Only when all four came back yes did it earn the right to become an idea. Three yeses and a no would have sent us back to watching, not building.
How it fits the bigger picture
Find Opportunity is activity 01.01 in the framework, the very first thing you do, before any idea exists. It feeds straight into the idea statement (01.02), where the qualified opportunity gets written up as a single, testable sentence. Get the opportunity wrong here and every later stage inherits the mistake, because the whole framework is built on the assumption that the problem underneath it is real.
What it can do
It tells you whether there is a problem worth the next nine stages of work. A qualified opportunity gives you a reason to build that survives the first hard question from a sceptical friend, an investor, or your own doubts at month six. It anchors everything that follows to a real pain rather than a personal preference.
What it can’t do
It can’t tell you what to build, or whether your eventual solution will work. That is the job of the idea statement, the Discover research, and Stage 04 Evaluate. Finding the opportunity only proves the problem is worth solving; it stays silent on how. Treat a qualified opportunity as permission to start, not as a finished plan.
See the full 10-stage process →
Try it yourself
Write down a problem you keep noticing, in one plain sentence, with no solution attached. Then run it through the four tests: is it real, frequent, painful, addressable? Be honest about which ones you are guessing at. If you can’t point to real people who have the problem, your next job is to go and find them, not to start designing. The strong opportunities pass all four; the weak ones quietly fail one and hope you don’t check.
Want a structured first pass? Start the Free Sprint → and the GPT will help you frame and qualify the opportunity before you commit to an idea.
Your opportunity checklist
Project notes: watching before building
▸ From the notebook · optional reading
How Dan and Anna Hartley spotted the proofing-box opportunity in a cold Stockport kitchen, and resisted naming a product for a fortnight.
3 min read · click to open
It started with a binned loaf. Anna had left a sourdough to prove overnight on the worktop in their Stockport kitchen, and by morning it had barely moved. The kitchen had dropped to 15°C. She binned it, swore, and started again. The third time it happened in a month, Dan said the thing every founder says: “Someone should make something for this.”
We almost named a product on day one
The temptation was to sketch a heated box that afternoon. I asked them to hold off. “Before you draw anything, prove the problem is bigger than your own kitchen.” The risk at this stage is solution-first thinking: you fall in love with the gadget and stop checking whether the pain is real for anyone else.
What we did instead
We spent a fortnight watching, not designing. Anna read the Sourdough School forums and counted the “my overnight prove failed” posts: dozens, every cold week, all with the same flat-loaf photos. We worked through the common workarounds people described, the oven light left on, the airing cupboard, a hot water bottle wrapped in a towel, and every one was fiddly or unreliable. That told us the pain was real, frequent, and painful enough that bakers kept trying daft fixes.
The addressable test was the easy one. The audience sat in one place, the Sourdough School community, reachable direct, and a steady-temperature box was well within what a small Stockport team could build with a Stoke-on-Trent ceramic shell and a Manchester PCB.
What the fortnight bought us
- Cost. Two weeks of reading and counting. No CAD, no spend.
- Saved. The confidence to commit. When we finally wrote the idea statement, it rested on a qualified problem rather than Dan’s hunch, and not one later stage had to revisit whether the opportunity was real.
The loaf in the bin was the cheapest market research they ever did. Naming the product a fortnight late was the best discipline they ever kept.
— Idea stage, project notes, 2026
— Next in Idea → Write idea statement