Application portfolio management (APM) is the discipline of treating your applications as an investment portfolio — knowing what you have, what it costs, what value it delivers, and what to do about it.
Application portfolio management treats your applications the way a fund manager treats holdings: as a set of assets with costs, returns and risks that should be reviewed together and rebalanced deliberately, rather than acquired one at a time and never revisited.
The contrast is with how estates normally grow. Each application arrived through a defensible individual decision. Nobody ever decided to run four systems doing content management, but that is what the accumulation of good local decisions produces over a decade.
The costs of an unmanaged portfolio are rarely visible in one place, which is why they persist:
Four dimensions, kept deliberately small so they can actually be maintained:
| Dimension | What you are asking | Typical sources |
|---|---|---|
| Cost | Total annual cost to own and run | AP, licensing, hosting, support effort |
| Business value | How much the capability depends on it, and how well it serves | Business owner assessment, user survey |
| Technical health | Supportability, currency, architectural fit, defect load | Technical owner, vendor lifecycle dates |
| Risk | Security, compliance, continuity, key-person exposure | Security register, continuity plans |
Cost and technical health can be gathered largely from systems. Business value cannot — it requires asking people, and that is what makes it the dimension most often skipped and most often decisive.
Dedicated APM tooling is genuinely useful at scale, particularly for keeping data fresh across a large federated estate. It is also a common way to spend a year and a six-figure sum before producing a single decision.
For an estate under a few hundred applications, a well-structured spreadsheet does everything the first two rounds of analysis require. Tooling solves a maintenance problem, and you should only take on that solution once you have proven the analysis produces decisions worth maintaining. Buy the platform after the first rationalisation has paid for itself, not before.
Keep the first pass shallow and complete rather than deep and partial.
The single biggest determinant of whether APM survives is whether it is wired into a decision that happens anyway. Attach the portfolio review to annual planning, so the estate is assessed when budgets are set. Attach a lightweight check to procurement, so nobody buys a fifth content management system without someone noticing the other four.
APM run as a standalone initiative produces a report. APM run as an input to funding decisions changes the estate.
The Applications Assessment & Rationalisation Toolkit gives you a ready APM starting point — a scored inventory, portfolio calculator, capability map and cost view, with a completed worked example.
