A SaaS spend audit is the most practical piece of IT housekeeping a UK small or mid-sized business can do this year. Most organisations with 20 to 250 staff now pay for somewhere between 40 and 150 separate software subscriptions, bought on company cards, expensed by individuals, bundled into supplier invoices or quietly auto-renewed every January. Nobody owns the full list, so nobody can say with confidence which tools are essential, which overlap, and which were last opened by someone who left the business eighteen months ago.
This guide sets out the method a virtual CIO uses to run a software licence audit from a standing start: how to discover every subscription, how to measure real usage, how to decide what to keep, consolidate or cancel, and how to stop software sprawl creeping back. It is written for finance directors, operations managers and owner-managers who want a clear, evidence-based view of SaaS cost management — and a repeatable process rather than a one-off cull.
What is a SaaS spend audit? Definition and context
A SaaS spend audit is a structured review of every cloud software subscription an organisation pays for, matched against who actually uses it, what business process it supports, what data it holds and when the contract next renews. The output is a single, owned register of applications plus a decision for each one: keep, right-size, consolidate, renegotiate or retire.
It differs from a traditional software asset management (SAM) exercise in two important ways. First, the spend is fragmented: on-premises licences used to arrive through one reseller on one purchase order, whereas SaaS arrives through dozens of channels — direct debits, Amex statements, app-store purchases, Stripe receipts in personal inboxes and line items buried inside a marketing agency’s monthly invoice. Second, SaaS carries data and security risk as well as cost. Every forgotten subscription is a place where customer data, staff personal data or intellectual property may still be sitting, governed by terms nobody has read and protected by a password that may have left with a former employee.
That is why the audit is a natural virtual CIO responsibility rather than a purely financial task. Finance can see the spend, IT can see the sign-ins, and the business owners know which tools genuinely matter. A vCIO pulls the three views together, applies a consistent decision framework and turns the result into a policy the organisation can live with. If you have already worked through our guide to Microsoft 365 Copilot licensing costs, you will recognise the same discipline: know what you pay for, know who uses it, and tie every licence to an outcome.
Start the audit at least 90 days before your largest renewal date. Most annual SaaS contracts require 30 to 60 days’ written notice to cancel or reduce seats, and many auto-renew at list price if you miss the window. Auditing in the month of renewal leaves you with no negotiating room at all.
SaaS sprawl risk scoring — where most UK SMEs sit today
Before discovering a single subscription, it helps to understand where the typical risks lie. When we assess a new client’s software estate, the same patterns appear again and again. The score cards below summarise the areas we rate first, grouped by the kind of exposure they create. A “high” badge means the issue is common and expensive or risky to leave alone; “mid” means it needs attention within the audit cycle; “low” means it is usually under control but worth confirming.
The pattern is consistent: the core productivity suite is usually well managed because it is visible and centrally billed, while the long tail of departmental and individual tools is where cost and risk accumulate. The audit method below is designed to illuminate that long tail first.
Software licence audit by the numbers
Every organisation is different, but the ranges below reflect what a first-time SaaS spend audit typically uncovers in a UK business of 30 to 200 staff. Treat them as orientation, not as a forecast for your own estate — the point of the audit is to replace estimates with your own evidence.
The second figure is the one that tends to surprise boards. Inactive seats accumulate because adding a user is easy and urgent, whereas removing one is nobody’s job. A starter needs access on day one, so someone buys a seat; a leaver’s seats are rarely reclaimed unless the leaver process explicitly lists every application. If your onboarding is already automated — see our walkthrough of new-starter IT onboarding with Autopilot and Entra — the same identity groups can drive automatic seat removal at the other end of the employee lifecycle.
Manual spreadsheet audit vs a vCIO-led SaaS management approach
There are two broad ways to run the audit. Many businesses start with a spreadsheet exported from the accounting system, circulated round department heads for comments. It is cheap and it does produce a list, but it tends to stall at the “who uses this?” question and is rarely repeated. The alternative is a structured, evidence-based audit that combines finance data, identity-provider sign-in logs and owner interviews, ending in a maintained register and a governance policy.
Spreadsheet clean-up
Finance-led, one-off
vCIO-led SaaS audit
Cross-functional, recurring
The structured approach takes more effort in the first cycle — typically four to six weeks elapsed, a few hours a week from finance and IT — but each subsequent quarterly review takes a fraction of that because the register already exists and the owners already know their role. The rest of this guide follows that structured method.
Where SaaS spend actually hides
Discovery is the step most audits get wrong, because the obvious source — the supplier list in Xero, Sage or QuickBooks — only shows software paid for by invoice or direct debit. The chart below shows, from our audit experience, the share of discovered applications that were found only through each source. In other words, if you skipped that source you would have missed those applications entirely.
Two sources deserve special mention. OAuth grants — the “Sign in with Microsoft” or “Sign in with Google” consents staff click when trying a new tool — reveal free and trial applications that already hold access to company mailboxes, calendars or files. In Microsoft Entra ID you can review these under Enterprise applications; in Google Workspace they appear under Security → API controls → App access control. Many of these never cost a penny, which is exactly why they never appear in finance data, yet they can carry more data risk than a paid tool with a signed contract.
Bundled supplier invoices are the other blind spot. Marketing agencies, web developers and outsourced bookkeepers frequently pay for tools on your behalf and recharge them as part of a monthly fee. When the relationship ends, the subscription — and sometimes your data or domain — remains in the supplier’s account. Ask every material supplier for a written list of any software they hold on your behalf.
How much of your SaaS estate is actually governed?
One useful headline measure for a board pack is the share of paid applications that meet a minimum governance standard: a named business owner, a known renewal date, sign-in through single sign-on (SSO) or at least enforced multi-factor authentication, and a data processing agreement on file where personal data is involved. In a first audit, the typical figure is uncomfortably low.
The goal of the first audit cycle is not to reach 100% — that is unrealistic for the long tail — but to bring every application that holds personal data, financial data or customer-facing content into the governed set, and to retire or consolidate as many of the rest as practical. Moving from roughly a third to above 80% of spend under governance within two quarters is a realistic and defensible target for most SMEs.
The SaaS spend audit timeline — a 30-day method
A first SaaS spend audit for a business of 30 to 200 staff can be completed in about a month of elapsed time if the work is sequenced properly. The timeline below is the sequence a virtual CIO typically follows. Each stage produces something concrete, so even if the audit is paused, the work done so far still has value.
Cancellation itself often happens later than day 30, because notice periods and renewal dates dictate when savings land. That is normal. The audit is complete when every decision is recorded and the dates are in the calendar; the cash benefit follows over the next one to twelve months.
Decision framework — the SaaS rationalisation readiness gauge
Before moving into cancellations, it is worth scoring how ready the organisation is to make and sustain decisions. We use a simple 100-point readiness score built from five questions, each worth up to 20 points: Is there an executive sponsor? Is there a complete inventory? Is usage evidence available for the top 20 applications by spend? Does every material application have a named owner? Is there a written purchasing policy for new software?
A score in the low forties is typical: there is usually a sponsor and a partial inventory, but little usage evidence, few named owners and no purchasing policy. Businesses below 40 should spend more time on discovery and ownership before cutting anything, because cancelling a tool without an owner’s agreement is the fastest way to break a process nobody had documented. Above 70, the organisation is ready to move straight to consolidation and renegotiation.
The five decision outcomes are deliberately simple:
- Keep — the tool is used, owned, secure and fairly priced. Record the owner and renewal date.
- Right-size — the tool is valuable but has unused seats or an over-specified tier. Remove seats or downgrade at renewal.
- Consolidate — two or more tools do the same job. Choose one, migrate users and data, then retire the others.
- Renegotiate — the tool is essential but the price, term or terms are poor. Use the renewal window to negotiate.
- Retire — the tool is unused, unowned or replaced by something already licensed. Export data, then cancel.
SaaS cost management — typical savings by category
Where do the savings come from? The table below shows the categories of SaaS spend where a first audit most often finds opportunities, with typical annual spend ranges for a 50-person UK business and the most common action. Figures are indicative and exclude VAT; your own numbers come from the discovery stage.
| Category | Typical annual spend (50 staff) | Common finding | Usual action |
|---|---|---|---|
| Collaboration and file sharing | £2,000–£8,000 | Dropbox, Box or WeTransfer Pro alongside SharePoint and OneDrive already licensed in Microsoft 365 | Consolidate |
| Video and messaging | £1,500–£6,000 | Zoom and Slack paid seats alongside Teams | Consolidate or right-size |
| Design, PDF and e-signature | £3,000–£10,000 | Adobe Acrobat Pro on every laptop where a few users need editing; two e-signature tools | Right-size and consolidate |
| Sales and marketing tools | £6,000–£30,000 | CRM tier above need, abandoned email, social and SEO tools | Renegotiate and retire |
| Project and task management | £1,500–£8,000 | Asana, Monday and Trello in different teams alongside Planner | Consolidate |
Collaboration overlap is the most common single finding because Microsoft 365 Business Standard and Premium already include Teams, SharePoint, OneDrive, Planner, Forms, Bookings and Lists. Teams frequently adopted alternatives before those tools matured, and nobody revisited the decision. That does not mean the alternative should always go — Slack, for example, may be deeply embedded in an engineering team’s workflow — but the overlap should be a deliberate choice, not an accident.
Remember that savings on paper are not savings in the bank. A tool that saves £4,000 a year but needs £6,000 of migration effort and three months of disruption may be better kept until a natural transition point. The audit should record both the annual cost and the estimated switching cost.
SaaS governance benchmarks and KPIs
Once the register exists, a handful of KPIs keeps the board informed without turning software governance into a bureaucracy. The benchmarks below show the typical position at first audit alongside a sensible target for twelve months later. Each row shows the typical first-audit figure; the paragraph that follows sets out reasonable targets.
Typical first-audit position for UK SMEs
Reasonable twelve-month targets are 100% named ownership for every paid application, 100% of renewal dates recorded, SSO on every application that supports it at your plan tier, MFA everywhere else, a data processing agreement for every tool holding personal data, and seat activity above 90%. The last measure matters most financially; the SSO and DPA measures matter most for UK GDPR accountability and for evidence when you answer a cyber insurance proposal form or a client’s supplier security questionnaire.
These KPIs also rely on clean data. If your finance system codes software inconsistently, fix the nominal codes first — our guide to data quality in business reporting covers the principles of consistent categorisation that make dashboards trustworthy.
Common SaaS audit mistakes to avoid
Most failed audits fail for predictable reasons. The list below covers the mistakes we see most often, all of which are avoidable with a little planning.
- Cancelling before exporting data. Many vendors delete data 30 to 90 days after cancellation. Export records, files and audit logs first, and check whether you have a legal retention obligation — HMRC expects most financial records to be kept for six years.
- Treating free tools as harmless. A free AI note-taker or file converter with access to company mailboxes can carry more data protection risk than a paid tool under contract. Review OAuth consents, not just invoices.
- Relying on managers’ opinions of usage. “Everyone uses it” is rarely true. Check sign-in and activity logs before agreeing seat counts.
- Ignoring notice periods. An annual contract with 60 days’ notice cancelled 45 days before renewal will renew for another year. Build the renewal calendar before making decisions.
- Consolidating without a migration plan. Moving three teams from three project tools to one needs data migration, training and a cut-over date, or people quietly keep using the old tool.
- Leaving accounts owned by individuals. Subscriptions registered to a personal email address or a former employee’s login are a continuity risk. Transfer ownership to a shared, company-controlled admin account.
- Making it a one-off exercise. Without a purchasing policy and quarterly review, sprawl returns within twelve to eighteen months.
Do not cancel an application you cannot fully explain. Some tools quietly underpin integrations — a Zapier account moving web leads into the CRM, or a forms tool feeding a payroll process. Before retiring anything, ask the owner to name every process that touches it, and check for API keys or webhooks pointing at it.
SaaS spend audit checklist — the 12-point essentials
Use this checklist to run the audit or to check that a supplier’s audit has covered the essentials. Each item should produce evidence you could show to a board or an auditor.
- Executive sponsor named and scope agreed in writing, including the spend period and review threshold.
- Twelve months of supplier payments, card statements and expense claims exported and filtered for software.
- Vendor names normalised and every recurring charge annualised in pounds sterling, including VAT treatment.
- Enterprise application and OAuth consent lists exported from Microsoft Entra ID or Google Workspace.
- Material suppliers and agencies asked for a list of software they hold on the company’s behalf.
- Paid seats compared with active users over 30 and 90 days for every application above the threshold.
- A named business owner agreed for every paid application.
- Renewal date, term, notice period and price-escalation clause recorded for every contract.
- Data held, data location, SSO/MFA status and data processing agreement recorded for every application holding personal data.
- A keep / right-size / consolidate / renegotiate / retire decision recorded with a reason.
- Data exported and integrations checked before any cancellation; cancellation confirmations filed.
- Purchasing policy published, leaver checklist updated and first quarterly review scheduled.
The register itself can live in SharePoint Lists, a simple database or a dedicated SaaS management platform. For most businesses under 150 staff, a well-structured list with an owner column, a renewal-date column and a quarterly reminder is enough. Dedicated platforms become worthwhile when the estate passes roughly 150 applications or when automated discovery through finance and identity integrations would save significant manual effort.
Mini case study — a 64-person professional services firm
A Leeds-based professional services firm with 64 staff across two offices asked for help after its finance director noticed software costs had grown faster than headcount for three consecutive years. Nobody could produce a full list of tools, and the firm was about to complete a client security questionnaire that asked which cloud services held client data.
Discovery found 83 paid applications and a further 41 free tools with OAuth access to Microsoft 365 data. Nineteen paid applications had no identifiable owner. The firm was paying for Dropbox Business, Box and WeTransfer Pro alongside SharePoint; two e-signature platforms; three project management tools; and Adobe Acrobat Pro for every employee, although activity logs showed only eleven people had edited a PDF in the previous quarter. Four subscriptions were registered to former employees’ personal email addresses.
Over the following six months the firm consolidated file sharing onto SharePoint and OneDrive, standardised on one e-signature tool and one project platform, reduced Acrobat Pro to the people who needed it and moved everyone else to the free reader, revoked 33 of the 41 OAuth consents, and transferred ownership of every remaining account to a company-controlled admin identity. Fourteen applications were brought behind single sign-on. Annual software spend fell, but the finance director said the larger benefit was being able to answer the client questionnaire accurately and quickly.
“We expected to find some waste. What we didn’t expect was how many tools had client data in them that nobody was looking after. The register means we can now answer a security questionnaire in an afternoon, and renewals don’t surprise us any more.” — Finance Director, professional services firm, Leeds
SaaS spend audit at a glance
| Topic | Key fact |
|---|---|
| What it is | A structured review of every software subscription against usage, ownership, risk and renewal terms |
| Who should sponsor it | Finance director or managing director, with IT and department heads |
| Typical first-audit duration | About 30 days elapsed for 30–200 staff |
| Best time to start | At least 90 days before the largest renewal date |
| Discovery sources | Ledger, cards, expenses, OAuth consents, SSO logs, supplier invoices, renewal emails |
| Typical inactive seats at first audit | 20–35% of paid seats unused for 60+ days |
| Most common overlap | File sharing, video and project tools alongside Microsoft 365 |
| Decision outcomes | Keep, right-size, consolidate, renegotiate, retire |
| Data protection focus | DPA, data location and SSO/MFA for every app holding personal data (UK GDPR) |
| Before cancelling | Export data, check integrations, confirm retention duties |
| Ongoing cadence | Quarterly light-touch review plus a 90-day renewal calendar |
| Register tooling | SharePoint List or simple database under ~150 apps; SaaS management platform above |
How Cloudswitched runs SaaS spend audits
Our Virtual CIO service runs the audit end to end alongside your finance team: discovery across finance and identity data, usage evidence, owner interviews, contract and data protection review, and a decision log that the board can sign off. We then help you execute consolidation and migrations, set up the register and renewal calendar, and lead the quarterly reviews so the work stays done.
Get a clear view of your software estate
Cloudswitched’s virtual CIOs help UK businesses build a governed, right-sized SaaS portfolio with named owners and no renewal surprises.
Talk to us about Virtual CIO servicesFrequently Asked Questions
What is a SaaS spend audit?
A SaaS spend audit is a structured review of every cloud software subscription a business pays for, matched against actual usage, a named owner, the data the tool holds and its renewal terms. The result is a single register of applications and a recorded decision for each: keep, right-size, consolidate, renegotiate or retire. Unlike a quick look at the supplier ledger, a proper audit combines finance data with sign-in and activity logs, so decisions are based on evidence rather than opinion.
How often should a UK SME run a software licence audit?
Run a full software licence audit once, then move to a light-touch quarterly review. The quarterly review checks new subscriptions, upcoming renewals in the next 90 days, seat activity for the top applications by spend, and any leavers whose access needs removing. A full re-audit every two to three years, or after a merger, restructure or major platform change, keeps the register honest.
How long does a SaaS audit take?
For a business of 30 to 200 staff, the first audit usually takes around 30 days of elapsed time, with a few hours a week from finance, IT and each department head. The cash benefit lands over the following months as notice periods expire and renewals come round. Subsequent quarterly reviews typically take half a day once the register and ownership are in place.
How do we find shadow IT and unapproved SaaS tools?
Look beyond the accounts ledger. Company card statements and expense claims reveal tools bought by individuals, while OAuth consent lists in Microsoft Entra ID or Google Workspace show applications staff have connected to company accounts, including free ones. Endpoint inventory from Intune or your RMM tool, renewal emails in shared inboxes and lists requested from agencies and suppliers fill the remaining gaps. Treat discovery as amnesty rather than enforcement, so staff are comfortable declaring what they use.
Is SaaS cost management worth it for a small business?
Usually, yes. Even a 20-person business commonly pays for several dozen subscriptions, and unused seats, overlapping tools and auto-renewals at list price add up quickly. Just as important for a small business is the risk side: knowing which tools hold customer and staff data, and making sure they are not owned by a single person’s login, matters for UK GDPR accountability and for business continuity.
What should we check before cancelling a SaaS subscription?
Export any data you need, confirm how long the vendor retains data after cancellation, and check whether you have a legal duty to keep the records — HMRC generally expects financial records to be retained for six years. Ask the owner to list every process the tool supports, and look for integrations, API keys or webhooks that rely on it. Then give notice in writing within the contractual notice period and file the confirmation.
Does a SaaS audit help with UK GDPR compliance?
Yes. UK GDPR requires organisations to know where personal data is processed and to have appropriate contracts with processors. A SaaS audit produces exactly that evidence: a list of applications holding personal data, their data location, whether a data processing agreement is in place, and how access is secured. It also feeds directly into your record of processing activities and makes responding to subject access requests easier because you know where to look.
Should we buy a SaaS management platform?
For most businesses under roughly 150 applications, a well-structured list in SharePoint or a simple database, with an owner, a renewal date and a quarterly reminder, is sufficient. Dedicated SaaS management platforms automate discovery by connecting to finance systems, card feeds and identity providers, and they track usage continuously. They become worthwhile as the estate grows or when manual discovery is consuming significant time each quarter.
How do we negotiate a better SaaS renewal?
Start 90 days before renewal with evidence: actual active users, your growth plans, and the alternatives you have evaluated. Ask to right-size seats, to move to a tier that matches your usage, to cap annual price increases, and to align renewal dates across products from the same vendor. Multi-year commitments can secure better pricing but reduce flexibility, so weigh them against how confident you are that the tool will still fit in two or three years.
Who should own SaaS governance — IT or finance?
Both, with clear roles. Finance owns the spend data and the purchasing policy; IT owns identity, security and the technical review; each application has a business owner who decides on seats and renewals. A virtual CIO typically sits across all three, running the register and the quarterly review and reporting the KPIs to the board.
Related reading
If you are tightening up software and IT governance, these recent guides cover closely related ground:
Bring your software spend under control
A Cloudswitched virtual CIO can run your first SaaS spend audit, set up the register and renewal calendar, and lead the quarterly reviews that keep sprawl from returning.
Speak to a Virtual CIO








