Architects of Dependence: How We Became Tenants in Our Own Systems

PART I: THE SCREEN

They Sold You a Moat. It Was a Puddle.

Basketball fans know this play.

Michael Jordan wants the hoop. Scottie Pippen sets a screen on Isiah Thomas. While Pippen and Thomas fuss with each other... elbows, hips, jaws working... Jordan drives the lane and scores. The screen’s entire purpose is to occupy the defender with a confrontation that feels urgent but is, by design, a distraction. The ball was never where the fuss was. The fuss was the point.

If you’ve read my earlier work, you know I use this metaphor when the machinery of distraction needs naming. I used it for partisan politics. I’m using it again now, because the enterprise software industry has been running this exact play on its customers for two decades. And the customers are only just now looking up from the fuss to notice that the ball is gone.

The screen in enterprise software has many moving parts, and every one of them was designed to keep you occupied while the real play happened somewhere else.

Per-seat pricing. Multi-year contracts with auto-renewal clauses buried in paragraph fourteen. “Enterprise-grade” feature gates that locked basic functionality behind pricing tiers named after precious metals. Certification programs that trained your employees to depend on the vendor’s ecosystem. Implementation consultants who billed $300 an hour to configure software that should have been configurable out of the box. Integration specialists. Migration specialists. Optimization specialists. An entire cottage industry of specialists whose job was to make the simple complicated enough to justify their invoices.

All of it... every contract, every gate, every certification, every specialist... was designed to make you believe one thing: that what the enterprise does requires the enterprise’s infrastructure. That the problems are too complex. The data too sensitive. The workflows too mission-critical. The compliance requirements too intricate. That you, the small team, the solo operator, the thirty-person shop, could not possibly replicate what the platform provides.

While you fussed with vendor lock-in and eighteen-month implementation cycles and the annual pricing “adjustment” that somehow always adjusted upward, the real play was happening: AI capabilities were becoming API calls. The moat around enterprise intelligence was evaporating molecule by molecule. And nobody told you, because the moat was where the money was.

Were their motives noble, they would not need subterfuge.

That’s from an earlier series, and I’m bringing it back because it has never been more precisely applicable than it is right now. The subterfuge was the screen. The screen was the pricing model. And the pricing model just met its executioner.

The Seat Compression

The math is not complicated. I need you to sit with it for a moment because its simplicity is the whole point.

A company has ten analysts using Salesforce. Ten seats. Ten licenses. Ten monthly payments. The platform charges per human who logs in. The revenue model scales with headcount. More humans, more seats, more money. This is the engine that built a $72 billion remaining performance obligation and a stock price that once commanded thirty times forward earnings.

Now: an AI agent handles what those ten analysts used to do. The data entry. The pipeline management. The reporting. The follow-up cadences. Not all of it perfectly... not yet... but enough. Enough that the ten seats become three. Maybe two. The platform still runs. The CRM still holds the data. The invoice shrinks by seventy percent.

That’s not disruption. That’s arithmetic.

Atlassian lost thirty-five percent of its market value. Salesforce lost twenty-eight percent. Not because their software stopped working. Because the humans who paid for it stopped being necessary in the same numbers. Wall Street’s term for this is “seat compression,” and the name is apt. The seat is being compressed. The human is being compressed out of it.

The question CIOs are asking now is not “How many employees will use this tool?” It’s “How many tasks can this AI complete?” That’s not a pricing adjustment. That’s an extinction event for the per-seat model. The unit of value is no longer the human who logs in. It’s the task that gets done. And tasks don’t need logins.

The Commoditization of Intelligence

On January 30th, 2026, Anthropic pushed eleven open-source AI plugins to GitHub.

Not a new model. Not a benchmark. Not a research paper with promising charts. Eleven functional tools that could autonomously handle legal reviews, financial reconciliation, sales pipelines, and customer support. End to end. No human required. No enterprise license required. No implementation consultant required. Open source. Free.

Four days later, $285 billion in software market value was gone.

The market did not panic because of what the plugins did. The market panicked because of what the plugins proved: the intelligence locked behind enterprise paywalls was never the moat. It was never proprietary. It was never the thing that justified $200 per seat per month. The intelligence was increasingly commoditized, available to anyone with an API key and a weekend.

The moat was the data. Your customer records. Your transaction history. Your compliance logs. Your institutional memory. That was always the real asset, and you were paying the vendor to sit on top of it and charge you rent to access your own property.

AI agents don’t need the vendor’s user interface to get to that data. They need the API. They need the database connection. They need the export. And once they have it, the $200-a-seat dashboard becomes a window you don’t need to look through anymore, because the agent is already inside the house.

The industry has a phrase for what’s happening, and it’s the most honest thing the enterprise software world has said in years: not one shark, but thousands of piranhas. Each micro-tool replaces a narrow feature. Each AI agent automates a specific workflow. Individually, they’re small. Collectively, over time, enough feature slices hollow out entire products. The shark was the enterprise platform. The piranhas are the solo developers, the two-person startups, the citizen developers with no-code tools and AI agents who are building surgical instruments while the giants are still sharpening Swiss Army knives.

