1. Start with how you work, not with software
Write down the handful of processes that matter most, such as quote to cash, purchase to pay, stock to dispatch, and month-end. Note where things get re-typed, delayed or lost. That list becomes your brief, and it stops demos from steering you towards features you'll never use.
2. Questions worth asking any ERP provider
- Which businesses like ours, in size and industry, run on it in Australia today? Can we speak to one?
- How does it handle GST, BAS reporting, Single Touch Payroll and e-invoicing (Peppol), out of the box or through an add-on?
- What does it connect to that we already use, such as banks, ecommerce, payroll or a warehouse system?
- Who does the implementation: the vendor, a partner, or us? Who supports us after go-live, and in which time zone?
- What will we need to customise, and what happens to those changes when the software updates?
- How do we get our data out if we leave?
- What is the total cost over five years, including licences, implementation, training and support?
3. Cloud or on-premise
Cloud (subscription)
- Lower upfront cost, paid per user per month.
- Updates and backups are handled for you.
- Works from anywhere; relies on a good internet connection.
On-premise (your own servers)
- Higher upfront cost for licences and hardware.
- More control over data and customisation.
- You, or an IT provider, look after updates, security and backups.
Most new systems for small and mid-sized businesses are now cloud-based, but the right answer depends on your industry, data and existing IT.
4. What drives the cost
- Users and modules: how many people need access, and which parts of the system you switch on.
- Implementation: setting the system up to match your processes is often the largest single cost.
- Data migration: cleaning and moving customers, products, stock and history.
- Customisation and integrations: every change from the standard adds build and upkeep.
- Training and change: time your team spends learning, and running old and new side by side.
5. How a project usually runs
Discovery and design, then configuration, data migration, testing, training, go-live and a period of close support. A small business with standard processes can be live in a few months; complex or multi-site projects often take a year or more. A realistic plan, an internal owner with time set aside, and clean data matter more than the software you pick.
Want a second opinion on where to start? Tell us about your business and we'll come back with sensible next steps.
Start your brief