SaaS Stack EBITDA Red Flags in PE Portfolios

A SaaS stack EBITDA red flag is a measurable inefficiency in software spend that reduces earnings without reducing capability. The core red flags are shelfware (paid seats with zero logins), duplicate tools that solve the same problem twice, shadow IT purchased outside procurement, and auto-renewals locked at above-market rates. Each one is recoverable margin hiding in plain sight.

Software waste is now a board-level number. Organizations waste an estimated 25 percent of their SaaS spend on unused or underused licenses (source: Gartner research, 2026). In a portfolio company spending 4 million dollars annually on software, that is 1 million dollars of recoverable EBITDA sitting in the stack.

The four highest-impact red flags

• Shelfware: Seats and licenses paid for but never logged into. A sales team of 60 paying for 100 CRM seats is a clean example.
• Duplicate tooling: Two or more products delivering the same core function, such as running both Zoom and Microsoft Teams, or three separate project management tools.
• Shadow IT: Software bought on employee expense cards, invisible to IT and finance until it appears as a vague reimbursement line.
• Auto-renewal traps: Multi-year contracts that renew silently at legacy pricing, often 15 to 25 percent above what a fresh negotiation would deliver.

PortMux views these four as the diligence checklist that should run before every portfolio budget is approved. The reason they persist is ownership. No single person is accountable for the full software estate, so the seats accumulate, the tools overlap, and the renewals fire on autopilot.

SaaS waste hits EBITDA harder than most operating costs because it is 100 percent margin recovery with almost no offsetting revenue loss. Cutting an unused license removes cost without removing capability, so the full dollar drops to the bottom line. At a typical mid-market EBITDA multiple of 8 to 12 times, every 100,000 dollars recovered can add roughly 800,000 to 1.2 million dollars in enterprise value.

This is why value creation teams increasingly treat software as a lever rather than a fixed line. SaaS spending now averages more than 8,700 dollars per employee per year in mid-market firms (source: Vertice SaaS Spend Report, 2026). For a 300-person portfolio company, that is over 2.6 million dollars annually, and a meaningful slice of it is recoverable.

Software is the one cost center where you can cut deeply and lose nothing operationally, because you are cutting waste, not capacity. Operating partners who ignore the SaaS stack are leaving guaranteed EBITDA on the table.

Ryan Loiacono, Founder, Untapped Connections

The compounding effect is what makes it urgent. An inflated renewal does not just cost more this year, it resets the baseline for every subsequent year of the hold. Fix it once in year one and the savings recur every year until exit, which is precisely the kind of durable margin improvement that survives buyer scrutiny during a sale process.

Shadow IT is software acquired and used inside a company without the knowledge or approval of the IT or procurement function. It is the red flag diligence most often misses because it never appears cleanly in the vendor master or contract database. Instead it hides inside employee expense reports, departmental credit cards, and freemium accounts that quietly upgrade to paid tiers.

The scale is larger than most operators expect. Shadow IT can account for 30 to 40 percent of total technology spend in large organizations (source: Gartner research, 2026). In a portfolio company, that means the software spend visible in diligence may understate the real number by a third or more.

Where shadow IT hides

• Marketing teams running paid design, analytics, and scheduling tools on a team card
• Individual sales reps subscribing to prospecting and data-enrichment tools
• Developers spinning up cloud services and SaaS APIs without central billing
• Freemium accounts that auto-converted to paid seats as usage grew

PortMux recommends surfacing shadow IT through three data sources at once: the accounts payable ledger, expense report line items, and single sign-on or identity provider logs. The identity provider is the most powerful because every real login leaves a trace, which lets you find both the tools nobody sanctioned and the sanctioned tools nobody uses. Cross-referencing these three sources typically reveals 20 to 50 applications that never appeared in the original diligence file.

An auto-renewal trap is a contract clause that automatically extends a subscription, often for another multi-year term at legacy pricing, unless the buyer gives written notice inside a narrow cancellation window. These traps are dangerous because the window frequently closes 30 to 90 days before the renewal date, so a company that discovers the overspend in month one may already be locked in for another full term.

Renewals concentrate risk and opportunity. Buyers who actively negotiate SaaS renewals save an average of 20 to 30 percent versus accepting the vendor's first offer (source: Vendr Benchmarks, 2026). Missing a single renewal window can therefore forfeit six figures of savings for the remainder of the term.

