Helixr Perspective #35

Independent ERP Advice: Choosing the right solution

Two colleagues discussing a decision at a laptop in a warehouse

Share:

Related solution

Process transformation

We combine people, processes and systems to make your business work better.
Major ERP decisions rarely have one right answer. Independent advice starts from your business needs and weighs the full range of options, rather than starting from a product.

ERP platforms have long provided the backbone for core processes, bringing finance, procurement, manufacturing and supply chain together with consistent data, standard processes and reliable controls. For many businesses, that integrated approach remains the right one.

The range of options has widened, though. Specialist applications now offer sophisticated capability in areas once handled almost entirely inside ERP, and better integration makes it more practical to connect them. That creates choice, and it makes technology decisions more complex.

When the decision is significant, most organisations ask for advice. It comes from vendors, integrators and consultants, and most of it is capable and honest. It is still worth understanding where it starts from, because the stakes are high. McKinsey reports that only 25 to 35% of large technology programmes achieve their targeted EBITDA and cash-flow impact, while 65 to 80% exceed budget or timeline*.

How advice is shaped

The software industry works through relationships between vendors, integrators, consultants and support providers. These partnerships are part of how complex programmes are delivered, and customers benefit from the product knowledge and delivery experience that comes with them.

Those relationships also shape where providers concentrate their expertise. A consultancy that specialises in one platform will know it well and will naturally be more used to recommending solutions within it. A vendor will understandably promote products that support its roadmap.

This is not a criticism of anyone. It does mean that advice starts from a position, and that the position may not be the same as the customer’s. A solution can be technically capable of meeting a requirement without being the most appropriate or cost-effective one.

Independence is also a matter of degree. Helixr is an SAP partner, and we work with other platform providers too. What matters is whether relationships are disclosed, and whether they limit the answers an adviser is able to give.

The range of answers available

A system-agnostic assessment should be capable of producing different recommendations depending on the organisation’s starting point. In our experience, there are at least five.

  • Stay and optimise. Where the ERP is stable and fit for purpose, removing unnecessary customisation, simplifying processes and improving master data can deliver much of the benefit of a major programme. Support, security and regulatory needs still need a credible plan.
  • Transform. Where systems are fragmented, costly to maintain or unable to support essential requirements, such as new regulatory regimes or multi-site planning, a major ERP transformation may offer the strongest return.
  • Phase. Plants, regions or business units can be modernised in waves, which manages operational risk and spreads investment over time.
  • Replace specific capabilities. Individual functions can move to specialist applications where the requirements are deeper than the ERP can comfortably meet.
  • Integrate and separate. Connecting systems more effectively, or separating parts of the landscape where business models or regulatory needs genuinely differ, can deliver more than replacing everything.

In complex environments, the strongest strategy often combines several of these within one roadmap. An adviser who can recommend only one or two should say so.

These options matter most when ERP is under review because of maintenance deadlines, changing commercial arrangements or business events such as acquisitions, new product launches or shifts in manufacturing strategy. A vendor’s lifecycle timetable should not determine the whole technology strategy**.

Deciding what belongs in the ERP core

One of the most useful questions is which capabilities stay inside the ERP and which are better delivered elsewhere.

Many organisations have pursued consolidation, extending the ERP to cover more functions. That delivered standardisation and control, but it also produced landscapes with heavy customisation, duplicated functionality and processes built around old technology constraints.

In manufacturing and supply chain, the distinction is often clear in practice.

  • Typically in the core: stable, regulated, transactional processes where one data model and tight control matter most, such as order-to-cash, procure-to-pay and financial posting.
  • Candidates for specialist platforms: capabilities with deep functional requirements or rapid change, such as planning across multiple plants and distribution networks, shop-floor execution and data collection, enterprise labelling and document automation in regulated markets, and financial consolidation and planning.

These choices have to be weighed against the cost of integration. Every additional application adds responsibilities for data quality, security, support and end-to-end process coordination. In regulated manufacturing, validation and batch traceability also need to be considered from the start.

For some organisations, a highly integrated ERP remains the best approach. For others, a stable core with carefully selected specialist applications offers more value and flexibility. The decision should follow the operating model, not a general preference for consolidation or diversification.

What good independent advice looks like

Good assessment starts with the business, not the product. It begins with objectives and pain points, such as service levels, lead times, inventory, compliance and constraints on skills and capacity. It then looks honestly at the current estate: what works, where complexity and technical debt have built up, and which limitations genuinely hold the business back.

Options are compared on a consistent basis. That means functionality and fit, implementation and operating cost including change management and skills, integration and data requirements, operational continuity and risk, and flexibility for future changes in products, footprint and regulation.

Advice also needs practical delivery experience behind it. A recommendation that looks attractive on paper can become far less compelling once data migration, licensing, interfaces, validation and business continuity are understood. Advisers need to be able to say whether the architecture is achievable across your sites, and whether the benefits justify the investment and risk.

Questions worth asking any adviser

These apply to vendors, integrators and consultancies alike, including us.

  1. What relationships do you hold with the vendors and platforms we might consider, and do you receive any payment or incentive linked to them?
  2. Which of the options we are weighing do you not deliver, and will you tell us if one of them is the better answer?
  3. Does your recommendation include doing less, or nothing, and what would that cost and return?
  4. What assumptions sit behind the business case and the estimate, including how AI-assisted tooling has been reflected, and can we test them ourselves?
  5. What are the costs and downsides of your preferred route?
  6. Can you describe, without naming the client, a time when your advice differed from the vendor’s position?

Independence in practice

We have seen the benefits of this approach. In one engagement with a global organisation, the client evaluated its existing provider’s proposed solution for a core business function alongside an alternative platform. Following a detailed assessment, the organisation selected the alternative, and Helixr supported its implementation.

The decision reflected the business requirements and the capabilities of the available solutions, rather than a preference for a particular provider.

Where Helixr fits

Helixr combines experience of complex enterprise environments, including life sciences manufacturing and supply chain operations, with an independent approach to solution selection. We recognise the continuing value of established ERP systems, and that specialist technologies or targeted improvements may deliver better outcomes for particular functions.

In practice, that can mean:

  • optimising an existing ERP-centred landscape to remove complexity and improve performance;
  • supporting a major ERP transformation that creates a modern backbone connecting planning, manufacturing, packaging, logistics and supply; or
  • introducing specialist capabilities around a stable core where they add clear business value.

If you are facing an ERP decision and would like a view that is not tied to a single answer, we would be happy to talk.

*McKinsey, “The end of ERP as we know it? Five ways AI is disrupting ERP”, 11 May 2026 

** For SAP ECC customers, our Insight on Insight on support beyond 2027 sets out what the recent EU decision means for these options.

Connect with Helixr
Let’s have a conversation. Contact us to find out more about what we can do for you.