The 25% That's Killing Your EBITDA
By the AuditSentinel Financial Intelligence Desk
Gartner has stated it plainly, and the language leaves no room for interpretation: "Organizations that fail to attain centralized visibility and coordinate SaaS life cycles will overspend on SaaS by at least 25%, due to unused entitlements and unnecessary, overlapping tools."
The forecast runs through 2027. For venture-backed companies, that means every funding round between now and then will be priced against a SaaS line item inflated by a minimum of 25% waste. This article models exactly what that means for your EBITDA — across funding stages, headcount levels, and exit timelines.
The Baseline: What You Think You're Spending
Zylo's 2026 SaaS Management Index establishes the floor. Median SaaS spend per employee: $9,455. Median annual SaaS spend per organization: $20.6 million. IT controls just 15% of that spend; business units control the remaining 81%.
Let's establish the declared-spend baseline across three venture stages:
| Stage | Headcount | Declared SaaS Spend | IT-Managed (15%) | Shadow (85%) |
|---|---|---|---|---|
| Seed | 15 | $141,825 | $21,274 | $120,551 |
| Series A | 50 | $472,750 | $70,913 | $401,838 |
| Series B | 200 | $1,891,000 | $283,650 | $1,607,350 |
These are the numbers your finance team reports. Now apply Gartner's correction.
The Real Spend: Gartner-Adjusted
Gartner's 25% overspend figure applies to the total SaaS portfolio — not just the shadow portion. The organization that declares $472,750 in SaaS spend is actually spending $590,938. The discrepancy — $118,188 — is pure leakage: unused licenses, duplicate tools, forgotten subscriptions, and AI seat purchases that bypassed procurement entirely.
At Series B scale (200 employees), the declared $1.89 million becomes a real spend of $2.36 million. The leakage: $472,750 annually.
That's not a rounding error. That's a fully-loaded senior engineering hire. Or six months of a mid-market sales team. Or the difference between 18 months of runway and 22.
The EBITDA Model
For venture-backed SaaS companies, EBITDA is the metric that bridges growth-stage narratives to exit-stage valuations. Here's what the 25% leakage does to it.
Scenario: Series A SaaS Company, $5M ARR, 50 employees
| Line Item | Declared | Actual (Gartner-Adjusted) |
|---|---|---|
| Revenue | $5,000,000 | $5,000,000 |
| COGS (incl. declared SaaS) | $2,500,000 | $2,618,188 |
| Gross Margin | 50% | 47.6% |
| OpEx | $2,000,000 | $2,000,000 |
| EBITDA | $500,000 | $381,812 |
| EBITDA Margin | 10.0% | 7.6% |
A 2.4 percentage point EBITDA margin compression doesn't just change the financial narrative. At a 10x revenue multiple — standard for growth-stage SaaS — that margin difference translates to a $1.18 million valuation gap. From one line item. That nobody in finance is tracking.
The Compounding Effect Over Funding Cycles
Shadow AI spend isn't static. Gartner forecasts software spend growth accelerating to 15.2% in 2026 — the fastest-growing segment of $6 trillion in global IT spend. AI applications are the primary driver. ChatGPT is now the single most expensed application across Zylo's dataset.
If AI tool spend grows at 30% annually (conservative, given current adoption curves), the 25% leakage figure compounds:
| Year | Declared SaaS Spend (50 emp.) | 25% Leakage | Cumulative Waste |
|---|---|---|---|
| Year 1 | $472,750 | $118,188 | $118,188 |
| Year 2 | $543,663 | $135,916 | $254,103 |
| Year 3 | $625,212 | $156,303 | $410,406 |
Over a three-year holding period between Series A and a target exit, the company leaks $410,406 — roughly 8% of a $5M Series A raise — into subscription line items nobody can explain during diligence.
The Renewal Trap
Zylo's data reveals that SaaS renewals now account for 87% of total software spend. This means the vast majority of the 25% overspend isn't happening at the point of initial purchase — it's happening at renewal, when unused licenses auto-renew, duplicate tools persist, and the AI subscriptions that employees bought on corporate cards continue billing silently.
For finance teams, this creates a specific operational pathology: the monthly SaaS bill looks consistent, so nobody investigates. But consistency at an inflated baseline is the most expensive kind of consistency.
The Diligence Translation
When a Series B investor or strategic acquirer models your financials, they don't use your declared SaaS spend. They use trended industry benchmarks — and those benchmarks now include Gartner's 25% adjustment.
If your declared spend is $472,750 and the investor models $590,938, the $118,188 gap doesn't just appear in the financial model. It appears in the diligence questionnaire: "Explain the variance between declared SaaS spend and industry benchmarks. Provide line-item reconciliation."
The worst answer to that question is genuine surprise that a gap exists.
What To Do Before Your Next Raise
1. Run a SaaS inventory audit. Not the list your IT team maintains — the list your corporate card statements and expense reports actually support. Expect to find 40-60% more applications than you thought.
2. Identify the AI-specific leakage. ChatGPT Team, ChatGPT Plus, Midjourney, Jasper, Copilot, Notion AI — separate these from infrastructure SaaS. They're growing fastest and escaping oversight most completely.
3. Model the EBITDA impact. Run the numbers above against your own headcount and ARR. Know your Gartner-adjusted EBITDA margin before an investor calculates it for you.
4. Build the reconciliation narrative. If you can explain the gap — "we identified $118K in shadow AI spend, remediated $90K, and are monitoring the remaining $28K" — the diligence conversation becomes about operational maturity, not operational chaos.
Data sources: Zylo 2026 SaaS Management Index (median spend, IT control %, renewal share), Gartner IT spending forecasts 2025–2027 (25% overspend, 15.2% growth rate), IBM Cost of a Data Breach Report 2025 ($4.4M average breach), MedhaCloud mid-market SaaS portfolio analysis (38% IT-managed spend).