The Defection

Klarna replaced Salesforce with a homegrown AI stack.

Read that again.

One of the most complex CRM operations in fintech... a company processing millions of transactions across multiple countries with regulatory requirements that would make a compliance officer weep... looked at the biggest CRM on earth and said: we can build something better ourselves. Faster. Cheaper. More aligned with how our business actually works instead of how Salesforce thinks our business should work.

And they did.

That’s not an anomaly. That’s a leading indicator. When a fintech unicorn walks away from the most entrenched CRM in the world, it tells you something about what’s possible. And everywhere, in every enterprise procurement office, the same question is surfacing as 2026 renewals come due: can an AI agent deliver the same value for a fraction of the cost?

The answer, increasingly, is yes. Not perfectly. Not yet for every use case. But sufficiently. Sufficiently for the CFO to notice. Sufficiently for the renewal conversation to become a renegotiation. Sufficiently for the vendor to hear a word they have not heard in two decades of subscription dominance: no.

The Subterfuge

Here is where I need you to pay very close attention, because this is the part that should make you angry.

The enterprise vendors are raising prices. Twenty percent. Thirty percent. Some as high as thirty-seven percent. They are calling it an “AI surcharge.” An “innovation fee.” A “platform enhancement adjustment.” The language varies. The play does not. They are charging you more for the software while simultaneously proving... by their own AI product launches, by their own earnings-call language about “agentic transformation”... that you need the software less.

They’re charging you more for software while simultaneously proving you need it less. Tattoo that somewhere.

This is the screen at its most elegant. The AI surcharge is not a fee for new capability. It’s a fee for the privilege of remaining locked in while the lock is being picked from the outside. It’s the hotel minibar model: charge $14 for a Coke because the customer is captive and the alternative requires putting on pants and walking to a gas station. Except now, the gas station delivers. For free. And the Coke is better.

The enterprise vendors know this. Their earnings calls are full of the language of adaptation... “agentic workflows,” “AI-native architecture,” “outcome-based value delivery.” They are pivoting as fast as organizations of their size can pivot, which is to say: not fast enough. Because the piranhas don’t wait for your quarterly roadmap review. They ship on Tuesday.

The Complexity Mystique

Now I need to name the deepest screen of all. The one that survives even after the pricing model dies and the seat compression finishes and the piranhas have had their meal. The one that will be the enterprise vendors’ last line of defense, and the one they’re already retreating to.

The complexity mystique.

It goes like this: Fine, maybe AI can handle the simple stuff. Maybe a solo developer can build a landing page or a scheduling tool or a basic CRM. But enterprise software... real enterprise software... includes compliance infrastructure. Security layers. Governance protocols. Audit trails. Multi-system integrations. Role-based access control. Disaster recovery. Business continuity. Session management. Data residency requirements. These are serious, complex, regulated concerns that require serious, complex, expensive infrastructure.

Every word of that is true.

And here’s the part they don’t want you to hear: every one of those capabilities is increasingly reproducible by a competent developer with the right AI agents and a clear governance protocol.

Compliance infrastructure? That’s a checkpoint file and a convention. Audit trails? That’s a logging pipeline and an immutable data store. Governance? That’s a cascading set of rules that every session reads before it touches anything. Business continuity? That’s a protocol that says every session writes its state to permanent storage before it ends, every new session reads the last checkpoint before it starts, and no work is ever batched to the end where a timeout can destroy it. Disaster recovery? That’s a filesystem rule: write to permanent storage immediately, verify the write landed, never trust the ephemeral.

The mystique was that these things were inherently complex. That they required teams of specialists and six-figure consulting engagements and quarterly governance reviews in conference rooms with whiteboards and catered lunch. The reality is they were made complex. Made complex to justify the price. Made complex to maintain the screen.

A four-level cascading governance protocol... global rules, shared conventions, family-level standards, project-specific instructions... is not a six-month Deloitte engagement. It’s a hierarchy of markdown files and the discipline to follow them. It is, in fact, the same pattern as a legal system: constitutional law, federal statutes, state law, local ordinance. We figured out the architecture centuries ago. The enterprise vendors just repackaged it in Confluence and charged you a subscription.

I’m telling you all of this... the seat compression, the commoditized intelligence, Klarna’s defection, the AI surcharge subterfuge, the complexity mystique... because you need to understand what the screen was hiding before I show you what’s on the other side of it.

The screen was hiding a fact so simple that the entire enterprise software industry was built on the hope you’d never notice it:

The enterprise was never a capability. It was a price. And the price just got undercut by a developer with a Mac Mini and a governance protocol that fits in a Git repository.

In Part II, I’m going to show you the governance protocol. Not abstractly. Not theoretically. The actual architecture. Twenty codebases. Three families. Eighty-three cron jobs. Sixteen namespaces. Four levels of governance. Every dependency chain. Every session handoff rule. Every anti-pattern guardrail. The full topology of a one-person enterprise that does what most IT departments need a floor of an office building to do.

And I’m going to show you the gaps, too. Because this is not a commercial. It’s a receipt.

The moat was a puddle.

The screen just got pulled down.

Look at what’s behind it.