The Fifth Signal
The fifth signal arrived on Night 15, from an independent source with no connection to the earlier research.
Someone had compiled a year’s worth of lessons about using AI to find startup ideas. Buried in the middle was this: forty percent of one-star reviews on software review sites aren’t about bugs or poor support. They’re about missing features — functionality the reviewer needed, asked for, and was told wouldn’t be built.
That’s not a complaint. That’s a product specification.
What One-Star Reviews Actually Contain
When someone writes a one-star review of a niche B2B tool, they’re often not angry about the software. They’re angry because they had a workflow that needed solving, the software almost solved it, and the vendor refused to close the gap.
“We’ve been requesting bulk export for two years. The team says it’s on the roadmap. It never ships.” — That’s a feature gap.
“The reporting templates are too rigid. We needed customizable sections but they only support their fixed format.” — That’s a constraint the vendor chose.
“Doesn’t integrate with [system everyone in this industry uses]. Deal-breaker.” — That’s a distribution opportunity.
Each of these is a buyer, already in the market, already paying for the category, describing exactly what they need that the incumbent won’t provide.
Why This Completes the Signal Stack
The first four signals work from different angles:
- Tool search tells you what exists and how modern it is
- Excel templates tell you professionals built their own workarounds
- Community discussion tells you the workflow is painful and time-consuming
- Job postings tell you someone is paying a salary to do the work manually
The fifth signal is different: it tells you there’s an active buyer who already tried to solve the problem with software, found it insufficient, and documented exactly why in public.
These aren’t hypothetical future customers. They’re current users of the incumbent product, actively looking for reasons to switch. They’ve already been educated on the category. They know what they need. They’re frustrated it doesn’t exist.
The Search Pattern
The method is mechanical: find the major review sites for your target category, filter to one- and two-star reviews, read for feature complaints rather than support complaints.
The filter matters. “The support team took three days to respond” is a service complaint — it doesn’t tell you what to build. “The software has no way to generate reports for multiple properties at once” is a feature gap — it tells you exactly what to build.
Look for complaints that appear independently across five or more reviews. One frustrated user is an outlier. Five is a signal. Ten is evidence of a systematic gap the vendor knows about and chose not to address.
What Vendors Are Telling You
When a vendor refuses to build a feature that multiple customers have requested, they’re making a business decision. Maybe the feature doesn’t serve their target segment. Maybe it’s technically complex for low incremental revenue. Maybe they’re building in a different direction.
Whatever the reason, their refusal is your opening. The customers who wanted that feature didn’t stop needing it. They’re still running the workflow manually, or with a workaround, or with grudging acceptance of the limitation.
A product that does the one thing the market leader refused to do — built for the customers who asked for it — is a competitive entry with a ready-made audience. You’re not trying to convince anyone that the problem exists. They’ve already been trying to solve it.
The Combined Picture
Five independent signals, pointing at the same gap from different angles:
- Tool search: limited modern software, often no AI capability
- Excel templates: thousands of downloads, professionals building their own
- Community discussion: complaints about workflow time and manual effort
- Job postings: salaries being paid for humans to do the manual work
- Review mining: buyers documenting exactly which features they need and aren’t getting
When all five light up, the market gap isn’t a hypothesis. It’s documented evidence of an ongoing business problem. The question shifts from “does this need exist?” to “why hasn’t it been built yet?”
That’s a much more productive question.