Distribution Is a Feature You Design, Not a Channel You Buy

There’s a moment in most product timelines where someone says, “The product’s good — now we need to figure out distribution.” It sounds reasonable. It’s also the tell that distribution was treated as a phase instead of a property, a thing you bolt on at the end rather than something you build into the thing itself. The products that spread most naturally didn’t find a channel after the fact. They were shaped, from early on, so that using them was the distribution.

Start with the two ways a product can reach a new person. One is that you go get them — ads, campaigns, cold outreach, a sales motion. You pay, in money or effort, per person, and the day you stop paying the reaching stops. The other is that an existing user reaches them for you, as a natural consequence of getting value from the product. The first is a channel you buy. The second is a feature you design. Both are legitimate. But only one compounds, because only one turns your users into your growth.

The reason “buy a channel” feels like the default is that it’s legible. You can put a budget on it, attribute it, forecast it. Designed distribution is squishier and slower to show up in a dashboard, so it loses the argument in most planning meetings — right up until the paid channel gets expensive or crowded and the whole growth story turns out to be rented. When you rent your distribution, you don’t own your growth. You’re one auction, one algorithm change, one CAC spike away from the line going flat.

So what does it mean to design distribution into the product? It means the act of getting value naturally produces a reach — and there are a few distinct shapes this takes, worth telling apart.

The most obvious is when the product is more valuable because you brought someone in — a shared document, a message thread, a split expense. Here you invite people not to help the company grow but because the product doesn’t fully work alone. The reach is inseparable from the value.

A quieter shape is the artifact: the product, used normally, produces something the user wants to send out into the world — a design, a page, a chart, a link — and that thing carries a trace of where it came from. The user isn’t evangelizing. They’re just sharing their work, and the tool rides along inside it.

Subtler still is the status shape — where being an early or fluent user is itself worth signaling, so people talk about the product to say something about themselves. You can’t manufacture this, but you can leave room for it instead of designing it out.

The unifying idea is that in each case, distribution isn’t a thing users do for you — it’s a thing that happens because they got what they came for. The moment you have to bribe, nag, or guilt someone into sharing, you’ve admitted the distribution isn’t really in the product; it’s a tax you’re adding on top, and users can feel the difference. Referral programs that work are usually amplifying a share that already wanted to happen. Ones that don’t are trying to manufacture one that doesn’t.

Which reframes the design question in a useful way. Instead of “how do we get the word out,” the question becomes: when someone gets value from this, what naturally leaves the building? An invite, an artifact, a link, a mention — some trace of the product carried outward as a side effect of ordinary use. If the honest answer is nothing, then no marketing budget is fixing the underlying issue, because you’ve built something people use in private and are hoping they’ll talk about in public.

You still buy channels sometimes — to prime the pump, to reach the first users who’ll do the reaching after. But treat paid reach as the ignition, not the engine. The engine is the part of the product where getting value and spreading value are the same motion. Design that in early, while the shape of the thing is still soft, and distribution stops being a problem you’ll solve later. It becomes a feature you shipped.

The concepts, to look up: network effects, viral loops and the viral coefficient (k-factor), and the distinction between inherent/organic virality and incentivized referral.