Stage 4
Client-Side SI Oversight
You Have an SI. You Need Someone Watching the SI.
The build is active. ECC has its own run team. Now the question shifts from operational stability to delivery governance: is the SI actually delivering what was promised, on the timeline that was promised, at the quality that was promised? The SI's financial incentive is milestone completion — not your operational outcome. Stage 4 is independent governance: someone watching the SI whose incentive is YOUR outcome.
The ISG "State of SAP Migrations" study found that weak governance — not technical challenges — is the primary cause of migration delays. We are not the SI. We are the client's technical representative inside the program — structurally independent, technically equipped, and accountable to outcomes rather than milestones.
Recognition Pattern
You're here if…
- You have an SI under contract for your S/4HANA migration and no independent governance function to validate their progress claims.
- Your project steering committee reviews are based entirely on the SI's own status reporting — green/yellow/red dashboards without underlying data.
- The first change orders have arrived, and you're not sure whether the scope changes are legitimate or whether you're being change-ordered to death.
- Go-live dates have already slipped once — or the SI has signaled they might — and there is no objective framework for evaluating readiness.
- You are approaching a go-live decision and your only data source for system readiness is the SI that has a financial incentive to go live.
- You have no independent validation that the data migration mock results actually reconcile with ECC production.
- Your legal, compliance, or audit teams are asking whether governance artifacts — RACI, risk log, milestone acceptance criteria — are in place, and the honest answer is that you don't know.
- The SI is recommending a go-live date that concerns your internal team but you lack the technical language to formally object.
Risk Assessment
What's at risk
The most dangerous point in any SAP migration is not the technical build. It is the governance gap between what the SI is delivering and what the client believes is being delivered. That gap opens at kickoff and widens throughout the project. By the time it becomes visible — usually at the first go-live slip or the first post-cutover crisis — it has already consumed the contingency budget, the available timeline, and the organizational trust needed to recover.
The ISG "State of SAP Migrations" study — 200+ large-company decision-makers — found that weak governance, not technical challenges, is the primary cause of migration delays. Almost 60% of SAP migrations fall behind schedule and exceed budget simultaneously. Only 8% complete on schedule. SI financial incentives are structured around milestones, not delivery outcomes. When milestone-based contracts meet advisory teams with variable staffing quality, the result is predictable: scope inflation, timeline compression at the end, and a go-live that happens before the system is ready.
The documented failure patterns are consistent. Zimmer Biomet: a $69M contract with Deloitte that produced 51 change orders totaling $23M, five go-live slips, and a warehouse management module that ruptured the supply chain on launch day — the SI had advised the July 4 go-live without disclosing identified showstopper risks. The damages claim reached $172M; the market cap impact reached $2B. Lidl spent €500M over seven years on an SAP retail implementation before declaring the project unachievable and abandoning it entirely. National Grid's post-go-live stabilization cost $585M and required 850 contractors at $30M per month for over two years. The pattern is the same: no independent governance function.
What We Deliver
Independent Governance
Architecture Review Gate
Independent review of the proposed S/4HANA technical architecture against your actual business requirements and data volumes. HANA sizing validated against real production data — not the SI's scoping estimates. Integration design reviewed. Clean core strategy defined: what stays in S/4HANA core, what moves to BTP extensions, what gets retired. This gate happens before the SI begins significant build investment — when changes are cheap.
Data Migration Validation Gate
A minimum of two full mock migration cycles completed with production-like data volumes — not the SI's self-certified "data migration complete" checkbox. Trial balance reconciliation: 100% match between ECC and S/4HANA general ledger balances. Record count matching: extracted versus loaded counts per migration object. Open AR/AP reconciliation at ≤0.1% variance. Business Partner data at 99.5% completeness minimum. Independent validation — not SI self-certification.
Integration Testing Sign-Off
All interface connections tested under realistic production load conditions — not unit tests against stubbed endpoints. RFC call volumes validated against actual ECC production traffic patterns: 600 RFC calls per minute has been documented as a threshold that creates lock entry errors; this must be known and tested before go-live.
Change Order Scrutiny
Every change order logged with: description of scope change, schedule impact in days, budget impact in dollars, business justification, and approval signatures. No change order is processed without documented scope justification traceable to a specific gap in the original statement of work. We maintain that log. We require that documentation. And we escalate when the pattern is present.
Defect Density Tracking
Open defects by severity (S1/S2/S3/S4) per workstream, with trend lines over time and age tracking for open items. Not a green/yellow/red dashboard — underlying data. We track open items at the workstream level, identify when defect aging is inconsistent with go-live confidence, and surface the discrepancy to the steering committee before the go-live decision is made.
Go/No-Go Decision Framework
A structured, evidence-based go/no-go decision — not an SI recommendation. Trial balance reconciliation at zero variance. Zero Severity-1 technical issues open. System performance meeting established benchmarks under production-representative load. Business users confirming operational readiness. CFO or finance director formal sign-off on data acceptance criteria. Explicit risk acknowledgment required for any go-live scheduled on a holiday weekend.
Engagement Structure
How it works
Phase 1 — Embedded from SI Kickoff
We are present from program initiation — architecture review gate, RACI validation, contract scrutiny, governance artifact establishment. The earlier the independent governance function is in place, the lower the cost of catching problems.
Phase 2 — Active Through Build and Test Phases
Quality gate reviews at each phase transition. Change order scrutiny as scope changes emerge. Defect density tracking established from the first UAT cycle. Data migration mock validation executed independently of SI reporting.
Phase 3 — Cutover and Go-Live
Cutover readiness validation completed before the go-live recommendation is accepted. Go/No-Go framework applied. Independent assessment delivered to the steering committee and executive sponsor before the final decision.
Phase 4 — Hypercare Overlap
We remain embedded through the hypercare period — providing a second opinion on SI stabilization progress and an independent view of post-go-live defect patterns before the SI exits. Typical SI governance engagement: 6–24 months from kickoff through hypercare exit.
Field Evidence
What happens without independent governance
Zimmer Biomet retained Deloitte — a 25-year sole-source partner — without competitive oversight or independent governance. The result: 51 change orders totaling $23M on a $69M contract, five go-live slips, a warehouse management module that halted supply chain operations at launch, and a $172M lawsuit.
National Grid deployed SAP without independent program governance. Post-go-live stabilization cost $585M. Financial close extended from 4 days to 43 days. 15,000+ vendor invoices unpaid. Lidl spent €500M over seven years before concluding the project was unachievable. The root cause was not technology — it was the absence of governance maturity. These are not edge cases. ISG found that 55–75% of SAP migrations exceed budget. Only 8% complete on schedule.
55–75%
Migrations That Exceed Budget
Only 8%
Complete on Schedule
$172M
Zimmer Biomet Claimed Damages
€500M
Lidl Abandoned Project Cost
Deep Dive
Related resources
SI Behind Schedule? Five Signals
Five signals your SI is behind schedule — before they tell you.
Change Order Scrutiny Framework
What every change order log must contain — and what it means when it doesn't.
Go/No-Go Decision Checklist
The 12 conditions that must be satisfied before ECC goes dark.
Zimmer Biomet: Lessons for Every SAP Client
What the $172M lawsuit teaches every organization with an SI under contract.
The SI is watching the SI. You need someone watching the SI.
Independent governance is not a luxury. It is the primary determinant of migration outcomes. Start with a 30-minute governance assessment — no pitch, no obligation.