You don't own your software — you rent it, and the rent compounds: the SaaS subscription tax
Renting your stack feels cheap because the first invoice is small. But the per-seat subscription is a curve that bends against you — every new hire, every tool, every renewal adds rent you pay forever, and roughly a third of it buys nothing. Owning the system flips the curve: you pay to build once, then the next user costs almost nothing, and the asset is yours.
The subscription model won because the first invoice is small. Instead of paying to build or buy a system outright, you pay a little per user per month and you are live by Friday — no big cheque, no project, no risk. That trade is genuinely good when you are starting out, and it is why almost every business now runs on rented software. The catch is hidden in the shape of the deal. A subscription is not a price; it is a curve. It starts low and it bends upward, because the thing you are renting is priced per seat and per month — so it grows with your headcount, with the number of tools you add to cover the gaps, and with every renewal that quietly steps up. You did not buy a tool. You signed up to pay rent for as long as you are in business, on terms that get more expensive precisely as you succeed.
At the level of the whole business, that curve has gotten steep. The average company now runs 106 separate SaaS applications [1], and worldwide spending on them passed 299 billion dollars in 2025, up almost 20 percent in a single year [2]. The number that should stop an operator cold is not the total, though — it is the leak. Across organisations, roughly 36 percent of the SaaS licenses they pay for are never used, which works out to about 19.8 million dollars a year, per organisation, spent on software nobody opens [3]. Gartner puts the same finding in plainer terms: about a quarter of every dollar spent on SaaS goes to unused or underused software [4]. You are not just renting; you are renting more than you use, and you cannot see how much because the bills arrive separately, monthly, from a dozen different vendors.
This piece is not an argument against SaaS — renting is the right call for plenty of things, and we will say where. It is an argument about ownership: about understanding that a subscription stack is a cost curve you have agreed to ride upward forever, that a meaningful slice of it is pure waste by the time you are a real company, and that for the systems your business actually runs on, there is a different curve available — one you own, that bends the other way.
Start with why the rent compounds, because the per-seat model is engineered to. When you rent software, the vendor's price is tied to the two things you most want to grow: how many people use it and how long you keep using it. So the bill rises automatically with your headcount — every hire is another seat on every tool they touch — and it rises again at renewal, when last year's introductory rate steps up. Then it rises a third way that nobody plans: tool sprawl. A subscription is cheap enough that any team can add one to fix a single problem, so they do, and the average company ends up running 106 of them [1]. Each one is individually defensible and collectively a fortune, and because they are billed separately, no single invoice ever looks alarming. That is the trap in one sentence: the cost is large, but it never arrives large.
Now the part that turns a fair deal into a bad one — the waste. Independent measurement of real SaaS portfolios finds that roughly 36 percent of the licenses companies pay for are simply never used: the employee left, the project ended, the team switched tools, but the seats keep billing [3]. That is not an edge case; it averages out to about 19.8 million dollars a year for a large organisation, and about 1,739 dollars per employee per year, spent on software nobody opens [3]. Gartner reaches the same place from the top down — roughly 25 percent of all SaaS spend goes to unused or underused entitlements and overlapping tools [4]. Read those two numbers together and the picture is stark: you are riding a cost curve upward, and a quarter to a third of what you pay at every point on that curve is buying you nothing at all.
The reason the waste survives is structural, not careless. When your business runs on rented tools, no one owns the total. Finance sees a row of small recurring charges; each department sees a tool it needs; nobody sees the 106-app portfolio as one number with a third of it dark. Worse, you usually cannot just turn the waste off — multi-year contracts, auto-renewals, and the data trapped inside each tool mean cancelling an app you have outgrown is itself a project [1]. So the leak persists not because people are wasteful but because the architecture of renting hides the total and raises the cost of leaving. The subscription that was frictionless to start becomes expensive to stop.
Set against that is the curve almost nobody draws on the whiteboard: ownership. When you build the system your business actually runs on, the cost arrives the other way around — high at the start, because building is real work, then almost flat, because the marginal cost of the next user, the next record, the next small feature is close to zero. You are not paying per seat; you are paying for infrastructure that does not care whether ten people or a hundred use it. The two curves — rising rent, flat ownership — cross somewhere, and where they cross is the whole decision. For a tool you will use lightly for a year, the rent never reaches the crossover and renting wins easily. For the system at the centre of your business that you will run for a decade and grow headcount on, the rented curve sails past the build cost and keeps climbing, while the owned one sits flat underneath it [2].
So the operator's test is not "build or buy" in the abstract — it is which side of the crossover each system lives on. Three questions sort it fast. First, is this core or peripheral? Rent the peripheral things — email, video calls, accounting, the tools every business uses the same way; there is no edge in owning them and the vendor's scale beats yours. Own the things that are how your business specifically works: the CRM that holds your pipeline, the operations system that runs your jobs, the customer-facing app that is your product. Second, how long and how wide? The longer you will run it and the more seats it will grow to, the further past the crossover renting carries you. Third, what does leaving cost? If your most important data lives inside someone else's tool on someone else's terms, you do not own your business's memory — you are renting that too. The subscription model is a brilliant way to start and a quietly punishing way to run a business at scale. Rent what is common and cheap to leave. Own what is core, long-lived, and yours — and stop paying rent on the curve that only bends one way.
The default modern view: subscriptions mean no upfront cost, no maintenance burden, automatic updates, and someone else on call at 3am. Building is slow, risky, and you become responsible for it forever. There is a lot of truth here, and for most software a business touches it is the right answer — nobody should build their own email or video conferencing. The blind spot is treating it as a universal law. "No upfront cost" is not the same as "cheap"; it is the cost deferred and spread, and on a long enough timeline, spread-forever beats paid-once only until it doesn't. Camp A is right about the periphery and wrong to extend the rule to the core.
The reaction camp, often arriving after a renewal shock: add up five years of per-seat fees, compare it to a one-time build, and renting looks like a slow robbery. The arithmetic is real for the right systems — but the camp overreaches by ignoring what the rent actually pays for. A subscription is not only software; it is hosting, security patches, uptime, support, and continuous improvement you would otherwise have to fund yourself. Build everything and you do not escape cost, you just move it onto your own plate and call it free. Ownership wins decisively for core, long-lived systems; for everything else, "just build it" trades a predictable bill for an unbounded responsibility.
The position we hold: there is no single answer, only a line you draw tool by tool. For each system, ask where it sits on the cost crossover — peripheral and short-lived stays rented, because the rent never catches the build; core, long-lived, and headcount-scaling gets owned, because the rented curve runs away from you. The job is not to pick a side but to see the whole portfolio as one number, know which third of it is dark, and consciously decide which systems are worth owning. Most businesses have never drawn the line at all — they rent everything by default and discover the curve only when the invoices finally add up.
Camp A is right about the 90 percent of tools that are common, peripheral, and cheap to leave — rent those without guilt. Camp B is right about the handful of systems your business actually runs on — own those before the rent curve runs away. The mistake is applying either rule to everything. Draw the line deliberately: subscribe to what is common, build what is core, and never let a stack of small recurring charges become a major cost nobody is watching. The first invoice being small is exactly why the total goes unexamined for years.
- 01If you added up every SaaS subscription your business pays — across every team and every vendor — what is the annual total, and does anyone in the building actually know it without doing the work to find out?
- 02Of the seats and licenses you are paying for right now, what share is genuinely used week to week — and how would you even check?
- 03Which of your systems are core (how your business specifically works) versus peripheral (what every business uses the same way), and are you renting the core when you should own it?
- 04For the tool that holds your most important data, what would it actually cost — in money, time, and lost history — to leave it, and does that exit cost mean you really control your own business memory?
- 05For each major system, how many years and how many seats until the cumulative rent passes what it would have cost to build and own — and which ones are already past that line?
- [1]BetterCloud — 2025 State of SaaS report: the average organisation runs 106 SaaS applications (down from 112), with consolidation slowing and contractual lock-in making unused apps hard to retire.
- [2]Gartner — Forecasts Worldwide Public Cloud End-User Spending (Nov 2024): spending on Cloud Application Services (SaaS) is forecast to grow from USD 250.8 billion in 2024 to USD 299.1 billion in 2025.
- [3]Zylo — 2026 SaaS Management Index: roughly 36 percent of SaaS licenses go unused, averaging about USD 19.8 million per organisation per year (about USD 1,739 per employee), with SaaS spend per employee around USD 4,830.
- [4]Gartner — Infographic: Why Are You Wasting Your SaaS Expenditure?: organisations that fail to centralise SaaS visibility overspend by at least 25 percent, with roughly a quarter of SaaS spend going to unused or underused entitlements and overlapping tools.
- [5]Productiv — State of SaaS Management: the average enterprise tracks around 342 SaaS applications, and the number of apps at companies declined for the first time in over a decade as scrutiny of subscription spend rose.
We build the systems worth owning — so the core of your business runs on an asset you control, not a rent curve that only bends upward.
Renting is right for the common, peripheral tools — and quietly punishing for the systems your business actually runs on. We help you draw the line: what to keep subscribing to, what is worth owning, and where the crossover sits for your stack. Fifteen minutes to map your subscriptions and find the rent that is buying nothing.
Book a free 15-min consultation