Shipping

The instinct is to wait. Finish it. Polish it. Make it good before anyone sees it. The problem is that “good” is a moving target you can’t hit without outside eyes — so you polish in private, forever, and the thing never ships. The fix is uncomfortable and it works: ship the half-done thing, on purpose, and let real feedback do the editing you can’t do alone. Why “done in private” is a trap Polishing in private has two hidden costs that usually don’t show up on any timeline: ...

The advice is always to “go all in.” Quit the job, burn the boats, commit fully. But most people can’t — and most people who do still need the bridge that comes before the leap. So here’s the less romantic, far more useful system: ship on evenings and weekends, in the margins, and let the calendar do the heavy lifting. The honest calendar math A side project doesn’t die from a lack of passion. It dies from a lack of time to show up consistently. So the first move is brutal and clarifying: count the actual hours. ...

Everyone wants the breakthrough — the big launch, the viral hit, the overnight success. And everyone quietly knows that’s not how it works. What actually works is so boring it gets ignored: ship one tiny thing, every single week, without fail. The system doesn’t sound impressive. That’s the point. It’s the unglamorous, compounding engine that separates people who have a body of work from people who want one. Here’s the whole thing. ...

Ask someone what it costs to build a product solo and they’ll name the visible line items: a coding-tool subscription, an API bill, a domain, maybe a designer. Those are the cheap parts, and they total to less than you think. The expensive parts never show up on an invoice. They’re time, attention, and the quiet load of being the only decision-maker. This is the honest accounting no one gives you before you start — and it matters, because the thing that actually sinks solo projects isn’t running out of money. It’s misreading what the real cost is. ...

Every solo builder knows the rhythm. Week one is electric: the idea is alive, the first build session flies by, you can already see the finished thing. Week two is momentum. Then week three arrives, and with it a specific, quiet death. The project doesn’t fail at the hard part. It fails in week three — when the novelty has worn off, the ugly middle has begun, and the end is suddenly very far away. This is the pattern, and it’s more predictable than anyone wants to admit. Here’s why it happens, and the system that gets you through it. ...

For two decades, having an idea and wanting to ship it meant a familiar list of reasons to wait: find a co-founder, hire an engineer, raise money, build a network. “Solo founder” was shorthand for couldn’t find a co-founder. One person with an idea was treated as a freelancer with delusions of grandeur, not a real company. That wall is gone. In 2026, the honest reason not to ship has been quietly dismantled — not by a hype cycle, but by a measurable collapse in the cost of building software. The tooling changed underneath us, and the data says so. This post is the case for why, if you have an idea now, nothing should stop you — with the receipts, and the honest limits. ...