Essay // July 2026
The Gap Economy
Somewhere in your business right now, there is a subscription nobody needs. It has been renewing automatically for two, maybe three years. The person who signed up for it left. The person paying the invoice doesn't know what it does. The person who knows what it does doesn't know it's still active. Nobody canceled it because noticing it cost more than paying for it.
That account is not an anomaly. It is a business model.
A layer becomes profitable when it lives in the space between what one party knows and what the other can be bothered to find out. The real estate agent doesn't earn their commission because they're uniquely skilled at paperwork — they earn it because the gap between what they know and what you know is wide enough that paying them costs less than closing it yourself. Every B2B vendor with an auto-renewal clause, every middleman who controls access to a network, every coordinator whose value is knowing who to call — all of them are extracting a toll from a gap. Not creating value. Maintaining distance.
What makes this uncomfortable is that attention asymmetry sits upstream of information asymmetry. The unused subscription survives not because the information about it is hidden — it's in the invoice, it's in the product, it's accessible to anyone who looks. It survives because scrutiny never reaches it. The CEO would cancel it in thirty seconds if it crossed their desk. It never does. The hierarchy dilutes attention on its way down until nobody with enough context to care is looking at the thing worth scrutinizing. That gap — between what someone would do if they knew and what actually happens because they don't notice — is where an enormous amount of the economy quietly lives.
The same dynamic runs inside companies, just at smaller scale. Budget, headcount, influence, relevance are all scarce and competed for continuously, and a fast product ship isn't just a market move — it's an internal resource reallocation event. The teams who benefit from how things currently work have both the most to lose from moving fast and, after years of accumulation, the most political leverage to slow things down. This is why companies older than ten years almost never ship fast, and it has nothing to do with technical capability. The constraint is the accumulated weight of people whose authority is load-bearing on the current architecture. The moat faces outward. The anchor faces in.
Cydia is the cleanest illustration of what this costs. Jailbreakers had widgets, multitasking, and custom interfaces years before Apple shipped them as innovations. The capability was never the invention — the packaging and permission were. Every major iOS release was Apple closing a gap that an underground community had already crossed, monetizing the distance between what their engineers knew was possible and what their business model allowed them to release. The capability sat there, fully formed, and the mainstream user had no idea. The discrepancy between what is and what could be, at any given moment in any given industry, is almost always staggering to anyone willing to look directly at it. The gap is the product.
AI doesn't introduce new capability so much as it introduces a new cost structure for crossing gaps — and it's doing it simultaneously, across every dimension that made gap maintenance profitable. Information, attention, access, coordination: the attack is not sequential. Previous disruptions collapsed one layer at a time and let the system restabilize around new intermediaries before the next wave arrived. This one doesn't allow for restabilization. The rate of change is itself accelerating, and systems built for a particular trajectory have no preparation for the trajectory bending. You can adapt to a new normal. You cannot adapt to a normal that keeps accelerating.
What's left when the layers finish collapsing is first principles. Seller and buyer. Party A and party B. Not because the world becomes simple, but because every layer that couldn't justify itself under direct scrutiny finally stops being able to avoid it.
That's the whole story. Everything else was gap maintenance.