In the last essay, I argued that most writing fails because it lacks transmission currency. Persuasion optimizes for the immediate yes. Transmission optimizes for what happens after everyone leaves the room — whether the person who heard the idea gains enough social, operational, or intellectual capital to repeat it voluntarily.

That distinction doesn't stop at prose. It's the most understated structural divide in product architecture.

Most software products are persuasion engines. Every screen, every onboarding tooltip, every conversion flow is tuned to move a user from awareness to activation to credit card. Teams get very good at this. Then they look up and their viral coefficient is sitting at zero, and they conclude they need a referral program.

They don't. They need to understand what the user carries out of the building.

I spent years running GTM for enterprise software, and I watched the same pattern repeat at every company. The roadmap fills up with features that flatter the buyer in a demo: governance controls, permission hierarchies, executive dashboards. Features designed to win a procurement checklist. And they do win it. The contract gets signed.

Then the line workers log in. The product that dazzled a VP in a forty-five-minute demo turns out to be tedious in daily operation. It gives the people who actually use it no leverage in their own network — nothing they can hand to a colleague, show a client, or point to as proof they're good at their job. So it sits inside the enterprise like a monolith. Renewal becomes a knife fight, expansion never happens, and the CEO wonders why a product with 94% logo retention has no organic growth.

That's a persuasion product. It's built to close. It was never built to spread.

A transmission system inverts the design question. Instead of asking how do we reduce friction in the checkout flow, it asks: what artefact does this user generate during normal operation that makes them look capable when they share it?

The persistent delusion in growth engineering is that virality is a layer you bolt on downstream — a share button, a referral discount, a pop-up begging the user to invite three teammates.

Those aren't transmission mechanics. They're administrative interruptions. Nobody invites a colleague to save 5% on a subscription. Nobody publishes a product output to earn a badge.

People transmit when the act of transmission pays them, and it pays in exactly four currencies:

Status. Sharing this output makes me look like an elite operator in front of people whose opinion I care about.

Validation. This tool renders a chaotic problem into a legible framework that proves my team's lived experience was real.

Identity. Using this product — visibly — signals which tribe I belong to and which philosophy I've bet on.

Operational utility. Handing this link to someone else reduces my own coordination overhead. Sharing is literally faster than not sharing.

Calendly is the cleanest case of the fourth currency. Its core output — the booking link — cannot function without leaving the platform. Every act of using the product is an act of distributing it, and the recipient gets value before they ever create an account. Loom runs on the first: a well-made Loom makes the sender look like someone who respects your time, and the video plays instantly for a recipient who has never heard of Loom.

Notice what both have in common: the recipient gets paid first. No sign-up wall, no gate between the link and the value. The sender gets status or saved time; the recipient gets the goods. That's the transaction that a share button can never manufacture, because a share button transmits the product's message. A transmission mechanic transmits the user's competence, with the product along for the ride.

I've written before about why CryptoDickbutts and Nouns outlived thousands of better-funded projects: their outputs were remix-ready, and remixing them conferred identity. Same physics, different substrate. The meme that spreads and the product that spreads are obeying the same law.

If you're a founder or GTM engineer staring at a roadmap, run these three questions before you write another line of frontend code:

1. What is the default artefact? Does normal use of your product produce a static database entry visible only to logged-in users — or a clean, self-contained artefact that stands on its own outside the platform? If your product's output can't survive being pasted into someone else's Slack, you don't have a transmission mechanic. You have a filing cabinet.

2. Who gets paid when the link is opened? Trace the full transaction. The sender should gain one of the four currencies. The recipient should get instant value with zero friction. If the recipient hits a sign-up wall, you've taxed the exact moment you should be subsidizing — and your users know it, which is why they stop sharing.

3. Is there a transmission gate? Every artefact that leaves your product carries your product's name. Does the system have the discipline to refuse low-quality outputs? A product that lets users ship embarrassing artefacts is spending its transmission budget on anti-marketing. High standards at the output layer aren't friction. They're what makes the artefact worth staking your status on.

Diagnosis is cheap, so here's the mechanism. If you're sitting on an existing persuasion product, you don't need a redesign. You need to find the one moment in your current workflow where a user already produces something they're proud of — a finished analysis, a resolved ticket, a completed project, a number that went up — and you need to do three things to it:

First, make it exportable as a standalone object: a link, an image, a public page. Not a PDF attachment. Something that renders instantly wherever it lands.

Second, strip every barrier between the recipient and the value. The sign-up prompt comes after the recipient has gotten the goods, or it doesn't come at all.

Third, make the artefact flatter the sender, not the product. Your logo is a watermark, not a headline. The user's work is the headline.

That's it. One artefact, engineered properly, outperforms every referral program you will ever build — because it doesn't ask the user to do marketing. It pays them to do their job in public.

Persuasion products build expensive machines to drag customers across the finish line, one at a time, forever. Transmission systems turn every active user into a carrier.

Distribution is hard. Don't fuck it up by building a product that has to ask permission to exist.