You Don't Need More Ideas. You Need Better Signals.
Most builders spend their time searching for opportunities.
The problem?
Opportunities rarely announce themselves.
They hide inside repeated frustrations.
Yesterday I realized something interesting.
A profile isn't the opportunity.
A comment isn't the opportunity.
A post isn't the opportunity.
But when hundreds of people repeat the same frustration, a pattern appears.
And patterns are where opportunities live.
Most people look at:
followers
likes
engagement
Few people look at:
repeated complaints
repeated questions
repeated confusion
One complaint is noise.
A hundred similar complaints is a signal.
And signals become opportunities.
Stop asking:
"What should I build?"
Start asking:
"What frustration refuses to disappear?"
That's usually where the opportunity is hiding.
Agree — and I'd add that the most reliable signal source is often your own repeated frustration, not other people's. Every product I've built started as something that annoyed me enough times that I'd already half-built the workaround by hand: a TV app because I kept losing track of where I was in a series between seasons, a routing tool because the "fastest" route is never the good one on a motorcycle.
The advantage of scratching your own itch is that you can tell a real pattern from a polite complaint, because you've lived it rather than inferred it. The failure mode is assuming your itch is universal — so I still pair "a hundred people repeat this complaint" with "and I personally feel it." The second half is what keeps you honest when the build gets hard.
Exactly. What people complain about isn't always the problem. What they repeatedly build workarounds for usually is.
Digital receipts that actually work for your business (not just a paper trail)
Every time a customer walks out with a paper receipt, that's it — you've lost them. No way to reach them again, no idea if they're a repeat customer, no real data on what's driving your sales.
I'm building a platform that turns every receipt into a digital touchpoint:
Digital receipts — clean, branded, sent via link or card tap instead of (or alongside) paper
Built-in loyalty — repeat customers get recognized and rewarded automatically, no separate app or card
Customer dashboard — a simple visual view of who's buying, when, and what's trending
AI insights — plain-language nudges, like flagging customers likely to churn or your actual peak hours
Plugs into what you already use — sits on top of existing POS/billing, so there's no rip-and-replace
Scales — works for a single location or multiple branches
The bet: business owners shouldn't need enterprise software or a data analyst to understand their own customers. Digitizing something they already do (printing receipts) should be enough.
Currently building and testing with real merchants. Would love feedback
A receipt records a purchase. A digital receipt can start a relationship. That's the real upgrade.
Exactly.
The best startup ideas rarely come from brainstorming sessions. They come from patterns in customer pain.
That's why market validation matters so much. FoundersBar helps founders identify real demand before building: https://foundersbar.com/market-validation-for-startups
Turn signals into startups, not assumptions.
Agreed. Repeated pain is a stronger signal than isolated feedback. The next challenge is separating symptoms from the underlying pattern creating those repeated complaints. That's where the real opportunity usually hides.
Yes, we need to solve a problem which users have. They will be gladly willing to pay for it. Also, make the price, such a good deal, that paying is a no brainer.
I have noticed this too. The useful ideas often come from small problems that people mention again and again, not from trying to invent something completely new. I also created my own tools based on the problems they solve.
A signal becomes useful when it changes a decision. I would define the action and threshold beside each metric: what would make you continue, narrow the segment, or stop? Without that rule, more dashboards can create the feeling of evidence without reducing uncertainty.
I see this all the time with Alora, which is the home health software we use. The features that end up making the biggest difference aren't the flashy new ones. They're the ones that solve the same frustrations agencies keep running into over and over. When everyone is asking the same questions or struggling with the same workflow, that's usually a pretty good sign of what actually needs to be built next.
The venting versus workaround split is a great filter. I would add a third pile that founders running more than one business live in constantly: the problem is real, a workaround already exists, but nobody has time to notice the workaround is failing until it already cost something. That gap between a workaround quietly breaking and someone actually seeing it is basically the whole reason I built FounderFlow.
The "one complaint is noise, a hundred is signal" line is the part most people skip. The same filter is brutal when you turn it inward on your own todo list, because most of what we plan is noise dressed up as progress. A single interesting idea feels urgent, but the real signal is the frustration that keeps resurfacing week after week. I've started treating my week the way you treat opportunities here: instead of asking what could I do, I ask which two or three things actually move me toward the one goal, and everything else waits. That's basically how I use AgileTask.ai, forcing a short list instead of a long one. Curious how you separate a real repeated signal from a loud one-off that just happens to be recent and top of mind?
The distinction between noise and signal gets even sharper when you ask why the same frustration keeps returning. Repeated pain usually points to a system, not a one-off problem.
This is exactly the mental shift that changed how I
approach building.
"One complaint is noise. A hundred similar complaints
is a signal.", that's the whole game. The hard part
isn't understanding that intellectually, it's doing
the work of finding where those repeated frustrations
are actually happening across the places builders talk.
I've been thinking about this problem long enough that
I built something around it, BuildScout scans HN,
Product Hunt, YC, and funding news to surface exactly
these patterns, filtered through your specific stack
and constraints so you're not just seeing what's
trending for everyone else.
The thing I'd add to your framing: the signal only
matters if it's matched to who you are as a builder.
The same frustration is an opportunity for one person
and completely irrelevant for another depending on
their stack, time budget, and what they want to learn
by shipping.
If you're working on something in this space I'd love
to compare notes, feels like we're thinking about
the same problem from different angles.
Really appreciate you sharing that. I like the idea that signals only matter in context not every pattern is an opportunity for every builder. Looking forward to seeing what you build.
Do you not think that leaves an entire genre of products outside of your scope?
If you are only solving problems then nothing would get built that nobody asked for.
I get that it's much easier to get the first users when there's a pressing obvious need, but what about apps that do something people never thought about.
Great point. I don't think every breakthrough starts with an explicit user request. Many category-defining products began as something people couldn't articulate. My argument is that even those breakthroughs usually connect to a deeper, unspoken tension or latent behavior. The request may be invisible—but the signal rarely is.
This is a good reminder that validation starts before building. Talking to users and spotting repeated pain points usually leads to better products than chasing the latest trend.
Exactly. I'd add one more layer: validation isn't just about confirming the problem exists—it's about understanding why it still exists. Many pain points survive because they're tolerated, normalized, or hidden behind workarounds. That's often where the biggest opportunities are.
This is a solid reframing—especially the shift from “idea hunting” to “signal detection.”
In practice, the hardest part isn’t spotting patterns, it’s validating whether the “repeated frustration” is actually unsolved or just unaddressed loudly. A lot of signals look big on social platforms but collapse when you check willingness to pay or existing workarounds.
The strongest opportunities usually sit at the intersection of:
and business impact (time, money, risk)
If you only track noise vs repetition, you still miss the “why now” factor. Timing is often what turns a known frustration into a real market gap.
Still, the core idea is right: builders don’t suffer from lack of ideas, they suffer from weak signal filtering.
Exactly. Complaints are weak signals. Workarounds are strong signals. When people build their own temporary solution, they're already telling you the problem is worth paying to solve.
Yeah, this hits. I built DictaFlow from exactly the "pile two" signal you're talking about. The frustration wasn't that dictation didn't exist, it was that every tool already out there broke in Citrix and VDI environments, those locked-down corporate setups where you can't install anything and paste is disabled. Doctors and lawyers were doing all kinds of manual workarounds: copy and paste from a separate window, use a phone app next to the desktop, pre-dictate into a notes app then type it all again. The fact that people were building these rituals told me there was real demand, not just venting. The hard part was exactly what you said, filtering the "this is annoying" from "I'm already spending 20 minutes a day working around this."
That's a great example.
The moment people start building their own workaround, they're no longer just expressing frustration they're revealing intent.
Complaints tell us what hurts. Workarounds tell us what people care enough to fix.
In many cases, the workaround is already the first version of the product waiting to be discovered.
TruthLoop AI — Find what's being avoided.
The distinction I'd add: not all repeated frustration is equal signal. A hundred people complaining about the same thing splits into two very different piles, and only one is an opportunity.
Pile one: people venting. "X is so annoying." Loud, repeated, real frustration, but no behavior attached. They'll complain forever and never pay to make it stop.
Pile two: people who've already built a workaround. Duct-taped a Zapier flow, a spreadsheet, a manual Sunday-night ritual. Same frustration, but now there's evidence they'll spend something (time, money, effort) to solve it.
A hundred complaints is a signal that a problem exists. A handful of documented workarounds is a signal someone will pay. The second pile is smaller and far more valuable, and it's the one most "listen for repeated complaints" approaches miss because the workaround posts are quieter than the rage posts.
This is basically the thesis I ended up building Builder Brief (it's listed here on IH) around so the post hit home. The hardest part wasn't finding repeated frustration, it was filtering the venting from the "I'm already solving this myself" signal. That filter is most of the value.
A complaint tells you where attention is.
A workaround tells you where value is.
The interesting question is: what problem is important enough that people keep solving it manually?
That's often where the hidden opportunity lives.
TruthLoop AI — Find what's being avoided.
This hits home. I built Hello First — a voice-first blind dating app — not from brainstorming sessions but from following a persistent frustration signal: people feel judged by photos before anyone even reads their profile on dating apps. That repeated frustration (from friends, Reddit threads, and personal experience) became the entire blueprint. No photo uploads, no swiping on looks — just voice profiles and turn-based reveals. Following the signal instead of chasing ideas made all the difference. Now live and building! 🎙️
Interesting.
Most people start with an idea and look for a problem.
The strongest opportunities seem to start with a recurring problem and reveal the idea later.
TruthLoop AI – Find what you're avoiding.
What's a repeated frustration you've noticed recently that might actually be a hidden opportunity?
The biggest mistake I see: people look for opportunities in trends. I’m starting to think opportunities hide in recurring frustrations instead.
This comment was deleted 22 days ago.