For many organisations, an SAP S/4HANA transformation is one of the largest operational and technology investments they will make this decade.
Yet despite the scale of the investment, many S/4HANA programmes begin to lose traction long before implementation starts, and this failure is rarely caused by the technology or the system integrator (SI). In most cases, the trajectory is set much earlier, during Phase Zero. This is when critical decisions are made on assumptions that have not been properly tested. The uncomfortable truth is that many organisations start S/4HANA programmes without fully understanding the problem they're trying to solve or the environment they're operating in. Everything that follows, including SI selection, then becomes measurably more difficult.
For leadership teams preparing for enterprise transformation, this is where programme risk often begins.
The Hidden Cost of a Weak Phase Zero
The impact of poor upfront planning rarely appears immediately. Most programmes will initiatively look healthy with established governance and mobilised delivery teams. The problems emerge later.
We typically see organisations beginning to experience:
Six to twelve month delays caused by re-scoping and redesign
Budget overruns driven by unplanned complexity and change requests
A lack of alignment between stakeholders and the SI delivery model
Persistent friction between internal teams and external partners
Escalating commercial pressure during implementation
In some cases, complete SI replacement mid-programme
At this stage, the organisation is already committed and recovery becomes significantly more expensive than prevention: contracts are already signed, teams are already in place and leadership expectations are already set. The organisation is no longer building a transformation but is attempting to stabilise one.
What Phase Zero in an SAP S/4HANA Programme Should Deliver
A successful Phase Zero provides clarity before major delivery decisions are made. That includes:
A Realistic Understanding of Current-State Operations
Many businesses rely too heavily on outdated documentation or assumed process contingency. Effective discovery focuses on how the organisation operates today across functions, regions and systems.
Alignment Around Business Outcomes
Successful S/4HANA programmes are not driven solely by technical go-live milestones, they're aligned around measurable business outcomes, including:
Operational efficiency
Process standardisation
Improved reporting and visibility
Scalability
Cost optimisation
Better decision-making capability
Visibility of Programme Complexity
Strong Phase Zero activity identifies risk early across areas such as:
Data readiness
Integration dependencies
Legacy system architecture
Governance maturity
Change readiness
Internal capability gaps
At this stage, organisations either reduce risk or embed it unintentionally.
Clear Criteria for SI Selection
Perhaps most importantly, Phase Zero should define what type of SI is required. Different SIs are built for different delivery environments, with some being highly-effective in template-led, standardised rollouts, and others being better suited to complex, business-led programmes involving high levels of customisation, regional variation or operational change.
Why Organisations Compress Phase Zero
Most businesses don't ignore Phase Zero, but they do accelerate through it, usually because of:
Pressure to maintain momentum
Budget scrutiny from leadership teams
Overconfidence in existing internal knowledge
Limited stakeholder engagement outside core programme teams
Early SI influence shaping the programme definition
Urgency to progress into RFP and procurement activity
It can appear efficient on the surface, but in practice, it creates blind spots that you may only notice during implementation. We continue to see organisations enter SI selection confidently, only for major scope and complexity gaps to emerge six to nine months later. At that point, you're no longer selecting a partner, you're managing costly issues that should have been identified earlier.
How Weak Phase Zero Leads to Poor SI Selection
Most SI procurement processes appear rigorous. There are RFPs, commercial comparisons, stakeholder scoring, capability presentations and governance reviews.
But the quality of the decision depends entirely on the quality of the inputs behind it. A weak Phase Zero makes procurement misleading rather than effective.
1. SIs are Pricing Different Programmes
If scope isn't properly defined, every SI interprets the programme differently.
One may price for a highly standardised rollout, another may assume broader business transformation, and another may optimise around speed and reduced cost. All proposals can appear commercially valid while being fundamentally incomparable.
2. Procurement Favours the Strongest Sales Narrative
When programme clarity is weak, decisions often default towards brand recognition, existing relationships, presentation quality and commercial positioning over long-term delivery fit. This creates the gap between the SI that wins the work and the SI best positioned to deliver successful outcomes.
3. Programme Complexity Appears Too Late
Weak discovery consistently underestimates:
Data remediation effort
Integration complexity
Regional process variation
Internal resource constraints
Change management
This is when programmes begin to experience increased change requests, commercial disputes, timeline slippage and escalating governance pressure. Often, the SI is responding to a moving target rather than underperforming against a stable one.
4. The Delivery Model Doesn't Match the Organisation
This remains one of the most common issues in large-scale SAP transformation. An SI delivery model that works effectively for one organisation may fail entirely in another. Without a realistic understanding of operational complexity, organisations struggle to assess:
Whether the SI has delivered in comparable environments
Whether their governance model fits internal structures
Whether they can support long-term transformation goals
Whether they have depth in critical business areas
At that point, SI selection becomes an expensive operational risk.
Why These Issues Are Increasing Across the SAP Market
The current S/4HANA market is amplifying these challenges. Organisations are now operating with:
Greater cost pressure
Reduced tolerance for delivery drift
Higher expectations around transformation ROI
Increasing competition for experienced SAP talent
Accelerated programme timelines
More complex global operating environments
As a result, mistakes made during Phase Zero surface faster and with greater commercial impact than they did historically.
What Strong SAP S/4HANA Phase Zero Planning Looks Like
Organisations that execute successful transformation programmes treat Phase Zero as a strategic workstream in its own right, not simply a gateway to implementation. In practice, this involves:
1. Discovery That Challenges Assumptions
Effective discovery doesn't simply validate existing internal thinking, it pressure-tests assumptions across operations, governance, systems and business readiness. This often requires broader stakeholder engagement and external perspective.
2. Defining Outcomes Before Scope
Leading organisations establish:
Where process standardisation is appropriate
Where operational differentiation must remain
What measurable success looks like post go-live
What the future operating model should support
This creates stronger alignment between business strategy and programme delivery.
3. Honest Assessment of Complexity
Strong programmes assess complexity realistically across data, integrations, governance, change readiness, internal capability and regional operating models.
4. SI Selection Based on Operational Reality
Only once this foundation exists does SI selection become commercially significant. At this stage, organisations can properly evaluate relevant delivery experience, programme fit, scalability, functional depth, governance capability and long-term partnership suitability. That's when SI selection becomes a strategic transformation decision rather than a procurement exercise.
Most SAP S/4HANA programmes don't struggle because organisations lack ambition or investment, they struggle because critical early decisions are made without enough clarification.
This is where Phase Zero comes in. If rushed, compressed or under-scoped, the consequences extend far beyond the planning stage. They impact SI selection, programme delivery, commercial performance and ultimately transformation success itself.
For organisations preparing to begin an S/4HANA transformation, the most valuable work often happens before implementation formally begins. If the right questions are being asked. most delivery issues are visible far earlier than most businesses realise.
How we can help:
We're increasingly supporting organisations across Europe and the US at the earliest stages of their transformation journeys. This includes providing interim CIOs and Transformation Leaders, advising on Phase Zero and supporting with key hires across SAP, data and enterprise technology.
If you're planning a global transformation, entering Phase Zero or considering whether you have the right leadership in place, this early-stage support is often the difference between a programme that delivers and one that falls short.
If you're currently planning your programme or are assessing your strategy, let's talk.