The fastest, cheapest build is rarely the cheapest one to live with. A look at the long-tail cost of shortcuts founders take when they're trying to ship.
§The Three Hidden Bills
- The support bill — every shortcut becomes a ticket in three months.
- The retention bill — users churn quietly long before they file complaints.
- The rewrite bill — the one that eats your Series A.
§The 30/60/90 Test
Before we ship a shortcut, we ask three questions. At day 30, will I be glad I did this? At day 60, will I have to explain this to a new engineer? At day 90, will this be the reason we can't add the next feature? Two yeses out of three is usually a no.
Software has a half-life. The cheaper you build it, the shorter it gets.
§Where We Spend, Where We Don't
We don't try to make everything bulletproof — that's a different mistake. Our internal rule of thumb: invest in the seams (auth, data model, payments, deploys) and stay cheap at the surface (marketing copy, secondary flows, internal admin).
§The Compounding Math
A shortcut that costs ten extra minutes per ticket, hit a thousand times, is a hundred and sixty engineering hours. That's a full sprint your team doesn't get back. The cheapest software is the kind you don't have to apologize for at retro.
§Buying Time Is a Real Strategy
Sometimes shipping the shortcut is right. The mistake isn't taking the shortcut — it's not writing down what you took, and what it'll cost when you replace it. The TODO comment that nobody reads is the most expensive line in the codebase.
