Annual software spend
The baseline and the saving. Track it per employee as well as in total.
Protect margin
A software stack audit for service businesses
Most established service businesses did not choose their software stack. It accumulated. A tool bought for one project, a subscription a former employee set up on a company card, three products that each do scheduling, and an expensive platform used for a fraction of what it can do. Nobody is quite sure what everything costs or who owns it.
Signs you need this
- You cannot list every software subscription the business pays for without checking card statements.
- Two or more tools do the same job, such as two file storage services or two scheduling apps.
- Staff retype the same information into several systems because they do not connect.
- Former employees may still have access to some systems, and nobody is sure which.
- Software costs have crept up every year without a clear decision behind each increase.
A software stack audit takes stock. It lists every tool, what it costs, who uses it and what it is for, then decides for each one whether to keep it, connect it better, consolidate it or cancel it. Often the most valuable result is not a new tool but fewer tools, better configured, with someone accountable for each.
How it works
Build the inventory
Pull every recurring software charge from card statements, accounting software and invoices. Add free tools staff rely on. For each, note cost, renewal date, contract terms, owner, number of seats and what it is used for.
Check actual usage
Compare seats paid with seats used, using admin consoles where available. Talk to the people who use each tool about what they rely on and what frustrates them. Usage data plus conversations beats either alone.
Map overlap and gaps
Group tools by job: communication, files, CRM, accounting, scheduling, project tracking. Identify duplicates, features you pay for but do not use, and places where data is retyped between systems.
Decide keep, connect, consolidate or cancel
For each tool, make a recommendation with the reason, the saving or cost, and the risk of change. Owners approve the decisions. Contracts and renewal dates determine the order of changes.
Assign owners and review annually
Every remaining tool gets a named owner responsible for access, renewal decisions and value. Put renewal dates in a shared calendar and revisit the inventory at least once a year.
Ways to do it
| Approach | Best fit | Notes |
|---|---|---|
| Do-it-yourself inventory | Small businesses with a modest number of tools and an operations lead who has a few days to spend on it. | A spreadsheet, card statements and admin console checks go a long way. The hard part is making decisions and following through on cancellations. |
| SaaS management software | Larger teams with many subscriptions and frequent staff changes. | Tools in this category can discover subscriptions and track usage. Weigh the subscription cost against the likely savings; for many small firms a spreadsheet is enough. |
| Your IT provider or MSP | Businesses already working with a managed service provider that handles accounts and devices. | They can often report on Microsoft 365 or Google Workspace licenses and security. They may be less focused on whether business applications deliver value. |
| Independent fractional technology lead | Owners who want an outside view tied to business priorities, without a vendor's interest in selling more software. | This is part of what we do. A typical first step is the inventory and usage review, then a written recommendation with savings and risks. |
How we deliver this: AI automation for small business or fractional CTO leadership, scoped in writing and run over 90 days. See pricing or the sample scope.
What we would measure
Paid seats versus active users
Unused licenses are often the quickest saving.
Number of tools per job
Fewer tools doing each job usually means less retyping, less training and less risk.
Tools with a named owner and renewal date
The measure of whether the stack stays under control after the audit.
Risks and how we handle them
| Risk | Mitigation |
|---|---|
| Cancelling a tool that someone relies on for an important but invisible task. | Ask users before cancelling, announce changes in advance, and keep data exports from cancelled tools for an agreed period. |
| Losing data or history when consolidating systems. | Export and verify data before migrating, run old and new in parallel briefly, and check retention requirements for your industry. |
| Former staff or contractors retaining access to systems with client data. | Use the audit to remove stale accounts, enforce multi-factor authentication and set up an offboarding checklist. |
When not to do this
If you have a small number of tools, each with a clear owner and purpose, a full audit is overkill. A quick annual check of renewals and seats will do. And an audit is not useful if nobody has the authority or time to act on it. Agree who will make and carry out the decisions before starting.
Common questions
How do I find all the software my business pays for?
Start with card and bank statements for the last twelve months, then your accounting software's vendor list and email receipts. Ask each team what they use, including free tools. Admin consoles for Microsoft 365 or Google Workspace show connected apps. Expect to find a few surprises.
How much can a software audit save?
It varies widely and we would not promise a figure. Savings typically come from unused seats, duplicate tools and plans set above what you need. The less visible gains, such as less retyping and fewer security gaps, can matter as much as the subscription savings.
Should we consolidate onto one platform?
Sometimes. All-in-one platforms reduce integration work but may do some jobs less well than specialist tools. A practical rule is to consolidate where tools overlap heavily, and keep specialist tools where they clearly support how you deliver work. Decide job by job.
What security issues does an audit usually find?
Common findings include former employees with active accounts, shared logins, missing multi-factor authentication, and client data stored in tools nobody manages. These are often more important than cost savings. We would address access and authentication issues first.
How often should we review our software stack?
A full review once a year is reasonable for most service businesses, with renewal decisions made as each contract comes up. Keep the inventory current by requiring that any new subscription has a named owner and is added to the list before purchase.
By industry
Software stack audit for your industry
IT managed service providers
Find overlapping MSP tools, unused licenses and vendor sprawl before your next renewal. A clear keep-cut-connect plan.
See the details →Marketing agencies
List every tool and seat your agency pays for, find overlaps and unused licenses, and decide what to keep or cancel.
See the details →Nonprofit organizations
Review every nonprofit system, discount and renewal, find overlap and decide what to keep, connect or cancel.
See the details →Guides
How to hire a fractional CTOIs a fractional CTO worth it for a small business?Questions to ask a fractional CTOHow much does a fractional CTO cost?When to hire a CTOSelf-hosting n8n for small business
Questions
What does a fractional CTO do for a small business?How much does a fractional CIO cost?What does a vCIO (virtual CIO) do?How much does AI automation cost for a small business?How do I automate my small business?
Glossary
Token (in AI models)Shadow AIAI readiness assessmentFractional CTOFractional CIOvCIOTechnology roadmapSaaS sprawl
Other solutions
KPI and pipeline dashboardsDocument intake and data extractionInvoicing and collections follow-upInternal knowledge assistantJob scheduling and dispatchHiring and staff onboardingAI usage policy and governanceSystems integrationContract and document review supportCompliance documentationTechnology vendor selection
Next step
Bring one expensive workflow. Leave with a clear next step.
In 30 minutes we look at one recurring workflow, what it costs you today and whether there is a credible case to improve it. If there is not, we will say so.
Book a 30-minute workflow review
Not ready to talk? Take the 3-minute check
30 minutes with Phil or Martin. No technical brief, no pitch deck. Phil or Martin replies personally, usually within one business day.