How Gumroad got its users
The founder has written publicly about his failures and his finances for over a decade. The personal audience carries the product.
Confirmed. The team said it publicly, or the signals leave no room for doubt.
Reproducible, but it will cost you real money, real months, or a skill you may not have.
The edge you do not have: A personal audience built across a decade of public writing
- A launch that does not start from zero
- A direct relationship that survives algorithm changes
- 12 to 36 months of publishing before launch
- Accepting that you are the face of the product
- A topic where you have standing
Founder-led in 2026
Works extremely well, but it is an asset you build before the product, not during.
Everything on this channel →The play
5 steps, in the order they ran them.
- 1
Write the failure post before you have a win. On sahillavingia.com the founder published "Reflecting on My Failure to Build a Billion-Dollar Company" and "No Meetings, No Deadlines, No Full-Time Employees", naming what he cut and why. Those spread partly because he was already known in SF. Copy the shape, not the reach: one decision you regret, the real figure attached, no lesson bolted on the end. Host it on your own domain so it stays linkable when the platform dies.
done whenYour last public post about the company: could a competitor have written it from your landing page alone? If yes, you published marketing, not a founder post. Nothing in it cost you anything to say.
- 2
Put the meeting in the footer. gumroad.com links "Board meetings" from its footer straight to YouTube, sitting beside Terms and Privacy, and the current one is an annual meeting announcing a new CEO on camera. The format is a plain walkthrough: the numbers, what shipped, what did not. Run yours quarterly, half an hour, screen sharing your real dashboard. The copyable part is the placement, a buyer trips over it on your site instead of a post that scrolls away.
done whenOpen your own site footer. Is there one link a rival founder would refuse to publish? If every entry is legal boilerplate and help docs, you have a brochure, not a founder channel.
- 3
Ship the codebase as the pitch. github.com/antiwork/gumroad is the live app under MIT, tagline "See what sticks", and the star count is printed on the gumroad.com homepage as proof. The contribution rule is odd enough to be worth stealing: no inbound review queue, you fork, open the PR on your own fork, then email support@gumroad.com with the link, and user-facing changes need screenshots, QA steps and test results. That rule is the story developers repeat.
done whenCan a stranger open one artifact of yours and judge it without talking to you? Code, a spec, a real price list. If everything sits behind a demo request, there is nothing for anyone to pass around.
- 4
Be customer zero with a public URL. The founder keeps his own seller profile at sahil.gumroad.com, so every post about selling doubles as a live demo. The homepage promise is "Go from 0 to $1" and gumroad.com/pricing states the split plainly: direct links take 10% + $0.50, sales coming through Discover take 30%. Sell one small thing of your own through your own product, publish the storefront link, and let people check the claim instead of trusting it.
done whenAre you a visible user of your own product, with a public link proving it? If your name appears nowhere in your product's own public data, buyers read every claim you make as advertising.
- 5
Know what you cannot copy. Gumroad opened its own funding round to its own sellers on Republic, written up at sahillavingia.com/ipo, turning customers into shareholders. It filled because years of public writing and the book The Minimalist Entrepreneur had already built the crowd. The audience did that, not the tactic. With no crowd, the honest substitute is ownership-shaped rather than equity: a lifetime price lock for your first buyers, named publicly, honoured forever.
done whenCount who would actually notice if you posted tomorrow. If the honest answer is a handful of people, any move that needs a crowd on day one fails, and you are back to the first four steps.
The product itself
read from gumroad.com, live“Go from 0 to $1”
Run this against your own product
Carries the play above, and is written to tell you no when this channel is out of reach for you.
The same twelve channels as an agent skill. It reads your repository and eliminates what you cannot run. Open source, MIT.
curl -o ~/.claude/skills/howtodistribute/SKILL.md https://howtodistribute.com/skill.md
How big it got
Numbers published openly by the founder
What else they ran
They ran the same play
Want this verdict on your product?
Describe it. You get back the channel I would run in your place, the 30-day plan, and the number at which you stop.