Where Founders Should Publish

Assembling the appearance of distribution takes a single afternoon: a homepage, a newsletter, a LinkedIn presence, a static archive, a checkout link and a community chat. Put together, they can pass for a go-to-market plan, even though nothing connects one piece to the next.

Founders who would rather do product work or research tend to rank distribution below building in value and below strategy in analytical rigor. The old rule still holds: a product with no route to customers depends on luck. When the product is itself judgment, in the form of notes, briefings or decision tools, distribution is how the business actually runs, and the article, the relationship and the paid instrument work as one system. The usual mistake is to treat a channel you can see as a capability you own.

Run the media stack like a balance sheet: what you own, what you owe readers, what you have earned the right to charge for, and what it costs to keep running.

Start from what the reader needs at each stage

Asking where to publish turns the decision into a question of fashion. GitHub Pages gives public access and durable links; Substack bundles email, discovery and paid tools; card checkout through Stripe or a wallet rail can handle payment; a private review pack can establish credibility before a launch. All of them are useful, and none of them is the business.

Better questions follow a relationship as it develops. A stranger arriving cold needs evidence that the work deserves attention. A reader who comes back needs a way to receive the next piece without depending on an algorithm. Payment should follow demonstrated interest, which a button on the page does nothing to show, and partners and buyers need proof that the writing is shaping real decisions.

Four jobs publishing has to do

A workable distribution plan for a founder has four columns, kept deliberately plain.

None of the columns works alone. A public page with nothing behind it does not create an audience, and a checkout button does not fulfill a product.

Public shelf: work a stranger can judge

A cold reader should be able to scan a few titles and tell whether the author holds a consistent point of view, which takes dated issues, stable URLs, enough depth to evaluate the thinking and a clear indication of which decisions each piece supports.

Static hosting such as GitHub Pages suits this because the setup stays simple, with few moving parts, readable files and links people can share. Its limit is that a host only delivers pages. It will not build a subscription habit, a payment flow or a way for readers to reply, so a founder who stops at the shelf ends up with a library.

Relationship rail: making readers reachable again

The rail turns a single visit into an audience you can reach again. Newsletter platforms such as Substack handle email delivery, free and paid tiers and some discovery. Substack's guidance on paid tiers puts reach and engagement before any charge, and that order is right: move to paid only when readers return, reply, forward pieces or ask for operating help. What you are building is the relationship and the editorial commitment behind it, and if the commitment is thin, a polished rail just makes that easier to see.

Conversion right: earning permission to charge

Conversion right is permission to ask for payment without seeming to undervalue the reader's judgment. It needs a defined buyer, a concrete benefit, an access rule and a fulfillment promise.

For a modest monthly strategy note, the buyer is a founder, consultant or operator who needs a clearer view on automation, governance, market entry, capital or distribution. What they pay for is an instrument they can use, such as a scorecard, a board memo or a buyer checklist, and the payment tools follow from that promise. Card rails and Substack paid tiers cover the common reader base, and Stripe sits underneath many creator checkouts. A stablecoin option can reduce friction for some cross-border buyers, but it still needs refunds, access controls, records, support and trust, so add it only when it solves a buyer problem you have documented.

Proof loop: checking whether the others work

Proof is the least visible column, and it keeps the other three honest. Before adding surface area, check these signals:

1. Do the people arriving match the intended audience, or is it casual interest?
2. Do engaged readers move from one piece into the rest of the archive?
3. Do replies name buyer problems that could be packaged as paid work?
4. Does the public output make conversations with partners, investors, customers or candidates easier?
5. Does each issue sharpen the paid promise, or only add volume?

A smaller audience that sends qualified replies can outperform a larger one that shows no purchase intent, sends no referrals and does nothing for product judgment.

Build the columns in this order

Early teams do better building the columns in sequence than opening every channel at once:

1. Shelf first. Publish enough coherent public work for a cold reader to assess the thinking. Coherence counts for more than any single standout post.
2. Then the rail. Once the shelf is credible, capture repeat readers where you can reach them directly. The public archive stays the permanent record; the rail manages the reading habit.
3. Then one narrow paid product. Do not paywall the whole archive at the start. Let the free work demonstrate judgment and charge for packaged implementation support, at a modest price so the first conversion does not cost you trust.
4. Then extra rails, only when needed. Each additional payment or distribution path should fix a specific friction, and should not turn into a parallel plan.

One example stack

The framework is general, and the tools below are one set of choices. Here is an illustrative mapping, offered as an example and not a prescription:

Another team could use a custom domain, Beehiiv or Ghost for email and Lemon Squeezy for sales, or hold off on paid work until warm introductions confirm demand. Either arrangement is sound as long as the four columns are named and tracked.

Write one page before you expand

Before launching or expanding a founder media stack, answer these on a single page:

1. What is the canonical public shelf, and what should a cold reader conclude after three pieces?
2. What is the relationship rail, and how does a reader become reachable again?
3. What is the first paid product, and why is it more useful than another free essay?
4. Which payment and access path is live now, and which have you deliberately left off?
5. What proof would justify putting more into the publishing operation?

Without those answers, a founder can keep publishing indefinitely and never find out whether the work is building a company.