What a Software Portfolio Audit Covers (and What You Get at the End)
Most companies don’t have a software problem. They have a visibility problem. Somewhere between the third internal tool and the fifth “temporary” integration, they lost track of what they actually own.
A software portfolio audit fixes that. Here’s what one covers.
1. A complete inventory
Every application, integration, script, automation, dashboard, and spreadsheet that does more than a spreadsheet should. For each one:
- What it does: stated purpose versus actual use
- Who depends on it: users, downstream systems, and business processes
- What it costs: licensing, hosting, maintenance time, and coordination overhead
- Who maintains it: or the fact that nobody does
2. A dependency map
Systems don’t exist in isolation. The audit traces:
- How data flows between systems
- Integration points and how they fail
- Shared credentials and access patterns
- Single points of failure
This is usually where the surprises are, such as the nightly script that three departments unknowingly depend on.
3. A risk assessment
Not all technical debt is equal. The audit identifies:
- Key-person dependencies: systems that stop being changeable when one person leaves
- Undocumented logic: business rules buried in code nobody reads
- Security exposure: credentials in repositories, outdated dependencies, missing access controls
- Compliance gaps: what would fail a security review or audit tomorrow
4. A prioritized action plan
A list of problems isn’t useful on its own. The audit ends with recommendations ranked by risk and return:
- What to keep: it’s working, so leave it alone
- What to consolidate: several tools doing one job
- What to rebuild: critical but too fragile
- What to retire: nobody will miss it
How the process works
Weeks 1–2, discovery. Stakeholder interviews, documentation review, and access to systems. The goal is the full picture, including what’s actually running rather than what’s on the org chart.
Weeks 2–4, analysis. Inventory, dependency tracing, risk assessment, and identifying redundancy.
Weeks 4–6, synthesis. Recommendations, cost estimates, and prioritization, delivered as an executive brief plus a technical appendix.
Readout. A working session with leadership to walk through findings and next steps.
What happens after
You have three options:
- Execute internally. The documentation is yours and is structured for handoff.
- Bring in help to execute, including ongoing ownership through managed software services.
- Do nothing for now. At minimum, you know what you’re carrying.
The audit is a fixed-scope engagement under a statement of work. If you continue into managed services, it sits under the same enterprise service agreement, with no second procurement cycle.
Learn more about the Software Portfolio Audit.
Tell us what you're running.
Two quick steps. I'll read it personally and reply with an honest read on your situation and whether our team can help, usually within one business day.
- I lead every engagement personally
- No sales sequences, and your details are only used to reply
Prefer email? [email protected]