Before starting an ERP implementation, a managing director needs to understand three things above all else: the project will take longer than expected, cost more than the software licence alone, and succeed or fail based on internal commitment rather than the technology itself. ERP implementations are as much an organisational change programme as a technical project, and the MD’s role is to sponsor that change actively, not delegate it entirely to IT. The questions below unpack the most important things to know before you sign anything.
An ERP implementation for a mid-sized company typically takes between 12 and 24 months from project kick-off to go-live. Larger organisations with complex processes, multiple legal entities, or significant data migration requirements should plan for 24 to 36 months or more. The most common mistake is underestimating the time needed for testing, training, and change management rather than the technical configuration itself.
The timeline depends heavily on the scope of the implementation. A phased rollout that starts with core finance and procurement before expanding to supply chain or customer experience will generally deliver faster initial value than a big-bang approach. However, phased projects require careful sequencing and strong programme governance to avoid scope creep between phases.
Accelerate. Adapt. Act.
One partner for the full SAP journey
Explore the services that help turn strategy into implementation, optimisation and long-term business impact.
View all services
One factor that consistently extends timelines is data quality. Migrating years of legacy data into a new ERP system almost always reveals inconsistencies, duplicates, and gaps that need to be resolved before go-live. Building data cleansing into the project plan from day one is not optional: it is a prerequisite for a stable launch.
ERP projects most commonly fail due to insufficient executive sponsorship, unclear requirements, poor change management, and underestimating the complexity of data migration. Technology is rarely the primary cause of failure. The underlying issue is almost always organisational: the business was not ready, aligned, or adequately resourced to absorb the change the implementation demanded.
A lack of clear ownership at the business level is particularly damaging. When an ERP project is treated as an IT initiative rather than a business transformation, key decisions get deferred, process redesign is superficial, and end users resist adoption because they were not involved in shaping the solution. This is precisely why a managing director’s active involvement matters so much.
Scope creep is another major risk. Every additional requirement added after the design phase has been approved introduces delay, cost, and complexity. A disciplined change control process and a willingness to say no to non-essential enhancements during the implementation are critical to keeping the project on track.
A successful ERP implementation requires active involvement from business leaders across finance, operations, supply chain, HR, and IT, not just the project team. The managing director or CEO provides executive sponsorship. Each functional area needs a senior business owner who can make decisions about process design and prioritisation. Without this cross-functional commitment, the project will stall at every significant design decision.
Beyond leadership, you need subject matter experts from each department who understand day-to-day operations well enough to validate that the new system supports real workflows. These are the people who will test the system, flag gaps, and ultimately train their colleagues. Identifying and protecting their time for the project is one of the most important resourcing decisions a managing director can make.
External implementation partners bring technical expertise and methodology, but they cannot replace internal knowledge of how your business actually operates. The best outcomes come from a genuine collaboration between a knowledgeable partner and an engaged internal team, not from outsourcing the thinking entirely. Browse our available solutions and tools to see how we support that collaboration in practice.
The total cost of an ERP implementation typically runs two to four times the annual software licence cost when you account for implementation services, infrastructure, data migration, training, and internal resource time. Many organisations focus on the licence fee and are caught off guard by the full investment required to make the system operational and adopted across the business.
The main cost categories beyond the licence include:
Post-go-live costs are also frequently underestimated. Hypercare support in the weeks after launch, ongoing system administration, and continuous improvement initiatives all require budget. A realistic business case for an ERP investment should model the full three-to-five-year cost of ownership, not just the implementation phase.
Before signing with an ERP implementation partner, you should have clarity on your business objectives, a realistic budget range, an agreed implementation scope, and internal resource commitments. Signing without these in place transfers all the risk to the client side, because the partner will define the scope for you, and that rarely ends well.
Specifically, you should be able to answer the following before any contract is signed:
The choice of partner matters as much as the choice of software. Look for a partner with proven experience in your industry, a track record of completed implementations at comparable scale, and a delivery approach that keeps your team in the driving seat. A certified SAP partner like TheValueChain, recognised at the SAP BeLux Partner Awards for measurable business impact, brings both the technical depth and the sector-specific knowledge to guide that conversation honestly from the outset. Get in touch with our team to start that conversation today.
An ERP implementation is successful when it delivers the business outcomes defined before the project started, not simply when the system goes live on time and on budget. Go-live is a milestone, not the finish line. True success is measured in the months and years that follow, through improvements in operational efficiency, data quality, process cycle times, and the organisation’s ability to adapt to new business demands.
Effective measurement starts with defining success criteria before implementation begins. These should be specific and business-focused: how long does it take to close the books each month, how many manual steps are involved in order processing, what is the error rate in inventory management? These baseline metrics give you something concrete to compare against once the system is live.
A well-executed digital transformation strategy does not treat measurement as an afterthought. Business process optimisation is an ongoing discipline, not a one-time event. The most successful ERP users treat go-live as the starting point for continuous improvement, using the data the system generates to identify further efficiencies and adapt their operations as the business evolves.
TheValueChain works with mid-to-large enterprises across Western Europe to turn ERP implementations into genuine business transformations. As a certified SAP partner with award-winning delivery, the team combines deep technical expertise with hands-on industry knowledge to make sure the solution fits the way your business actually works, not just how it looks on paper. The approach is practical, transparent, and built around your objectives from day one.
In practice, this means:
Whether you are evaluating ERP for the first time or preparing for a migration to SAP S/4HANA, TheValueChain brings the clarity and commitment that complex transformation projects demand. Get in touch with the team to start a straightforward conversation about what your implementation should look like.
Start by anchoring the business case in quantifiable operational problems rather than technology capabilities — late financial closes, manual workarounds, inventory inaccuracies, and disconnected systems all have measurable costs that can be translated into ROI. Model the full three-to-five-year cost of ownership, including implementation services, internal resource time, and post-go-live support, and set it against projected efficiency gains, headcount reallocation, and risk reduction. A credible business case also includes a contingency allowance of 15–20% on top of the core budget, which signals to the board that the numbers have been stress-tested rather than optimised to look attractive.
A big-bang go-live moves all users and processes onto the new system simultaneously on a single cutover date, while a phased rollout introduces the system incrementally — by module, business unit, or geography. Big-bang approaches carry higher short-term risk but eliminate the complexity of running parallel systems for an extended period; phased rollouts reduce go-live risk but require strong governance to prevent scope drift and integration issues between phases. The right choice depends on your organisation’s risk appetite, the interdependencies between your processes, and how much operational disruption the business can absorb at one time — a conversation worth having with your implementation partner before scope is finalised.
This is one of the most underestimated resourcing challenges in any ERP programme, and there is no clean solution — it requires an honest conversation at the executive level about priorities and backfill. The most effective approach is to formally ring-fence a percentage of key contributors’ time for the project (typically 30–50% for subject matter experts during peak design and testing phases) and to hire temporary cover or redistribute workload across the team to compensate. Treating project involvement as an unofficial add-on to someone’s existing role almost always results in either a poorly executed implementation or burned-out employees, and often both.
Training should be planned from the very beginning of the project, not bolted on in the final weeks before go-live — which is unfortunately the most common approach. Effective ERP training is role-based, built around the specific workflows each user group will perform in the new system, and delivered close enough to go-live that knowledge is retained but with enough time to address gaps. A change management workstream running in parallel with the technical implementation — covering communication, stakeholder engagement, and training design — is what separates organisations that achieve rapid user adoption from those that struggle with resistance and workarounds for months after launch.
The most damaging post-go-live mistake is withdrawing the project team and support resources too quickly, before the organisation has stabilised on the new system. A structured hypercare period — typically four to eight weeks of intensive support — is essential for resolving the issues that only surface under real operational conditions. Beyond hypercare, organisations frequently fail to establish a clear ownership model for system administration, continuous improvement, and change requests, which means the ERP gradually drifts out of alignment with how the business actually operates. Treating go-live as the end of the programme rather than the beginning of the optimisation phase is the single fastest way to erode the value of the investment.
The default should always be to challenge existing processes rather than replicate them, because lifting and shifting broken or inefficient workflows into a modern ERP system simply makes bad processes faster and more expensive to maintain. Process mapping tools like SAP Signavio allow you to document, analyse, and benchmark your current workflows against industry best practices before a single configuration decision is made, which gives you an evidence-based foundation for deciding what to redesign and what to retain. As a rule of thumb: if a process exists primarily because of a limitation in your legacy system, it is a strong candidate for redesign; if it reflects a genuine competitive differentiator or regulatory requirement, it is worth preserving and configuring accordingly.
It is possible, but the risk profile increases significantly, and the programme governance needs to reflect that. ERP implementations demand organisational stability and clear decision-making authority — both of which are typically under strain during a merger, acquisition, or period of rapid scaling. If the change cannot be delayed, the practical mitigation is to narrow the initial scope aggressively, ensure the programme sponsor has explicit authority to make decisions that cut across the competing priorities, and build additional contingency into both the timeline and the budget. Running two major transformation programmes simultaneously without additional resourcing is one of the most reliable ways to ensure both deliver below expectations.