What makes founder writing effective at building authority?

The examples that hold up share four traits: one subject held for years, evidence the writer personally owns, a specific reader in mind, and a venue that reader already visits. Authority compounds when the same name keeps showing up with useful, verifiable material in one lane. In our study of 180,011 LinkedIn posts by 4,485 founders and CEOs of funded startups, founders posting three or more times a week drew 24x the weekly engagement of founders posting less than monthly, and only 3.5% post that often, so consistency alone separates you from most of the field.

What is this kind of writing usually called?

You'll see a dozen labels for it: founder writing, executive content, authority content, founder-led content, op-eds, essays. The test matters more than the label. Strong examples share one shape: a named operator arguing a single clear idea from firsthand evidence, published where the people they want to reach already read. Paul Graham's essays, Tobi Lütke's layoff memo, and Sahil Lavingia's Gumroad essay all fit that shape, and none of them carried a category label when they went out.

Should a founder write it themselves or bring in help?

Either can work, and the deciding variable is the same: whose stories feed the drafts. Writing that builds authority runs on firsthand material, so a process that starts with your voice notes, your decisions, and your numbers can be delegated safely. A process where someone starts drafting on day one produces posts that read like a stranger doing an impression of you. At Megaphone we extract voice before writing a word, because when founder content doesn't sound like the founder, the root cause is almost always zero founder inputs at the start.

How long does founder writing take to build authority?

Plan in two horizons. An account that changes its approach usually needs six to eight weeks before the numbers move, and I'd commit to one subject for six to twelve months before judging the lane itself. The examples worth studying ran far longer than that: Paul Graham's essays have compounded for twenty years, and Basecamp's blog ran for years before the books grew out of it. Authority is a slow asset with a long shelf life, and the slowness is what keeps it scarce.

Founder Writing That Built Authority: Examples Worth Studying

The fastest way to decide whether founder writing is worth your time is to study the people it worked for. Below are four examples you can read today, each from a named founder or executive, each published somewhere public, with notes on what the writing did, why it worked, and what's worth copying. None of them were professional writers when they started, and the authority each one built has outlasted every individual post.

Four traits show up in every example: one subject held for years, evidence the writer personally owns, a specific reader in mind, and a venue that reader already visits. I review founder content daily at Megaphone, and the drafts that fail usually miss on the first two. Keep those four in view as you read.

One note on vocabulary before the examples. The pages that rank for this search mostly collect polished campaigns from big-company marketing teams. Those are fine as ads, and they're a different animal from what a founder needs, which is writing under a person's own name that makes a specific reader trust that person's judgment. Call it founder writing or executive content. The label you pick changes nothing about the four traits above.

Paul Graham: essays that compound for twenty years

Paul Graham co-founded Y Combinator, and the essays on his personal site, paulgraham.com, predate the fund itself. "How to Start a Startup" went up in 2005. "Do Things That Don't Scale" went up in 2013 and still circulates every time a new wave of founders discovers it. The writing follows one discipline: a single idea, argued in plain words, from things he saw firsthand as a founder and investor. In "How to Write Usefully" he lays out his own bar, which I'd paraphrase as telling the reader something true and important that they didn't already know.

Why it worked: the essays gave away judgment that was expensive to acquire, under his own name, in a format that doesn't age. Founders arrive at Y Combinator already trusting him because the essays did the trust-building for free, continuously, for two decades.

David Perell broke down Graham's writing process on his How I Write channel, in a video titled "The King of Internet Writing," and it's the best available look at how those essays get made, including how much rereading and cutting happens between the first draft and the version you see.

What to copy: pick the format that compounds. A feed post fades in a day, while an essay with a clear claim and your name on it keeps working for years. You don't need his talent to use his structure, which is one idea per piece, plain vocabulary, and a conclusion you'd defend in person.

Sahil Lavingia: the failure essay that reset the story

In February 2019, Gumroad's founder Sahil Lavingia published "Reflecting on My Failure to Build a Billion-Dollar Company" on Medium. He had raised venture money, missed the growth that raise implied, cut the team, and kept running Gumroad as the smaller, profitable company it turned out to be. The essay walks through the funding, the layoffs, and the revenue with the real numbers left in, at a moment when the standard founder move is silence.

