I Read the Indie-Founder Canon Sixteen Years Late

Altitude: reading, colliding

Rob Walling wrote Start Small, Stay Small in 2010. I read it in 2026, sat by a pool, with a product already built. Which is, according to the book itself, exactly the wrong order. It says so early and often: product last, marketing first.

Reading the canon this late turns out to be its own kind of experiment. I'm not reading it to learn what to do. I already did most of it, in the wrong order, without permission. I'm reading it to find out which of its rules were laws and which were artifacts of 2010. The split is more interesting than I expected.

The three hats

Walling's minimum viable founder wears three hats: developer, webmaster, marketer. Wear all three or the economics of a self-funded product don't work. It's the book's honest gate, and in 2010 it would have kept me out entirely. Twenty years of programme management is a real trade; it just isn't any of those three. The book wasn't wrong to draw the gate; I simply couldn't have walked through it. Not "wouldn't have found it easy." Couldn't.

That's the first thing reading late teaches you: some of the advice you'd have failed wasn't advice at all, it was a description of the entry requirements. And entry requirements can expire. The craft gaps that gated me out (design, code at product quality, marketing copy that doesn't read like an engineer wrote it) closed in about two years, for reasons Walling couldn't have predicted and doesn't need to be blamed for. The three hats still exist. What changed is the cost of acquiring them: years each, then; months, now, for someone willing to work with the tools honestly.

Product last, marketing first

The book's most famous rule, and the one I broke completely. But read it closely and the rule is really about validation, not sequence: prove a market exists and that you can reach it before you bet everything on the build. The sequence was just the cheapest way to do that in 2010, when building was the expensive part.

I inverted it: built first, and I'm doing the validation now, niched content as an experiment across personas, watching which door converts. It's the same principle, run late and at higher cost, because the product already exists while the question "who is this for?" is still being answered. I won't pretend that's better. It's survivable now in a way it wasn't then, because the build didn't consume years of savings. But the principle held. Validation isn't a stage you skip; it's a bill that arrives regardless. I'm paying it in arrears, and it's the same honest question I asked myself in Who Would Want Another Task App?

The outsourcing chapter

And then there's the chapter that made me laugh by the pool: the virtual assistants. Walling's answer to the one-person-many-hats problem was to rent other people: VAs for support and admin, contractors for design, outsourced developers for what's beyond you. Drip itself was built with a hired developer alongside him.

It's simultaneously the most dated chapter and the most vindicated one. Dated, because nobody starting today solves those problems with a team of assistants across time zones. Vindicated, because the principle (a solo founder must delegate everything that isn't their edge) turned out to be the load-bearing insight of the whole book. The mechanism got swapped out from under it. I run his playbook daily; the assistants just aren't human anymore, they're models: cheaper, instant, no management overhead, and no two-day wait for a reply from another continent. He described the shape of the solution perfectly. He just couldn't have named the technology.

What survived, what expired

So here's my scorecard, sixteen years late. Expired: the entry requirements (the three hats are now acquirable, not gates), the specific channels (the SEO and AdWords tactics are period pieces), the mechanism of delegation. Survived, completely: validate before you bet everything, delegate what isn't your edge, niche the marketing not the product, and the quiet warning underneath all of it, that the hard part was never the building.

That last one I can now confirm from the field. The tools made building cheap. Nothing made deciding cheap. Walling knew that in 2010. It just took me building an entire product to find out he was right. The fifteen years of lived problem the book couldn't have accounted for is the subject of The Product Was Me.