Planning an SAP Project: Concepts and a Planner
The ideas that hold an SAP project plan together, and a planner for a first estimate of an SAP DRC or S/4HANA Finance project: duration, phases, long-lead dependencies and risks.
Concepts · October 2026 · For finance, IT and project leads
A high-level estimation tool. The planner gives a first idea based on our planning defaults. It is not a quote or a commitment: every SAP project is different and has to be measured thoroughly before dates or costs are fixed.
Six Phases and Four Quality Gates
Most SAP projects follow SAP Activate. Four core phases, from Prepare to Deploy, bracketed by two more: Discover before the commitment and Run after go-live.
Discover
Qualify the scope, the landscape and the date, and decide whether the arithmetic closes. Days or a few weeks.
Prepare
Governance, plan, standards and environments; long-lead items start on day one.
Explore
Fit-to-standard: show the baseline, capture the differences, sign the design.
Realize
Configure, extend, integrate, migrate and test in sprints; integration and acceptance testing.
Deploy
Production set-up, cutover, go-live and stabilisation (hypercare).
Run
Operate and absorb change: new releases, new rules, new countries.
A quality gate is evidence, not a meeting
Between phases sits a gate: a package of deliverables signed by the client sponsor. No gate, no next phase. If the date forces the project on anyway, that is a logged, accepted risk with a named owner, not a silent decision.
Six Ideas That Hold a Plan Together
Plan backwards from the date that doesn't move
There are two clocks: the fixed date (a legal mandate, a year-end, the end of maintenance) and the plan. Only the second can change. The plan starts from the fixed date and works backwards, placing cutover, third-party testing and long-lead items first. If the arithmetic does not close, reduce scope, not quality.
Scope is a matrix, not a sentence
“E-invoicing for Spain” is not a scope. A matrix is: entities and countries, processes, document or report types, and source systems. It is built in Discover and frozen at the Explore gate; anything outside it is a change, priced and dated.
Start the slow things on day one
Certificates, authority registrations, provider contracts, bank connectivity, data cleansing: they don't depend on the project team and can't be compressed. They go on a register with a named owner and a date from day one of Prepare.
Adopt the standard by default
Instead of asking the business what it wants, show the standard working and record where reality differs. Every difference becomes a backlog item with a justification; an extension needs a business owner and a reason the standard cannot serve.
Plan for the overrun the market already reports
In Horváth's 2025 study of 200 companies, 65% went over budget on their S/4HANA programme, more than nine in ten missed their schedule and, on average, programmes took 30% longer than planned. Explicit contingency is not pessimism: it is planning with data.
Go-live is not the finish line
Go-live day proves the system runs; the first month-end close, or the first statutory reporting cycle, proves the project worked. Hypercare covers them, with clear exit criteria, and then Run begins.
Project Planner
Choose the project type and its shape, and plan from a start date or backwards from the date that doesn't move.
A high-level estimate only. Every SAP project is different and has to be measured thoroughly.
Based on 30 Advisory's delivery methods for SAP DRC and S/4HANA Finance projects, which follow the SAP Activate methodology. Durations, phase weights and lead times are 30 Advisory planning defaults, not commitments or benchmarks from published research. Market figures: Horváth, S/4HANA transformation study (2025), 200 companies.
A high-level estimation tool; not a quote, an offer or advice. Every SAP project is different and must be measured thoroughly: scope, landscape, release, data, team and legal dates. Confirm any plan with a detailed assessment before committing dates or costs.