How do I audit the software my business pays for?

Software spend has a way of growing in the dark. Nobody decides to overspend; it just accumulates one reasonable subscription at a time until the total surprises you. An audit is the light. It is a straightforward, repeatable exercise, and doing it once a year keeps your stack lean, honest and under your control rather than the other way around.

Step by step

1. List every tool from the money, not from memoryStart with your bank and card statements, not a list you write from recollection, because the tools you forget are exactly the ones wasting money. Capture every recurring charge across a full year to catch both monthly and annual billing. Add anything billed through app stores or payment services. The output of this step is a complete, honest inventory of what you actually pay for, which is more than most business owners expect. Do not stop at the obvious software line items either: some tools bill under a parent company's name you would not recognise, some hide inside a bundle, and some were signed up for by a team member on a shared card. The aim is a list so complete that nothing is paying itself quietly in a corner, because the whole value of an audit rests on it being built from what you truly spend rather than from what you happen to remember spending.
2. Record cost, purpose, usage and owner for eachFor every tool, note its annual cost, what it is for in plain words, how often it is genuinely used, and who owns it. The owner matters: a tool nobody can account for is usually a tool you can cut. This is the core of the audit, turning a list of charges into a table you can actually reason about. Be honest about usage, rating how the tool is used rather than how it was meant to be.
3. Flag overlap, poor fit and data riskNow read the table for problems. Mark tools that overlap, doing the same job as another. Mark tools that fit badly, the ones your team patches with spreadsheets or workarounds. And mark tools that hold important data you would struggle to get out, since that is a risk even if the tool works well. These three flags, overlap, fit and data risk, are where both savings and vulnerabilities hide, and naming them turns vague unease into specific decisions. Overlap and poor fit tend to point at savings: money spent twice, or hours spent patching. Data risk points at exposure rather than cost, which is why it deserves its own flag: a tool can be cheap, well-used and perfectly fitting, and still be a risk if it holds information you could not get back. Reading the table for all three at once, rather than only hunting for waste, is what turns an audit from a cost-cutting exercise into a genuine health check of your stack.
4. Sort each tool into cancel, consolidate, keep or replaceWork down the table and assign every tool one of four outcomes. Cancel the unused and the unaccountable. Consolidate overlapping tools into the best of them. Keep the ones that fit well and earn their cost. Replace the ones that fit badly, cost too much, or trap your data, whether with a better tool or a custom build. Most of the value of the whole exercise lands in this step, because it converts analysis into action you can take this week.
5. Act on the decisions before they go staleAn audit that ends in a nice table and no action saves nothing. Turn each decision into a concrete task with an owner and a date: who cancels this tool, who leads consolidating those two, who scopes replacing the one that fits badly. Do the easy cancellations straight away for immediate savings, and plan the consolidations and replacements carefully so you do not lose data or break a workflow in the rush. Where you decide to replace a tool with a build, treat that as its own considered project rather than something to do overnight. The gap between knowing what to do and doing it is where most of the potential saving quietly leaks away, so close it while the analysis is fresh and the reasons are clear in your mind.
6. Set a date to do it againPut a recurring reminder in the calendar to repeat this audit yearly. Software spend regrows the moment you stop watching it, so a one-off audit fixes today and an annual one keeps it fixed. Each repeat is faster than the last, because you already have the table. This single habit does more to control software cost over time than any individual cancellation, because it turns a heroic clean-up into ordinary maintenance.
7. Watch the trajectory, not just the totalWhen you run the audit each year, do not only compare this year's total against last year's; look at which tools are growing and why. A subscription that has crept up quietly through per-seat additions or renewal increases can become a major line over a few years without ever making a single alarming jump. Note the tools whose cost is climbing fastest and ask whether the value they return is climbing with it. These are the tools most likely to justify a harder look, whether that means renegotiating, consolidating, or replacing them. An audit that captures the direction of travel, not just the current figure, tells you where your software spending is heading, which is far more useful than a snapshot of where it sits today. Over a few cycles this turns the audit from a periodic clean-up into a genuine understanding of your software costs: what they are, where they are growing, and which decisions would bend the curve. That understanding is what lets you make deliberate choices about build versus buy from a position of knowledge rather than reacting to a bill that surprised you.