Book notes · Bootstrapping· 5 min read

Start Small, Stay Small: the book for developers who want to launch

Start Small, Stay Small from Rob Walling came out in 2010, and it is still one of the books I recommend the most to developers who want to launch something on their own. It is written exactly for that person: you can build, you have no funding, and you dont want to raise any.

The book is old, some tactics are a bit outdated. But the core idea is more relevant than ever, and it is the same idea the whole course is build on: distribution before product.

The bookStart Small, Stay Small· Rob Walling↗

What the book is about

Walling calls his reader a "micropreneur". Someone who builds a small, self-funded software business, often alone, often next to a job. The goal is not the next unicorn. The goal is a product that pays the bills and gives you freedom.

And for that you need a very different playbook than the startup world tells you. No big vision deck, no growth at all costs. Small niche, real demand, cheap marketing.

The key ideas

  • ▸Market first, product second. Most developers start with the product idea and look for buyers later. Walling says turn it around, find a market with a real problem and people who already spend money, then build for them.
  • ▸Pick a niche. A small market that the big players ignore is not a weakness, for a solo founder its the advantage. Less competition, easier to reach, easier to be the best.
  • ▸Test the demand before you build. Landing page, a few keywords, see if anybody shows interest. Months of coding for a product nobody wants is the most expensive mistake there is.
  • ▸Marketing is part of the product. If you can not say how you reach your customers, you dont have a business yet, you have a hobby project.

How it connects to the course

The opening of the course says it pretty direct: the default playbook is build for months, then go find "someone for marketing". Start Small, Stay Small is basically the long version of why this does not work.

Also the idea to pick your channel on day one, and to validate before you code, comes straight from this way of thinking. If you liked lesson 6 (smoke test, prototype, concierge), you will like this book.

Who should read it

Developers who want to build a small, bootstrapped SaaS and have not launched anything yet. If you already have paying customers and want to scale, the SaaS Playbook from the same author is the better next step.

↗Coaching

Don't do it alone.

Get direct feedback on your product, your motion and your first channels. One-on-one, or together with a small cohort of builders.

Book individual coaching

Your motion

I'll reply personally by email.

More articles

Go-to-market · PLG

Product-led growth: when the product sells itself

What product-led growth (PLG) really means, where it enters the funnel, which channels it runs on, what price it needs and how to test if PLG works for your SaaS before you build.

6 min read →

Go-to-market · SLG

Sales-led growth: when a human sells

What sales-led growth (SLG) means for SaaS: where it enters the funnel, the channels it runs on, why it needs a few thousand per account and how to validate SLG with ten calls.

6 min read →

Go-to-market · Enterprise

Enterprise: selling top-down to big accounts

How enterprise SaaS sales works: top-down selling to leadership, many stakeholders, 12 to 14 month cycles, $50k+ contracts, and the honest checklist before you go enterprise.

6 min read →

Go-to-market · Comparison

PLG vs SLG: product-led and sales-led growth compared

PLG vs SLG side by side: how product-led and sales-led growth differ in funnel entry, channels, pricing, buyer pain and the skills they ask from the founder.

5 min read →

Go-to-market · Decision

PLG or SLG? How to choose your go-to-market motion

A step-by-step way to decide between product-led (PLG) and sales-led (SLG) growth: define the job, rate the pain, check your market, do the price math and be honest about yourself.

6 min read →

Go-to-market · Strategy

Distribution > Product: why marketing is a day-one decision

Why software builders must pick their distribution channel before they write code: how the go-to-market motion decides price, channels and what you build first.

5 min read →

Book notes · Validation

The Right It: test the idea before you build it

Notes on The Right It by Alberto Savoia: why most new products fail, what pretotyping is, the XYZ hypothesis and how to collect your own data before writing code.

6 min read →

Book notes · SaaS

The SaaS Playbook: building a SaaS without venture capital

Notes on The SaaS Playbook by Rob Walling: the operator manual for bootstrapped SaaS founders, from the first customers to a profitable, multimillion-dollar business without VC.

5 min read →

Book notes · Jobs to Be Done

Jobs to Be Done: why people hire your product

Notes on Jobs to Be Done: Theory to Practice by Anthony Ulwick: the job as the unit of analysis, job maps, desired outcomes and how to find underserved needs for your SaaS.

6 min read →