Go-Live Is Not the Finish Line. It Is Where the Staffing Plan Breaks.

Every S/4HANA business case has the same shape. Cost and headcount climb through design and build, peak at cutover, then fall away. It is a clean curve. It is easy to approve. It is almost never what happens.

Look at where the installed base actually sits. Recent benchmark work puts a little over half of SAP customers as deployed on S/4HANA, but only about a third as fully complete. That gap is the entire story. Deployed means something is live. Complete means the parallel landscape is gone, the phased rollouts are finished, the interfaces are stable, the custom code is settled, and ECC has been switched off. Most of the market is sitting in between, and the space in between is where the budget goes.

The curve is drawn from the wrong event

Cutover is the event everyone can see. It has a date, a war room, a go or no-go call, and a communications plan. So it becomes the anchor for the resourcing model.

But cutover only proves the system starts. It does not prove the design holds. That gets proven at the first period close, at the first month with real transaction volume, at the first audit, at the first time an interface has to handle a peak day rather than a test cycle. Those events sit weeks and months after the date the staffing plan tapers.

What follows is predictable. Hypercare gets extended. Defects that were consciously deferred to protect the go-live date reappear as a phase two backlog nobody has resourced. The remaining rollout waves compete for the same people who just finished wave one. The ECC decommission, which is where a meaningful part of the savings case actually lives, sits unstaffed because it is nobody’s priority and everybody’s assumption.

What December 2027 changes about this

Mainstream support for ECC ends on December 31, 2027. That date is usually discussed as a start-by deadline. It is more useful as a finish-by deadline.

If a program goes live in the first half of 2027, the organization has perhaps two or three quarters of post-go-live runway before the old system stops being a safety net. Running parallel becomes uncomfortable. Falling back stops being an option. Stabilization work that would normally have twelve months of tolerance suddenly has to land inside a much tighter window, with the compliance and security clock running in the background.

That compresses risk into exactly the phase most business cases have already defunded.

The people problem underneath it

There is a pattern worth naming. The moment a program goes live is also the moment its team is most likely to disperse. Contract consultants roll to the next program because the next program is where the day rate is. Internal people who carried eighteen months of overtime take the promotion, the transfer, or the exit they have been holding. The two or three individuals who genuinely understand why a decision was made the way it was become the single point of failure for everything that follows.

Meanwhile the profiles needed in that phase are the scarce ones. Not generalists. Finance consultants who know the Universal Journal in a live environment. Data migration architects. Test automation specialists. Cutover and stabilization leads who have actually run a live S/4HANA period close rather than a test one. Integration people who can trace an interface end to end. That list is already thin in 2026, and every company converging on the same deadline is going to be shopping for it at the same moment.

What leadership should do differently

Three practical shifts.

First, model the staffing curve to the completion date, not the go-live date. If the plan does not show named capacity for the two quarters after cutover, the plan is not finished.

Second, separate run ownership from change ownership before the go-live date is set. If the same people own both, one of them will lose, and it will not be the incident queue.

Third, hire into your own delivery team for the post-go-live phase now rather than in 2027. The market is not going to loosen between here and the deadline. Every quarter of delay narrows the pool and moves the price.

Hirekraft has spent twenty years placing senior SAP consultants into client delivery teams across the US and Canada. The programs that come through this window in reasonable shape are consistently the ones that treated go-live as the middle of the resourcing plan rather than the end of it.

Cutover proves the system works. The quarter after it proves the business case does. Staff for the second one.