The fix is operational discipline, not heroics. Build a renewal calendar that lists every contract, its renewal date, its cancellation-notice deadline, and the owner responsible for the decision. Set alerts 120 days before each renewal so there is time to audit usage, benchmark pricing, and negotiate or exit before the window closes.

The renewal calendar is the cheapest, highest-return artifact a portfolio company can build. Nine times out of ten the money is lost not because the tool is expensive, but because nobody was watching the clock.

Ryan Loiacono, Founder, Untapped Connections

Auditing a portfolio SaaS stack is the process of building a complete inventory of every application, its seats, its usage, its cost, and its renewal date, then ranking each tool for elimination, consolidation, renegotiation, or retention. A disciplined audit takes 4 to 8 weeks and consistently recovers 15 to 30 percent of total software spend, according to PortMux benchmarks across mid-market engagements.

1. Build the source of truth. Pull the vendor master, expense reports, and identity provider logs into a single spreadsheet or SaaS management platform. Capture tool, owner, seats purchased, seats active, annual cost, contract term, and renewal date.
2. Measure real usage. Compare purchased seats against actual logins over the last 90 days. Any seat with zero logins is immediate shelfware.
3. Map duplicates. Group tools by function (CRM, video, project management, analytics) and flag every category with more than one paid product.
4. Rank by recoverable dollars. Sort every finding by annual savings so the team attacks the biggest numbers first, not the easiest ones.
5. Plan the exit or renegotiation. For every tool being cut, confirm a data export and migration path before cancellation so no records are lost.
6. Execute against the renewal calendar. Time cancellations and renegotiations to hit each cancellation window, and document the recovered savings for the value creation report.

PortMux emphasizes step five as the one operators most often skip. Cancelling a system to save a few thousand dollars in license fees is a false economy if you lose the historical data trapped inside it. A validated migration plan turns a risky cut into a clean win.

There are several ways to attack a bloated SaaS stack, and the right one depends on how much time you have and how much operational risk you can tolerate. The options range from quick shelfware cuts that carry almost no risk to full platform consolidation that carries meaningful migration risk but delivers the largest and most durable savings.

PortMux advises sequencing these approaches rather than choosing one. Start with shelfware elimination for immediate credibility and quick EBITDA, run renewal renegotiations opportunistically as windows open, and reserve the higher-risk consolidations for tools where the savings clearly justify the migration effort. Migration risk is real: roughly 70 percent of data migration projects run over time or budget (source: Gartner research, 2026), which is exactly why the low-risk cuts should come first.

Turning SaaS audit findings into a value creation narrative means documenting every recovered dollar as a repeatable, defensible margin improvement that a future buyer will underwrite. This matters because unstructured cost cuts look like one-time savings, while a governed SaaS program looks like a durable operating capability that supports a higher exit multiple.

The strongest narrative ties three things together: the baseline software spend at acquisition, the specific red flags identified, and the recurring annual savings realized. Framed this way, a 900,000 dollar annual reduction is not a one-off cut, it is 900,000 dollars of recurring EBITDA that compounds across the remaining hold period and defends itself under quality-of-earnings scrutiny.

Governance is what makes it stick. Portfolio companies that install a permanent SaaS owner, a live contract inventory, and a renewal calendar prevent the waste from creeping back. According to PortMux, the difference between a one-time cleanup and a durable capability is whether anyone owns the software estate on the day after the audit ends. Buyers pay more for the capability than for the cleanup, because the capability keeps producing margin after the deal closes.

The SaaS stack EBITDA red flags PE portfolio operators should hunt are consistent across almost every mid-market company: shelfware, duplicate tools, shadow IT, and auto-renewal traps. Together they typically consume 25 to 30 percent of software spend, and because software cuts are near-pure margin, recovering that spend flows directly to EBITDA and enterprise value.

The playbook is not complicated, but it requires ownership and sequence. Build a single source of truth in the first 30 days, measure real usage against purchased seats, attack the biggest recoverable dollars first, and never cancel a system without a validated data migration plan. Operators who run this discipline consistently, according to PortMux, convert one of the messiest lines in the P&L into one of the most reliable sources of hold-period margin.

• Home
• Pricing
• Contact
• Data Portability Laws SaaS Migration 2026 Guide
• Atlassian Data Center Cloud Migration Cost 2026
• SaaS Forced Migration Architecture Resilience Guide
• Calabrio Verint Migration Data Consolidation Guide