Skip to content
Article

Ghost subscriptions: the SaaS budget growing without IT's knowledge

The IT-maintained SaaS list is only 40–60% of the real number. The rest hides in anonymous payments, free tiers, personal accounts. Invisible on bills — but eating 20–30% of the budget.

June 3, 2026
8 min read
CostSaaS SprawlDiscovery

At the start of 2026, every CFO desk has a similar topic on it: SaaS bills aren't going down — they're going up. Renewal seasons produce the same picture every year — finance asks "What was this app, again?" at month-end close, and IT can't honestly answer. Because the person who bought the app wasn't on the IT team; it was a team lead with a corporate card, the contract sat in a single email, nobody is tracking.

We call this ghost subscriptions: the SaaS portfolio growing inside the organisation without IT's knowledge. This piece explains why ghost subscriptions are now unavoidable in a modern firm, why finance data alone cannot solve it, and why an inventory grounded in actual usage is the only durable answer.

Why ghost subscriptions are growing

Three simultaneous trends made this permanent after 2020:

  • One-click purchase — modern SaaS goes from email + credit card to active in 30 seconds. No IT approval step.
  • Widespread corporate cards — mid-level managers and team leads can buy with their own limits. Finance sees one line: "Stripe $89/mo", the provider is opaque.
  • Departmental autonomy — marketing, sales, design, engineering pick their own tools. Not because they want to bypass IT; that's just how the workflow is now.

In an average organisation, the SaaS list IT actually maintains is 40–60% of the real number. The rest is hidden in finance data behind anonymous payment-processor names like "Stripe" / "PayPal" / "Adyen".

Why finance integration alone is not enough

Traditional SaaS management tools try to solve ghost subscriptions from finance data: they connect to accounting, categorise, claim "we can save you 30%". This approach falls short for three reasons:

1. Anonymous payment processors

Payments through Stripe, PayPal, Adyen, iyzico appear in finance as just "Stripe payment". Which app, which team, which user — unknown.

2. Free tiers

Notion, Trello, Slack, Figma — many apps have a free starting tier. A team starts on free, gradually 20–50 people join, personal data flows. No bill ever reaches finance. Risk is maximal.

3. Personal account → corporate use

A designer starts on a personal Figma account and uploads corporate files there. No corporate card, finance integration is blind. But the data is the firm's, and so is the risk.

The right source: usage truth
Ghost subscriptions are only visible from the endpoint. What the user's browser is opening, what's installed on the machine, which IDE extension is running — not what a contract says, but what is being used. CenseCloud builds this inventory in the SaaS discovery solution through endpoint agent + browser extension correlation.

The four cost types of a ghost subscription

A ghost subscription hurts finance in four different ways:

  • 1. Duplication — marketing uses Slack, engineering uses Discord, sales uses Teams. Same need, three separate subscriptions.
  • 2. Idle product — the subscription is active, but nobody has used it in six months. The bill keeps coming.
  • 3. Idle seat — the app is in use, but half of the assigned seats haven't logged in for 90+ days.
  • 4. Renewal surprise — a one-year auto-renew, the team has changed, no usage, but you're committed to 12 more months.

Together these four costs typically equal 20–30% of a firm's SaaS spend. So the portfolio that's outside the inventory eats nearly a third of the annual SaaS budget by itself.

Finance sees only the visible tip; the real mass sits below the line — idle seats, duplicates, abandoned products, surprise auto-renewals. An endpoint inventory exposes the submerged portion.

Steps you can take this quarter

1. Endpoint-based SaaS inventory

Put the finance list aside. Build a real usage inventory through endpoint agent + browser extension. The delta is your ghost-subscription list.

2. Per-department showback

List which department is using each app, attribute the bill to that department. Decisions change when departments see their own cost.

3. 90-day usage baseline

Distinguish active seats, idle seats, and never-logged-in across a 90-day window. Renewal decisions made with data are decisions that hold.

4. Approval-thresholded purchase

As a policy: any SaaS purchase on a corporate card above $25/mo requires IT approval. Equivalent to: catching ghost growth at its starting point.

A 12-month renewal density map — the heaviest renewals cluster in a single month (red cell). Walking into negotiation blind to that cluster surrenders a year of pricing leverage in one signature.

Conclusion: an invisible bill can still be a real subscriber

To stop asking "What was this app, again?", finance data alone isn't enough — because ghost subscriptions by definition aren't there. The answer is an inventory grounded in actual usage and a showback model that makes departmental responsibility visible.

CenseCloud builds this inventory through endpoint + browser extension + finance correlation. See the SaaS cost solution or the CenseCost module for details.

See how it works in your stack

Book a 30-minute walkthrough — your inventory, your spend, your team. No deck.