How to Interview the People Behind Demand Signals

A demand signal is a gift. Someone on Bluesky complains about a problem, describes a workaround, or asks outright for a tool that doesn't exist. You've found a real pain, in the wild, from a real person.

But here's the uncomfortable truth: a signal tells you that someone has a problem. It tells you almost nothing about whether they'd pay to solve it, how much, or what the solution must look like. The gap between "people complain about this" and "people will buy this" is where most products die.

The fastest way to close that gap is to talk to the person who posted the signal. Not a survey, not a landing page with a waitlist button — an actual conversation. Here's a repeatable interview script that turns one signal into a validated customer, without the awkwardness of cold-messaging a stranger.

Why interviews beat surveys

Surveys measure what people say they'd do. Interviews reveal what they actually do. When you ask "would you use this?" in a survey, you get polite yeses from people who'll never open your product. When you ask someone to walk you through their last Monday morning, you get the truth — the workaround, the frustration, the exact moment they gave up.

The workaround test works precisely because behavior is more honest than opinion. An interview is how you get the behavior.

Step 1: Find the right people to talk to

Not every signal is worth an interview. You're looking for three things in the person who posted it:

1. The pain is current. They described the problem recently, not six months ago. A stale pain is a solved pain.
2. The pain is costly. They attached a cost — time, money, or stress. "This takes me four hours every Monday" beats "this is annoying."
3. They're reachable. They're active on the platform, they reply to people, they're not a bot.

If a signal has all three, that person is your interview. If it's missing one, keep looking. One good interview beats ten lukewarm ones.

Step 2: Open with the signal, not the pitch

The worst way to start is "I'm building a product that solves your problem, want to try it?" That's a pitch, and it makes people defensive.

The best way is to reference the signal itself. You're not selling — you're saying "I saw what you posted, and I'm curious." Something like:

"Hey — saw your post about the four-hour Monday reconciliation. I'm looking into that exact problem and would love to hear more about how you handle it. Got 10 minutes?"

Two things make this work. First, you're referencing their words, which proves you actually read what they wrote. Second, you're asking for their expertise, not their money. People love being treated as the expert on their own problem.

Step 3: Ask about the last time, not the general case

This is the single most important technique in the whole interview. Don't ask "how do you usually handle this?" — that gets you a rehearsed, idealized answer. Ask about the last specific time it happened.

"Walk me through last Monday. What time did you start the reconciliation? What did you open first?"

Specific questions force specific answers. You'll hear the real workflow — the Google Sheet, the manual copy-paste, the moment they realized it was going to take four hours. That's your product spec, written in their behavior.

Step 4: Find the money

At some point you need to know if this is a business or a hobby. Don't ask "would you pay for this?" — that's a survey question and it gets you a polite yes. Ask about what they're already spending.

"What does this cost you today? Not just money — time, tools, people."

If they're already paying for a tool, hiring someone, or burning hours they could bill, you have a budget. If they say "it's just a minor annoyance," you have a nice-to-have, not a product. The pain-points vs nice-to-haves distinction lives or dies right here.

Step 5: Test the solution without building it

You don't need a prototype to test a solution. You need a description that's specific enough to react to. Describe the smallest version that kills the pain — the one from your product spec — and watch their reaction.

"What if, on Monday morning, a report was already waiting for you that matched the sheet with zero manual steps? Would that change your Monday?"

Watch for the difference between "that sounds cool" and "when can I have it?" The first is politeness. The second is buying intent. If you get the second, ask the follow-up that seals it: "If I built that, would you be the first person I show it to?"

Step 6: End with a commitment, not a thank-you

A good interview ends with a concrete next step. Not "thanks for your time" — a commitment that moves the relationship forward.

"I'm going to build a first version of this. Can I send it to you when it's ready and get your honest take?"

If they say yes, you have a first customer in the making. If they hesitate, you've learned something valuable for free — the pain isn't sharp enough, or the solution isn't right. Either way, the interview paid for itself.

The whole thing in one paragraph

A demand signal is a lead, not a customer. To turn it into one, talk to the person behind it. Find someone with a current, costly, reachable pain. Open by referencing their signal, not pitching. Ask about the last time it happened, not the general case. Find what it costs them today. Test your smallest solution and watch for buying intent. And end with a commitment to show them the first version. Do that with a handful of signals and you'll know — before you write a line of code — whether you're building something people want or something you hope they'll want.

If you want to find more signals worth interviewing — 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.