Builder Brief

Builder Brief scans Reddit, Hacker News, and reviews for recurring problems people are already hacking workarounds for, then turns them into evidence-backed briefs. The pitch to myself when I started: help solo builders like me figure out what's worth building next, cause building is easy now and knowing what to build is the hard part.

I built it for founders. Founders were not the ones who showed up.

Over the last six weeks I ran a research campaign, roughly a thousand DMs to product and product-marketing people in my network, and read every substantive reply (about 40 real back-and-forths). I went in to test one question: is there a second audience here beyond solo builders? The answer came back louder and different than I expected.

The sharpest piece of feedback reframed the whole thing. A product leader pointed out that founders aren't actually short on signal, they're in customer conversations constantly. It's product teams at scaling companies who lose that direct contact as they grow, and quietly stop hearing what customers are frustrated by. That's the person who's missing the signal. Not the founder. The VP of product three orgs removed from the customer.

So the ICP is shifting. Product teams at scaling companies, primary. Builders and founders, still welcome, secondary.

A few other things the campaign taught me that I'm now acting on:

Don't oversell "validated gaps." Several sharp researchers pointed out that complaint-scanning surfaces hypotheses and the obvious gaps, the genuinely unmet needs are often silent (people complain about what exists). So the honest framing is discovery accelerator, a high-confidence starting point that feeds the research a team already does, not a replacement for it.

The most common objection was "how is this different from just prompting Claude or Perplexity?" The answer that landed: an LLM gives you a fluent guess from training data. It can't tell you a complaint recurred 40 times across 6 communities over 3 months versus once. Counting recurrence needs a live pipeline pulling and storing the actual posts, not a one-shot fetch. That distinction is now the center of how I explain the product.

And the strongest recurring request wasn't for more features, it was "meet me in my workflow." People want the signal as an MCP or a feed piped into the tools they already use, not another destination to visit. That's reshaping the roadmap.

Where things actually stand, honestly: ~2,000 briefs in the catalog, one paying customer, and one B2B data-licensing pilot in motion with a company that wants the underlying signal as a feed rather than the briefs UI. Small numbers. But the campaign turned a hunch I'd been sitting on for months into a direction I can actually build toward, and that felt worth more than any of the vanity metrics.

Currently rebuilding the homepage around all of this: an interactive "describe your idea and we'll research it" hero instead of a wall of ideas, and a section that directly explains why this beats prompting an LLM yourself.

Happy to answer anything, especially from anyone who's navigated the founder-tool-to-team-tool shift, cause that's the road I'm on now.

Builder Brief just got its first paying customer, 30+ days after launch.

Context: Builder Brief scans Reddit, HN, Indie Hackers, and founder newsletters every few hours and turns recurring complaints into structured problem briefs. Problem statement, validation evidence scored 1-5, competitors with pricing, source links. Free to browse, first brief free, $4.99 per download after. Built solo, after my last product (FollowUp) flopped at $18 in revenue across 4 months.

The interesting part isn't the milestone, it's that the buyer broke my assumptions.

I built Builder Brief for solo indie founders making $5 validation calls. The first person to pay is a researcher in the Netherlands who bought a marketing/growth brief, an LLM SEO audit tool. Not my ICP, not my market, not my content category.

So I pulled the first 40 users into a spreadsheet. Marketing & Growth briefs over-index 2.31x in saves vs their share of the catalog. Developer Tools, my single biggest category, under-indexes at 0.52x. I built a catalog heavy on the exact category my real audience cares about least.

The lesson connecting this to FollowUp: last time I validated the idea but not the artifact. This time I validated the artifact but assumed the audience. Same root mistake, different layer, I committed to an assumption before the data was in.

What I'm doing about it: not repositioning on 45 users (too thin), but broadening the next signal source toward where the audience actually is, and recalibrating at 100 and 250 users before touching positioning.

If you've had a first paying customer who wasn't who you built for, curious how you handled it, reposition toward them, or hold your focus and let them self-serve?