What the role actually covers
Strip the language back and transformation work is four things: moving off systems that no longer fit, standardising process across a business that grew without any, rebuilding the data so reporting can be trusted, and reshaping the team around the new way of working. The scale of it varies enormously. The pattern does not.
What a real mandate looks like: a candidate I work with implemented ERP, payroll, banking and expense systems, moving their previous business from reliance on Excel and email to automated workflows.[1] That is transformation at scale-up scale, and it is a two-year job disguised as a systems project. At the top end it appears bundled into executive briefs. An interim CFO role I recruited for required commercial and strategic partnership on M&A, capital allocation and banking relationships, alongside driving a significant ERP and systems transformation.[2]
Why these projects fail, and it is not effort
A Head of Finance told me the core problem in a critical finance transformation project was not a lack of effort, but a fundamental lack of standardisation.[3] That is the honest diagnosis for most of them. Teams work hard on a transformation while the underlying processes still differ by entity, by team and by person, so the new system inherits the old chaos and the project is judged a failure eighteen months later.
The symptom to watch is close time. A twelve-day month-end close is usually caused by manual data pulls from three different systems, reconciliation in Excel and reformatting for board reports.[4] That is a process and data problem wearing a systems costume. Buying a new ERP without fixing it just relocates the twelve days. The measurable win looks like the reverse: one accountant introduced process improvements at month end that reduced close time from nine working days to five.[5] No new platform in that sentence.
| Transformation run as a systems project | Transformation run as a process rebuild | |
|---|---|---|
| The starting diagnosis | The systems are wrong. Scope a platform selection and a migration timeline. | The processes differ by entity, team and person. Standardise first, then choose a system to carry it. |
| Why it fails | Not lack of effort. The new system inherits the old chaos, and the twelve day close simply relocates. | It usually does not. Close time falls because the work upstream got simpler, with or without a new platform. |
| Who should run it | A dedicated transformation director with a PMO. Real in large corporates, overhead in a scale-up. | The first senior finance hire or an interim executive with a bounded mandate and a defined end. |
Where the role sits by stage
In large Australian corporates, banks and insurers, finance transformation director is a real standalone title with a PMO, a budget and a multi-year programme. If that is your search, brief a firm that works corporate and consulting-adjacent change markets, because the candidate pool sits there.
In the startup and scale-up segment I work in, it almost never has its own title. Transformation is a mandate handed to a first finance hire or a first CFO, alongside everything else. The Head of Finance or Financial Controller who is the first senior finance hire at a business of 10 to 20 headcount is usually the person who ends up choosing the ERP, rebuilding the close and standardising the process.[6] Hiring a separate transformation director at that stage is buying overhead you cannot use.
The other common answer at that scale is AI rather than headcount. In our Q2 2026 State of the Market report, 86% of finance teams are engaging with AI in some form, with one-third past experimentation into active implementation or business as usual.[7] The practical version: an Australian scale-up controller refreshes their board pack every Monday with a single instruction, then checks revenue, cash and ARR against Xero and adds commentary, removing the manual rebuild entirely.[8] That is transformation delivered without a transformation hire.
If you are working out who should own this work at your stage, the finance team structure by stage is the faster answer here.
How to hire for it
Screen for standardisation instinct, not systems logos. Anyone senior has an ERP implementation on their CV. Far fewer can describe how they got three entities onto one process before the migration, which is the part that determines whether it works. Ask them to diagnose a twelve-day close and listen for whether they reach for process or for software.
Then screen for the delivery environment. Large-corporate transformation experience does not automatically transfer to a scale-up, where there is no PMO, no change manager and no budget for either. The best hires at this end are not defined by the size of their previous business, but by their ability to think when there is no playbook.[9] A candidate who ran a programme with forty people supporting them may struggle badly with the same mandate alone.
Finally, consider interim rather than permanent if the work has a genuine end. 48% of businesses are using interim cover while continuing a permanent search for senior finance roles,[10] and a bounded transformation is exactly the kind of mandate an interim executive is built for. Hiring permanently for a two-year project leaves you with a role you have to redesign in year three.
If the transformation has a defined end date, the interim route and what it costs are set out here.
Common questions
What does a finance transformation director actually do?
Four things: move the function off systems that no longer fit, standardise process across a business that grew without any, rebuild the data so reporting can be trusted, and reshape the team around the new way of working. A representative scale-up mandate looks like implementing ERP, payroll, banking and expense systems to move a business off Excel and email onto automated workflows. At executive level it often arrives bundled with M&A, capital allocation and banking relationships in an interim CFO brief.
Why do finance transformation projects fail?
Rarely for lack of effort. A Head of Finance told me the core problem in a critical transformation was a fundamental lack of standardisation, and that is the usual diagnosis. Processes differ by entity, team and person, so a new system inherits the old chaos. The tell is close time: a twelve-day month-end is typically manual data pulls from three systems, Excel reconciliation and reformatting for board reports. That is a process problem in a systems costume, and new software relocates it rather than fixing it.
Should a scale-up hire a dedicated transformation director?
Usually not. In startups and scale-ups this work has no separate title, it is a mandate handed to the first finance hire or first CFO alongside everything else. Hiring a standalone transformation director at 10 to 20 headcount buys overhead you cannot use. If the work is bounded, an interim executive is often the better structure: 48% of businesses now use interim cover while continuing a permanent search, and a two-year project is exactly the mandate interim is built for.
What should I screen for when hiring transformation capability?
Standardisation instinct over systems logos. Everyone senior has an ERP implementation on their CV, but far fewer can describe how they got multiple entities onto one process before the migration, which is the part that determines success. Ask them to diagnose a twelve-day close and listen for whether they reach for process or software. Then test the delivery environment: someone who ran a programme with forty people supporting them may struggle badly with the same mandate and no PMO.
References
- Story Recruitment candidate: implemented ERP, payroll, banking and expense systems, moving their previous business from reliance on Excel and email to automated workflows.
- Story Recruitment interim CFO mandate: commercial and strategic partnership on M&A, capital allocation and banking relationships, plus driving a significant ERP and systems transformation.
- A Head of Finance to Tom Hunter: the core problem in a critical finance transformation project was not a lack of effort, but a fundamental lack of standardisation.
- Tom Hunter: a 12-day month-end close is often due to manual data pulls from three different systems, reconciliation in Excel, and reformatting for board reports.
- Story Recruitment example of a quantified achievement: process improvements at month end reducing close time from 9 working days to 5.
- Story Recruitment focus: the first finance hire in a startup, typically a Head of Finance or Financial Controller, for businesses with 10 to 20 headcount and $5 to $10M ARR or less.
- Story Recruitment Q2 2026 State of the Market report: 86% of finance teams are engaging with AI in some form, with one-third past experimentation into active implementation or business as usual.
- Story Recruitment Australian example: a scale-up controller uses AI to refresh their board pack every Monday with a single instruction, then checks revenue, cash and ARR against Xero and adds commentary, eliminating the manual rebuild.
- Tom Hunter: the best first finance hires are not defined by the size of their previous business, but by their ability to think when there is no playbook.
- Story Recruitment Q2 2026 State of the Market report: 48% of businesses are using interim cover while continuing their permanent search for senior finance roles.