The 90/10 Flip: Distribution Is the Moat#

Two launches crossed our feed last month. Both ended the same way, and both builders eventually figured out the same thing.

Jack spent four months building a SaaS product. He coded every feature himself, polished the landing page for weeks, set up the onboarding flow, made sure everything was perfect. Launch day came. Zero paying customers. Not one signup. He sat staring at the analytics dashboard: zero conversions, zero traffic, zero everything. His own summary of the period is brutally honest: he optimized button colors, rewrote error messages, and refactored code that nobody would ever see. Busy, but not effective. He never once talked to a potential customer before building (source: his post on Indie Hackers, July 2026).

Alex took the opposite strategy and hit the same wall from another direction. He launched 37 different products over roughly five years. One went viral. Almost all the others struggled to get any traction at all. His conclusion after 37 launches: virality is rare and nearly impossible to predict, and most of his “failed” launches didn’t actually fail. They just grew much slower than he expected (source: his post on Indie Hackers, July 2025).

Same trap, two versions. Build first, distribute later. And later never comes, because the launch is treated as the distribution.

Here is the short version of this article: launching is not distributing, and distribution is the moat. A mediocre product with working distribution survives. A world-class product with zero distribution dies quietly. The fix that works, in both cases above, is a ratio flip: from 90% building and 10% distribution to the reverse. This article walks through why that flip works, what “distribution” actually means as a system instead of an event, and what the first ninety days look like when you do it right.

Why the Dashboard Looks the Same for Everyone#

We run growth for software companies, which means we spend our weeks inside other people’s analytics. After a few hundred accounts, the shapes repeat. The pattern is so consistent it stops being a surprise: a founder shows us a product that is genuinely good, with a dashboard that shows the truth anyway. Thirty visits a month. Zero conversations. A churn line that is technically flat because there are no customers to churn.

The founder’s explanation is almost always the same too. We need more features. We need a better landing page. We should launch again, harder this time.

The data in their own dashboard says none of that. The product was never the constraint. Nobody knew it existed. Distribution was the constraint, and it still is, months later, because the founder is still spending 90% of their time in the code editor.

This is not a small-founder problem. Every week we see the same shape in companies that have raised money and hired people. The hiring plan says “marketing later.” The roadmap says “features first.” Later arrives with a burned budget and a cold start.

The developer community already knows this at the level of a saying. “Brilliant developers would build incredible apps, but faced with $5K/month marketing agencies or confusing DIY tactics, they’d choose to go it alone” (r/indiehackers, linked from our market research). That sentence describes the exact moment the trap closes: the founder looks at the two available options, agency or DIY chaos, rejects both, and goes back to building. Going alone is not the failure. Going alone into the code editor is.

The Two Wrong Turns#

Before the flip, most founders try one of two strategies. Both fail for a predictable reason.

Wrong turn one: the launch-count strategy. Ship fast, ship often, and one of them will catch. Alex’s 37 launches is the extreme case, and his own data is the counter-evidence: 37 bets produced one viral hit and a long row of launches that grew slowly or not at all. The math looks attractive until you count the true cost. Every launch carries a hidden reset: a new audience to build, a new reputation to earn, a new set of “nobody came” weeks to survive. Volume of launches is volume of cold starts.

Wrong turn two: buy a channel. This is the $5K/month agency or the “tool of the week” route. Pay someone to post, or buy the tool that promises reach. The reason this fails is not the money. It is that an agency posting on your behalf, or a tool blasting on your behalf, does not contain the one thing distribution requires: a point of view that a specific audience recognizes as theirs. Channels amplify a promise. They do not create one. If no specific person feels addressed by your product, no channel will fix that, and you will conclude the channel is broken.

Both wrong turns share the same root error. They treat distribution as an event: a launch, a campaign, a post that goes viral. Distribution is not an event. It is a system that runs every day, and the system has one job: put your product in front of people who are already looking for what it does.

The Flip#

Jack’s fix was not a better launch. He stopped building and started listening, then he flipped his ratio to 90% distribution and 10% building. He stopped cold-pitching random founders and started looking for businesses that were already searching for solutions in his space, companies actively expressing intent. His first ten customers came from that shift, not from feature number 47 on the roadmap (source: Indie Hackers, July 2026).

The most useful comment on his post came from another builder, howardV, and it is worth quoting almost in full: “The first 10 customers usually don’t come from a bigger launch. They come from places where the pain is already visible: forum questions, competitor complaints, review sites, search queries, job posts, or people describing a broken workflow in public” (Indie Hackers comment thread, July 2026).

Read that list again, because it is the whole strategy compressed: forum questions, competitor complaints, review sites, search queries, job posts, public descriptions of broken workflows. Every item is a place where a human has already done the expensive part. They have admitted the problem, in public, in their own words, usually with details and numbers attached.

Distribution, done right, is mostly a matching problem: read where the pain is public, then show up there with the thing that addresses it. That is why the ratio flip works. Building in a vacuum produces a product and an audience of one. Building against a visible pain produces a product and a queue of people who already know they want it.

What a Distribution System Looks Like#

The flip sounds simple, so let us be precise about what replaces the code time. A distribution system, the kind that survives past week three, has four parts.

