A friend laid out her plan for a new cleaning business the other day, and the simplicity of it stopped me. Four homes. Cleaned for free. The only ask: a review from each one, honest, positive or negative. That's the entire launch.

No procedures manual, no pricing strategy, no brand positioning research. She'll learn her prices, her process, what clients actually want, which supplies to use, whether there's demand for organic products, all of it from inside four real kitchens. By the time she charges her fifth client, she'll know more about running her cleaning business than months of planning would have taught her.

I sat there thinking about what I did when I started mine. The distance between her approach and mine felt like a lesson I'd already learned and somehow kept forgetting.

What she described has a name in the software world: building in public. You start before the answers exist and you let the real work fill in the blanks.

It works in any business, because the thing you learn from real work is different from the thing you learn from planning. Planning teaches you what you think will happen. Doing teaches you what actually does. And the gap between those two is usually wide enough to throw out most of the plan.

I took the opposite path. From the time I went all in on building this business, I spent the better part of two years in a cycle of building systems and developing procedures and setting up tools for a version of the business that hadn't arrived yet.

When clients showed up and the real work started, the reality was different from the plan. The processes I actually ended up needing showed up through doing the work, and the ones I'd built in advance mostly gathered dust. Hours I could have spent with real clients, learning real answers, spent instead on plans for a business I'd imagined.

That would be a useful lesson if it only happened once. The same pattern, every time I took on something new: the business, the content system, whatever the next big build was. Spend months getting everything in place, and then watch the real version reveal itself the moment the work actually starts.

And what I keep coming back to, and this is the part that took the longest to see, is that fear sits underneath most of that building. You build the elaborate system because shipping the imperfect version is uncomfortable, because starting before you have all the answers means sitting with the uncertainty of not knowing how things will go, and that discomfort is real, but what sits on the other side of it is every piece of data you actually need.

So you delay. And the delay looks productive because you're building something. But the thing you're building is for a business that only exists in your head.

There is a balance and I want to be honest about it. The content system I built to hold up against a real publishing schedule, the one designed to keep me from burning out at volume, that was a real decision and it holds. You do need structure for a load you can see coming. But building a system for a load you haven't felt yet, from assumptions about work you haven't started, that's where the waste lives.

This newsletter is where the pattern changes. It ships before the first Episode. Before the content pipeline has been tested at full cadence. Before every piece is dialed in. Because the alternative is the same thing it has always been for me: another few months refining a launch plan while the real data, the kind that only comes from sending something and seeing what lands, sits on the other side of pressing send.

What does a reader respond to in a newsletter like this? What's the right length for something that lands in an inbox between breakfast and a first meeting? I have guesses. The answers come from sending.

The real system comes from doing the work. My friend had it from the start. It took me years of over-building to see it.

Her plan is four homes and one ask per home. Mine is one issue and one ask per issue. Both of us shipping before we feel ready.

Are you still building toward the thing, or have you already started doing it? Reply BUILDING or STARTED.