Optimizing the Cost of IT Operations
When a board sets a mandate to cut IT costs by 30% in 18 months, the instinct in most organizations is to freeze headcount and cancel projects. That approach usually saves money in the short term and destroys delivery capability in the medium term. This engagement took a different path — restructuring how the IT function operated rather than simply reducing its size.
The result: 38% reduction in IT operational spend within twelve months, with deployment frequency doubling over the same period.
The Situation
The client was a regional enterprise with operations across four countries and a centralized IT department of 210 people. IT spend had grown at 18–22% per year for three consecutive years. The CFO had flagged IT as the fastest-growing cost centre in the business, and the board had set a clear directive: reduce the run-rate by at least 30% within 18 months without materially impacting service delivery.
The CTO had ruled out a wholesale outsourcing arrangement — a previous attempt a decade earlier had ended poorly, with knowledge loss and a recovery that took two years. What was needed was a surgical approach: understand exactly where the money was going, where the inefficiencies were, and design a leaner model that the internal team could actually operate.
Nematix was engaged to run the diagnostic and design the target operating model.
The Challenge
The first problem was visibility. Despite the scale of IT spend, the organisation had no single view of where the money went. Budget was split across seven cost centres, three outsourcing contracts, eleven SaaS subscriptions, and internal headcount. Nobody had ever mapped these against the business value they produced.
The diagnostic surfaced several structural issues:
- 60% of engineering time was spent on maintenance, not product delivery — largely because technical debt in core systems required constant intervention
- Three overlapping monitoring tools were licensed simultaneously, each used by a different team that didn’t know the others existed
- Twelve contractors had been brought in for specific projects and never off-boarded; their contracts were still active and being invoiced
- Two of the three outsourcing contracts had auto-renewed at above-market rates; nobody had reviewed their terms in four years
- High-cost permanent engineers were doing work that could be done by less senior staff or automated — not because of competence gaps, but because of poor task routing and no structured escalation model
Our Approach
The engagement ran in two phases.
Phase 1 — Spend audit and opportunity mapping (weeks 1–8)
We mapped every line of IT spend to a business capability, then scored each capability by strategic value and cost efficiency. This produced a heat map: which functions were expensive and high-value (keep and protect), which were expensive and low-value (restructure or eliminate), and which were cheap and high-value (invest further).
We identified MYR 4.2M in annualised savings from immediate actions alone: terminating the inactive contractor contracts, consolidating monitoring tooling onto one platform, and renegotiating the two auto-renewed outsourcing agreements.
Phase 2 — Operating model redesign (weeks 9–28)
The larger opportunity was structural. We redesigned the IT operating model around three tiers:
- Core team — a leaner permanent team of senior engineers focused exclusively on architecture, security, and strategic delivery
- On-demand expertise — specialist skills (cybersecurity, data engineering, platform infrastructure) accessed through Nematix’s Expertise as a Service model as needed, not as permanent headcount
- Managed services — routine operations (L1/L2 support, infrastructure monitoring, patch management) moved to a managed services provider at a fixed monthly rate below the previous variable cost
We ran a parallel change management track — restructuring without communicating the rationale clearly is how you lose your best people. The CTO led internal communications; Nematix provided the data and narrative to support every conversation.
Outcome
At the twelve-month mark, the client’s IT operating cost had fallen by 38% against the prior-year baseline. Importantly, delivery performance improved over the same period.
| Metric | Before | After (12 months) |
|---|---|---|
| IT operational spend | Baseline | −38% |
| Deployment frequency | 2× per month | 4–5× per month |
| Engineering time on maintenance | ~60% | ~35% |
| Active vendor/contractor contracts | 47 | 28 |
| Support ticket resolution (SLA compliance) | 71% | 89% |
The board’s 30% target was exceeded. The CTO retained the team members they needed, and the engineers who remained reported higher job satisfaction — they were doing more meaningful work.
Key Takeaways
You can’t cut your way to efficiency. Blanket headcount reductions reduce cost and capability proportionally. The better question is whether the current cost structure reflects the value being delivered. In this case, it didn’t — and restructuring the model produced savings larger than any headcount freeze would have.
Contractor management is a hidden cost centre. Most organisations with contractors don’t actively manage off-boarding. Active contracts for inactive contributors are pure overhead and surface immediately in a spend audit.
The hybrid model outperforms both extremes. Neither full in-house staffing nor full outsourcing was the answer. A permanent core team handling strategic work, supplemented by on-demand expertise for specialist needs, produced the best outcome on both cost and quality dimensions.
This engagement draws on our Strategy & Transformation and Expertise as a Service capabilities. Contact us if your IT spend is growing faster than your delivery output.