Keep, consolidate, or retire before the next renewal.

Anonymised composite. Identifying names, brands, and contract vendors beyond commodity categories are withheld. Headcount, application counts, and savings bands are rounded.

The situation

ICT could produce vendor lists. Finance could produce invoices. Nobody could produce a single picture of which of just under 100 in-scope applications were duplicates, which licences were unused, which contracts renewed on autopilot, and which parts of the mandate they supported.

Collaboration, case, and reporting tools had multiplied across programmes. Ageing platforms sat next to new purchases. Systems had been bought and not used. End-of-life runtimes sat under processes that still touched citizens, finance, and reporting. A modernisation programme was on the agenda with no agreed keep / consolidate / retire path per application.

The risk was not only spend. The long tail of ungoverned acquisition had widened the IT risk surface, and nobody owned the stakeholder map for switching something off. PFMA-grade accountability was already required. Visibility was not.

Questions the current-state had to answer

• How do we identify low-hanging fruit that will reduce cost and give us more agility?
• Where can we identify cost savings by eliminating duplication?
• Where can we realise potential cost cuts?
• How can we reduce the overall IT risk surface from a long tail of ungoverned organic IT acquisition?
• How do we manage the impact, risk, and stakeholders of application rationalisation?
• In what applications should we increase investment, and which should we phase out?

What we did

The expeditionary team led a current-state of applications, capabilities, cost, and risk. Architecture and finance specialists, working with best-fit tools that complements existing tools, turned that into a living picture of the software portfolio leadership could query.

Each application was scored for mandate fit, business value, technical fit, cost, and risk, then placed on a keep / consolidate / retire / modernise path. Shadow IT was treated as a capability gap, not as employee mischief. Renewals inside 12 months were tagged so a recommendation could land before the vendor's calendar, not after. Architecture as a Service kept the model living, so a new purchase or a PFMA question could be tested against the portfolio as it stood, not against a binder from last year.

What became visible

Cost reduction and portfolio simplification. Redundant, unused, and high-cost applications were named with owners and a rand amount. Duplicate collaboration and reporting were the first harvest. Programme-level copies of the same capability were the political one: same job, several contracts.

Modernisation readiness. The living picture separated systems that should retire before a move from those that should re-platform or retain. New spend stopped following applications already marked to die.

Risk, compliance, and technical debt. End-of-life technologies and unsupported platforms under citizen, finance, and reporting processes were surfaced so remediation had a priority, not a scare story.

A decision before the vendor's calendar. The next cycle of spend had a keep / consolidate / retire path per application, not a debate after the invoice arrived.

Outcome

Inside the first operating quarter on the living picture, the organisation had a sequenced rationalisation list instead of a debate. Duplicate and unused applications were approved for consolidation or retirement against named capabilities. Renewals became decisions before the next cycle of spend.

The keep / consolidate / retire path put about 25 applications on a successor path. First harvest was unused seats on paid platforms and a few duplicate licences, sequenced before the next renewal. Exact contract values stay confidential. The shape of the result is the point: just under 100 in-scope applications on an 8,000-person portfolio became a portfolio with owners, a mandate line, and a rand figure, not a list that only procurement could see.

Time-to-value sat on the Architecture as a Service path: current-state, living picture, extract. Not an 18-month binder.

Cost management · Risk reduction · IT cost case study