Intranet TCO: SaaS vs open source and the costs buyers underestimate
Most intranet budgets are built around the price a vendor quotes on day one. For SaaS platforms, that quote is almost never what you end up paying. Understanding the intranet total cost of ownership means looking past the headline figure to hosting, per-user licensing, tier upgrades, add-ons, and the annual price increases baked into the contract. This article compares a per-user SaaS intranet against an open source intranet you own, and shows where the SaaS model quietly runs 30 to 40 percent (sometimes close to double) over the original budget. It is written for IT leaders, CFOs, and procurement teams who have to defend the real number.
In this article:
- Why does the SaaS quote tell you so little about what you will actually pay?
- How does per-user licensing scale against you as you grow?
- The tier trap: why the plan you picked will not be enough
- Enterprise tier: opaque, custom, and painful to renew
- How much do SaaS license prices rise every year?
- The add-on surcharge: plugins, integrations, and services the vendor does not include
- The real number: why SaaS TCO lands 30 to 40 percent over budget
- How does open source change the equation?
- How can you compare SaaS and open source honestly before you sign?
Why does the SaaS quote tell you so little about what you will actually pay?
The headline SaaS price is an entry point, not a lifetime cost. It usually reflects a starting tier, a starting headcount, and a starting year. Everything that moves after that (per-user growth, tier limits, add-ons, and contractual annual increases) sits outside the first quote, which is exactly why the first quote feels so reassuring.
A better frame is simple: multiply every recurring cost across a five to ten year horizon before you compare options. When you do that, a low monthly per-seat figure can turn out to be the most expensive path over time, because it recurs and climbs every single year while a one-time build cost does not.
How does per-user licensing scale against you as you grow?
SaaS intranets charge per seat, so your cost rises automatically with every new hire. There is no usage discount for the people who barely log in. If you have 1,000 employees, you pay for 1,000 seats whether they visit daily or twice a quarter.
Seat minimums can also push you above your real need. Monday.com, for example, now requires a minimum of 25 seats on its Enterprise plan, so a smaller team pays for capacity it does not use. Zoom out and the scale becomes obvious: organizations spend roughly 7,900 to 9,100 USD per employee per year on SaaS across their stack. Every seat you add to an intranet feeds that number.
Open source flips this. Adding users does not add a license fee, so growth in headcount does not automatically grow your intranet bill.
The tier trap: why the plan you picked will not be enough
The mid-tier plan that fit your budget rarely includes every feature you actually need. Advanced search, analytics, single sign-on, and governance controls tend to live in a higher tier. You sign for the middle plan, roll out the intranet, and then discover the gap.
Here is the painful part: upgrading a tier applies to every user at once, so the cost multiplies overnight. Effective cost jumps are real. A 7 percent renewal increase combined with feature caps that force add-ons can push your effective cost up 15 to 25 percent. And you usually find the gap after adoption, when switching is hardest and your negotiating leverage is at its lowest.
Enterprise tier: opaque, custom, and painful to renew
The top “Enterprise” tier usually drops the public price list entirely and moves to “contact sales.” Pricing is negotiated behind closed doors, which means two similar organizations can pay very different amounts for the same product.
Custom features, premium support, and required services get bundled into a single opaque number that is hard to benchmark. Renewals then become a drawn-out negotiation where the vendor holds the leverage and your switching cost is highest. This opacity is deliberate and widespread: 60 percent of vendors mask their price increases, making it hard for procurement to budget or compare alternatives. The result is a category of cost you cannot forecast confidently, which is the opposite of what a CFO wants in a multi-year model.
How much do SaaS license prices rise every year?
SaaS contracts commonly build in annual price increases that compound over the life of the deal. And these increases are running far faster than general inflation. Independent sources put annual SaaS inflation at roughly 8 to 15 percent, against general G7 inflation of around 2.7 to 2.8 percent:
- SaaStr reports about 8.7 percent year over year, near 5x the G7 rate.
- A Gartner analyst cited by Zylo puts increases at 10 to 20 percent in 2025, against IT budget growth of 2.8 percent.
- SoftwareSeni reports 11 to 12 percent annually for three straight years.
- CloudNuro sees 5 to 15 percent on average, with some vendors at 20 to 30 percent or more.
On top of that, 79 percent of IT leaders faced a SaaS price increase at renewal in the past 12 months. A worked example makes the compounding clear: at a conservative 10 percent annual increase, a per-seat price roughly 1.6x itself by year five and 2.6x by year ten, before any tier or add-on changes. Once your organization depends on the platform, renewal leverage sits firmly with the vendor.
The add-on surcharge: plugins, integrations, and services the vendor does not include
Over time, needs surface that the base platform does not cover. Marketplace plugins, extra connectors, and complementary services all carry their own recurring fees, and each one is another line that scales and renews rather than a one-time spend.
Ecosystem lock-in raises the bill too. Migrating Atlassian Data Center to Cloud runs about 28 percent more on average. Watch as well for consumption charges, mandatory support fees, monthly-billing surcharges, and the seat minimums layered on top of the subscription. None of these appear in the friendly first quote, yet all of them show up on the invoice.
The real number: why SaaS TCO lands 30 to 40 percent over budget
Now stack the effects together: per-user growth, forced tier upgrades, opaque enterprise pricing, annual inflation of 8 to 15 percent, and recurring add-ons. The common outcome is that real post-implementation cost runs at least 30 to 40 percent above the plan. Over a full contract life, the total can approach double the original estimate, because these costs recur every year and keep climbing.
To be clear, that is a modeled projection built on the verified inflation and add-on figures above, not a single published statistic. The point is structural: the gap widens with time, which is exactly what makes it so easy to underestimate at signing.
How does open source change the equation?
Open source changes the shape of the cost curve. There are no per-seat license fees, so cost does not scale automatically with headcount. When you need more, functionality can be adapted and extended to fit instead of forcing a tier upgrade for every user at once.
New capabilities are built once as a one-time cost, not a per-user fee paid monthly for years. Pricing is transparent: you own the code and pay for real work, not a negotiated enterprise number set behind closed doors. Your operating expense stays under your control, because no vendor can unilaterally raise rates at renewal. You keep full ownership of code, data, and hosting, backed by the wider Drupal ecosystem.
This is the model behind Open Intranet, built on Drupal 11. Because there are no per-seat licenses and no forced tier jumps, the lifetime number stays predictable, and the recurring line on your budget is hosting and the maintenance you choose, not an escalating subscription you cannot forecast.
How can you compare SaaS and open source honestly before you sign?
Model both options across the same five to ten year horizon, not month one. Then work through the details that decide the real number:
- Ask the SaaS vendor for the fully loaded figure: tiers, enterprise quotes, add-ons, and contractual annual increases.
- Insist on a price-cap clause and check the escalation cap the vendor will commit to in writing.
- Get enterprise-tier pricing and renewal terms documented now, not left to a future negotiation.
- Separate one-time build costs from recurring per-user costs so the comparison is apples to apples.
- Assign ownership for the functionality you will need later, and price it under each model.
- Revisit the model as headcount and features change, so the projection stays honest.
Do this once, carefully, and the intranet total cost of ownership stops being a surprise and becomes a number you can defend.
Ready to start?
If you want to see the real figures side by side, we will help you build a realistic five to ten year TCO model for a SaaS intranet versus an Open Intranet on Drupal 11, with no pressure to commit. It is the clearest way to see how open source turns recurring per-user fees into a predictable, owned cost. Reach out to Droptica and we will map it out with you.
