- CLOUD/EDGE
- RUN
- C5 · FINOPSCOMMAND™
- 12-MONTH RETAINER
Cloud cost governance,held for twelve months.Not a one-off optimisation report gathering dust.
A UAE enterprise had commissioned two cloud cost optimisation reports in the previous eighteen months. Both identified 25-35% waste. Neither optimisation was sustained six months post-report. The C5 retainer reframed the problem: governance operations as monthly SLA cadence, not annual assessment. Year-one cloud spend held to a governed trajectory ~32% below pre-engagement baseline.
N=1 ILLUSTRATIVE COMPOSITE — representative pattern for a UAE enterprise operating at scale. Details drawn from patterns across NexITC engagements and market data. Not a specific client narrative.
THE SITUATION
The situation
The client is a UAE enterprise in a regulated sector, operating a hybrid multi-cloud footprint across two hyperscaler UAE regions with monthly cloud spend in the low seven figures AED. Cloud adoption had been running for approximately four years, with governance discipline lagging spend growth — a common pattern where teams onboarded workloads faster than the tagging standard, rightsizing cadence, and reserved capacity discipline could catch up.
Two prior cloud cost optimisation engagements — one by an internal transformation office, one by a global SI — had identified aggregate waste in the 25-35% range. Both engagements produced comprehensive optimisation reports. Both reports were partially actioned in the following six weeks, then progressively deprioritised as other operational priorities surfaced. By month six, measured spend had drifted back to within 5-10% of pre-engagement baseline.
The CFO surfaced the problem in a board meeting. The pattern was clear: optimisation as one-off reports did not hold. Something structural had to change.
THE SPECIFIC QUESTION
The specific question
The clinic conversation surfaced what "structural" would mean. The CFO did not want a third optimisation report. The CFO wanted governance cadence — monthly SLA-measured operations that held cost trajectory continuously, with named accountability and quarterly release commitments the CIO's team could act on.
The Practice Lead's scoping response confirmed C5 as the right shape: a 12-month managed retainer against cloud spend governance outcomes, measured monthly, with the tagging standard, rightsizing cadence, and reserved capacity discipline held as operations rather than assessment. Retainer fee structured against governed cost trajectory, not consumed hours.
APPROACH AND TIMELINE
Approach and timeline
The retainer operates on a twelve-month cadence with monthly SLA cadence and quarterly release commitments.
Months 1-3 established baseline: comprehensive tagging standard rolled out across active workloads, rightsizing pass against the largest 40% of spend, reserved capacity commitment structured against the workloads with predictable steady-state consumption. Months 4-6 operationalised: monthly governance council with the CFO's team and the CIO's team, monthly SLA scorecards against cost trajectory targets, quarterly release for governance model adjustments based on operational reality.
Months 7-12 sustained operations: continuous tagging enforcement (automated where the tooling supported it, workflow-enforced where it didn't), monthly rightsizing rhythm against the 60% of spend not covered in Month 1's pass, reserved capacity revisions per quarterly release, and — critically — governance conversations with product teams onboarding new workloads before those workloads onboarded, not six months after.
Practice Lead attendance ran across all twelve monthly reviews. Escalation to CEO was invoked once, on a quarterly release scoping question requiring CFO-level agreement on cost trajectory targets.
WHAT WE RECOMMENDED AGAINST
What we recommended against
The recommendation the engagement was scoped to be willing to make.
Two elements the client's internal debate had assumed were in scope were recommended against during retainer scoping.
The proposed third-party FinOps platform licensing — approximately AED 400K annual licensing fee for a specialist FinOps tool the internal team had scoped — was recommended out of scope. The hyperscaler-native tooling captured 80-85% of the observability the third-party tool provided, at zero incremental licensing cost. Recommendation: operate against native tooling for the first four quarters of the retainer; revisit third-party tooling only if a specific observability gap surfaced that the native tooling could not close.
The proposed broad cost allocation reframing — a project to redesign the cost centre model across the enterprise to reflect cloud-consumption patterns — was recommended out of retainer scope. It was legitimate work but distinct from cost governance operations. Bundling it would have compromised the monthly SLA cadence discipline. Recommendation: cost allocation reframing as a separate finance-led initiative; retainer stays focused on governed cost trajectory.
Both recommendations were accepted. Neither the third-party FinOps platform nor the allocation reframing was activated during Year 1.
OUTCOMES
Outcomes
Cloud spend closed Year 1 approximately 32% below pre-engagement baseline, measured against monthly SLA cadence rather than one-off snapshot. The trajectory held month-over-month from Month 3 onwards, with no drift months — the operational discipline the two prior optimisation reports had failed to produce.
The tagging standard achieved approximately 96% coverage of active workloads by Month 6, sustained at that level through Year-end. The rightsizing operational rhythm surfaced approximately AED 850K in incremental annualised savings across Months 4-11, incremental to the Month 1-3 baseline pass. Reserved capacity discipline captured approximately AED 620K in annualised savings in the two quarterly release cycles that adjusted commitment shape.
The CFO's stated Year-1 success measure — "spend growth decoupled from workload growth" — was met in three consecutive quarters.
WHAT COMES NEXT
What comes next
The retainer renewed into Year 2 at a scoping conversation between the CFO and Practice Lead in Month 11. Year-2 scope expands to include DataOps governance for the workload cluster where cost governance surfaced data pipeline reliability as a related operational discipline — routing through C4 DataOpsCommand rather than expanding C5 scope.
Adjacent SKUs: C5 · A7 Cloud Cost Leak Scan™ · C4 DataOpsCommand™
Cloud spend drifting back after optimisation efforts?
Book a clinic. Practice Lead attends. Governance operations as monthly SLA cadence — not another optimisation report your team actions for six weeks before priorities shift.