Every company has a number they track carefully. Revenue, headcount, burn rate, customer acquisition cost. But there is another number that almost nobody tracks, and it is quietly eating into margins every single month: the total cost of software that nobody in the organization is accountable for.
This is not about unused software. That problem is well understood. This is about software that is actively being used but has no designated owner, no cost accountability, and no renewal oversight. It is software that exists in a gray zone where it is too important to cancel but too neglected to manage.
How SaaS Sprawl Happens
No company sets out to accumulate dozens of unmanaged subscriptions. It happens incrementally, through a series of perfectly reasonable decisions.
A marketing manager signs up for a social scheduling tool on a free trial. It works well, so they upgrade to the paid tier on the company card. An engineer adopts a monitoring service that integrates nicely with the existing stack. A sales rep starts using a prospecting tool that their friend at another company recommended.
Each of these decisions makes sense in isolation. The tool solves a real problem. The cost is modest. Approval, if it is required at all, is a quick Slack message to a manager.
But across an organization of 100 people, these decisions compound. Industry data consistently shows that mid-size companies use between 200 and 400 SaaS applications, and that 30-40% of that software qualifies as shadow IT, meaning it was adopted without going through formal procurement or IT approval.
Shadow IT is not malicious. It is a natural consequence of how easy modern software is to purchase and deploy. But it creates a specific and expensive problem: a large portion of your software portfolio has no formal owner, no review cycle, and no connection to your budgeting process.
What "Unowned" Really Means
An unowned software license is not necessarily one that nobody uses. It is one where no individual person is accountable for its cost, configuration, and continued relevance. In practice, unowned software exhibits some or all of these characteristics:
No one reviews the invoice. The charge appears on a credit card statement or in an expense report, but nobody is specifically tasked with verifying that the amount is correct, that the plan level is appropriate, or that the number of seats matches actual usage.
No one manages user access. People who have left the company or changed teams still have active accounts. New team members request access through informal channels, and nobody tracks the total seat count against the subscription tier.
No one evaluates the tool's value. The tool was adopted to solve a problem 18 months ago. Is it still the best solution? Has the team's workflow changed? Has a competitor emerged that offers better functionality at a lower price? Nobody is asking these questions because nobody is responsible for asking them.
No one plans for renewal. The subscription auto-renews annually, and the first anyone hears about it is the charge notification. By then, the cancellation window has passed, and you are locked in for another year.
The Real Numbers
The financial impact of unowned software is substantial and measurable. Here are the numbers that should concern any operations or finance leader:
Unused licenses within active subscriptions. Flexera's annual State of ITAM report consistently finds that organizations waste 25-30% of their software spend on licenses that are either completely unused or significantly underused. For a company spending $300,000 per year on SaaS, that is $75,000-$90,000 in annual waste.
Duplicate tools across teams. When there is no central visibility into what software the organization uses, different teams frequently adopt different tools for the same purpose. It is common to find two or three project management tools, multiple file-sharing platforms, and overlapping analytics subscriptions. Each one costs money and fragments workflows.
Missed downgrade opportunities. Many SaaS products offer tiered pricing based on features or user counts. Without an owner reviewing usage, companies routinely pay for enterprise tiers when a standard plan would suffice, or maintain 50-seat licenses when only 20 people actively use the tool.
Auto-renewal at increased rates. SaaS vendors frequently increase prices at renewal time. Without an owner paying attention, these increases go unnoticed and unchallenged. A 10-15% price increase across 50 unmonitored subscriptions adds up quickly.
Taken together, companies that conduct their first thorough SaaS audit typically discover they can reduce software spend by 20-35% without eliminating any tool that is actively providing value.
A Framework for Auditing Your Software Spend
If you suspect your organization has an unowned software problem, and if you have more than 30 employees, you almost certainly do, here is a structured approach to identifying and addressing it.
Phase 1: Discovery (Week 1-2). Gather a complete list of every software subscription your company pays for. Pull credit card statements, expense reports, and procurement records for the last 12 months. Ask department heads to list every tool their teams use. Cross-reference against SSO logs and identity provider records if you have them. The goal is a single, comprehensive list.
Phase 2: Classification (Week 2-3). For each tool on the list, answer four questions. Who uses this tool? How many active users does it have versus how many seats are we paying for? Who originally purchased or adopted it? Is there a clear owner responsible for it today? Any tool where the answer to the last question is "no" or "I am not sure" goes on the unowned list.
Phase 3: Assignment (Week 3-4). Every tool on the unowned list needs an owner. Work with department leads to identify the right person for each tool. The owner should be someone who uses the tool, understands its value, and has the authority to make decisions about its future. This step alone, simply assigning accountability, often triggers immediate action. New owners frequently discover unused seats, unnecessary plan tiers, or tools that the team has outgrown.
Phase 4: Right-sizing (Week 4-6). With owners in place, give each one a mandate: review the subscription within 30 days. Specifically, they should verify the user count matches actual usage, confirm the plan tier is appropriate, check whether the tool is still the best option for the problem it solves, and note the renewal date and cancellation terms.
Phase 5: Ongoing governance (Permanent). Auditing once provides a point-in-time cleanup. Preventing recurrence requires a system. New tools must be registered with an owner when they are adopted. Ownership must transfer when people leave or change roles. Renewals must trigger a review. This is where purpose-built tools like OwndUp provide lasting value. Instead of relying on spreadsheets that go stale, a dedicated ownership registry keeps your software inventory current, connects every license to a responsible person, and alerts owners before renewals hit.
Preventing Recurrence
The audit framework above solves the immediate problem. Preventing it from coming back requires three organizational habits:
Establish a lightweight procurement process. This does not mean bureaucratic approval chains. It means a simple norm: before adopting a new paid tool, register it in your ownership system, assign an owner, and note the cost and renewal date. At companies under 200 people, this can be as simple as a Slack message to an IT or ops channel.
Make ownership part of onboarding and offboarding. When a new employee joins, they should understand that any tools they adopt will be tracked under their name. When an employee leaves, every tool they own must be reviewed and reassigned. Both of these steps take minutes and prevent months of waste.
Run a quarterly SaaS review. Block 60-90 minutes each quarter for department leads to review their team's software inventory. Are all tools still in use? Are the right people listed as owners? Are there any upcoming renewals that should be evaluated? This single meeting consistently saves organizations thousands of dollars per quarter.
The Accountability Principle
At its core, the unowned software problem is an accountability problem. Every tool in your organization was adopted by a real person to solve a real problem. But without a system to maintain that connection between tool and person, accountability erodes over time.
The fix is not more monitoring or automated discovery. Those tools tell you what software exists. They do not tell you who is responsible for it. The fix is a simple, enforced principle: every software license has one owner, and that owner is accountable for its cost, its users, and its continued relevance.
Companies that adopt this principle do not just save money on software. They make faster decisions about tool adoption, respond more quickly when tools need attention, and build a culture where every dollar of spend has a name attached to it.
The software your company uses should be a portfolio of deliberate, accountable investments, not a pile of recurring charges that nobody is watching.