Here's a question almost no builder asks before opening Cursor: do you have a product distribution plan, or just a product? The industry has spent a decade telling you to find product-market fit, and almost no time on the question that kills more side projects: can you, specifically, reach the market this product needs? A great product you can't distribute is a hobby. Not a failure — a hobby. And the brutal part is that distribution fit is mostly determined before you write a line of code, by what you chose to build and who you happen to be. This post is about checking that fit honestly — and what to do when the product you built and the channels you can reach don't line up.
Distribution-product fit: the test nobody runs
Product-market fit asks: does the market want this? Distribution-product fit asks: is there a path from where users are to where your product is, and can you walk it? Both have to be true. Builders obsess over the first because it's about the product — the thing they control and love. The second is about channels, audiences, and standing, which feel like someone else's department.
There's no department. There's you.
The test is uncomfortable in its simplicity: name 3 specific channels where your target users already gather, and for each one, write a sentence about why anyone there would listen to you. Not "social media" — a named subreddit, a named newsletter, a keyword cluster with search volume you've actually checked, a Discord you're already in. If you can fill in all 3 lines, you have the skeleton of a distribution plan. If you can't, no amount of additional features will fix that, because the problem isn't the product. It's the route to it.
Every channel has a shape — and it has to match your product
Channels aren't interchangeable. Each one fits certain products and rejects others, and a mismatch means you can execute perfectly and still get nothing.
SEO fits products people search for — the problem has a name and a query. It's slow (typically months before meaningful traffic, sometimes longer) but compounds, and it suits builders who'd rather write than network. Terrible fit for products solving problems nobody knows they have.
Communities (Reddit, Hacker News, niche Discords, Indie Hackers) fit products with a sharp, recognizable pain and a demo that lands in 1 screenshot. Fast feedback, spiky traffic, allergic to anything that smells like marketing. You need standing — accounts and history, not a day-old profile with a link.
Cold outreach fits products with an identifiable buyer and real money attached — you can find 50 people by title and write each a relevant email. High effort per user, fine when 1 customer is worth a lot, absurd for a $5/month consumer app.
Paid ads fit products with decent margins and a funnel you've already measured. Buying traffic before you know your conversion rate is just paying to learn that your landing page leaks — measure first, then spend (know your funnel performance covers what to instrument).
An existing audience fits everything — if you have one. Most builders don't, and pretending otherwise is the most common silent failure mode in indie hacking. There are honest workarounds — we cover them in first 100 users without an audience — but they're channel strategies in disguise, not exemptions from the question.
The point: a product for tired parents of newborns is a poor fit for a builder whose entire network is dev Twitter. Nothing wrong with the product. Nothing wrong with the builder. Wrong pairing.
Match the product to the channels you can actually reach
So run the logic in the right direction. Most builders pick a product, then go hunting for channels. Inverting it is more honest: start from the channels where you already have reach or standing, and ask what those people need.
Take inventory — it's shorter than you'd like, and that's fine. Where do you already post and get responses? What communities know your name? What do you rank for, even accidentally? Which 20 people would open an email from you? What problems do you understand deeply enough to write about for a year?
That inventory is your real distribution surface. A product whose users live inside it starts with a working route to market on day 1. A product whose users live outside it starts with a cold-start problem stacked on top of a launch problem. Sometimes the unlaunched project sitting in your repos is genuinely good and genuinely wrong for you — and the right move is matching it to someone who has the distribution surface it needs, rather than forcing yourself to become a different person to market it.
Write the 1-page plan before you write more code
A real product distribution plan fits on a page. For your top 3 channels: who's there, what you'll post or send, what response would count as a signal, and what effort it costs per week. Then add the only 2 numbers that matter at this stage — a rough guess at how many people you can put in front of the product in month 1, and what fraction might plausibly care. Hedge both; they're guesses. The exercise isn't about precision, it's about discovering whether the answer is "a few thousand" or "I honestly don't know," because those lead to different decisions.
Then the gate: if the plan's honest answer is "I can't reach these users," stop building features. More code can't fix a routing problem. Your options are to change the product's audience, build standing in a new channel (months, not days — budget for it), or accept that this one needs distribution muscle you don't have and decide what that means.
When the product is right but the distribution isn't yours
That last case is more common than anyone admits, and it's exactly the gap LaunchBuddy was built for. It's a launch studio: you submit your unlaunched project, and if we pick it, we build it onto our harness, ship it live, and operate the distribution — the channel work, the funnel, the growth — as our job, not your second job. You keep ownership; you pay a flat fee or share revenue, and you can kill or port out anytime. Part of our free assessment is exactly the question this post asks: does this product have a reachable audience, and what's the route? It's 1 of the 4 axes we score every submission on.
If your project's been rotting in a tab because the building was fun and the distributing never started, get the free honest assessment. If it's a no, you get the why — including whether the problem is the product or the route. 60 seconds, 1 link, at launchbuddy.app.