How to Audit Your Software Stack in an Afternoon

Most companies can’t tell you what software they’re actually running on. Not because they don’t care — because the stack grew one tool at a time, each added to solve an immediate problem, and nobody ever stepped back to see the whole picture. A stack audit takes an afternoon and almost always finds money.

Step 1: Inventory everything

Pull the list of every SaaS subscription from your accounting system or card statements. Add the tools that don’t show up as line items — the free tiers, the spreadsheets that function as systems, the one-off scripts. The goal is the complete list, not the official one.

Step 2: Group by function

Sort the tools into buckets: sales, finance, ops, HR, support, reporting, communication. Now the overlaps jump out. Two tools in the same bucket doing similar jobs is the most common — and most fixable — source of waste.

Step 3: Map the connections

Draw lines between tools that need to share data. For each line, ask: does data flow automatically, or does a person move it? Every manual line is friction, re-entry, and a place where the data drifts out of sync.

Step 4: Flag the spreadsheet bridges

Wherever a spreadsheet sits between two systems, you’ve found a gap your tools don’t cover. Those bridges are undocumented systems with real version, error, and key-person risk. (More on that in How to Eliminate the Spreadsheet Problem.)

You don’t need a consultant for the first pass — you need an honest afternoon and the complete list. The patterns are usually obvious once you can see the whole stack at once.