The pain
In many organisations, accountability for software and applications is diffuse. This ambiguity invites fragmented procurement, overlapping tools and uncontrolled spending. When ownership is unclear, teams invest in redundant capabilities, fail to retire obsolete licences and struggle to achieve consistent performance across systems. The financial signal is the cost of underutilised or duplicative technology, the maintenance burden on IT and the opportunity cost of not consolidating investments into higher-value platforms.
Ask a simple question about any application in the business: who decides whether we keep paying for this? In a well-run estate there is a name. In many businesses the honest answer is "IT pays the bill", "finance approves the card payment" or "the person who bought it left last year". Paying, approving and using are not the same as owning.
Why businesses tolerate it
Unclear ownership rarely comes from negligence. Modern software is easy to buy on a card or through a free trial, so teams solve their own problems quickly. That speed is valuable. The difficulty is that nobody is then made responsible for the tool's cost, usage, security, renewal and eventual retirement.
The FinOps Foundation's guidance on SaaS highlights how purchasing now runs through many channels at once, including direct from publishers, resellers, managed service providers and cloud marketplaces, and stresses that each tool needs a clear owner and that spend visibility has to be unified across those channels. It frames this as decentralised financial accountability rather than leaving everything to a central IT budget.
Operational consequence
Shadow IT tendencies emerge as teams buy and deploy tools without central governance, leading to licence fragmentation, security risks and inconsistent data practices. IT backlogs grow as teams request support for overlapping tools, while renewals and negotiations become messy across departments.
The UK NCSC's guidance on shadow IT is useful here because it avoids blame. It notes that shadow IT is rarely malicious and usually appears when sanctioned tools lack functionality or approval processes are slow. It also sets out the risks: data held in services without proper access controls, devices and services outside normal protections, and a visibility gap that prevents the organisation managing risks it does not know exist.
Typical symptoms of an ownerless estate:
- two or three tools doing the same job in different departments;
- renewals arriving as surprises, with no time to negotiate or cancel;
- licences still assigned to former employees;
- IT supporting applications it did not choose and cannot configure;
- customer or company data stored in places nobody has assessed.
Financial consequence
The cost consequence is framed as wasted spend and inefficiency, including underutilised licences, high maintenance costs and delayed retirement of obsolete systems. While exact figures depend on the size of the organisation, the pattern is well understood: governance clarity reduces redundancy and improves the return on technology investments.
An illustrative cost model
All figures below are illustrative assumptions, not benchmarks. Replace them with your own application register and invoices.
Assume a business runs 60 software applications with a combined annual cost of R3,600,000. A review finds that 15 of them, costing R720,000 a year, have no accountable business owner.
| Component | Illustrative assumption | Annual cost |
|---|---|---|
| Duplicated tools | 4 of the 15 unowned applications duplicate capability already owned elsewhere, costing R240,000 between them | R240,000 |
| Unused seats | 25% of seats unused across the remaining 11 unowned applications (R720,000 − R240,000 = R480,000) | R120,000 |
| Un-negotiated renewal uplift | 8% automatic price increase accepted on the same R480,000 because nobody reviewed the renewal | R38,400 |
| IT support overhead | 15 applications × 2 hours a month × 12 months = 360 hours × R450 an hour | R162,000 |
| Total illustrative waste | R560,400 |
In this example, ownerless applications generate waste equal to about 15.6% of the entire software budget (R560,400 ÷ R3,600,000), even though they account for only 20% of the spend (R720,000 ÷ R3,600,000). The point is not the precise percentage. It is that unowned spend tends to carry a disproportionate share of waste, because no one is positioned to challenge it.
The model leaves out costs that are harder to price but often larger: a data incident in an unassessed service, a failed audit, or the opportunity cost of budget that could have funded a better-integrated platform. The related pain of paying for software licences employees no longer use covers the seat-level arithmetic in more depth.
Urgency
Unclear ownership becomes commercially urgent when:
- software spend is growing faster than headcount or revenue;
- finance cannot produce a list of applications with owners and renewal dates;
- a security questionnaire, insurance renewal or audit asks where company data is stored;
- a restructure, merger or departure exposes tools nobody can explain;
- renewals regularly auto-renew without review. See supplier contracts renewing without review.
If the business cannot name an owner for every material application, it is not managing software spend. It is simply paying it.
Resolution
- Assign clear ownership for software inventories, licences and application portfolios.
- Centralise procurement, sunset redundant tools and consolidate vendor relationships where possible.
- Establish a living catalogue of applications with usage metrics and renewal alerts.
- Institute cost-visibility dashboards and quarterly reviews of technology spend against value delivered.
- Promote standardisation and interoperability to reduce bespoke, cost-heavy integrations.
Ownership does not mean bureaucracy. A workable model gives each application a named business owner who answers for its purpose, users and value, with IT responsible for security and access and finance responsible for the commercial commitment. Useful measures from the FinOps SaaS guidance, such as the ratio of active to provisioned users and the share of the portfolio covered by redundant applications, give each owner something concrete to review. Following the NCSC's advice, a fast and simple approval route for new tools reduces the incentive to buy around the process in the first place.
A Digital Systems Audit is one way to build the first register and identify where ownership, duplication and cost need attention.
Bottom-line meaning
Clear accountability for technology choices reduces waste, unlocks budget for strategic capabilities and accelerates value realisation from the technology stack. Uncontrolled spending is not a software problem; it is an ownership problem expressed in software invoices. Once every material application has someone who answers for it, duplication, unused seats and unreviewed renewals become visible, and most of them become easy to remove.
Sources and further reading
- FinOps for SaaS - FinOps Framework Technology Category (last verified 10 October 2026)
- Shadow IT guidance (last verified 10 October 2026)
Related Mellorca reading
- How Many Software Subscriptions Do You Pay For? The Cost of Not Knowing
- Paying for Cloud Resources Nobody Uses
- Unassigned Enquiries: Why Leads Go Cold Before Anyone Owns Them