There is a conversation I have had many times with IT leaders at mid-market organizations — companies with $500M to $2B in revenue, typically running SAP ECC, now facing the 2027 migration deadline. The conversation usually starts with a question about system integrators or deployment models, but it almost always ends up in the same place: the staffing problem.

The staffing problem is this: a well-run S/4HANA transformation requires a set of capabilities that most mid-market organizations simply do not have on staff — and cannot economically justify building. The talent exists in the market. It is expensive, in high demand, and largely employed by the firms that also want to sell you an implementation. The structural tension this creates is one of the most consistently underestimated risks in mid-market SAP programs.

What a proper program team actually requires

Let me be specific about the capabilities a mid-market S/4HANA program genuinely needs in order to deliver well. This is not a theoretical framework — it is a composite of what I have seen matter, repeatedly, in programs that went well and programs that did not.

Core capabilities required for a well-run mid-market S/4HANA program
Program Governance
A senior program manager who has led SAP transformations of comparable scope — not IT project management generalists. Someone who can read what an SI is doing, identify schedule risk before it becomes a delay, and manage the politics between internal stakeholders and an external delivery team without losing either relationship.
Solution Architecture
An architect who understands both the SAP standard model and your industry's process requirements well enough to validate design decisions independently. Not someone who will defer to the SI's recommendations because they lack the depth to challenge them.
Data Migration
A dedicated data migration lead — not a functional consultant doing data work on the side. Someone who has managed the full complexity of moving HR master data, payroll history, open items, and legacy attachments across a real cutover event. This is one of the highest-risk workstreams in any program and the one most frequently under-resourced.
Change Management
An organizational change lead who understands SAP programs specifically — the disruption that process standardization creates, the training demands of a system that works fundamentally differently from ECC, and how to build adoption momentum in an organization that is simultaneously trying to keep the business running.
The gap: Each of these roles requires 10–20 years of SAP-specific experience to perform at the level a complex transformation demands. At market rates, fully loaded, you are looking at $350K–$500K per senior resource per year. A properly staffed client-side program team for a $15M implementation typically requires four to six such roles. The math does not work for most mid-market organizations.

The three strategies companies use — and what they actually cost

In my experience, mid-market organizations facing this gap typically choose one of three paths. Each has a real cost that rarely appears in the original budget.

Strategy one: Delegate to the SI. The most common response to the talent gap is to lean on the SI to fill it. The SI provides a program manager, an architect, a data migration lead. They are capable people. The problem is the conflict of interest that Matt Hough describes in the adjacent piece on these pages — when the entity overseeing delivery is also the entity doing the delivery, the oversight function degrades. Change orders get approved that might not survive independent scrutiny. Design risks go unvoiced. The client-side team, understaffed and dependent on the SI for information, gradually loses the situational awareness to push back effectively.

Strategy two: Hire experienced talent. Some organizations attempt to build the team properly — hiring senior program managers and architects as permanent staff or extended contractors for the duration of the program. This can work, but it introduces its own challenges. The best SAP talent is in high demand and often not available on the timelines that mid-market programs need. Recruitment takes longer than expected. And individuals hired specifically for a transformation often leave or disengage once the program enters steady-state operations — leaving an institutional knowledge gap at exactly the moment when stable expertise matters most for post-go-live optimization.

Strategy three: Promote from within. The internal IT director becomes the program manager. A functional consultant steps into the architect role. The HRIS manager leads data migration. These individuals know the organization deeply, which is genuinely valuable. What they almost always lack is the program-level pattern recognition that comes from having done this before — having seen where the second-order problems emerge, having negotiated with an SI through a contentious design decision, having managed a cutover that hit unexpected complications at 2am.

"The internal team knows the organization. The SI knows the technology. The gap — pattern recognition from having actually done this before — is what independent advisory is built to fill."

Why the cost-quality trade-off is not actually a trade-off

The framing that mid-market organizations often use — we cannot afford the senior talent, so we will make do with what we have — treats this as a cost management decision. I want to challenge that framing directly.

A $15M SAP implementation running 30% over budget costs $4.5M in unexpected spend. A go-live delay of two months, with a team of fifty people waiting and an SI billing at daily rates, typically runs $800K to $1.5M. A failed user adoption problem — where the system goes live but business processes revert to workarounds within six months — can be significantly harder to quantify but represents a material failure of the program's entire business case.

The talent gap is not a constraint to be managed. It is a risk to be mitigated. And the mitigation cost — bringing in experienced, independent advisory capacity at the program level — is almost always less than the expected value of the problems it prevents.

What the alternative looks like

The model that works for mid-market organizations is one that separates two things that often get conflated: the day-to-day execution capability, which the SI provides, and the senior oversight and pattern recognition that sits above the SI and works on behalf of the client. These are not the same function and they should not be performed by the same organization.

Concretely, this means an independent senior advisor — or a small team of two to three — who are present at the key decision points throughout the program lifecycle. Not embedded in the delivery team, not managing day-to-day tasks, but available to review design decisions before they are committed, to validate that the program governance is functioning as designed, to ask the questions that the client's internal team does not yet know to ask.

This is not a new model. It is how major capital projects in other industries — construction, infrastructure, aerospace — have been managed for decades. The owner's representative, who works exclusively for the project owner and has no financial interest in the contractor's choices, is a standard feature of complex project delivery precisely because the alignment problem is well understood.

SAP transformations are complex capital projects. The mid-market has been slow to apply this model, largely because the SAP advisory industry has been dominated by firms that also do implementation work. The structural incentive to keep advisory and delivery integrated — it is more profitable — has obscured the value of keeping them genuinely separate.

The 2027 deadline is creating a moment of urgency that makes it easier to make the right choice or the fast choice. The organizations that will look back on this period with satisfaction are the ones that treated the talent gap as the program risk it actually is — and addressed it directly, rather than hoping the SI would fill it.