Why it worked: candor that specific is scarce, so it reads as instantly credible. Thousands of founders had lived a quieter version of the same arc, and he said the part they'd only say privately. The essay has been linked and cited for years, and it reset Gumroad's story on his terms instead of the market's.

What to copy: the material you're most tempted to hide usually carries the most authority. You don't need a failure that large, only one true story with the numbers still attached and a reason you're the one qualified to tell it.

Tobi Lütke: a memo written on the worst day

In July 2022, Shopify cut roughly 10% of its staff, and CEO Tobi Lütke published the internal memo on Shopify's public news site the same day. It names the bet he had made, that pandemic-era ecommerce growth would hold, and then states plainly: "I got this wrong." There's no euphemism in it, and the reasoning and the ownership sit in the same paragraph.

Why it worked: executive content gets judged hardest under pressure, and most companies retreat into boilerplate exactly when the most people are reading. The memo got studied across tech because it sounded like a person who understood what the decision cost the people affected, and that impression transfers to every future thing he publishes.

What to copy: write the hard decision in your own voice before someone else summarizes it in corporate voice. The days you'd rather say nothing are the days the writing counts double, because a hard announcement draws a bigger audience than anything else you'll publish, and almost none of those readers expect candor from it.

Jason Fried and David Heinemeier Hansson: a blog that filtered customers for years

Basecamp's founders wrote Signal v. Noise for years, short opinionated posts about small teams, calm work, and the case against growth at any cost. The books Rework and It Doesn't Have to Be Crazy at Work grew directly out of that writing, and Rework became a New York Times bestseller built from arguments the blog had been testing in public for a decade.

Why it worked: the opinions were sharp enough to repel readers who disagreed, which concentrated the readers who agreed. Customers arrived pre-sold on how Basecamp works, and job openings drew applicants who had been reading for years. One lane, held for a very long time, in a voice two people genuinely owned.

What to copy: hold opinions sharp enough to cost you some readers, because the readers who stay are the ones who'll buy from you, work for you, or fund you. If nobody could disagree with your last ten posts, you've been publishing announcements, and an announcement feed never earns that kind of reader.

The same bar on LinkedIn and X

Essays and memos set the ceiling, and the venue where most founder writing now lives is softer than any of the examples suggest. In our study of 180,011 LinkedIn posts by 4,485 founders and CEOs of funded startups, the median founder earns 39 reactions, comments and reposts on a typical post, and 82% of founders post less than once a week. The founders posting three or more times weekly, 3.5% of the field, drew 24x the weekly engagement of those posting less than monthly. Measured against the four people above, almost nobody is running the play at all, which is most of the opportunity.

I've run the single-lane version myself. I've written about marketing in one lane for years, and that discipline built my X account to 93k followers. I was also the first CMO at Copy.ai, where we grew from $0 to $2.5M ARR in under a year. The same traits carried both: one subject, firsthand material, and a schedule I could hold through busy quarters.

If your readers live on LinkedIn more than anywhere else, the platform deserves its own treatment, and I've covered it in how executives build authority on LinkedIn.

What to copy, in order

If you're studying these to decide whether to start, here's the sequence I'd lift from them.

Pick the lane before the first post. Graham wrote startups, Fried and Heinemeier Hansson wrote calm work, and neither wandered. Commit to one subject for six to twelve months, which is the minimum window I'd give any lane before judging it.
Build from material only you have. Every example above runs on firsthand evidence: Lavingia's own revenue, Lütke's own bet, Graham's own portfolio of observed startups. The audience map and voice guide we build for clients exist to surface this material first, because generic inputs produce generic writing no matter who's drafting.
Write plainly and claim something. Each example can be summarized in one sentence a reader could disagree with. If yours can't, it's not finished yet.
Choose the venue your reader already visits, then hold the schedule. Graham owns his site, Lütke used the company newsroom, Lavingia went where founders read long essays. Your version is probably LinkedIn or X on a weekly rhythm you can keep, since a feed that flickers on and off teaches readers to stop checking.

None of these four waited until they had spare time. The writing was how they processed the work they were already doing, published where it could earn trust. If you want to know how far your current feed sits from this bar, take the free feed diagnostic quiz at megaphonestudio.com. It takes a few minutes and tells you what to fix first.