How to Find Product Demand on Bluesky (Before You Build)

Every founder wants the same thing: proof that people want what they're about to build. The problem is where to look. Surveys are polite. Interviews are filtered. But there's one place where people say exactly what they want, unprompted, in public: Bluesky.

Bluesky is still early enough that the signal-to-noise ratio is unusually good. It's full of builders, indie hackers, and early adopters who talk about their problems openly. And unlike a survey, these posts aren't filtered through politeness — they're people living with a problem right now.

Here's the system for mining it.

Step 1: Search the pain, not the product

The biggest mistake is searching for your product name. Nobody is asking for your product — they're asking for the outcome it provides.

Instead, search for the language of pain:

"I wish there was a way to..." — a direct admission of an unfilled need
"I can't find a tool that..." — active searching, high intent
"I've been doing X manually" — a workaround that's begging to be automated
"Does anyone know a tool for..." — a public request for a solution
"I'd pay for..." — explicit buying intent

These phrases are demand signals. They tell you a problem exists, that people care enough to post about it, and that they're actively looking for a fix.

Step 2: Cluster by underlying problem

A single post is an anecdote. A cluster of posts is a market.

When you find a signal, don't stop at one. Search for the same pain in different words. If you find 20 people in a month all describing the same frustration with slightly different phrasing, you've found a real, recurring problem worth building for.

The key is to cluster by the underlying problem, not the surface complaint. "I hate reconciling expenses" and "spreadsheets for invoicing are killing me" are the same problem wearing different clothes.

Step 3: Score for urgency and buying intent

Not all demand is equal. When you've got a cluster, score each signal:

Is there a current cost? Are they losing time or money to this problem today? If yes, it's a pain point. If no, it's a nice-to-have.
Is there urgency? Are they looking for a solution now, or just musing? Urgency predicts action.
Is there buying intent? Did they say they'd pay, or just complain? "I'd pay for this" is a purchase signal; "this is annoying" is just data.
How many people share it? One person's pain is an anecdote. A cluster is a market.

Step 4: Validate with the workaround test

The strongest signal of all is a workaround. If people are already solving the problem with spreadsheets, duct tape, and manual processes, you've found real demand — they've voted with their time.

Ask: how are people solving this today? If the answer involves frustration and manual effort, you're not guessing at demand. You're reading it directly off the market.

The takeaway

You don't need a six-month research project to validate an idea. You need to listen to the right place — and Bluesky is one of the best places to listen right now.

The demand is already public. People are already telling you what they want, in their own words, every single day. The only question is whether you're listening.