Shadow IT: The Per-Seat Cost You’re Not Tracking

Shadow IT is any software a team pays for without IT or procurement signing off on it — a marketing team’s reporting tool, a sales rep’s prospecting add-on, an ops team’s project tracker. None of it shows up in a single line item, which is exactly why it’s expensive: every one of those tools bills per seat, and per-seat costs on tools nobody is tracking grow without anyone noticing.
Why mid-market companies are the most exposed
Companies in the 200-2,000 employee range sit in the worst spot for this. They’re big enough that individual managers have a card and the authority to buy a $15/seat tool without a procurement review, but not big enough to have a dedicated SaaS-management function watching for it. Enterprises have procurement gates; small companies have few enough tools that someone just knows what’s running. Mid-market is where visibility gaps are widest.
How the cost compounds silently
- Team growth multiplies it automatically. A shadow tool at $20/seat for 8 people becomes $20/seat for 25 people as the team hires, with no one re-evaluating the tool or the price along the way.
- Duplicate tools stack. Two teams often adopt overlapping tools independently because neither knew the other had already solved the same problem.
- Renewals auto-escalate. Shadow subscriptions renew on a manager’s card with no one reviewing the new-year price increase against actual usage.
Where shadow IT actually hides
| Source | Why it’s invisible |
|---|---|
| Expensed company cards | Shows up as a line item, not a licensing category, in expense reports |
| Free-tier-to-paid upgrades | Started as a free trial a manager approved informally, then auto-upgraded |
| SSO-connected apps | Employees connect apps via “Sign in with Google/Microsoft” without a purchase order |
| Per-team departmental budgets | Approved locally, never rolled up into a company-wide software register |
Finding it before it finds you at renewal
Your SSO or identity provider’s connected-app list is usually the single best source, since most shadow tools get connected through it even when they were never formally procured. Pair that with a pass through expensed card statements for recurring software charges. For the full step-by-step process, see how to run a SaaS spend audit.
The structural fix, not just visibility
Finding shadow IT is step one; the recurring problem is that most of what teams reach for shadow tools to do — a lightweight dashboard, a client-facing status view, a simple intake form — is exactly the kind of narrow, repetitive workflow a custom-built tool handles on one flat monthly fee instead of a per-seat subscription that grows with headcount. Consolidating three or four shadow tools into one purpose-built system, run for a flat fee, often costs less than what any single one of them was already billing.
Model what consolidating a specific shadow tool would save with the savings calculator.
Frequently asked questions
Is shadow IT always a security risk?
Not automatically, but it’s always a visibility risk — data living in a tool IT doesn’t know about can’t be secured, backed up, or governed to the same standard as sanctioned systems. The cost problem and the risk problem usually get fixed in the same pass.
How much shadow IT does a typical mid-market company have?
It varies too much by company to cite a universal figure honestly — what’s consistent is that the first formal audit almost always turns up more tools than IT expected. Run your own audit rather than benchmarking against a number that may not reflect your org.
Should every shadow tool just be shut down?
No — some solve a real problem well and are worth formally adopting. The goal is visibility and a deliberate decision per tool: keep it sanctioned, consolidate it into something else, or retire it — not a blanket ban that pushes teams back into buying things quietly.
Related articles
- TCO: SaaS Add-Ons vs. Custom-Built Software
A total-cost-of-ownership framework comparing SaaS add-on licensing to a custom build — beyond the sticker price of eith…
- An IT Director’s Guide to Consolidating Shadow SaaS
A step-by-step playbook for IT directors to find, classify, and consolidate shadow SaaS tools before the next renewal cy…
- A CFO’s Guide to Cutting Software Costs
A framework for CFOs to cut per-seat SaaS spend without cutting the tools teams actually need — audit, right-size, then…
- Data Ownership: SaaS CRM vs. a Custom-Built Portal
HIPAA, GDPR, and SOC 2 govern how a vendor handles your data — not who controls where it lives. That distinction matters…