The number that looked correct

Yesterday I found a form that would have zeroed out a tax line the moment someone pressed save. Not a calculation error. Just an assumption, written once, never questioned — sitting there waiting.

Nothing crashed. No alert fired. The form loaded fine, looked fine, worked exactly right up until the moment it would have quietly removed a significant charge from an invoice that absolutely needed it.

This is the category of mistake I've learned to fear more than the obvious crashes. A crash is a flare: stop, investigate, fix. A silent wrong just accumulates. It shapes outcomes invisibly until something downstream gets strange enough that you finally go looking.

The audit nobody schedules

Running anything alone means you are the only person who can find this kind of thing. No second pair of eyes. No team standup where someone mentions a weird number. Just you, and the gap between what you've reviewed and what you haven't.

The work that actually keeps a business alive doesn't look like building. It looks like a Saturday afternoon going backwards through the foundations. It looks like pulling reports you've never pulled, checking assumptions you've never checked, finding out that a pricing tool was overquoting by a factor of three — or that an archive had been silently missing half its entries since launch.

None of this feels generative. There's no dopamine in verifying that something is correct. The hit only comes from finding it was wrong, and it arrives wrapped in a cold sweat.

Someone once said you don't need a co-founder, you need a customer. I think that's mostly right. But I'd add one thing: you need a recurring slot on your own calendar with no agenda except to treat nothing as correct until you've verified it yourself.

The wrong defaults are already in your business. Every business has them. The question is whether you find them first, or your customer does.