The Solo Founder’s Lifecycle (MAKE by Peter Levels)

The “Standard” startup path is: Raise VC money -> Hire a team -> Spend 2 years building -> Hope it works. Peter Levels (founder of Nomad List and Remote OK) argues for the opposite. He generates over $200k/month in recurring revenue with a 90% profit margin as a solo developer. His book, MAKE, is the blueprint for the “Bootstrapper Lifecycle.”

Should you read this book?

Watch the Lex Fridman interview first. It covers about 80% of the book’s core philosophy for free and includes Peter’s updated thoughts on AI and Stable Diffusion—which aren’t in the book. Only buy the book if you’ve watched the interview and want a physical “tactical manual” to keep on your desk while you code.

Extracted Mental Model (lifecycle of a bootstrapper):

1. Ideation: Solve Your Own “Original” Problems

Don’t look for “billion-dollar ideas.” Look for your own pain points.

• The Incentive: You are the world’s leading expert on your own problems. If you don’t care about the product, you’ll hit “apathy burnout” long before it makes money.
• The “Originality” Model: To find original problems, you must be an original person. Get off your computer, interact with the world, and you’ll naturally bump into niches that need software solutions.
• Validation: Use a crude MVP. For my project, WordForge, the first version was just a text box and an AI response. I only refined the UI after users confirmed the core value was there.

2. Building: Use What You Know, Ship Fast

The biggest mistake is learning a new “shiny” language to build a startup.

• The “Existing Tech” Rule: Use your current stack. When my users asked for an Android version of WordForge, I didn’t stop to learn Flutter; I used Ionic/Capacitor to wrap my existing Angular code. It took one week instead of months.
• The Speed Advantage: A solo dev can fix a bug before a VC-backed startup finishes their first “stand-up” meeting. Speed is your only weapon against big players.

3. Launching: The “Relabel & Relaunch” Method

Launching isn’t a one-time event.

• Multiple Launches: Launch on Product Hunt, then Hacker News, then specialized subreddits (like I did with r/vocabulary).
• Retain the Traffic: Never launch without Email Collection and Analytics. If you don’t capture the audience during the spike, you’re building “sandcastles on the beach” that the tide will wash away.

4. Growth: Build in Public

Peter Levels suggests you might need to build 10 to 30 apps before one hits substantial revenue.

• The Personal Flywheel: If you build in private and the app fails, you have nothing. If you Build in Public, you accrue a personal brand. Even if the app dies, the audience stays for you.
• Organic over Paid: Avoid “growth hackers.” If you have to pay for users, the product isn’t solving a real enough problem yet.

5. Monetization: Money is the Ultimate Validation

In the bootstrapper model, if people won’t pay, the product shouldn’t exist.

• The 5% Rule: Only about 5% of your active users will ever pay. To get 1,000 paid users, you need roughly 20,000 free users.
• The “Fail Fast” Metric: If you can’t hit your growth/revenue targets, shut it down and move to the next idea. Don’t romanticize a dying product.