Skip to content

Does a mid-sized business need an ERP?

Short answer. A mid-sized business needs an ERP, or something that does an ERP's job, when stock, orders, purchasing, jobs and finance sit in separate tools and people spend real time joining them up. Some businesses suit a packaged ERP. Many are better served by an inventory or operations product connected to Xero, or a custom system built around their operation. How standard your processes are usually decides it.

Many small separate notebooks being gathered under one large binder with a red spine
In this guide · 6 minute read

What an ERP is

ERP stands for enterprise resource planning. In plain terms, it's one system holding the records that run the business: what you sell, what you buy, what's in stock, what's been made or delivered, and what's been invoiced and paid. Because everything shares one database, a sale reduces stock, flags a reorder when it's needed and posts to the accounts without anyone re-keying it.

Most ERPs are sold as a set of modules, and businesses switch on the ones they need. The names vary from vendor to vendor, and few businesses use every one, but the core list usually looks something like the one below. Read it as a map of functions to check against your own operation, whichever route you end up taking.

  • 01Finance: general ledger, accounts payable and receivable, bank reconciliation and tax.
  • 02Sales and orders: quotes, sales orders, pricing, customer accounts and credit limits.
  • 03Purchasing: purchase orders, supplier records, receiving and supplier bills.
  • 04Inventory and warehousing: stock across locations, transfers, batches, serial numbers and stocktakes.
  • 05Manufacturing or assembly: bills of materials, work orders and production costs.
  • 06Projects and jobs: job costing, time, materials and progress billing.
  • 07Reporting: margins, stock value, cash flow and performance across the business.
  • 08Sometimes also CRM, HR, payroll and service management, either built in or connected.
A sales manager pointing at a call score trend on a wall screen in a team meeting
Call scores reviewed with the team. Example screen; the name on it is invented.

The signs you need one

Most businesses don't set out to buy an ERP. They notice the gaps between their tools first, usually at month-end or in a busy season. If several of the signs below happen every week, it's time to decide how your systems should be joined up, and how much of that joining one product should do.

  • 01Stock figures in the system don't match the shelves, so someone checks by walking the warehouse.
  • 02Orders are typed from email or a webshop into another tool before they can be picked.
  • 03You can't see the true margin on a job or product until weeks after it's finished.
  • 04Purchasing relies on one person's memory of what's running low.
  • 05Month-end means exporting from several systems and reconciling in a spreadsheet.
  • 06A second site, warehouse or business entity has doubled the manual work.
  • 07Customers ask for order status and someone has to go and find out.

The three routes

Packaged ERP. Products such as NetSuite and Microsoft Dynamics 365 Business Central cover finance and operations in one system, including the general ledger, so they usually replace your accounting package. They're broad and well established, and they suit businesses whose processes are close to standard or who are happy to adapt to the product. They typically need an implementation partner to configure, and changing them beyond their settings takes specialist work.

An operations product plus accounting. Inventory and order products such as Cin7 or Unleashed handle stock, purchasing, sales orders and often assembly, and connect to Xero for the ledger. This route keeps the accounting your bookkeeper already knows and is quicker to start than a full ERP. It works well for wholesale, distribution and product businesses whose operations fit the product's model. The gaps tend to appear around unusual pricing, job work or processes the product doesn't cover.

A custom system around your operation. Here the operational core, such as jobs, orders, stock, scheduling and billing rules, is built to fit how your business runs, and connected to Xero or MYOB for the accounts. It suits businesses whose way of working is part of why they win, and who would otherwise be stacking several products and workarounds. It takes longer to start than a subscription, so it's usually built in stages, beginning with the part costing the most hours.

★★★★★

“TJ helped me in creating a super creative user interface. I got the results that I wanted.”
Fady ProTech · Client

How to choose

Start with your processes rather than with products. Write down how an order or job moves through the business, and mark the steps that are the same as everyone else's and the ones that are specific to you. Then put the same questions to each option, using your own examples instead of the vendor's demo data.

  • 01Which of our processes does it handle as they are, and which would we have to change?
  • 02Does it need to replace our accounting, or can Xero or MYOB stay?
  • 03How does it handle our sites, entities, units of measure and pricing rules?
  • 04Who configures it, who supports it, and how are changes made after go-live?
  • 05How do we get our data out if we leave?
  • 06How does the cost change as users, sites and transaction volumes grow?
Field service job apps for an electrician and a cleaner
Job apps for the people in the field. Example screen; the name on it is invented.

Implementation risks

Data is the first risk. Product codes, customer records, supplier details and opening stock need cleaning before they move, and years of inconsistent spreadsheets take longer to tidy than anyone expects. Plan a trial import early, check totals and a sample of records against the source, and agree who on your side signs off that the data is right.

Process change is the second. Any new system changes how people work, and a packaged ERP may ask for bigger changes than a system built around you. Involve the people who do the work, train them on their own examples, and run the new system alongside the old one on real orders until the numbers match. Staff who trust the stock figures stop keeping their own.

Over-scoping is the third, and the most common. It's tempting to switch on every module and replace every tool on one go-live date. Each extra module adds configuration, data and training to the same weekend. Start with the area costing the most, prove it in daily use, and add the next area once the first has settled. That applies whichever route you choose.

Terms in this guide

Questions owners ask us

What is the difference between an ERP and accounting software?

Accounting software records the financial result of what happened, while an ERP also runs the operations that produce it. Xero or MYOB tracks invoices, bills, payments and the ledger. An ERP adds the steps before those: quotes, orders, purchasing, stock movements, production and jobs, all in the same records. Many businesses get ERP functions by connecting an operations system to their accounting package, so the two don't have to be one product.

Can an ERP be put in one module at a time?

Yes, and it's usually the safer way. Most packaged ERPs let you start with finance and one operational area and switch on others later, and a custom system can be built in the same staged way. The catch is that the first stage has to be useful on its own, with working connections to whatever tools are still running, so the team isn't stuck between old and new systems with no link between them.

Are we too small for an ERP?

You might be too small for a full packaged ERP, but not for the problems one solves. Complexity matters more than headcount: a business with forty staff, three warehouses and thousands of products can need ERP functions more than a larger service business. If your stock, orders and accounts already connect well, you probably don't need one yet. If people join them up by hand every day, you need something that does.

Will we have to change how we work to fit an ERP?

With a packaged ERP, usually to some extent. The product is designed around common practice, and configuring it to match unusual processes takes time and can complicate later upgrades. Sometimes changing is good, because the standard way is simply better. Where your process is the reason customers choose you, it's worth protecting, either by choosing a product that already fits it or by building that part around how you work.

Show us how you run it today.

Thirty minutes with the people who would build it. We'll map where the hours go and tell you honestly whether custom software is worth it for you.