Somewhere in your business, a team may be paying for two tools that do the same job. A former employee may still have an account. And a useful app bought on a company card may now hold customer data without anyone in IT knowing it exists.
That is not just a purchasing problem. It is a question of who owns the organisation’s software portfolio, how each app fits the business, and whether the cost and risk remain justified.
The scale of the issue is significant. Zylo’s 2025 SaaS Management Index reports an average of $4,830 in SaaS spend per employee, up 21.9% year on year. Its analysis also estimates that organisations waste an average of $21 million annually on unused SaaS licences, a 14.2% increase. These are study-wide averages, not a prediction of what a UK SME wastes. But they are a useful warning: software costs can grow faster than visibility.
Zylo reports that business units account for 70% of SaaS spend, compared with 26.1% for IT. Productiv has also reported that 34% of SaaS purchases are made by departments outside IT, and that fewer than half of users were using all the SaaS apps licensed to them. The figures point to a gap between who buys applications and who can see, govern and support them.
The app portfolio is the issue
A renewal calendar can remind you that a contract is due. A shadow IT review can help uncover tools bought without approval. Neither, on its own, answers the wider portfolio questions:
- Do we have several apps doing essentially the same job?
- Are paid seats being used, and are they the right licence tier?
- Who is accountable for each app’s business value and information?
- Does the application still fit our operating model and technology strategy?
- What new exposure comes with AI features and add-ons?
The goal is not to block every new tool or centralise every decision in IT. Teams need room to solve real problems. The goal is to make sure each app has a purpose, a business owner and a proportionate level of oversight.

Build an inventory that tells you something useful
Start by bringing together the evidence you already have. Accounts payable, company card and expense records show where money is going. Identity-provider and single sign-on records can reveal apps connected to work accounts. Procurement records, staff conversations and a short departmental survey can help uncover free trials, smaller subscriptions and tools paid for outside the usual route.
A useful application register does not need to be complicated. For each app, record:
- Purpose and owner: what business need it serves and who is accountable for its value.
- Cost and commitment: price, number of seats, licence tiers, contract details and renewal terms.
- Use: active users and meaningful activity, not simply the number of accounts created.
- Information and access: the types of data held, integrations, access method and any privileged accounts.
- Decision: retain, consolidate, reduce licences, review, replace or retire.
The owner is not necessarily the person who bought the app. A department lead should be able to explain its business value; IT should understand access, integration and technical risk; and finance or procurement should be able to see the full cost and contractual commitment. If nobody can explain why an app remains, that is a reason to review it, not an automatic instruction to cancel it.
Treat AI add-ons as part of the same portfolio
AI features can arrive as a new subscription, an extra licence tier, a usage-based charge or an add-on within an existing service. Each may look modest in isolation. Across multiple departments, the costs, permissions and information flows can be less modest.
Include AI functionality in the app register. Ask what information it can access, whether staff may submit customer or confidential business data, how access is controlled, and whether usage creates variable charges. The decision should reflect the tool’s purpose and risk, not the novelty of the feature.
The NCSC guidance on SaaS security emphasises that SaaS security is a shared responsibility. An organisation still needs to manage users and permissions, suspend accounts when they are no longer required, and monitor relevant audit information. For small organisations choosing an online service, the NCSC also advises checking that the service is configured safely and that you are assessing the right version or plan: choosing a good service.
Where personal information is involved, app decisions should also sit alongside your data protection responsibilities. The ICO’s data security advice for small organisations is a useful starting point.
Make the review part of IT strategy
An app portfolio review should not be a one-off cost-cutting exercise. Build it into IT strategy so that applications are assessed when the business changes, new systems are proposed, or existing tools stop delivering clear value.
A practical review can follow five steps:
- Map the capability. Group apps by the work they support, such as finance, customer management, collaboration or document handling. This makes duplicate capability easier to spot.
- Check real usage. Compare paid seats with meaningful activity, recent leavers and the features people actually use. Define a suitable period for each service rather than treating one login as proof of value.
- Assess value and risk together. Consider business benefit, total cost, information sensitivity, access controls, integrations and the consequence of service disruption.
- Choose an outcome. Keep, consolidate, reduce, remediate, replace or retire. Where an app is removed, plan for data export, access removal and any operational dependencies.
- Set ownership and review dates. Give every retained app a business owner and a proportionate review rhythm. High-impact services warrant more frequent attention than low-risk tools.

This is where consultancy-first IT leadership matters. The Fractal IT Director approach is to connect software decisions to the operating model, people and infrastructure around them, setting that direction first and then bringing in the right execution support.
For example, where Microsoft Dynamics 365 Business Central is being considered as a strategic business platform, the relevant question is not simply whether it can replace one app. It is how it fits the wider application architecture, information flows and growth plans. A structured Dynamics 365 Jump Start can help businesses assess the route forward.
Likewise, the wider environment matters. The right Cloud Solutions and Network Solutions support can underpin applications, while Helpdesk Support can help users adopt approved tools consistently. Voice and Connectivity may also belong in a technology estate review where communication services and recurring costs overlap. For business-critical systems, Disaster Recovery planning should reflect the applications the organisation depends on.
These are execution services beneath the strategy, not substitutes for deciding what the business needs in the first place. Managed IT Services can provide ongoing operational support, while Technology Expense Management can help bring software and technology spending into clearer view.
A manageable first month
A small business does not need to catalogue every feature in every app before making progress.
- Week one: agree an executive sponsor and gather payment, procurement and identity records.
- Week two: ask department leads what tools they use and what work each one supports.
- Week three: identify duplicate capabilities, unused seats, ownerless apps and tools handling sensitive data.
- Week four: assign owners, agree review levels and act on the clearest opportunities, such as removing seats for leavers or consolidating genuinely overlapping services.
Track a handful of measures: the proportion of apps with an accountable owner, unassigned or inactive licences, spend by department, apps with completed risk reviews, and high-priority applications with an agreed continuity plan. These measures show whether visibility and accountability are improving, not just whether a spreadsheet exists.
A mature IT strategy does not aim for the fewest possible apps. It aims for a coherent portfolio: software people need, costs the business understands, data handled appropriately and owners who can explain the value.
The app nobody remembers buying may still be useful. But until it has an owner and a clear place in the portfolio, nobody can confidently say what it is costing, or what it is allowed to do.
For an overview of the wider Evestaff group, visit evestaff.co.uk.
SEO keywords:
- Cloud Solutions
- Disaster Recovery
- Dynamics 365 Jump Start
- Helpdesk Support
- IBM i Management
- Managed IT Services
- Network Solutions
- Technology Expense Management
- Voice and Connectivity
Join The Discussion