There is a moment on every large SAP programme that nobody puts in the plan.
It happens just after the system integrator is selected. The procurement process is finished. The decision has been signed off. The board is relieved. The chosen SI is mobilising and building their team, onboarding their people, working through their commercials. On the client side, there is a collective exhale. The hard part, everyone assumes, is done.
It isn't. The hard part is about to begin, and the first few months after selection are where more retail transformations quietly lose control than at any other single point in their lifecycle.
We have seen this from the inside consistently on greenfield retail S/4HANA programmes. The pattern is consistent enough that it is worth naming.
When an SI is selected, two things happen at once. The client's procurement and evaluation team, who have been intensely engaged for months, step back. On the opposite side, the SI's delivery team - who will run the programme - step in. Between those two movements there is a gap. For a few weeks, sometimes a few months, nobody is really holding the client side of the programme.
That gap is not a scheduling inconvenience. It is where the foundational decisions get made: outstanding enterprise decisions, governance structures, the cadence of reporting, who signs off scope, how change requests are handled, what "done" means for each workstream, how benefits will be measured and by whom. These decisions are made early, often informally, and they are extraordinarily hard to unwind later.
However, the uncomfortable truth is that in that gap, the only party with the capacity, the motivation and the expertise to shape those decisions is the SI. And the SI, entirely reasonably, will shape them in a way that protects the SI.
This needs saying clearly: a good SI is essential, and the better ones are very good indeed. The point is structural, not moral.
An SI on a fixed-price programme has a defined scope and a margin to protect. That is the contract. When governance is being set up, their interest is in a change-control process that protects them from scope creep in their direction. When reporting cadence is agreed, their interest is in reporting that demonstrates progress against their deliverables. When "done" is defined, their interest is in a definition they can confidently hit.
None of this is bad faith. It is simply what it means to be the supplier. However, it means that if the client side is not equally well represented in those same early conversations, the programme's foundational architecture gets built with a quiet, persistent lean — away from the client's interests and toward the SI's.
By the time that lean becomes visible, usually six to nine months in, when a major change request lands, or a workstream slips, or the benefits case starts to look softer than promised, it is baked into how the programme runs. Re-negotiating it then is expensive, slow, and damaging to the relationship.
Three features of retail S/4HANA programmes make this gap more dangerous than in other sectors.
The first is the big-bang reality. Many retail programmes go live across the full estate at once — every store, every channel, on a single date. That removes the safety valve of phased delivery. Foundational decisions made in the quiet months cannot be quietly corrected in a later phase, because there is no later phase. There is one shot.
The second is integration density. A modern retailer's landscape is not just SAP. It is point of sale, e-commerce, warehouse management, planning, and a web of bespoke and third-party systems. The decisions about how these integrate and, crucially, how data flows between them in a way that stays clean-core and compliant are made early. Get them wrong and you are not just carrying technical debt; you can be carrying licensing and architectural traps that surface, expensively, after go-live.
The third is the change burden. Retail workforces are large, distributed, and often have limited prior exposure to SAP. The hearts-and-minds challenge of moving thousands of store and head-office colleagues onto a new platform is enormous and it is almost always under-resourced at the start, because in the quiet months change feels like a problem for later. It is not. The change strategy set in the first 90 days determines whether adoption lands or stalls.
The answer is not a bigger SI, or a tougher contract, or more governance meetings. It is having someone on the client's side of the table, with real delivery expertise, who is present and active during exactly the window where the client would otherwise step back.
That role does three things: -
It owns the client side of the foundational decisions — governance, reporting, scope control, the definition of done — so that the programme's architecture is built balanced, not leaning. It is in the room when the cadence is set, asking the client's questions, not the SI's.
It manages the SI relationship as a partnership of equals — holding the SI to account on outcomes, not just activity, while keeping the relationship constructive. The best client-side leaders make the SI better, because a well-governed programme is easier for everyone to deliver.
And it owns the things the SI structurally cannot — independent benefits realisation, the client's change and adoption strategy, and the honest assessment of whether the programme is actually delivering what the business needs, as opposed to what the contract specifies.
This is what we mean by the Business Integrator model. Not a second SI. Not an extra layer of cost for its own sake. A client-side leadership capability that is present precisely when the client is most tempted to step back, and most exposed if they do.
If you are about to mobilise a greenfield retail S/4HANA programme, the question is not whether your SI is good. It probably is. The question is whether your side of the table is as well represented, as early, and as expertly as theirs.
Because the quiet months are not quiet. They are the loudest months of the entire programme — you just cannot hear them yet.
Limelight is an independent, client-side SAP Business Integrator. We sit in the client's corner on complex S/4HANA transformations - owning leadership, governance, SI management, change and benefits on behalf of the business. We have done this on greenfield retail programmes including Harrods, delivered on time and under budget in under eighteen months. Read the case study here