The most expensive thing in your business is probably not a salary line or a software subscription. It's a rule nobody has questioned in three years. A default nobody remembers setting. An assumption you inherited from whoever came before you, or from a version of yourself that was operating under completely different conditions.
We keep watching this across different domain simultaneously and it keeps pointing at the same thing: the gap between the world a system was designed for and the world it's actually operating in is where the damage hides.
Consider what Peter Attia's team recently outlined about protein restriction in kidney care. For decades, patients with kidney disease were told to cut protein. The reasoning was sound for its era. But the research that built that rule came from a time before modern dialysis, before better biomarkers, before we understood the downstream cost of muscle loss in aging patients. The rule outlived its justification. Doctors are still handing it down because it was handed to them. Patients are paying for it with their bodies.
Now look at what's happening to your email. Security researchers have demonstrated that CSS inside an email can escape its intended boundary and manipulate the surrounding webmail interface, affecting Gmail, Outlook, Proton Mail and others. The entire webmail security model was built on a boundary assumption: that content inside a message stays inside the message. That assumption is now a liability. The defenses were real when they were designed. The attack surface evolved. The defenses didn't.
Seth Godin noticed the same tension from a different angle. He points to a village in Luxembourg where a farmer still ties a donkey to a bridge in the shadow of a major financial hub, and asks us to sit with that juxtaposition. Not mockingly. Seriously. The past and the future coexist, and the distance between them is not automatically resolved by time passing. The donkey is still there. The bridge carries both of them.
That image is useful because it resists the startup reflex to declare everything old as obviously wrong. Sometimes the old thing still works fine. The problem isn't age. The problem is when nobody checks whether the old thing still fits. When the rule becomes invisible. When the assumption becomes air.
Tom Vek is rebuilding a digital music player that takes streaming-era audio seriously as an experience, not just a utility. He's not building it out of nostalgia. He's building it because the assumption that convenience automatically equals a better product turned out to be wrong in ways that only became visible after a decade of living with the tradeoff. Streaming gave us everything and took something away we didn't notice until later. He noticed. He's doing something about it.
And over in founder-land, the community wisdom thread on what actually constitutes a moat when anyone can build the same features keeps circling back to the same uncomfortable answer: authenticity, trust, relationships, things that can't be copy-pasted from a competitor's product page. The assumption that product features are defensible is an old rule. The market keeps proving it wrong. The founders who keep acting on it keep losing their edge to people who figured this out two years earlier.
Here's the thread: the rules you're running on were written for a different environment. That's not a criticism. That's physics. Every system is tuned for the conditions it was born into. The danger isn't having old rules. The danger is treating them as permanent.
We see this constantly in the businesses we work with. The scrappiest founders, the ones doing $1M to $3M mostly on instinct and momentum, they're often running on assumptions they set when they had twelve customers and no recurring revenue. The pricing model made sense then. The support workflow made sense then. The "we don't really do contracts" policy made sense then. Now it's killing them slowly and they can't see it because the rule has become invisible.
The process for auditing this is almost embarrassingly simple. Pick any standing rule in your business, anything that happens the same way every time without anyone deciding it that week, and ask three questions. First: what problem was this solving when we created it? Second: does that problem still exist in the same form? Third: what would we do if we were setting this up for the first time today?
Most of the time, the answer to the third question is different from what you're actually doing. Sometimes radically different. That gap is the tax.
The medical establishment paid the protein-restriction tax in patient muscle mass for decades. Webmail providers are currently paying the CSS boundary tax in user security. Streaming platforms paid the experience-quality tax and handed that opening to anyone paying attention. Founders pay these taxes quietly, in conversion rates that don't quite close, in client relationships that erode, in pricing that leaves money on the table every single month.
Paying a tax you know about is a decision. Paying one you don't know about is just losing.
The best thing you can do this quarter isn't a new feature or a new campaign. It's an hour, maybe two, walking through the rules you've stopped questioning and asking whether they still fit the business you're actually running. Not the business you started. The one you have now.
The world you built your defaults for is gone. The donkey is still on the bridge. That's fine. Just make sure it's there because you chose it, not because nobody remembered to check.