building in a vacuum
Months of heads-down building toward a launch nobody asked for. The most common, most expensive mistake there is.
The most common and most expensive mistake there is: disappear for six months, build the thing in your head, launch to silence. It feels like progress because you’re shipping. You’re shipping against a guess.
Coding is the comfort zone. Mine too. It’s quiet, it’s in your control, and nobody tells you no. Selling is the opposite — fifty cold calls a week and hearing no from forty-five of them. So founders hide in the build and call it work. When a team in my cohort tells me the next three months are for scaling the dataset and adding features, I tell them no: the next three months are ninety percent sales and ten percent product. The question that reveals whether you’re ready is simple — are you ready for fifty cold calls a week? The pause after that question is usually the whole answer.
The tell that you’re in a vacuum is that your evidence is all internal. Friends using it for free. A waitlist. Good session times. None of it survives contact with “will you pay.” A well-funded app once sent me beautiful analytics — thirty-three-minute sessions — and a retention floor of zero. Great numbers, empty bucket. Building the next feature wouldn’t have helped; the thing already didn’t hold water.
There’s a person this happens to: bright, fast, builds five products in a year — a bot, a location app, a billboard marketplace — all clever, all dead. He thought his problem was sales. His real problem was that every time he hit a wall he went and found a new wall, so he never learned where the first one was weak. A vacuum is also hiding from the one hard thing in front of you by starting something easier.
The shortest loop back to reality is a person who might pay, this week, and the single question of whether they will. Everything you’d build in the next six months, you can test in the next six days by trying to sell it.