The subscription line is the visible tenth of the tax. The rest compounds quietly: ceilings on what you can build, set by each vendor's product imagination; data locked in formats you cannot leave, which funds the pricing power used against you at every renewal; workflows bent to fit tools instead of tools bent to fit you; and an improvement loop that belongs to the landlord, in the exact era when improvement loops decide who compounds.
The anti-pattern is not using rented tools, which every sane business does; it is renting the load-bearing layer, the site, the instruments, the knowledge, where the tax falls on differentiation itself. The audit that reveals it takes an evening, and the era's collapse in build costs means the exits are finally affordable.
- The subscription is the tax's smallest line: ceilings, lock-in, workflow distortion, and the forfeited improvement loop carry the real weight.
- Lock-in funds the leverage used against you: proprietary formats convert your accumulated work into the vendor's pricing power.
- Workflow distortion is the invisible middle: businesses bend to their tools' shapes and forget which compromises were choices.
- The improvement-loop forfeit is the era's cost: rented surfaces improve on the vendor's schedule while owned code compounds with every model release.
- The tax concentrates on the load-bearing layer: rent the commodity plumbing cheerfully, and move the site, instruments, and knowledge to owned ground.
Skip the AI Course. Get It Installed.
The AI Native Activation is one working session. You leave with AI installed on your machine, loaded with your business, and producing real work the same day.
See the AI Native ActivationRather talk it through? Book a Rapid Transformation Call.
The subscription line hides the tax's real structure
Total a business's SaaS spend and you have measured the rent's visible tenth. The full structure, in ascending order of weight:
- The direct spend: real, growing a little each renewal, and the least of it. Most owners could double this line and lose less than any item below.
- The ceiling tax: everything you wanted to build and could not, because the tool's editor did not imagine it. Each declined improvement is invisible on any invoice and cumulative in every engine's answers.
- The lock-in tax: your data and configurations in proprietary formats, which converts leaving into rebuilding, and rebuilding-cost into the vendor's pricing power. You fund the leverage at every renewal you cannot credibly refuse.
- The distortion tax: workflows bent to the tool's shape, compromises made so long ago they read as how-we-work.
- The improvement-loop forfeit: the largest, newest line, covered below, because it is the one this era reprices.
The accounting habit that reveals it: for each load-bearing tool, ask not 'what does it cost' but 'what has it declined to let us become.' The second question is where the tax lives.
Lock-in converts your work into the landlord's leverage
The mechanism deserves slow-motion viewing, because businesses fund it against themselves. Every month of using a proprietary tool deposits accumulated work into the vendor's format: the pages built in their builder, the automations configured in their language, the records shaped to their schema. The deposits feel like progress, and they are, and they are also collateral.
At renewal, the collateral prices the exit: leaving means rebuilding the accumulation, so the vendor's increase is measured not against alternatives but against your rebuilding cost, which they know and you feel. The pattern is general enough to be a business model: acquire with generous tiers, deepen the deposits, then reprice the captives, and the recent history of SaaS is a museum of the pattern.
The defenses are structural, chosen at adoption rather than at renewal:
- Standard formats over proprietary ones, wherever the choice exists: files that any tool reads owe no landlord anything.
- The export habit: whatever must live in a tool gets copied out on a calendar, converting hostage-grade lock-in into inconvenience-grade.
- The walk-away test at procurement: 'how do we leave' asked before entering, because exits are cheap to preserve and expensive to excavate.
Owned assets skip the whole mechanism: files you hold collateralize nothing.
Workflow distortion: the business bends and forgets it bent
The subtlest line of the tax: rented tools impose their model of how work happens, and businesses conform, then forget the conformity was a compromise. The onboarding sequence shaped by what the email tool's automations allow. The client records structured by the CRM's fields rather than the practice's actual questions. The content calendar built around what the scheduler supports instead of what the strategy wants.
Each bend was rational in the moment, the tool could not do X, so the business stopped doing X, and the accumulation is a practice quietly running on the intersection of its vendors' imaginations. The tell that distortion has set in: process questions get answered with tool names. 'How do we onboard?' produces 'we use [platform]', which is an answer about the landlord's shape, not the business's judgment.
What the distortion costs in this era specifically: your captured method is supposed to be the business's differentiating asset, and a method that has spent years conforming to rented shapes has been sanded toward the same generic processes every other tenant runs. The audit is one evening: list your core workflows, and for each, write what it would look like if no tool constrained it. The gaps are the distortion, itemized, and most owners are startled by the list's length.
The improvement-loop forfeit is the tax the era repriced
The newest line dwarfs the old ones, because the era changed what infrastructure can do. Owned code now sits inside an improvement loop: your AI reads all of it, so upgrades ship weekly at conversation prices, and every model release makes the loop faster, the same shift that has non-developers shipping and a quarter of a recent Y Combinator cohort running almost entirely AI-generated codebases.
Rented surfaces forfeit the loop entirely: the vendor's product improves on the vendor's schedule, for all tenants identically, and your AI can touch only whatever surface the product exposes. The forfeit's price, quarter by quarter:
- The compounding gap: owned-core competitors ship structural improvements weekly, answer pages, schema depth, new instruments, while the rented business's equivalent list ages in a feature-request queue.
- The differentiation gap: vendor improvements arrive for every tenant at once, so nothing the platform ships can distinguish you from the other tenants running the identical upgrade.
- The intelligence gap: your AI's growing capability lands on whatever it can reach, and a business whose assets are behind vendor walls watches its own intelligence layer improve uselessly.
Five years ago the forfeit was theoretical, because nobody's AI was improving anything. Now it is the largest line on the ledger, and it compounds against the tenant.
Paying off the tax: the exit sequence
The exits are affordable now, and the sequence matters more than the speed:
- Sort the portfolio first: commodity plumbing, payments, email delivery, scheduling, stays rented cheerfully, because its tax is small and its alternatives are worse. The exits are for the load-bearing layer: the site, the method-instruments, the knowledge, the workflow glue that encodes how you work.
- Start with the knowledge, this month: the captured method, contexts, and standards into plain files you hold. Zero risk, immediate payoff, and it un-collateralizes the most important deposits.
- Move the site next: the primary machine-readable asset onto owned code, with redirects preserving history, which opens the improvement loop where it pays most.
- Rebuild the instruments as you touch them: each rented workflow that comes up for renewal or friction gets the one-question review, own or re-rent, decided on load rather than habit.
- Install the procurement discipline going forward: standard formats, export habits, walk-away tests, so the tax stops re-accumulating behind the exits.
A year of unhurried sequence converts the dangerous quadrant, and the felt change arrives earlier: the first weekly improvement your AI ships to your own site is the moment the tax becomes visible in reverse. Standing up the foundation of that year, the capture, the owned setup, the working loop, is exactly what our AI Native Activation session does.
The PLB Perspective
The rent metaphor is precise in a way most metaphors are not, and I push owners to take it literally: a business whose site, instruments, and knowledge live in vendors' products is a business operating out of leased premises where the landlord also owns the furniture, the filing cabinets, and the improvement rights. The monthly check is the smallest part of any lease like that. The lease terms are the business, and nobody reads them until renewal.
What makes this the right decade to pay off the tax is the asymmetry that opened: the costs of renting compound upward, every renewal, every ceiling, every quarter of forfeited improvement, while the cost of owning collapsed, from developer retainers to conversational maintenance. Renting everything used to be the only sane advice, because the ownership alternative was priced for enterprises. That inverted because the prices did, and advice that does not track its own premises becomes the tax's best friend.
And I will name the deepest line on the ledger, the one no audit column holds: renting the load-bearing layer teaches a business to think like a tenant, to ask what the tools allow rather than what the strategy wants, to experience its own infrastructure as weather. Ownership reverses the psychology along with the economics: the site becomes clay, the instruments become drafts of better instruments, and the owner starts asking what to build next, which is the question this whole era rewards. The tax was never just money. It was the habit of asking permission.
Cindy Anne Molchany · Founder
The commodity layer with compliance weight: payments, email delivery, authentication, calendars, video, accounting, solved problems where vendors' scale and security teams genuinely protect you, and where switching costs stay low because the data is standard. The keep-renting test has two parts: does it carry none of your differentiation, and could you leave within a month? Two yeses and the subscription is hygiene, not tax.
Price the exit, not the subscription: for each load-bearing tool, estimate the hours to rebuild what lives inside it, your pages, automations, records, in a portable form. That number is the collateral funding the vendor's pricing power, and it is also the ceiling on your negotiating position at renewal. Add the improvement backlog the tool has declined, and the annual figure usually embarrasses the subscription line it hides behind.
That trade description is a decade old: owned assets in the AI era maintain conversationally, describe the fix, review, ship, at hours per quarter for a well-scoped core, and the same loop that maintains also improves, which no subscription offers at any price. The honest modern trade is subscription fees plus ceilings plus lock-in against commodity hosting plus conversational upkeep, and the second bundle wins for the load-bearing layer.
Usually the website platform, because it holds the primary machine-readable asset and forfeits the most improvement-loop value, with the knowledge layer captured into owned files as the zero-risk prerequisite step. Instruments follow as their rented equivalents come up for friction. The order tracks load and loop-value, not subscription price, which is why the cheapest tools are often the last to go and the free ones sometimes first.
AI-Native means the business runs on a foundation designed for the AI era: expertise captured where AI can work from it, infrastructure you own, and AI acting inside workflows rather than waiting in a browser tab.
Four dividing lines: where the intelligence lives, who initiates the work, what accumulates, and what compounds. Usage is an activity that resets daily; native is a property of the business that appreciates.
Quieter than the hype suggests: a morning brief that wrote itself, work that starts from drafts instead of blanks, judgment moments arriving prepared, and an owner whose day is mostly the parts that need her.