ERP selection

ERP total cost of ownership in Australia: a three-year comparison worksheet

A practical three-year ERP cost model for comparing licences, implementation, integrations, internal effort, support, upgrades, and commercial risk on the same basis.

ERP proposals are difficult to compare because each supplier draws the commercial boundary differently. One quote may include implementation, support, hosting, test environments, and integrations. Another may show only software subscriptions and a tightly limited phase-one estimate.

A useful ERP total cost of ownership model puts every option on the same three-year basis. It separates recurring software cost from delivery cost, internal effort, operating support, and a clearly named risk allowance. The goal is not to predict every dollar. It is to expose differences before they become contract variations or post-go-live surprises.

Start with one comparable scope

• Define the same entities, users, sites, warehouses, processes, integrations, reports, data volumes, and Australian requirements for every bidder.
• Separate phase one from later improvements. If one proposal defers manufacturing, advanced warehousing, payroll integration, or consolidation, do not compare its first-year price with a proposal that includes those outcomes.
• Record every assumption beside the cost it affects. Common examples are customer data quality, number of historical years, availability of internal subject-matter experts, and whether existing integrations can be reused.
• Treat exclusions as commercial inputs. An excluded bank interface, data-cleaning task, test environment, or report still needs an owner and a budget.

The eight cost groups to model

1. Software subscriptions: full users, limited users, devices, modules, environments, storage, transactions, AI consumption, and third-party applications.
2. Implementation services: discovery, solution design, configuration, project management, testing support, training, cutover, and hypercare.
3. Data migration: extraction, cleansing, mapping, trial loads, reconciliation, document attachments, history, and archive access.
4. Integrations: design, middleware, API or transaction charges, development, monitoring, error handling, vendor testing, and ongoing support.
5. Internal effort: process owners, finance and operations specialists, data stewards, testing, training, communications, backfill, and executive decisions.
6. Operating support: partner retainer, vendor support tier, internal administration, security reviews, access management, and month-end or peak-period coverage.
7. Change and upgrade work: regression testing, extension maintenance, release review, retraining, report changes, and improvement backlog.
8. Risk allowance: uncertain scope, custom development, weak source data, unresolved localisation, integration dependencies, and contractual exposure.

Build the three-year worksheet

• Year 0 and year 1 should include implementation, initial subscriptions, migration, integration delivery, internal project effort, backfill, training, cutover, and contingency.
• Year 2 should include recurring subscriptions, support, internal administration, integration operations, release testing, training for new starters, and the first improvement tranche.
• Year 3 should repeat the operating baseline and add known growth: user volumes, entities, storage, transactions, new sites, add-ons, or contract changes.
• Show GST consistently. Microsoft's Australian Business Central pricing page, for example, states that displayed prices exclude GST. Mixing tax-inclusive and tax-exclusive figures creates a false difference.
• Keep one column for confirmed supplier cost, one for buyer-estimated internal cost, and one for risk allowance. Do not hide uncertainty inside a single total.

Normalise software and licence costs

• Use named roles rather than one average user count. Full finance, operations, warehouse, manager, approver, read-only, device, and external users can have different licence treatment.
• Confirm which capabilities require a higher edition, add-on, consumption charge, or separate product. Microsoft currently publishes different Australian prices for Business Central Essentials, Premium, and Team Members, while agent use can require separately charged Copilot Credits.
• For Odoo, separate subscription choice from implementation and hosting design. Odoo's official material distinguishes its plans and implementation packs, while its hosting documentation says Odoo Online is not compatible with non-standard apps. Custom-app needs can therefore change both delivery and hosting cost.
• For quote-led products such as NetSuite, require the proposal to identify platform, user, module, environment, support, and renewal assumptions separately. A single bundled number is difficult to govern after the initial term.
• Model the expected user and transaction profile in year three, not only the go-live profile. A low first-year total can reverse as sites, subsidiaries, modules, or automation volumes grow.

Cost internal effort properly