Part one: an intent inventory. A running list of where your target customer’s pain shows up in public. For developer products this usually means forums like Reddit and Hacker News, communities like Indie Hackers, job postings that describe the workflow you automate, changelogs and launch threads of adjacent tools, and review sites where users complain about the incumbent. You are not inventing channels. You are listing the places where the words your customer uses already exist.

Part two: small, native, repeated output. One idea, expressed natively per place: a story for one platform, a technical walkthrough for another, a question-answer for a community that punishes promotion. Copy-pasting the same text everywhere is how you get banned and ignored in six places at once. The output is small because consistency beats volume. A founder who posts three times a week for six months in the one community where their buyers gather will outperform the founder who launches five products in five months.

Part three: evidence behind every claim. Every number you put in public needs a source, a sample, and a date. This is not compliance theater. It is the difference between content that gets quoted and content that gets scrolled past. AI search engines now cite third-party pages in most answers, and they only cite pages that contain verifiable facts. Content with traceable evidence is the asset that keeps paying after the post stops trending. Content without it is noise that makes your brand less quotable over time.

Part four: a review loop. Monthly, not daily. What got replies? What got cited? Which of the five places you showed up in actually contains buyers? The loop is what turns patience into compounding. Without it, patience is just waiting.

Why Patience Only Works With a System#

Alex’s second lesson is the one most founders do not want to hear. His current project, Refgrow, took over six months to get its first paying customer. Then it started growing slowly and steadily with almost no marketing budget (source: Indie Hackers, July 2025). Six months of near-zero signal, followed by compounding.

That sequence looks like luck from the outside and feels like failure from the inside. It is neither. It is the natural shape of trust-based distribution: the first ninety days are spent becoming visible to the people who will later buy. Nothing visible happens in the dashboard during that phase, because the dashboard only measures the end of the funnel.

The founders who survive the six months are not the most patient ones. They are the ones running a system they can point to. The dashboard is empty, but the intent inventory is growing, the community replies are accumulating, the evidence library is building. When the first customers arrive, the system is already there to compound them.

We should be direct about our own interest here. We built a company on this exact model: we run distribution systems for software companies, and we publish our numbers, because the numbers are the proof. The client campaigns we run on the outreach side hold a 7 to 10 percent reply rate against an industry typical of around one percent (company data). The reason is not exotic copywriting. It is the same matching logic as Jack’s flip: research the visible pain first, then write one sentence that proves you saw it.

The First Ninety Days#

If you are sitting on a silent launch right now, here is what the flip looks like in practice, week by week.

Weeks 1 to 2: build the inventory. Write down the five places where your buyers admit their problem in public. Spend one hour a day reading, not posting. Save the exact words they use. Those words are your future headlines.

Weeks 3 to 8: answer before you announce. Show up in those places and answer real questions, with real specifics. No product link in the first weeks. The goal is to become the recognizable answer, not to pitch. In communities that run on trust, this phase is the entire difference between a member and a marketer.

Weeks 9 to 12: let the product appear inside the answers. By now you have a history of being useful. When your product genuinely fits the question, it shows up as the tool you use, with the result attached. That is not promotion. That is the answer getting better.

Then keep going. Month four is when the dashboard starts to move, and month six is when it starts to look like a business.

FAQ#

Is distribution really more important than the product?

For survival, yes. A mediocre product with a working distribution loop gets feedback, iterates, and improves. A great product with no distribution gets no feedback and dies unchanged. Product quality decides how big you get. Distribution decides whether you get to find out.

Where do I find the places where pain is already public?

Start with the five sources from howardV’s comment: forum questions, competitor complaints, review sites, search queries, and job posts. Add one more: changelogs and launch threads of the tools your buyers already use. People describe the workflow they wish existed right next to the tool that almost provides it.

How long until this works?

Plan for six months before judging it. Refgrow took over six months to its first paying customer and now grows steadily with almost no marketing budget. Jack’s flip produced his first ten customers after his ratio change, following four months of building in silence. The honest range is three to six months of consistent, native output before the curve turns.

Do I need a budget for this?

No. Every channel in the system above is free except your time. The expensive mistake is the opposite one: paying for reach before you have a message that a specific person feels addressed by.

I already launched and it was silent. Is it too late?

The launch is not the product’s only chance. Distribution systems run on new output, not on re-launching old news. Start the ninety-day loop now. In most communities, the founder who shows up consistently for ninety days outranks the founder who launched once, regardless of who launched first.

Bottom Line#

Jack’s four months of silent building and Alex’s 37 quiet launches are the same story told twice: the product was never the problem, and the launch was never the distribution. The fix in both cases was the 90/10 flip, applied as a daily system: find where the pain is already public, answer it natively and repeatedly, keep every claim evidence-backed, and review monthly while the curve is still flat.

You can have a mediocre product with great distribution and survive. You can have a world-class product with zero distribution and die. The moat is not what you build. It is how you get found.

Sources: Indie Hackers, “I built a SaaS that got 0 paying customers at launch. Distribution was the real problem all along” (Jack Builds, July 2026, incl. howardV comment thread); Indie Hackers, “I’ve launched 37 products in 5 years and not doing that again” (AlexBelogubov, July 2025); r/indiehackers thread on developer marketing agencies (2026); company client data (7-10% outreach reply rate).