ERP for small business: when you need one and how to start small.

What an ERP does for a small business

An ERP (enterprise resource planning system) keeps the records that run the business in one place: customers, quotes, orders, stock, purchasing, production or jobs, and the documents that link them. Accounting software records the money once a sale or purchase has happened. An ERP records the work that leads up to it.

For a small team, the value is less about features and more about one version of the truth. When sales, the warehouse and accounts all look at the same order, fewer things fall between the cracks.

Signs you have outgrown spreadsheets

Spreadsheets are a sensible start. They become a problem when they turn into the system everyone depends on but nobody owns. Check how many of these sound familiar.

• RekeyingThe same order is typed into email, a spreadsheet and the accounting software.
• Stock surprisesYou find out an item is out of stock after it has been promised to a customer.
• Slow quotesQuoting means hunting through old emails, price lists and supplier files.
• One person knowsKey steps live in one person’s head or inbox, so holidays and resignations hurt.
• Month-end scrambleReports are rebuilt by hand every month and the numbers rarely agree the first time.
• No statusNobody can answer “where is this order?” without asking three people.

If three or more apply, an ERP or at least one connected system is worth a serious look. The ERP and workflow integration checklist goes through the same signs in more detail.

Which module to start with

The best first module is the one that removes the most rework, not the one at the top of a brochure. A rough guide by type of business:

Whatever comes first, set up the master data properly: one customer list, one product list with consistent codes and units, and agreed price rules. Most ERP pain later traces back to this step being rushed.

Keep compliance where it already works

Australian small businesses usually already have accounting software, such as Xero or MYOB, that handles GST, business activity statements (BAS) and Single Touch Payroll reporting to the ATO. There is rarely a reason to move that. A practical small-business ERP sends invoices and bills to the accounting software through an integration, so the bookkeeper keeps working in the tool they know.

• Agree which system is the source of truth for customers, products and prices, and sync in one direction where possible.
• Map tax codes once, so every invoice arrives in the accounting software with the right GST treatment.
• Leave payroll and STP in the payroll or accounting software unless there is a strong reason to change.
• If customer or staff personal information moves between systems, check how the Australian Privacy Principles apply to you.

Off-the-shelf, configured or custom

Packaged ERP products can be quick to start and come with support, but you may need to change how you work to fit them. Configured products sit in the middle. A custom ERP fits your terms, approvals and exceptions, but you need a builder who will maintain it. There is no single right answer; the choice depends on how unusual your workflow is and who will look after the system.

We compare the three options in custom ERP vs off-the-shelf ERP. If custom looks right, our custom ERP service builds one module at a time on one set of data.

A small start in five steps

1. Pick one workflowChoose the process that causes the most rework, such as quote to order, and write down how it runs today, including exceptions.
2. Clean the master dataMerge duplicate customers, fix product codes and units, and agree price rules before anything is imported.
3. Set up the first moduleConfigure or build only what that workflow needs, connected to your accounting software.
4. Run it alongside the old wayUse both for a short, agreed period, compare the results and fix gaps before switching over.
5. Add the next moduleOnce the team relies on the first module, add the next one that removes the most friction.

How long it takes and what drives the cost

Time and cost depend far more on scope than on the software. The main drivers are how many modules you need, how messy the existing data is, how many systems must be connected and how much training the team needs. A single module with clean data can be running in weeks; a multi-site rollout with several integrations takes longer.

At Optivise AI, a custom module typically takes about a week to build, plus testing, and each module is accepted before the next one starts. Scope and fees are agreed in each proposal.