Closed the FY24/25 centralised European digital platform budget, serving 18 markets, at 0.02% variance against a multi-million-pound plan.
→ 0.02% variance against plan, FY24/25.
Problem
The European digital platform budget was a single, centralised budget for lead technology and digital platform costs, including suppliers and vendors. It served 18 markets across Honda Automobiles, Motorcycles and Power. It ran through a network of global agencies with onshore, nearshore and offshore resource. There was no consistent governance cadence or forecasting process. That made it hard to know, at any point in the year, whether the platform was on track financially.
Context
I joined as European Digital Platform Section Manager in June 2023, with two direct reports and responsibility for the platform's commercial performance as well as its delivery. Budget ownership sat with the role from day one. On a programme this size, serving 18 markets and multiple agency partners, a small forecasting error compounds quickly. I treated the budget as a product I was accountable for, not a spreadsheet someone else would check.
Business objective
Bring financial rigour to a complex, centralised, multi-agency budget serving 18 markets without slowing down delivery. The target was accurate forecasting and early visibility of variance, not just a lower number at year end.
Customer/user objective
Internal stakeholders, finance partners and market teams needed to trust the numbers they were being given. That meant forecasts they could plan against and a governance cadence that surfaced problems before they became write-offs.
Constraints
Eighteen markets meant eighteen sets of local pressures and priorities feeding into one plan. Delivery could not stop while the finance model was rebuilt. And the platform was mid-transition on other fronts at the same time, including a change of lead technology supplier, which added uncertainty to some of the cost lines.
Stakeholders
Finance partners, market leads across the 18 territories, agency account leads, and my own team, including the Delivery Manager and Digital Specialist who reported to me. Budget decisions touched all of them, so the governance model had to work for people with very different levels of financial detail in their day-to-day roles.
Research and discovery
I started by mapping how the existing budget process actually worked, market by market and agency by agency, rather than how it was assumed to work. The gaps were consistent: no single forecasting method, inconsistent update cycles, and no regular point at which spend was reconciled against plan.
Options considered
One option was to leave the process alone and manage variance reactively at quarter end, which is what had been happening. Another was to centralise everything into one rigid template imposed on all 18 markets regardless of local need. I chose a middle path: a single forecasting model and governance cadence, but with enough flexibility for markets to feed in their own numbers on a consistent schedule.
Prioritisation
Centralised governance came first because without it, everything else was guesswork. A new forecasting model only works if the inputs feeding it are reliable and arrive on time. I prioritised building that discipline before trying to optimise spend itself.
Delivery
I built a new forecasting model and centralised the documentation that had previously been scattered across markets and agencies. I established a regular budget governance cadence, so spend was reviewed against plan on a fixed schedule rather than when someone noticed a problem. Throughout FY24/25 I monitored spend continuously and intervened early wherever a variance started to emerge, rather than waiting for a formal checkpoint.
Decisions made
I decided to centralise governance before trying to renegotiate individual costs. Fixing the process came first, because a better number achieved through the old process would not have been repeatable. I also decided to keep the cadence simple enough that market teams would actually use it, rather than building something comprehensive that people would work around.
Trade-offs
A more rigid, top-down process might have given tighter control sooner, but it would have met more resistance from markets and been harder to sustain. I accepted a slower build in exchange for a model that markets would actually follow. I also accepted that early intervention meant raising issues before they were fully understood, which occasionally meant flagging a variance that resolved itself later. I judged that early visibility was worth more than avoiding the odd false alarm.
Business outcome
The FY24/25 budget closed at 0.02% variance against a multi-million-pound plan. The governance model was adopted as standard practice for the platform going forward.
Customer outcome
Finance partners and market stakeholders had a forecast they could rely on and a governance cadence that gave them early warning of any issues, rather than a surprise at year end.
Lessons learned
Budget accuracy at this scale is a process outcome, not a forecasting trick. The 0.02% figure came from consistent inputs and a regular review cadence, not from a clever model applied once. Treating financial governance as part of the product function, rather than handing it entirely to finance, meant issues were caught at the point they were still cheap to fix. I can't point to one dramatic save the cadence produced, and I don't think that would be the honest story here. What it did was stop small variances compounding into a year-end surprise, which is a less dramatic claim than catching a single crisis, but it's the more accurate one.
What I'd improve today
I would build automated reconciliation between supplier invoices and contracted rates earlier in the process. Some of the consistency in the later cadence still relied on manually cross-checking invoices against agreed terms in the first few cycles, and building that automation in from the start would have freed up time for analysis rather than reconciliation.
