ThreadSonar
dogfood · local
field notes · August 21, 2026 · 3 min read

The anatomy of a "what do you all use for..." thread

Max · founder, ThreadSonar

Every few minutes, somewhere public, a person with budget types some version of the same four words: "what do you use for..."

It's the closest thing the open internet has to a raised hand. No form filled, no demo booked, and yet more honest than either, because the asker chose the venue precisely to route around vendors. I've read thousands of these threads at this point, first as a founder doing it manually, then through the product we built to do it for us. They have an anatomy, and knowing it changes how you act on them.

The lifecycle, hour by hour

Hours 0 to 6. The thread is live. The asker is checking replies compulsively, because it's their problem and they posted it thirty minutes ago. Anything useful posted here gets read, upvoted, and responded to. This is the entire window for a conversation, as opposed to a billboard.

Hours 6 to 48. Peak reply accumulation. The asker is still around but triaging. First replies have staked out positions; later replies mostly agree, pile on, or nitpick. A vendor arriving now can still land, but they're responding to the room, not just the asker.

Day 2 onward. The thread is a document. The asker has often already chosen. But the thread starts its second life: it ranks for the exact query it contains, lurkers arrive from search in a steady drip for years, and AI engines fold it into what they recommend. Whatever the top replies say is now the semi-permanent answer to that question.

The practical takeaway is uncomfortable for anyone doing this manually: the difference between hour 3 and day 3 is the difference between a sales conversation and a hope.

Reading the asker

Two threads with identical titles can be worlds apart in value, and the tells are all in the details:

  • Trigger events beat curiosity. "Our contract renews next month" or "they just raised prices 40%" or "we're switching off X" signals a decision with a deadline. "Curious what people like" is a browser, not a buyer.
  • Constraints are gifts. "Under $100/mo," "must be self-hosted," "team of six." Constraints mean they've thought about it, and they let you disqualify yourself honestly, which is its own kind of credibility.
  • The author's history matters. A founder asking in r/sales is a buyer. An intern collecting options for a slide is a slide. A vendor asking is fishing for a thread to promote in. Thirty seconds on the profile usually settles it.
  • Watch for the anti-signal. Someone explicitly excluding your category ("no AI tools please," "nothing subscription-based") looks like a hot lead to a keyword system and is actually the most dangerous kind of false positive. Respect the exclusion; reply anyway only if you can genuinely help within their constraints.

Who actually wins the thread

Not the best product. The best reply. Which is usually: specific to the asker's stated constraints, honest about tradeoffs, willing to name alternatives, disclosed if the author has a stake, and present within the window. The lurkers, who outnumber the asker ten thousand to one over the thread's life, consistently reward exactly one behavior, which is being more useful than promotional.

There's a quiet corollary: if your category's recurring threads are being won by a competitor's happy users, that's not bad luck, it's a standing distribution loss you can measure. And if they're being won by nobody, the seat is empty.

The four words fire constantly. The only real question is whether you find out in hour three or year three. Everything we build is basically an answer to that question, but the anatomy is the same no matter how you do the finding: read the asker, respect the room, watch the clock.

ThreadSonar finds the live conversations that matter to your product and maps them into one inbox. First leads in under five minutes.

Start listening