5 Costly Business System Selection Mistakes to Avoid | ANZ

When a new business system fails, the fallout goes far beyond frustration. According to Gartner research, nearly 75% of ERP implementations fail to meet business expectations, with projects exceeding budget by an average of 178%. For mid-sized organisations, these failures translate to hundreds of thousands—sometimes millions—of dollars wasted.

But here’s the good news: most system selection disasters are entirely preventable. By understanding and avoiding five common pitfalls, you can dramatically improve your chances of implementing systems that actually deliver on their promises.

Understanding the True Cost of Poor System Selection

The price tag of a failed system implementation extends far beyond the initial investment. When Melbourne-based manufacturer Patterson Industries selected an inventory management system that couldn’t handle their complex component tracking, the visible costs included $180,000 in software licenses and $250,000 in implementation services.

However, the hidden costs were far worse:

Staff worked overtime for months attempting to reconcile inventory discrepancies, costing an additional $85,000 in labour.

Customer deliveries were delayed, resulting in penalty payments exceeding $120,000.

The company eventually abandoned the system after 14 months, writing off the entire investment while starting the selection process from scratch.

This ripple effect is common. A poorly chosen system impacts not just the department it’s designed for, but cascades through interconnected business processes. For example, an inadequate CRM system affects not only sales but also marketing effectiveness, customer service quality, and financial forecasting accuracy.

Mistake #1: Inadequate Requirements Analysis

“We need a better accounting system” is not a requirements statement. Yet many businesses begin their selection process with similarly vague notions.

Wellington-based logistics company Harbour Connect made this exact mistake. Their finance team requested a “more modern finance system with better reporting.” After spending $95,000 implementing their chosen solution, they discovered it couldn’t handle multi-currency transactions—a critical requirement they had failed to document explicitly.

To avoid this pitfall:

Start with business objectives, not system features. Ask “What business outcomes do we need to achieve?” rather than “What features do we want?”

Document specific use cases with measurable outcomes. For example: “The system must generate consolidated financial reports across our three entities within four hours of month-end.”

Prioritise requirements using a clear classification system. One effective approach is the MoSCoW method: Must have, Should have, Could have, Won’t have.

Bring in actual end-users during the requirements phase. The accounts payable clerk who processes 100 invoices daily will identify practical needs your finance director might miss.

Mistake #2: Superficial Vendor Evaluation

Polished demos and persuasive salespeople rarely reveal whether a system will work in your specific environment. Yet many businesses base their decisions primarily on these superficial factors.

Create a structured evaluation framework that weights criteria based on your specific priorities. For instance, a retail business might weight POS integration capabilities at 25% of the total score, while a professional services firm might assign just 5% to this feature.

When Sydney-based engineering firm Westbrook Associates evaluated project management systems, they created a decision matrix that awarded points across 32 specific criteria. This systematic approach revealed that their initial frontrunner actually scored lowest on their most critical requirements.

Additionally:

• Request vendor references in your specific industry and of similar size
• Create scripted demonstration scenarios based on your actual workflows instead of letting vendors control the demo
• Investigate vendor financial stability, support history and product roadmap
• Arrange hands-on testing sessions where your staff can try the system with realistic scenarios

Mistake #3: Underestimating Implementation Costs

The sticker price of software typically represents just 30-40% of the total implementation cost. Unfortunately, many businesses budget primarily for licenses while underestimating everything else.

Common hidden costs include:

• Data migration: Cleaning, mapping and transferring data from legacy systems often requires specialised expertise
• Customisation: Modifications to meet specific business requirements can quickly double implementation costs
• Integration: Connecting with existing systems often involves unforeseen complexity
• Business process redesign: Adapting workflows to accommodate new system capabilities
• Hardware upgrades: Additional servers, networking equipment or end-user devices
• Ongoing support and maintenance: Annual costs typically range from 15-22% of the initial license price

For accurate budgeting, consider the experience of New Zealand retailer Coastal Outfitters. When implementing their inventory management system, their initial budget of $125,000 grew to $215,000 after accounting for all implementation components. They ultimately built in a 20% contingency buffer that proved essential when they encountered unexpected data migration challenges.

Mistake #4: Neglecting User Training and Change Management

Even perfectly selected systems fail without proper user adoption. Research from Prosci shows that projects with excellent change management are six times more likely to meet objectives than those with poor change management.

When Auckland-based financial services firm Morgan Partners implemented a new practice management system, they allocated just two days for staff training. The result? Three months of productivity loss as users struggled to complete basic tasks, with some reverting to spreadsheets and paper tracking.

Effective training and change management requires:

• Tailored training programmes for different user roles and learning styles
• Identifying and empowering internal champions who can support their colleagues
• Clear communication about how the new system benefits both the company and individual users
• Sufficient practice time in test environments before going live
• Post-implementation support to address questions and challenges during the critical first months

Remember that resistance to new systems is normal and should be expected. Planning for it rather than being surprised by it makes all the difference.

Mistake #5: Failing to Plan for Scalability and Future Growth

A system that perfectly meets today’s needs but can’t adapt to tomorrow’s requirements is ultimately a poor investment. Yet many businesses focus exclusively on current capabilities without considering future scenarios.

Brisbane-based logistics company Eastern Freight learned this lesson the hard way. Their warehouse management system worked flawlessly for their initial three locations, but couldn’t support their expansion to seven warehouses just 18 months later. The company faced the difficult choice of constraining growth or replacing a recently implemented system.

To avoid this mistake:

• Document anticipated growth scenarios for the next 3-5 years
• Ask vendors specific questions about scaling limitations (number of users, transaction volumes, locations)
• Understand the upgrade path and how future functionality will be delivered
• Evaluate the vendor’s development roadmap to ensure it aligns with your strategic direction
• Consider whether the system architecture can accommodate emerging technologies you might adopt

While you shouldn’t pay for capacity you won’t need for years, building in reasonable room for growth prevents costly system replacements.

Building a Successful System Selection Roadmap

Avoiding these five mistakes requires a structured approach to system selection. Consider this framework:

1. Establish a cross-functional selection team representing all stakeholder departments
2. Document specific business objectives the new system must support
3. Develop detailed requirements with clear prioritisation
4. Create a comprehensive evaluation scorecard with weighted criteria
5. Build a realistic budget encompassing all implementation components, including training and change management
6. Conduct thorough vendor evaluations using

Want to see how we apply this for NZ and AU businesses? Learn more about our approach to digital strategy.