ERP Isn’t a Purchase. It’s a Long-Term Relationship
People often think of an ERP implementation as the finish line. In reality, it’s just the start.
By the time most businesses reach the point of selecting a new ERP system, a lot has already happened. There may have been years of internal discussion about upgrading or replacing what they already have. Perhaps an existing supplier has announced an end-of-life date, quietly forcing the conversation. Maybe the business is starting to fall behind with ageing technology and looking to move towards something newer. There could be frustration around reporting and visibility of data, with teams spending too much time pulling information together from different systems just to answer fairly basic questions.
Eventually, the conversation turns into action.
You have internal discussions to define priorities. What does the software need to do? What’s essential? What can wait? Some companies handle this scoping internally; others bring in external support to help clarify requirements or produce an RFP.
Then comes the research. The calls. The discovery sessions. The demos. The site visits.
By the time a platform is finally chosen, there’s often a sense of relief. A decision has been made, a direction agreed, and it can feel like the hardest part is over.
This is where ERP projects are often misunderstood.
Choosing the system and getting live isn’t the end of the story. It’s merely the first chapter.
Whenever I speak with businesses looking for a new ERP system, I try to make one point early on. ERP isn’t really a product you buy. It’s a service and a partnership that grows and evolves alongside your business. The requirements you define during selection are a snapshot in time. They reflect where the business is today, not necessarily where it will be in three, five or ten years’ time.
Markets evolve.
Businesses change how they operate.
Technology moves on.
A few years ago, hardly anyone asked about AI. Now it appears on almost every requirements document.
You can make informed assessments, plan for likely scenarios and define a sensible roadmap for the future, but the reality is that change rarely follows a straight line.
If the first chapter of an ERP journey is implementation, the next chapter should be one of continuous improvement. In practice, that’s where the real gains are made and where you ensure the system stays aligned and relevant over time.
This is also where the idea of continuous investment comes into play. Not investment in the sense of ripping things out and starting again, but ongoing attention to how the system is used and how well it continues to support the business.
Quite often, an ERP will be implemented well and still highlight further opportunities for improvement once it’s in day-to-day use. In the ERP world, this is often referred to as optimisation. Taking what’s already been delivered and refining it based on real usage rather than assumptions made earlier in the project.
Once the system is live, businesses gain access to more credible and consistent data than they had before. That visibility can reveal inefficiencies, inconsistencies or workarounds that simply weren’t obvious during selection or implementation. In some cases, the ERP will have been configured around those weaknesses, not because it was the wrong approach at the time, but because it reflected how the business was operating then. With better insight, it becomes much easier to decide what still makes sense and what no longer does.
Over time, most businesses will also want more from their ERP. New functionality. Additional modules. Better reporting. Changes to support growth, new services or new ways of working. None of this is unusual. It’s simply what happens when a system becomes embedded in how a business runs.
This is where thinking long term really matters. What might you need from the system in the future, and what will that look like in practice? How easy is it to make changes? How empowered are you to do things yourselves, and where do you rely on external support? What does ongoing support actually cost, and what does a day rate look like once you are live, because that rate will apply to every future change, enhancement and improvement.
These questions often receive less attention during selection than functionality lists or implementation timelines, but over the life of an ERP system they can have a significant impact on both cost and flexibility.
That’s why ERP is ultimately as much about the right relationship as it is about the right software.
Is the vendor aligned with your business and your industry? Do their aspirations for the product align with where you want to go? Are they actively investing in improving the platform, or simply maintaining it? Are they flexible in how they work with you, and willing to adapt as your needs change?
An ERP partner should be in it for the long haul. Someone who understands that go-live is not the end point, but the foundation for an ongoing relationship. Someone who can support continuous improvement over time, rather than treating ERP as a project that is delivered, signed off and forgotten.
Thinking about ERP in this way changes the conversation. It moves the focus away from trying to predict the future perfectly and towards choosing a platform and a partner that can adapt when the future inevitably turns out differently.
ERP isn’t something you get done and move on from. It becomes part of how your business operates, how decisions are made and how change is managed. When approached as a long-term relationship rather than a one-off purchase, it can continue to deliver value well beyond the initial implementation, not because it stayed the same, but because it was allowed to evolve.
