How to Find Product-Market Fit Using Demand Signals

Product-market fit is the most overused and least understood phrase in indie hacking. Everyone says they're "searching for it." Almost nobody can tell you what it looks like when it arrives. So they chase vanity metrics — signups, page views, follower counts — and mistake noise for signal.

Here's the uncomfortable truth: product-market fit isn't a feeling, and it isn't a dashboard number. It's a pattern. And that pattern shows up in the demand signals people leave behind, long before it shows up in your revenue chart.

What product-market fit actually is

Product-market fit is the moment when the demand for what you're building stops being something you have to manufacture and starts being something you have to keep up with. People aren't asking you to explain the problem anymore — they're asking when they can have the solution.

The classic test is Sean Ellis's: if 40% of your users would be "very disappointed" if your product disappeared, you have it. But that test requires users. Before you have users, you have something more useful: demand signals.

A demand signal is any trace that someone has a problem they're actively trying to solve. A complaint on Bluesky. A workaround someone describes in a forum. A question about a tool that doesn't exist. These aren't leads — they're evidence. And when you learn to read them, you can find product-market fit before you build, not after.

The signal that you've found a real problem

The first thing product-market fit requires is a problem sharp enough that people are already spending money, time, or attention on it. You can't manufacture this. You can only find it.

The workaround test is the fastest way to check. If people are duct-taping together a solution with spreadsheets, scripts, and manual copy-paste, they have a real problem. The workaround is the demand signal — it's proof they'd rather suffer through a hack than live with the pain.

When you see the same workaround described by people who don't know each other, you're not looking at one frustrated person. You're looking at a market. That's the first sign of product-market fit: the problem is real, current, and shared.

The signal that people will pay

A real problem isn't enough. Plenty of products solve real problems nobody will pay to fix. The second signal is money — not what people say they'd pay, but what they're already spending.

This is where the pain-points vs nice-to-haves distinction matters. A nice-to-have is a problem people acknowledge but won't budget for. A pain point is a problem that's costing them something they can measure — hours they could bill, a tool they're already paying for, a hire they're considering.

When you find demand signals that mention cost — "this takes me four hours every Monday," "we pay two people to do this by hand" — you've found a pain point. That's the second sign of product-market fit: the problem is expensive enough that solving it is worth money.

The signal that your solution is right

The third signal is the hardest to see before you build, but it's the one that matters most. It's the moment when your specific approach to the problem resonates.

You can test this without a product. Describe the smallest version that kills the pain — the one from your product spec — and watch how people react. The difference between "that sounds cool" and "when can I have it?" is the difference between a nice idea and product-market fit.

The people who say "when can I have it?" are showing buying intent. They're not being polite. They're telling you they have the problem, they've tried to solve it, and your framing of the solution matches how they think about it. That alignment — between your solution and their mental model of the fix — is the third signal.

How to read the signals before you build

You don't need a product to start collecting these signals. You need a system. Here's a repeatable one:

1. Find the problem. Search for complaints, workarounds, and "is there a tool for X" questions in the niche you're targeting. The demand-signal playbook walks through where to look and what counts as a signal.

2. Check the cost. For each problem you find, ask: what is this costing people? If you can't find evidence of cost — time, money, or stress — it's a nice-to-have, not a market.

3. Test the solution. Describe your smallest solution to the people who posted the signals. Watch for "when can I have it?" over "that sounds cool."

4. Rank what you find. Not every signal is worth acting on. The score-and-rank framework helps you separate the signals that point to a real market from the ones that are just noise.

The signal that you've actually found it

Here's the thing nobody tells you: product-market fit doesn't announce itself. It sneaks up on you. One day you realize you're not explaining the problem anymore — you're explaining the roadmap. People aren't asking "what does this do?" They're asking "when is the next version?"

That's the pattern. The demand signals that used to be scattered complaints have become a steady stream of people who want what you're building. The workarounds have stopped. The "is there a tool for X" questions now point at you.

When that happens, you haven't just found a market. You've found product-market fit. And you found it the honest way — by reading the signals people were already leaving behind, instead of hoping your product would create demand that was never there.

The whole thing in one paragraph

Product-market fit is a pattern, not a feeling. It shows up in three demand signals: a problem that's real and shared, a cost that makes it worth paying to solve, and a solution that resonates with how people already think about the fix. Find those three signals before you build, and you'll know you're building something people want — not something you hope they'll want. Build the smallest version that kills the pain, watch for "when can I have it?", and let the demand signals tell you when you've arrived.

If you want to find those signals — real complaints, workarounds, and buying intent from people who don't know each other — that's exactly what DemandOrca does. It watches public Bluesky posts, classifies the demand signals, and clusters them into opportunities you can build against. See what people are asking for right now.