The last time you build this

Yesterday I spent a few hours on something I've done three or four times before — setting up the same kind of tool, for the same kind of purpose, in slightly different ways each time. This time I built it properly. Wrote the template. Locked in the pattern. Made it so the next version takes twenty minutes instead of an afternoon.

I should have done it the second time. Maybe the third. Instead I did it the fourth.

That's not a confession of failure. That's how systems actually get built in a solo business. The first version is a prototype. The second is a patch on the prototype. The third is when you start feeling the weight of the improvisation. The fourth — if you're paying attention — is the one you build right.

There's a line I keep coming back to: it's not important to get it right the first time; it's vitally important to get it right the last time. I used to read that as permission to be sloppy early. Now I read it as an instruction: decide when the last time is. Don't drift into the fourth version — choose it. Make it the one that counts.

The alternative is permanent improvisation. And permanent improvisation feels productive right up until you notice you're a full-time workaround for problems you've already solved, more or less, two or three times before.

The builder and the operator are the same person

When you run everything yourself, you are both the one building the system and the one operating it. That means every hour you spend doing instead of systematizing is an hour you'll spend doing again. The ratio tilts slowly. You don't see it until you're spending half your week on things that used to take a fraction of it.

The discipline is recognizing the moment when the thing you're doing should become the template. Not because you're scaling, not because you're adding staff — just because you'll do it again. That's enough reason.

Yesterday was that moment for me. I built the version I won't have to rebuild.