Long read
RGP’s survey of 400 CFOs: nearly half say transformation demands exceed capacity. Decide who finishes your go-live, and with what time
Many programme plans treat go-live as the finish. We think that for the finance team it is where a heavy stretch of work begins.
On 3 November 2026 RGP published a survey of 400 chief financial officers (CFOs) and equivalent finance leaders. In it, 49% say their transformation agenda exceeds their organisation’s ability to execute. So the work after your go-live will land on a team that may already be full.
Decide now who finishes that work, with how many hours a week, and by what date. Then have your programme lead confirm it before go-live, not after.
Below: the two-minute version, what the CFOs said, what the survey can carry, a worked example in hours and 4 moves for your plan.
The two-minute version
The scene. A go-live moves the programme’s work onto the people who run the business. In finance, that means the first closes on the new system, the data fixes and the new reports.
In this issue. RGP’s survey of 400 CFOs, published on 3 November 2026, puts numbers on the capacity those people have.
What changed against the belief that go-live is the finish:
- New. RGP, 3 November: 49% of the CFOs say their transformation agenda exceeds their organisation’s ability to execute. Just 31% say at least three-quarters of their major initiatives delivered the intended results on time over the past 3 years.
- Escalating. The AI agenda adds to the same team’s load, and the same survey ties capacity to AI returns (below).
- Holds. We found no company this week that published measured results from a recent go-live. The case for planning the weeks after go-live rests on capacity, and RGP asked 400 CFOs about exactly that.
The bottom line: put a named person, a number of hours a week and a date against the work that follows go-live. Do it while there is still time to move other work out of the way.
Where capacity falls short, fewer CFOs report an AI return
RGP asked 400 CFOs and equivalent finance leaders about their outlook and their capacity. Its release reports these findings:
- 89% are positive about their organisation’s financial outlook for the next 12 months.
- 49% say their transformation agenda exceeds their organisation’s ability to execute.
- Just 31% say at least three-quarters of their major strategic initiatives delivered their intended business results on time over the past 3 years.
- 88% report high accountability without corresponding control in at least one area of the enterprise.
One line in the release matters most to a sponsor. Among CFOs whose agendas exceed capacity, 24% report positive AI returns. Among those whose capacity meets or exceeds demand, 79% do.
That is RGP’s comparison of 2 groups of finance chiefs, not proof that capacity causes the return. It still points one way. The CFOs whose capacity meets demand are far more likely to report a return.
We read the 88% as mattering after go-live too. The CFO answers for the new system’s numbers from the first close. Much of the work that produces them is still in other hands: the integrator, the IT team, the data owners.
Scott Rottmann is RGP’s president of consulting services. In the release he said companies “have learned how to allocate capital, but they haven’t learned how to allocate change”.
The survey measures the whole agenda, and go-live adds to it
RGP, a professional services firm, sells on-demand talent and consulting to finance chiefs, so it has an interest in a capacity gap. Its full report sits behind a sign-up form, and we have not seen the full method. The release says iResearch Services ran the survey in September 2026, at organisations with annual revenue of $250 million or more. The results are unweighted.
The figures describe transformation programmes in general. They do not measure what happens after a go-live, and we do not read them that way.
What they do show is the starting point. Nearly half these finance chiefs say the agenda already exceeds what they can execute. A go-live adds weeks of work to that agenda, and it adds it to the same people.
So the question for your programme is who does the work the go-live creates, and what they stop doing to make room.
Illustrative: 8 weeks after go-live, in hours
Every figure here is invented, to show the sum. Use your own.
A finance team of 12 goes live on a new system. For the first 8 weeks, 3 jobs land on it:
| Work after go-live | People | Hours a week each | Weeks | Hours |
|---|---|---|---|---|
| Fixing data the move left wrong | 4 | 6 | 8 | 192 |
| Rebuilding reports the board reads | 2 | 8 | 8 | 128 |
| Teaching the new steps to the rest of the team | 2 | 4 | 8 | 64 |
| Total | 384 |
That is 384 hours, about 10 working weeks for one person. Against 12 people for 8 weeks at 40 hours a week, 3,840 hours, it is 10%. Price it at your own hourly cost, and whether 10% fits is the question for your team.
The plan shows the integrator’s support ending at week 4. Nobody’s other work has been moved.
If the team was already full, those 384 hours come from somewhere. The month-end close runs late, or the next initiative waits. Either way, the choice gets made by default, in week 3, by whoever is busiest.
Written down before go-live, the same 384 hours become a decision. You choose who does each job, and what waits.
List the work that follows go-live, before the date
Write down every job the finance team will carry in the first 8 weeks after go-live. Start with the closes, the data fixes, the reports and the teaching. Ask the integrator what its plan hands over, and when its support ends.
Put an estimate of hours a week beside each job. A rough figure now beats an exact one after the date. If you are already live, run the same list for the weeks still ahead.
Done when: one list shows each job after go-live, with hours a week and the week it should end.
Put one name and a number of hours against each job
Give each job one named person. Agree the hours a week with that person and with their manager, not only with the programme.
If the hours do not fit inside anyone’s week, say so on the list. That gap is the most useful line on it.
Done when: every job has a name and a number of hours a week, and each named person has agreed them.
Choose what waits, and write it down
If the hours exceed the team’s room, something else has to move. Pick it before go-live: a report that can run monthly instead of weekly, or an initiative that starts a quarter later.
Write the choice down, with the date it comes back. A delay you chose can be explained to a board. A delay that happened by default cannot.
Done when: the plan names the work that waits and the date it restarts, and the CFO has signed it.
Have the programme lead confirm it before the date
Take the list to your programme lead. Ask them to confirm the names, the hours and what waits, in writing, before go-live.
Then set 2 dates to look again: week 2 and week 6 after go-live. On each date, compare the hours spent with the hours planned.
Done when: the programme lead has confirmed the list, and the 2 review dates are in the diary.
We expect those 4 moves to take a few meetings with the people you name, and each of them gives up some hours to attend. Your list may show they take more. We think they cost less before go-live than in week 3, when the team is already behind.
A Baseline report grades how an organisation runs change, step by step, red, amber or green. To see one, read ours, which is BusinessGPS assessed by its own Baseline: the BusinessGPS Baseline report.
Sources
- RGP, RGP Study: 89% of CFOs Report Positive Financial Outlook, Yet Nearly Half Say Transformation Demands Exceed Capacity, press release, 3 November 2026. rgp.com