Start here
This FAQ is written for the directors, executives and sponsors who own an SAP S/4HANA implementation and cannot independently verify what they are being told about it. It covers a stalled or failing SAP implementation, a program that is over budget or has missed its go-live date, a dispute with the System Integrator, and a cyber attack that has taken SAP down.
Ownerstone is an independent SAP crisis advisory based in Atlanta, Georgia. Boards, C-suite & PE Operating Partners retain it to conduct an independent SAP S/4HANA program review: establishing what is actually happening, quantifying the financial and operational exposure, and setting out the realistic options. The firm does not implement SAP, does not supply consultants, has no commercial relationship with SAP or any System Integrator, and has no stake in the outcome. It reports only to the owner. The same review is applied at Quality Gates to prevent a crisis, and after a cyber event to verify the recovery.
This page is for the owners of an SAP implementation. It is not a resource for implementation partners or SAP consultants seeking engagements.
The warning signs are usually visible for quarters before the cost becomes public. Lamb Weston reported that its ERP transition reduced net sales by approximately $135 million and Adjusted EBITDA by approximately $95 million in a single quarter (fiscal third quarter 2024 results, released April 4, 2024; see Public cases referenced).
If this is your program, write to [email protected]. One paragraph on where it stands is enough. A reply comes within one business day; the conversation is confidential and carries no obligation.
Request a Confidential AssessmentConfidential. No obligation. Reply within one business day.
SAP S/4HANA is the current generation of SAP's enterprise resource planning (ERP) software, the core system for finance, supply chain, and operations that most of these programs are implementing.
The System Integrator (SI) is the consulting firm contracted to build and deliver the system.
A Quality Gate is the formal checkpoint at the end of a program phase at which the owner decides, on evidence, whether the phase is complete and the next phase, and usually the next tranche of funding, may be released.
A Change Request (CR) is a formal, priced addition or alteration to the agreed scope. The Change Request log is the record of all of them, and it shows whether the company is paying for new scope or for the integrator's rework.
Basic Questions
For anyone meeting the idea of an independent review for the first time
01Our SAP S/4HANA implementation has stalled. Who can independently review it and get it back on track?
When an SAP S/4HANA implementation stalls, the organization requires a dedicated SAP crisis advisory: an independent, conflict-free firm retained directly by the program owner rather than by the System Integrator (SI).
Asking the incumbent SI to review its own work creates an obvious conflict of interest, while engaging another large implementation firm often leads to a pitch to rip and replace the existing build with their own staffing bench. Instead, an independent crisis advisory acts exclusively as an owner's advocate, inspecting live system evidence to establish ground truth, quantifying financial and operational exposure, and laying out realistic options to stabilize the architecture and execute a controlled path to go-live and stabilization. See question 4 to learn what steps to take next.
Related engagement: Transformation Rescue
02What is an SAP crisis advisory?
An SAP crisis advisory is an independent firm engaged by program owners and executives to establish ground truth, quantify operational and financial exposure, and set out a realistic recovery strategy. It is deployed when a transformation is stalled, distressed, or in dispute; following a business-disrupting cyber event; or at critical Quality Gates to verify that physical system evidence supports the decision to proceed.
A crisis advisory works for the owner alone, reporting directly to the executives and Board members who carry the risk, and never through the System Integrator.
03How is an independent SAP crisis advisory different from an SAP implementation partner, and who does it work for?
An independent SAP crisis advisory is an independent reviewer who does not implement SAP, sell SAP software licenses, or supply implementation staffing. It has no stake in the outcome other than the client's successful go-live and stabilization. Its deliverable is a plain, candid diagnosis of the program with actionable recovery options, backed by decades of enterprise experience, to help the client, its team, and its System Integrator succeed.
Read more: Independence
04Our SAP implementation is in trouble. What should we do first?
Executive leadership should resist the instinct to ask for more status reports and instead take three actions in sequence:
- (a) Establish the facts first. Obtain objective evidence, independent of the program team and the System Integrator: whether defects are being closed faster than they arrive in testing, what the latest data-migration rehearsal shows, and whether milestones have been signed off by the business owners or only by IT and the integrator.
- (b) Enforce operational controls. Freeze all non-essential scope and hold the design to the minimum viable scope, stop approving new spending, replace percentage-complete reporting with binary milestone sign-offs, and give business process owners the authority to hold a module back until they can demonstrate the process in the new system.
- (c) Re-baseline on verified evidence. Evaluate the true cost of pausing the program, phasing the rollout, or continuing, and bring the Board a recommendation, including a contract reset or System Integrator replacement where the evidence supports it.
Related engagement: Transformation Rescue
If this is your program, write to [email protected]. One paragraph on where it stands is enough. A reply comes within one business day; the conversation is confidential and carries no obligation.
Request a Confidential AssessmentConfidential. No obligation. Reply within one business day.
05How do we tell whether our SAP implementation is failing or just late?
In a late program, milestones slip, budgets adjust, and scope changes occur, but there is clear evidence that the underlying work is catching up to the plan. In a troubled program, these four indicators reveal systemic breakdown:
- (a) frequent milestone slippage,
- (b) spending that outpaces actual verified progress,
- (c) uncontrolled scope creep after a freeze, and
- (d) status mismatch, where a "green/amber" status report directly contradicts the ground-truth reality experienced by business and technical teams.
Any one of these indicators shows that the program has crossed the line from late to structurally troubled and warrants an independent review before further budget is released.
Related engagement: Risk & Capital Assurance
06What is an independent SAP S/4HANA program review, and who conducts one?
An independent review is an examination of the program by a firm with no stake in its outcome: it does not build the system, does not supply the consultants, and is not paid by the System Integrator. It is carried out by experienced practitioners who have successfully rescued troubled SAP programs in the past. These reviews are conducted either at critical Quality Gates or when a program is in active crisis. Primary evidence is collected directly from the system itself, along with test and defect records, Change Request logs, PMO records, program risks, architectural blueprints, and design documents, rather than from status report decks. The product is a concise written report to the owner, readable by a Board in 20 minutes, that states the verified position, quantifies exposure in dollars and time, and presents actionable options with a clear recommendation. Ownerstone conducts such reviews for Boards, C-suite & PE Operating Partners, and reports strictly to them.
Related engagement: Independent Verification & Validation (IV&V)
07Why do SAP implementations fail, and can ours be prevented from failing?
SAP implementations fail for reasons that are usually visible early: scope that was never frozen, data that was never fully rehearsed, business owners who never signed off those future business processes, and governance that relied on the System Integrator's own reports. In most cases, an SAP implementation failure can be prevented if warning signs are detected early and course correction is applied well before go-live. The public record of failed SAP implementations reveals that warning signs were visible for quarters before the failure became public.
Effective prevention spans four critical areas:
- (a) Program Readiness & Contract Review: Verifying the initial roadmap, contract terms, governance model, and team capacity before committing initial capital.
- (b) User Adoption & Operational Change: Assessing business readiness, process ownership, and end-user adoption early to prevent post-go-live operational paralysis and system rejection.
- (c) Independent Quality Gate Verification: Verifying primary evidence at every key milestone so funding releases depend on verified delivery rather than vendor status reports.
- (d) Cyber Resilience Verification: Confirming for live environments that a clean, isolated restore of SAP exists before a security event occurs.
Each review is time-bound, fixed in scope, and represents a minor proactive investment compared to the financial impact of rescuing a distressed program.
Related engagement: Risk & Capital Assurance; SAP Cyber Resilience Review
08A cyber attack has taken SAP down. Who verifies the recovery is safe before we reconnect?
In an ordinary situation, no independent party fulfills this role. Standard incident response teams focus on threat containment and technical server restoration, leaving a critical gap in verifying whether restored financial and operational data is safe to run the business. Rushing to reconnect without independent validation risks secondary data corruption, audit failure, and unexpected operational halts. Ownerstone provides Boards, C-suite & PE Operating Partners with rapid, independent verification to confirm whether the recovery plan is credible, whether the SAP landscape is transactionally sound, and whether system reconnection can proceed safely. Ownerstone does not perform forensics, ransom negotiation, or crisis communications; those remain with the incident-response firm and counsel.
Related engagement: SAP Cyber Recovery Assurance
09Can each phase of our SAP program be independently verified before we release the next budget?
Each phase can be independently verified through an Independent Quality Gate Review before the next budget is released. A Quality Gate is the transition point at which the owner or leadership decides whether everything in the previous phase was completed according to specifications before advancing to the next phase and releasing the budget. Conducting an Independent Quality Gate Review at these milestones provides objective verification based on primary evidence to align the Board, sponsors, and System Integrator on risks and deviations. By catching subtle process changes, architectural drift, scope creep, and technical debt early on, an independent Quality Gate review reduces the likelihood that the enterprise will ever need a crisis engagement.
Related engagement: Independent Verification & Validation (IV&V)
10What happens if the independent review finds our SAP program is in worse shape than reported?
Uncovering serious risks is uncomfortable, but confidentiality is strict and the client remains in control. Ownerstone establishes the facts from primary evidence, quantifies the exposure, and presents realistic recovery options. Leadership retains all decision-making authority. If requested, the firm provides independent oversight while the internal team and System Integrator execute the remediation. Its role is to safeguard the owner's interest: it oversees the turnaround without disrupting the team or taking over the program.
Related engagement: Transformation Rescue
The Board of Directors
Audit chairs and directors who must oversee what they cannot see
11What is the Board's exposure when an SAP rollout goes wrong?
The Board faces critical risks, including governance failure, shareholder litigation, and lasting damage to its reputation for fiduciary oversight. When program warning signs have been visible for quarters and directors cannot demonstrate that they requested independent, ground-truth evidence, exposure rises. Shareholder actions have followed troubled transformations; Lamb Weston's ERP-related suit survived a motion to dismiss in May 2026. These risks are directly mitigated by conducting independent program reviews, which establish the documented diligence and evidence-based Quality Gates required to protect both the enterprise and the Board.
Related engagement: Risk & Capital Assurance
12What evidence should the Board ask for on an SAP implementation, beyond status reports?
At every funding milestone or Quality Gate, the Board must look past vendor narratives and demand empirical evidence behind the numbers. Every SAP program is unique, but essential governance artifacts include:
- (a) Commercial Controls: A cumulative Change Request log with attached costs to measure scope expansion against the contract baseline, alongside a realistic forecast of remaining budget versus unresolved technical debt and deferred scope.
- (b) Data Migration Proof: Results of a full-volume data load, rehearsing migration with 100% of the enterprise's live data, backed by independent reconciliation matching legacy source records to the new SAP ledger.
- (c) Testing Integrity: Open defect trends categorized by severity and age, ensuring script pass rates reflect root-cause resolution rather than re-testing workarounds.
- (d) Operational Readiness: Documented proof that business process owners, not the System Integrator, are driving scope priorities and signing them off, alongside a fully tested fallback plan for shipping and invoicing.
An SAP program that cannot produce these primary artifacts upon request requires immediate, independent verification before the next funding approval or go-live decision is approved.
Before a Board meeting, the same four areas form the independent briefing the Board receives, readable in 15 to 20 minutes. It compares self-reported vendor status against verified progress, concludes with a definitive gate recommendation (Pass, Conditional, or Hold), lists any program-specific risks identified during the review, and sets out the questions the Board should put directly to management and the System Integrator in executive session before approving the next phase or releasing budget.
Related engagement: Risk & Capital Assurance
13Should independent verification at every SAP Quality Gate be a standing Board control?
For an SAP program of any scale, independent Quality Gate validation should be a standing governance control. Making independent verification mandatory provides the Board with a documented record of proactive oversight, while eliminating the friction and delay of commissioning an emergency review after a crisis emerges. When implementation teams and System Integrators know that program deliverables will be independently verified at every milestone, primary work products are consistently prepared with far greater rigor and accuracy.
Related engagement: Independent Verification & Validation (IV&V)
14Does commissioning an independent SAP review mean the Board has lost confidence in management?
Bringing in an independent validation means the Board is doing its job of overseeing what it cannot see. When viewed as a routine control at Quality Gates and commissioned through the Audit Committee, independent validation is healthy supervision to ensure both the customer and System Integrator are successful. Expecting internal project leaders to self-assess, or expecting a System Integrator to report its own deficiencies, creates an inherent conflict of interest. Independent oversight is sound corporate hygiene that protects the enterprise, management, and the Board alike.
Related engagement: Risk & Capital Assurance
If this is your program, write to [email protected]. One paragraph on where it stands is enough. A reply comes within one business day; the conversation is confidential and carries no obligation.
Request a Confidential AssessmentConfidential. No obligation. Reply within one business day.
Private Equity Operating Partners
Owners protecting their investment thesis
15How does a troubled SAP program threaten EBITDA, covenants and exit timing?
The primary risk to a Private Equity Operating Partner is the destruction of the investment thesis. An SAP program is often the largest single discretionary spend in a portfolio company, and the one most capable of imperiling debt covenant compliance and exit valuations. A troubled rollout erodes EBITDA through unbudgeted System Integrator spend, triggers prolonged Transition Service Agreement (TSA) overruns in carve-outs, and stalls top-line revenue through operational friction. An unstable SAP system can force delayed exit windows, degrade fund IRR, and invite severe buyer valuation haircuts during exit due diligence. Independent program controls protect the equity story by validating technical debt, budget burn, and operational readiness before capital is released or go-live is authorized.
Problems surface as delayed invoicing, swollen inventory, rising DSO, and unplanned System Integrator spend, which hit EBITDA and working capital head-on and degrade debt-to-EBITDA leverage ratios. In carve-outs, deployment delays can trigger escalating TSA penalties alongside double-run operational costs. At exit, unresolved technical debt uncovered in sell-side diligence becomes a valuation haircut or an indemnity escrow. An independent diagnostic gives the sponsor early, verified numbers on the exposure so reserves can be adjusted, remediation enforced, and the exit timeline protected before issues surface in buyer diligence.
Related engagement: Business Value Assurance
16How quickly can we tell whether a portfolio company's SAP implementation is a value risk?
Conduct a rapid independent screening focused on four core areas: remaining cost to complete, current operational exposure, TSA or covenant risk, and whether reported progress matches verified empirical evidence. If three or more adverse signals appear, such as an uncosted Change Request backlog, compounding test defects, or failed full-volume data reconciliations, a deeper diagnostic is justified immediately before the 100-day plan is locked or the next capital tranche is released.
Related engagement: Risk & Capital Assurance
17Should an SAP program be reviewed during acquisition due diligence?
Evaluation should happen during pre-acquisition due diligence, as soon as the confidential information memorandum (CIM) or data room reveals an active or recent SAP program. A rapid independent screen at that stage is inexpensive and often alters the risk view, deal terms, or valuation assumptions long before the letter of intent (LOI) is finalized or the 100-day plan is locked. Evaluating an SAP rollout early ensures that unbudgeted System Integrator exposure, hidden technical debt, or looming Transition Service Agreement (TSA) risks are priced directly into the purchase price adjustment before capital is committed and liabilities are assumed.
Related engagement: Business Value Assurance
18How do we keep an SAP carve-out from blowing through the TSA?
TSA exits fail when the focus is on technical go-live rather than operational independence. To prevent carve-out EBITDA erosion from escalating monthly TSA penalties and double-run infrastructure costs, operating partners must enforce a Minimum Viable Product (MVP) scope, freeze non-essential customizations, and tie vendor milestones to binary operational sign-offs. An independent review checks whether data separation, cutover, and Day-1 operations will actually be ready before the TSA expires. The output shows remaining cost, delay risk, and monthly TSA exposure so the sponsor can act while options still exist, protecting carve-out margins and keeping the exit timeline intact.
Related engagement: Operational Integrity
19We are 90 days from TSA expiry and the System Integrator says we are on track. How do we verify that?
Mandate an immediate, independent verification of four non-negotiable operational checkpoints:
- (a) 100% Full-Volume Data Load Rehearsals: Demand verified ledger-to-ledger reconciliation reports between legacy systems and SAP using live historical and transactional data.
- (b) Interface & Day-1 Cutover Dry Runs: Confirm end-to-end integration across supply chain, banking, and customer-facing interfaces, ensuring Day-1 operational independence without relying on legacy seller support.
- (c) Zero-Tolerance Defect Burn-Down: Review open Severity 1 and 2 defect backlogs to verify that fixes reflect true root-cause code resolution rather than temporary testing workarounds.
- (d) Hypercare & Operational Ramp Readiness: Test internal team proficiency and cutover execution timings under real-world stress conditions.
A short, fixed-duration independent diagnostic verifies whether data separation, cutover, and Day-1 operations will actually be ready before the TSA expires. The output exposes remaining cost, delay risk, and monthly TSA penalty exposure so the sponsor can act while remediation options still exist.
Related engagement: Operational Integrity
20Can an independent SAP review protect the exit multiple?
Buyers routinely discount valuation, demand escrows, or enforce purchase price adjustments when they uncover an unstable or opaque ERP environment during sell-side due diligence. Unresolved Severity 1/2 defects, deferred architectural scope, and unverified data migrations are modeled directly as post-close operational hazards. A focused pre-exit review surfaces the exact issues that attract diligence scrutiny, allows targeted remediation, and replaces software uncertainty with verifiable empirical evidence. Validating system integrity and the absence of excessive customization early neutralizes the buyer's ability to argue for a lower multiple, defending the equity story and preserving full exit value.
Related engagement: Business Value Assurance
21Can we get an independent view of a portfolio company's SAP program without alarming management?
PE operating partners should position the engagement as standard sponsor governance or routine Board-level risk control rather than an investigation or vote of no confidence. Work collaboratively with the portco CFO, not around them. When framed as objective operational assistance, an independent review supports management by cutting through vendor asymmetry, identifying hidden technical bottlenecks, and securing the empirical evidence needed to hold the System Integrator, or internal project teams, accountable. Executed through light-touch document reviews and targeted technical interviews, the process minimizes operational friction while providing operating partners with ground-truth exposure numbers.
Related engagement: Risk & Capital Assurance
If this is your program, write to [email protected]. One paragraph on where it stands is enough. A reply comes within one business day; the conversation is confidential and carries no obligation.
Request a Confidential AssessmentConfidential. No obligation. Reply within one business day.
The C-Suite
Organizational, financial, operational and cyber risk
22Why do SAP implementations fail on the customer's side, not only the integrator's?
System Integrator underperformance is rarely the sole root cause of an SAP crisis. The customer organization can frequently compound project risk through unrealistic timeline expectations, frequent sponsor turnover, demands that the new system replicate legacy workarounds, and deep internal resistance to standard processes. Assigning key team members and subject matter experts to a demanding transformation on a part-time basis can create severe deliverable drag, while single-threading design validations and approvals through one or two key individuals creates crippling project bottlenecks.
Left unchecked, these internal dynamics lead to governance paralysis, overloaded subject matter experts, and excessive custom code. An independent review surfaces these client-side root causes as plainly as vendor execution failures, giving executive leadership objective mitigation options to realign internal governance alongside vendor delivery.
Related engagement: Transformation Rescue
23What belongs on an SAP go-live readiness checklist, and what happens when it is skipped?
A go-live readiness checklist that an owner can rely on has three items at its core:
- (a) a full-volume data load reconciled to the source,
- (b) a full day of real transactions run end-to-end by the company's own people, and
- (c) a validated manual fallback plan for shipping and invoicing.
Around them sit signed go-live criteria, Severity 1 and 2 defect closure with root-cause fixes, cutover dry runs with timings, hypercare staffing that prevents team burnout, and sign-off of each process by its business process owner rather than by the System Integrator.
When the checklist is skipped, the operational risk is a breakdown of core business execution. Warehouse shipments stall, order processing stops, invoicing halts, and the month-end close slips, hitting fulfillment, billing, and cash collection in rapid succession. Customers feel the impact on Day 1. Managing cutover preparation like an aviation pre-flight checklist surfaces hidden go-live risks and protects ongoing business operations.
Related engagement: Operational Integrity
24Should we keep paying the System Integrator while our SAP program is in trouble?
Pay only for work that meets contractually agreed criteria. Immediately stop approving Change Requests that represent vendor rework or fixes for unfulfilled original scope. The boundary between legitimate scope expansion and vendor rework is explicitly documented in the Change Request log. An independent review can classify these entries quickly, enabling executive leadership to freeze improper billings, enforce contractual holdbacks, and tie future fee releases strictly to verified deliverable acceptance rather than calendar milestones.
Related engagement: Expert Witness & Litigation Support
25Can we recover money from the System Integrator for a failed SAP implementation?
Recovery is possible in certain cases, but it depends entirely on the contract terms, liability caps, and the strength of the evidence. The pending litigation between Zimmer Biomet and Deloitte serves as a high-profile reference point for the industry on system integrator liability. System Integrators commonly cite routine invoice approvals and payment releases as evidence of deliverable acceptance, which is why approvals should be tied to verified deliverables. Financial recovery or fee concessions require objective proof rather than operational frustration. The necessary evidence must exist first, which is why formal record preservation must start early on with the help of Legal counsel. An independent review secures this evidentiary foundation by converting project friction into concrete artifact trails: verifying delivered work against the Statement of Work (SOW), isolating vendor rework within the Change Request log, and connecting specific technical omissions directly to financial exposure.
Related engagement: Expert Witness & Litigation Support
26Should we replace our SAP System Integrator mid-implementation?
Replacement is one of three options, and usually the last to be exercised. The alternatives are a commercial reset that ties payments to tested milestones, or targeted reinforcement of failing workstreams while the incumbent remains on core configuration. Which option fits depends on two facts: whether the underlying architecture is sound, and whether the working relationship can be repaired.
Replacing an integrator mid-stream triggers steep friction in knowledge transfer, timeline re-baselining, and commercial disputes, and it will not fix internal client bottlenecks like unmade business decisions or poor data readiness. Where objective system evidence shows the architecture is sound and the vendor will accept accountability, a reset is faster and less expensive. Where it shows otherwise, an independent review establishes the documented record needed to execute a transition on the owner's terms. Ownerstone has no stake in which option is chosen.
Related engagement: Transformation Rescue
27Can independent Quality Gate reviews reduce the risk of an SAP write-off?
Independent Quality Gate reviews reduce the risk of a surprise write-off. Capitalized software costs become an impairment risk when it turns out that what was paid for was never actually delivered or operationally viable. A verified record at each Quality Gate, matching what physically exists in the system against what was invoiced, gives finance leadership and external auditors a factual basis for capitalization decisions as the program proceeds. Validating functional capability before funds are capitalized prevents the accumulation of unrecoverable technical debt and protects the balance sheet long before go-live.
Related engagement: Risk & Capital Assurance
28What does an SAP implementation that is over budget or delayed really cost?
The ultimate risk is that the program becomes a value-destruction exercise rather than a business transformation investment. Total financial exposure extends far beyond direct vendor cost overruns. It is the compounding impact of extended carrying costs, delayed operational benefits, and sudden balance-sheet impairment. Schedule slippage drains millions in duplicate legacy costs while permanently eroding NPV by pushing supply chain and working capital savings into future quarters. Unquantified technical gaps prevent accurate impairment testing, exposing leadership to surprise write-offs and auditor friction. The critical executive question is not "How much more will SAP cost?" but "Will the business still achieve the financial benefits that justified the investment?" Establishing an empirical estimate-to-complete provides leadership and the Board with a defensible baseline to set necessary reserves, satisfy external auditors, and make definitive go-forward funding decisions.
Related engagement: Risk & Capital Assurance
If this is your program, write to [email protected]. One paragraph on where it stands is enough. A reply comes within one business day; the conversation is confidential and carries no obligation.
Request a Confidential AssessmentConfidential. No obligation. Reply within one business day.
If your question is not here
Write to [email protected]. A reply is provided within one business day. The first conversation is confidential whether or not an engagement follows.
Confidential. No obligation. Reply within one business day.
Ownerstone is an independent SAP crisis advisory that reports to Boards, C-suite & PE Operating Partners, and never to the System Integrator. Ownerstone is not affiliated with, endorsed by, or a partner of SAP SE.
Public cases referenced
Lamb Weston Holdings (fiscal third quarter 2024 results, released April 4, 2024; SEC Form 8-K, Exhibit 99.1): the company estimated that its ERP transition reduced net sales by approximately $135 million and Adjusted EBITDA by approximately $95 million in the quarter. A shareholder suit over ERP disclosures survived a motion to dismiss in May 2026.
Zimmer Biomet v. Deloitte (filed September 2025): claim for damages over an ERP program; motion to dismiss pending as of September 2026. Figures in the complaint are allegations, not findings.
Source for the Lamb Weston figures: Lamb Weston Holdings, Inc., Form 8-K Exhibit 99.1, fiscal third quarter 2024 results, April 4, 2024 (sec.gov).