I think the way the forward looking CFO positions approach this (that keeps development velocity high without the 20 layers of paperwork to get CFO approval in old system) is as follows.
New feature coming online, team sits with cost/acctg side and says, we expect our budget needs to go up by $X / month.
Either third party or now AWS budgets for a given tag/project/account are prepared daily.
If the daily / hourly rate > expected, inquiries as to why are made, discipline if needed (rare).
Many CFO's are so happy to be out of the CapEX game, out of the Oracle audit game they will probably put up with a fair bit of a tradeoff there.
Those same CFO's have had a lot of trouble when a project doesn't work out under old approach. Now they just spin down everything in AWS over a few hours.
Govt side in particular, the datacenter buildout costs are CRAZY and the utilization often terrible.
I think this really hits it on the nose. CapEx is “cheap” long-run but often insanely difficult. It only makes sense if you have the scale (1) to control variance (2) to amortize planning costs (3) and it provides a competitive advantage. Meanwhile sysadmins with no knowledge of accounting will complain that on-prem is cheaper. This is why cloud wins.
New feature coming online, team sits with cost/acctg side and says, we expect our budget needs to go up by $X / month.
Either third party or now AWS budgets for a given tag/project/account are prepared daily.
If the daily / hourly rate > expected, inquiries as to why are made, discipline if needed (rare).
Many CFO's are so happy to be out of the CapEX game, out of the Oracle audit game they will probably put up with a fair bit of a tradeoff there.
Those same CFO's have had a lot of trouble when a project doesn't work out under old approach. Now they just spin down everything in AWS over a few hours.
Govt side in particular, the datacenter buildout costs are CRAZY and the utilization often terrible.