The First One Is Always Bad

Every business I've been around looks obvious in hindsight and looked insane at the time. That gap is the whole story, and almost nobody writes about it while they're standing in it.

What you see from the outside is the finished version. The site that converts, the process that runs without anyone babysitting it, the number that went up. What you don't see is the eleven versions before it that didn't work, most of which were embarrassing enough that nobody kept a record.

I've started things that worked and things that didn't, and the pattern is the same either way: the first attempt is bad. Not "needs polish" bad. Actually bad. And the only people who get to a good version are the ones who were willing to ship the bad one first and let reality tell them what was wrong with it.

That's not a motivational point. It's a practical one. You cannot debug a thing that doesn't exist. Every hour spent planning in your head is an hour spent guessing, and your guesses are worse than the market's answer. Always, without exception.

Starting is an operations problem, not a courage problem

Most advice about starting is emotional. Be brave. Take the leap. Believe in yourself. I don't find that useful, because I've never met anyone whose problem was a shortage of belief. The problem is that "start a business" isn't a task. You can't do it. It's not on any calendar. So it sits there indefinitely while you do things that are tasks.

Everything I've actually gotten off the ground started when I stopped treating it as a decision and started treating it like any other piece of work: what is the smallest thing that has to exist by Friday, and what has to be true for that to happen.

You don't need to be ready. You need a deadline, one deliverable, and somebody who'll notice if it doesn't show up.

That's it. That's the whole mechanism. The reason it works is that it converts an identity question (am I the kind of person who does this) into a scheduling question, and scheduling questions have answers.

What "small" actually means

People hear "start small" and still build something that takes three months. Small means smaller than that:

• Not a company. One conversation with one person who might pay you.
• Not a system. One documented step of the thing you currently do from memory.
• Not a content strategy. One post, published, badly.

The point isn't that the small thing succeeds. The point is that it generates information. A real attempt, even a failed one, tells you more in a week than a month of thinking will, because it's the only way to find out which of your assumptions were actually load-bearing.

And there's a second-order effect worth naming. Once something exists, you stop arguing about whether to do it and start arguing about how to make it better. Those are completely different conversations, and only one of them goes anywhere.

---

So, this

Which brings me to why this post exists.

I've been meaning to write for a long time. I had the domain sitting there. I had a list of things I wanted to say. What I didn't have was a published post, which meant I had nothing, and I knew it every time I looked at the empty site.

I could have waited until I had a proper archive, a design I loved, a schedule I was confident I'd keep. I've watched myself do exactly that with other things, and the honest name for it is procrastination with a nicer vocabulary.

So this is the bad first version. It'll get better. I'm writing about the two things I actually know something about: building and running businesses, and building the systems underneath them. I'll be publishing regularly rather than waiting for pieces to feel finished.