Stop defending the budget every quarter. Build an optimisation engine that recycles real, transactable savings into its own next phase — without asking finance for another pound.
I've spent enough time on both sides of the managed service relationship to recognise the pattern. The pitch rarely changes: commit the budget, trust the methodology, and the transformation will follow. The capability you're paying for doesn't exist yet — but the slides are excellent.
What follows is predictable. You spend the next several quarters defending an investment that hasn't yet produced anything you can point a CFO at, while the programme runs in permanent survival mode. The cause is almost never the ambition or the methodology. It's the economics.
When you position ITAM or FinOps as a cost centre that needs continuous budget allocation, you're working against the grain of how organisations behave. Finance resists ongoing spend on capabilities whose value isn't immediately legible — and no amount of conviction overcomes that.
So can a programme fund its own evolution out of the savings it generates?
Most programmes lose credibility for one reason: they present cost avoidance as if it were the same thing as a saving. "We could have spent this, but now we won't" holds up right until finance asks the obvious questions — was this budgeted? Was it contracted? Or was it spend that was never going to happen anyway?
When I talk about a self-funding model, I mean direct cost savings only: a hard reduction in expenditure that was contracted, budgeted, and actively flowing out of the business. Money you can track to the penny and reinvest without going back for fresh approval.
"Spend we didn't make." Not contracted, not budgeted, can't be reallocated. A useful number for a report — and little else.
Contracted, budgeted spend that was leaving the business and now isn't. Trackable, accountable, reinvestable.
The model rests on a straightforward principle. When you identify and actually transact a genuine cost reduction, 20% flows back into the programme; the other 80% returns to the business. That split is deliberate — substantial enough to fund real capability, low enough that finance doesn't resist.
The critical move is to agree this structure before any analysis starts — not after you've delivered value and find yourself negotiating from a weaker position. You put budget reality on the table, ingest actual spend data, run it against usage telemetry, and set targets on what the data shows, not what you'd like it to show.
The biggest source of friction isn't complexity — it's persuading an organisation to be honest about how it actually spends. There's genuine discomfort here: embarrassment about waste, uncertainty about inventory accuracy, and protective instincts around data that might expose past decisions.
People are reluctant to surface the shadow IT, the contracts nobody fully understands, the licence sprawl everyone suspects, and the vendor relationships where they sense over-extraction but can't prove it. The way through is to make their success the objective — to make them look credible to their CFO, CIO and procurement leadership. When people believe you're there to improve their standing rather than demonstrate your own cleverness, the defensiveness drops.
Here's a failure mode that quietly destroys credibility: identifying savings that cannot be converted into budget relief. You spot significant over-licensing, leadership starts planning how to redeploy the capital — then the contractual reality lands. You're locked into a multi-year agreement with committed spend that can't be reduced mid-term.
This is why contract analysis comes before any savings commitment — examining terms, use rights, exit clauses and renewal windows, and separating what can be executed now from what's locked. The FinOps Foundation has noted that organisations absorb substantial audit penalties precisely because they lack visibility into unused or poorly managed licences.
When savings don't materialise where you first projected, that isn't failure — it's a normal part of discovery, provided you can move quickly to the next opportunity. The analytical platform we use, Acuity, lets us test multiple hypotheses in parallel; if one area proves weak under scrutiny, we move to the next candidate without losing momentum, which keeps stakeholder confidence intact through a phase that would otherwise feel uncertain.
The opportunity space is genuinely large. The question was never whether the waste exists — it's whether you can locate it, quantify it precisely, and transact it within the constraints you actually face.
Run several savings hypotheses at once rather than betting the phase on one.
If one area proves weak under scrutiny, move to the next without stalling.
Visible progress during discovery is what preserves stakeholder trust.
The whole programme depends on demonstrating capability quickly. The fastest we've gone from data ingestion to a validated, presentable result was three days: a 12% cloud reduction, transactability confirmed, presented while the engagement still had energy behind it.
From there the model compounds. The first win funds the second phase, the second funds the third, and the third builds the internal capability that sustains everything afterwards — without external justification. Scope expands organically, funded by the value it generates.
I've seen programmes lose momentum after the first or second phase despite delivering genuine savings. The cause is consistent: no coherent roadmap beyond the immediate win, and no real commitment to the multi-phase journey.
What determines whether a programme compounds or fades is how clearly success is defined — tied to how each stakeholder is actually measured. Deliver against all three, with live monthly reporting each can take upwards, and everyone sees it as instrumental to their own success.
Measured on asset visibility & compliance. Give them coverage they can evidence.
Measured on cost reduction. Give them hard, transactable savings, monthly.
Measured on contract savings. Give them renewal-cycle wins they can own.
There's a structural reason to converge the two disciplines. ITAM gives visibility into on-premises infrastructure and traditional licensing; FinOps gives visibility into cloud consumption and dynamic optimisation. Together they cover ground neither sees alone. Gartner projects that organisations integrating ITAM and FinOps to manage SaaS and cloud-based AI will cut AI expenses by 30% through 2028.
Technology leader & cloud transformation specialist.
With 15+ years in IT driving cloud transformation across the UK and EMEA, I specialise in bridging deep technical expertise with the commercial outcomes that matter to enterprise buyers.
My career began on Microsoft Azure — where I built my foundation — and now spans large-scale multi-cloud estates running across AWS and Azure. I've held senior roles at Microsoft and at global partners including SoftwareONE, BCN and Akkodis, and worked directly with major enterprises such as Oracle and BT.
I've also contracted directly with AWS, leading FinOps and TCO engagements — helping organisations gain clarity on cost models, ownership boundaries, licensing optimisation and sustainable cloud economics.
I lead cross-functional teams to design, deliver and optimise enterprise-scale cloud programmes with measurable business impact:
Equally comfortable in the boardroom or the server room, I move seamlessly between CXO-level strategy, technical design workshops, pipeline reviews and delivery escalations. Whether you're starting a cloud-first journey, optimising an existing estate, or you need trusted leadership to de-risk transformation, I bring the platform fluency, commercial insight and delivery rigour to make it happen.
If you're structuring an ITAM or FinOps programme and want a self-funding model finance will actually sign off on, the easiest way in is a 30-minute call — and you do it without asking finance for another pound.