ERP implementations are among the most complex initiatives an organisation can undertake. They promise new levels of transparency, control, and agility, yet too many still fall short. Projects run over budget, take longer than expected, or fail to deliver the business improvements that executives were counting on.

The problem is not usually the technology. SAP S/4HANA Cloud, SuccessFactors, and other leading ERP platforms are proven, reliable, and scalable. The problem is in how they are implemented.

One of the most overlooked risks is the partner dynamic. Many ERP partners are highly skilled technically, but weaker when it comes to business process advisory. As a result, they fall into a pattern of saying “yes” to client requests. On the surface, this feels safe: the client gets what they ask for, and the partner avoids blame if something later breaks.

But safe is not the same as successful. An ERP partner that cannot challenge assumptions, push back on poor decisions, or guide clients toward fit-to-standard practices leaves the business exposed to failure.

The truth is simple. ERP projects succeed when partners combine technical skills with the confidence and process expertise to guide.

It is easy to see why “yes” becomes the default response.

• Technical focus without process strength: Many consultants know the system inside out but are less confident discussing the client’s broader business operations. If they are not sure how a design choice will impact finance, procurement, or compliance, they default to following instructions.
• Client-driven safety net: Some partners believe that if the client makes the decision, the responsibility for failure sits with them. If the project under delivers, the partner can say, “We built what you asked for.”
• Avoiding conflict: ERP projects are stressful and high stakes. It can feel easier to keep clients comfortable than to confront them with hard truths.

The result is an ERP system that mirrors the old world. Legacy processes are rebuilt inside a new platform. Data issues are papered over instead of solved. Customisations proliferate because no one was confident enough to explain why they were unnecessary.

That is how businesses end up with expensive, complex systems that still require workarounds and do not earn the trust of their people.

A confident partner does not just configure the system. They guide the business toward practices that are proven, sustainable, and aligned with cloud principles.

• They challenge assumptions. If a client wants to rebuild an old approval chain that adds no value, they explain why it should be simplified.
• They protect the long term. By resisting unnecessary customisation, they ensure upgrades remain simple and costs remain low.
• They strengthen adoption. By showing staff not just how the system works but why processes are changing, they build ownership and trust.
• They reduce risk. By insisting on data cleansing and fit-to-standard processes, they prevent failure before it happens.

This is not about being combative. It is about bringing the right mix of business process strength and technical expertise so clients can make informed decisions.

When Coriza partnered with Dulux PNG, the business was struggling. Systems were outdated, processes were manual, and staff did not trust the ERP. Customers even refused to pay invoices because proof-of-delivery documents were missing.

The easy path would have been to say “yes” to every request: rebuild processes as they were, configure around messy data, and hope for the best. Instead, we took the harder path.

• We told the business their data had to be cleansed and standardised before transformation could succeed.
• We challenged legacy processes, mapping them back to SAP best practice instead of replicating old inefficiencies.
• We worked with staff to build ownership, explaining why change mattered and giving them confidence to move work out of spreadsheets and into the system.

The results were significant:

• Day 1 month-end close instead of weeks of adjustments.
• Sales quotes in 24 hours instead of 4–5 days.
• On Time In Full (OTIF) above 95 percent, a direct lift in customer satisfaction.
• Warehouse operations digitised and accelerated, with bin locations and paperless workflows.

Perhaps the most important shift was cultural. Employees who had avoided SAP began asking how to use it for more of their work. That transformation did not come from saying yes. It came from having the confidence to guide.

The same approach shaped our work with other clients.

• Bubs Australia, a fast-growing FMCG company operating across Australia, the USA, and China, had fragmented systems that slowed order management. We were clear: their patchwork could not scale. By moving to SAP Cloud ERP and integrating with Shopify, they achieved real-time stock visibility, faster order processing, and a unified platform for international growth.
• The Cook Islands National Superannuation Fund relied on Excel for core finance and procurement. It worked in the short term, but left the organisation exposed to errors and inefficiency. Our position was firm: spreadsheets are not a system of record. By adopting SAP Cloud ERP, the Fund gained real-time bank reconciliation, stronger compliance, and audit-ready reporting.

In both cases, the outcome depended on more than technical configuration. It depended on telling clients the truth about what was holding them back, then guiding them toward best practice.

One of the biggest traps in ERP transformation is trying to replicate what came before. Clients ask for custom reports, bespoke workflows, or approval hierarchies designed for another era.

The problem is that cloud ERP is not meant to be a copy of legacy systems. It is built on decades of best practice. The businesses that succeed in the cloud are the ones that embrace that standard.

Larger enterprises that spent decades running heavily customised ERP systems have now made it a priority to simplify. Their common goals are clear:

• Remove customisations that created complexity and cost.
• Adopt standard content so the system is easier to run and easier to upgrade.
• Eliminate technical debt that has been holding them back.

For new adopters of cloud ERP, the lesson is obvious. Do not repeat the mistakes of the past. Do not replicate inefficiencies or build technical debt into your first system. Start clean, adopt standard, and design for the future.

If fit-to-standard and clean design are so clearly beneficial, why do many clients resist them?

• Familiarity: People are comfortable with the way things have always been done, even if those processes are inefficient.
• Perceived uniqueness: Every organisation believes its processes are different. In reality, most are standard variations already covered in cloud ERP.
• Fear of change: Simplification feels like losing control, when in fact it creates control by reducing hidden workarounds and errors.

This is where partner confidence matters most. Without it, clients default to old habits and partners fall into the trap of saying yes. With it, the business is guided toward choices that will stand the test of time.

Across industries and regions, four truths consistently separate successful projects from failed ones:

• Data is non-negotiable. Clean, consistent master data underpins everything.
• Customisation kills agility. Stick to SAP standard unless there is a clear, costed business case and an exit plan.
• People drive adoption. ERP is not just a system change, it is a cultural shift. Teams must understand why the changes matter.
• Transformation is a journey. Go-live is only a milestone. Continuous improvement is what sustains value.

Australian manufacturing illustrates why this matters. The sector contributes just 5.5 percent of GDP, down from double digits in past decades, yet still employs over 930,000 people. Costs are rising, demand is fragile, and churn is high, with 437,000 businesses opened in 2024–25 and 370,000 closed in the same period.

In this environment, transformation is not optional. It is survival.

Yet too many manufacturers still rely on spreadsheets, outdated systems, and manual workarounds. The result is slow reporting, unreliable customer commitments, and cash locked in the wrong inventory.

The truth is straightforward:

• Excel is not ERP.
• Manual processes do not scale.
• Siloed data kills transparency.

The Dulux PNG story shows what happens when these truths are accepted. Month-end closes fall to Day 1, customer reliability improves, and decisions are made on real-time data. That is the payoff of choosing a partner with the confidence to guide.

For CFOs, CIOs, and COOs, the choice of partner can make or break transformation. The right partner should:

• Challenge assumptions and explain alternatives.
• Insist on cleansing and standardising data before configuration.
• Resist unnecessary customisation and protect the long term.
• Stand by business outcomes, not just technical go-live.

These are the hallmarks of a partner that has both technical strength and business process confidence.

• Download our eBook: Manufacturing at a Crossroads. A Practical Guide to Digital Transformation
• Read Our Blog: Leading Manufacturing Business Transformation in PNG
• Review Related Services: Cloud ERP Consulting
• Book a Digital Discovery Assessment: Check functional fit before you start!
• Check out Our Other Services: Cloud Value Realisation