• ERP delivery consumes business capacity even when no invoice is raised. Estimate days by role for design, data work, testing, training, cutover, and stabilisation.
• Add backfill or lost-capacity cost where operational staff cannot absorb project work beside their normal roles.
• Do not treat a smaller partner estimate as automatically cheaper. If the proposal transfers configuration, testing, documentation, or training work to your team, the cost has moved rather than disappeared.
• Keep decision delay visible. Slow scope decisions and unavailable process owners create partner rework, extend subscriptions running in parallel, and weaken testing.

Price integrations as operating products

• Include build cost and recurring cost: middleware, connectors, API usage, monitoring, certificates, support ownership, vendor changes, and incident response.
• Ask who fixes a failed transaction when the ERP vendor, implementation partner, ecommerce platform, bank, payroll provider, and middleware supplier are all involved.
• Add regression effort for each major release or interface change. An integration that is inexpensive to build but difficult to observe can be costly to operate.
• Give manual fallback work a cost. If an interface fails and staff re-key orders, payments, or journals, that labour and control risk belong in the comparison.

Add commercial and delivery risk without inventing precision

• Apply a named allowance to uncertain items instead of adding an unexplained percentage to the whole project.
• High-risk items commonly include customisations, poor master data, unclear payroll or tax boundaries, first-time integrations, complex warehouses, multi-entity design, and compressed cutover dates.
• Test renewal, indexation, minimum commitments, user reassignment, storage, sandbox, termination, data extraction, and transition-assistance terms before signing.
• The Australian Cyber Security Centre's procurement and outsourcing guidance recommends defining security responsibilities, incident handling, subcontractor controls, data ownership, return or destruction of data, and exit arrangements. Those obligations affect supplier scope and should be costed rather than left as contract language only.

Compare value beside cost

• Keep the cost model beside measurable outcomes such as faster close, higher stock accuracy, fewer manual orders, stronger margin control, or lower support effort.
• Do not force every benefit into a speculative dollar value. Mark whether each benefit is evidenced, measurable after go-live, and owned by a named leader.
• Reject false equivalence. Two proposals are not comparable if the lower-cost option fails a mandatory process, control, security, or Australian operating requirement.
• Use cost per delivered outcome only after pass-or-fail requirements have been met. TCO is a decision input, not a substitute for product and partner fit.

Questions every final proposal should answer

• Which items are fixed price, capped, estimated, consumption-based, or excluded?
• What buyer effort is assumed for data, testing, training, project management, and cutover?
• Which required outcomes depend on add-ons, custom development, or a higher product edition?
• What changes at renewal, when user numbers grow, or when another entity, site, warehouse, or environment is added?
• Who owns integration monitoring, release regression, security response, and production support?
• What data export, transition assistance, and decommissioning cost applies if the relationship ends?

A practical decision sequence

1. Confirm mandatory scope and pass-or-fail requirements.
2. Normalise every proposal into the eight cost groups.
3. Validate licence and module assumptions against official product material.
4. Estimate internal effort with the people who will actually deliver it.
5. Add named risk allowances and test contract exposure.
6. Compare three-year cost beside product fit, partner evidence, and measurable outcomes.
7. Rebaseline the model after discovery and again before contract signature.

FAQ

• What should be included in ERP total cost of ownership? Software, implementation, migration, integrations, internal effort, support, upgrades, ongoing change, and a named allowance for material risk.
• Is a three-year model long enough? It is usually long enough to expose implementation and early operating cost while remaining understandable. Buyers with longer contract terms or major staged rollouts should extend it.
• Should implementation be a fixed percentage of licence cost? No. Delivery effort is driven by scope, data, integrations, process change, localisation, partner model, and internal capacity, not licence price alone.
• How should ERP proposals be compared? Put them against one scope, normalise exclusions and buyer effort, test mandatory requirements first, then compare three-year cost, commercial exposure, product fit, and partner evidence.

Sources used

• Microsoft Dynamics 365 Business Central Australian pricing page for current plan, user, GST, partner-services, and Copilot Credits treatment.
• Odoo official pricing, Success Packs, and Odoo 19 hosting documentation for subscription, implementation, custom-app, and hosting boundaries.
• Oracle NetSuite official product and professional-services material for product scope and quote-led implementation context.
• Australian Cyber Security Centre Guidelines for procurement and outsourcing for supplier responsibility, data, incident, subcontractor, and exit controls.