Working is not the same as done
Something that runs correctly and something that's finished are not the same thing, and the gap between them is where solo businesses quietly accumulate risk.
There's a category of work I keep underestimating: things that run correctly but aren't finished.
I found several of them yesterday. Scripts that had been doing their job for weeks, living outside any trackable record of the project — functional, verified, invisible to anyone but me. A security flaw that had been in place long enough to feel normal. Tools that helped real users but existed nowhere that a future version of me could find and trust. They worked. They were not done.
This distinction trips up founders more than it should. You build something, it solves the problem, you move on. Working starts to feel like a synonym for finished. It isn't.
Something is finished when it can survive you. When it's been made legible — to a collaborator, to your future self in three months, to the system that needs to know it exists. A fix applied once, in one place, is not finished until it's the kind of fix that doesn't need to be applied again.
The first time is research
There's a line I keep returning to: It's not at all important to get it right the first time. It's vitally important to get it right the last time.
Most entrepreneurs treat this backwards. They worry about the launch, the v1, the first sale, as if correctness is a function of how carefully they built the original. But the first version is almost always wrong in some dimension you couldn't see yet. Correctness doesn't happen then. It accumulates.
One of the things I was working with yesterday had logged roughly 18,000 past corrections — every time someone used it imperfectly, the imperfection was recorded. And then, all at once, those 18,000 mistakes became the material that made the system smart. Accurate enough to matter. The first 18,000 uses weren't wasted. They were the research.
That's the shape of a solo business too. You don't get to spend your early years in perfection. You spend them in correction. The discipline isn't getting the first version right — it's staying in the room long enough that your eventual right version is actually earned, not lucky.
Work that's running isn't done. Done means it will still be right when you're not watching.