2 builders who never spoke to each other
Log the build and the money in public
Keep a running public record of what you shipped this month and what it earned and cost, mistakes included. The record doubles as the thing that gathers an audience while there is no product to talk about, and a weekly write-up forces you to turn what you consumed into something of your own.
The method
- 01
Publish a monthly retrospective that includes your real income and expenses, so readers have the context behind whatever you are building.
- 02
Keep a page on the product site itself that logs the build as it happens.
- 03
Claim a product page on Indie Hackers before you launch, so there is somewhere people can find and follow the build.
- 04
Do the whole thing in public, including the mistakes, so the build itself becomes the audience-building content.
- 05
Publish a post once a week on whatever you figured out that week, which forces you to convert what you consumed into something of your own.
What it returned
- $2,000
Copied the format from Monica Lent's blog. His May figures: $2,000 in, $390 out, $1,610 net.
Added a page to MDX.one documenting the build in public.
Set up the MDX.one product page on Indie Hackers in the month before launch.
One weekly write-up sits between his daily posting quota and his monthly launch quota.
Sources
- May 2021: Retrospective & Income ReportBhanu Teja · bhanuteja.dev · May 2021: Retrospective & Income Report · undated
- ⭐️ I've decided to pursue a Bootstrap MBA – Jakob GreenfeldJakob Greenfeld · jakobgreenfeld.com · How to bootstrap an MBA · 2020-08-01
- Starting The Web App Challenge: From Zero to $5,000/month In 6 MonthsNathan Barry · nathanbarry.com · The Web App Challenge · 2012-12-31
the second source
Three plays a week, for the phase you are in
No roundup of links, no news. Three tactics more than one builder arrived at separately, with the numbers each one returned and the disagreements left in.
More in build in public
- Publish the revenue, including the months it falls7 unconnected · contested
- Publish the method, not just the finding5 unconnected · contested
- Expect your published numbers to recruit copycats4 unconnected · contested
- Announce the date before the plan is finished3 unconnected
- Work in the open so copying cannot hurt you3 unconnected
- Publish the build and the numbers as they happen2 unconnected