What Does ERP Software Really Cost in New Zealand?

An ERP subscription is easy to compare. The harder question is what it will cost to get the system working across your business.

The software fee is one part of that budget. There is also the work to agree processes, prepare data, configure the system, connect other applications and train your team. Your staff need time to make decisions and test the result while keeping the business running.

For a New Zealand business owner, a useful ERP budget should show the first-year cost, the ongoing cost and the work that could change either figure. It should also explain what happens if the implementation hours run out before the business is ready.

Allow for the full cost

Ask suppliers to separate these costs in their proposals:

Compare amounts in NZ dollars on the same GST basis. Check whether a monthly price requires an annual commitment, and which costs rise when you add users or expand the system.

Keep your team’s time visible even when it does not appear on the supplier’s invoice. Someone still has to do that work. Implementation planning guidance

Understand what the implementation quote covers

Ask whether the proposal is a fixed price for agreed deliverables, an estimate, or a block of consulting hours.

An hour allowance needs a scope behind it. A package covering basic setup and key-user training may be suitable for a small, straightforward operation. A business with several warehouses, complex pricing, production work and multiple integrations needs a different estimate.

Ask the supplier to connect the allowance to the work, responsibilities and acceptance criteria. Agree how progress, hours used and the expected cost to finish will be reported.

Why implementation hours run out

1. The real process is more complex than the estimate

“We buy and sell stock” can hide supplier rebates, split deliveries, landed costs and customer-specific prices. Each can affect configuration, migration and testing.

Walk through real orders, returns and exceptions during discovery. Show the spreadsheets and manual checks your team relies on. Record the agreed processes, outputs and exclusions in the scope. This gives both sides a better basis for the estimate. Project approach guidance

2. The scope keeps growing

A new report, approval rule or integration can be useful. Several additions can also consume the time reserved for testing and training.

Separate what the business needs for its first live operation from later improvements. Assess each proposed change for its benefit, cost and effect on the schedule. Suppliers should also document assumptions and exclusions, and explain differences from the estimate early. Scope and change controls

3. The project owner lacks authority or available time

A coordinator can arrange meetings but may be unable to settle conflicting requirements or approve a process change. Decisions then move between departments while work waits or is repeated.

Appoint an internal owner with authority to set priorities, secure staff time and resolve decisions, with a clear route to the business sponsor. Give that person time to do the job. Decision authority guidance

4. Data needs more work than expected

Duplicate customers, inconsistent item codes, obsolete products and unexplained opening balances need attention before migration. Repeated imports can consume consulting time if the source records keep changing or remain incomplete.

Assign people to clean and approve each dataset. Agree what history must move, then test an import and reconcile the results before the final transfer. Data migration guidance

5. User acceptance testing starts too late

User acceptance testing, or UAT, checks whether staff can run the business in the proposed system. It needs more than a demonstration of a straightforward sale.

Staff should test their actual work, including returns, partial deliveries, approvals and corrections, using representative data and their normal access rights. Late testing leaves less time to fix gaps and repeat the checks. UAT guidance

6. Staff are expected to learn alongside a full workload

Employee resistance can reflect unclear benefits, insufficient training or a process that makes a familiar task harder. Repeated explanations and continued spreadsheet work can consume time without improving adoption.

Involve the people who do the work. Listen to their concerns, explain what will change, and reserve time for practice. Plan cover for their normal duties where needed. Training and adoption guidance

7. Integrations and reports are treated as small extras

A connection needs rules for failed transfers, corrections and mismatched records. A management report needs agreed definitions and data that supports them.

Confirm these requirements early, including responsibilities across suppliers. Test the complete process and its failure cases. Recreating an old report or a manual workflow should have a clear business purpose and an allowance for the work. Integration and reporting guidance

8. The move to live operations is underplanned

Final stock checks, opening balances, unfinished orders and staff support all need an owner. A delay can also extend the period in which the business pays for both old and new systems.

Plan the switch, the readiness checks and the first weeks of support. Set aside time for final data checks and agree who can decide whether the business is ready to proceed. Go-live readiness guidance

Suppliers share responsibility for realistic estimates and clear progress reports. If agreed work needs more time, review the reason and the charging basis before approving additional spend.

A simple three-year ERP cost example

The following is an illustrative budget. The rates and allowances are assumptions, not market averages or a supplier quote. All amounts are NZD excluding GST, with recurring prices held constant.

The internal time is your team’s combined allowance for data preparation, decisions and testing. It is a planning cost, separate from supplier invoices. Add an allowance for the specific risks identified in your project.

If implementation needs another 20 consulting hours at the assumed $150 rate, that adds $3,000. In this example, that equals six months of software subscriptions. Understanding the work behind the implementation estimate can therefore matter as much as negotiating the monthly fee.

Ask for a budget you can manage

Before signing, get clear answers to these questions:

• Which business processes and deliverables are included for the first go-live?
• Who prepares data, makes decisions, performs UAT and signs off the result?
• What assumptions could change the hours, price or delivery date?
• How are defects, rework and new requirements handled and charged?
• How often will the supplier report hours used, work completed and the expected cost to finish?
• What support and recurring charges apply after go-live?

During delivery, compare the remaining allowance with the work still to complete. If the budget is under pressure, review priorities and the plan before committing more spend. Keep enough time for testing and training.

Where NexWave fits

NexWave is an option for New Zealand businesses that want a connected ERP with room to customise.

More implementation work for the hours you buy

NexWave uses AI and other internal tools to reduce implementation effort. For suitable QuickStart projects, the team estimates that its 24-hour allowance can cover work that would take at least 50 hours without its current tools. This is an internal estimate for the same work.

Those time savings are passed on to customers through fewer billable implementation hours. The team remains responsible for reviewing the result, and the project still includes the business decisions, data checks, training and UAT needed to get ready for go-live.

Its full Wholesale Distribution edition currently lists NZ$460 per month for 1–5 users on monthly pricing. NexWave pricing

Its QuickStart programmes advertise setup for under NZ$5,000 for qualifying smaller deployments. The core programme has a 24-hour allowance for basic configuration, a standard chart of accounts and key-user process training. The published scope targets teams of up to five users with straightforward requirements. More complex work needs a proposal that matches the business.

NexWave also supports code-level customisation and does not charge a separate monthly fee to maintain custom code. New development and later changes are assessed and priced through agreed work.

When comparing options, ask the NexWave team to put the required scope, responsibilities, implementation allowance and ongoing costs into one proposal. Use the same questions with every supplier so the decision reflects the full cost of getting the system into use.