Blog

ERP for small business: do you need one, or a few connected tools?

Benjamin · · 6 min read

ERP projects are large, disruptive and often disappointing. What an ERP does, how NetSuite, Business Central and Odoo compare, what the research says about ERP projects, and when connecting your existing tools is the better route.

An ERP (enterprise resource planning) system puts your core business data, including finance, inventory, purchasing, sales, operations and often HR, into one system with one database. For a growing business, the pitch is compelling: no more spreadsheets in between, one version of the truth. The reality is that ERP projects are large, disruptive and often disappointing, and many small businesses can get the benefits a different way, by connecting the tools they already use around a shared record.

This guide explains what an ERP does, the main options for smaller businesses and how they work, what the research says about ERP projects, and how to tell whether you need an ERP or a few connected tools.

What an ERP actually does

An ERP brings several functions together in one system:

  • Finance and accounting: ledger, invoicing, payables, receivables, reporting.
  • Sales and orders: quotes, sales orders, pricing.
  • Purchasing: purchase orders, suppliers, approvals.
  • Inventory and warehouse: stock levels, locations, transfers.
  • Manufacturing or projects: bills of materials, work orders, project costing.
  • Often HR, payroll, CRM and service as well.

The real value isn't any single module. It's that an order, the stock it uses, the purchase that replaces that stock and the invoice all share one database, so nothing is retyped and the numbers agree.

What the research says about ERP projects

  • Most ERP projects fall short of their business case. Gartner predicts that more than 70% of recently implemented ERP initiatives will fail to fully meet their original business case goals by 2027, as reported by TechTarget. The reasons are mostly organisational: no one owns the benefits after go-live, weak governance that allows endless customisation, business cases focused on replacing old systems rather than improving how work flows, and change management that never happens. (TechTarget)
  • Overruns are common even in successful projects. Panorama Consulting's 2026 ERP Report surveyed 170 organisations with a median annual revenue of about 200 million US dollars. The median project took nine months. More than a quarter of organisations went over budget, most often because of an unexpected need for additional technology, and almost a quarter went over schedule, most often because of organisational issues such as governance, resistance to change and process redesign. (Panorama Consulting Group)

Those studies are mostly of larger organisations with project teams and budgets to match. A small business has less room for a nine-month project that goes over.

The ERP options for smaller businesses

Oracle NetSuite

How it works: a cloud ERP covering financials, inventory, orders and more, configured to your business by NetSuite or a partner, with add-on modules as you grow.

Where it shines: fast-growing product businesses that need serious financials, multiple entities or multiple currencies.

Where it stops: implementation is a real project, usually through a partner, and ongoing customisation needs specialist skills.

Microsoft Dynamics 365 Business Central

How it works: Microsoft's ERP for small and mid-sized businesses, closely tied to Microsoft 365, Power BI and Power Apps, and usually implemented by a partner.

Where it shines: businesses already committed to Microsoft that want finance, inventory and projects in one place.

Where it stops: like other ERPs, it's a partner-led project, and anything specific to your process becomes customisation.

Odoo

How it works: a suite of modular apps (CRM, sales, inventory, accounting, manufacturing and more) on one database. The Community edition is open source under the LGPL licence. The Enterprise edition adds more apps, Odoo's hosting and support. (Odoo)

Where it shines: businesses that want to start with a few apps and add more, with the option to self-host.

Where it stops: breadth comes with configuration effort, and heavy customisation can make upgrades harder.

SAP Business One, Acumatica and Zoho

SAP Business One and Acumatica are established ERPs for smaller companies, both usually sold and implemented through partners. Zoho offers a bundle of its own apps that share data across finance, CRM, inventory and more. Each has the same trade-off: everything in one place, provided you adopt their way of working.

When an ERP is the right answer

An ERP makes sense when most of these are true:

  • Inventory, purchasing and finance are tightly coupled, for example in manufacturing, wholesale or multi-site retail.
  • You have multiple entities, currencies or warehouses, and consolidating them by hand is breaking down.
  • Your processes are broadly standard for your industry, so the ERP's way of working fits.
  • You can staff the project: an internal owner, time from every department, and a partner.
  • Your current accounting package is genuinely being outgrown, not just poorly connected.

When a few connected tools beat an ERP

Many growing businesses don't have an ERP problem. They have a connection problem. Their accounting package is fine. Xero, QuickBooks and Zoho Books are good at accounting. Their CRM is fine, and so is their shop. What's missing is the flow between them, which is currently a spreadsheet and a person.

For them, a lighter approach often works better:

  1. Keep the tools that do their job well. Accounting stays in the accounting package and customers stay in the CRM.
  2. Add the missing pieces as focused tools: an order or job system shaped around how you work, stock tracking, purchase approvals or a quote builder.
  3. Connect everything around a shared record. Each order, job or product exists once, linked to the customer in the CRM, the invoice in accounting and the stock movement in inventory.
  4. Put one view on top: a dashboard showing orders, stock, cash and what's stuck, from all the tools at once.

You get most of what an ERP promises, with data entered once and numbers that agree, without replacing systems your team knows. Each piece can go live in weeks, one process at a time. And if you later grow into a real ERP, the clean, connected data makes that move far easier.

How to decide

  • Inventory, manufacturing or multi-entity finance at the core, with standard processes: an ERP, chosen carefully and staffed properly.
  • Several good tools, but data retyped between them: connect them around a shared record instead.
  • One process unlike anything an ERP supports, and core to how you compete: a custom tool for that process, connected to your ERP or accounting package.
  • Not sure: map the processes first. The map usually makes the answer obvious.

Before you decide: map the flow, not the modules

  1. Follow one order from enquiry to cash, writing down every tool it passes through.
  2. Mark every handoff where someone retypes or re-checks data.
  3. Mark the numbers that disagree, like stock, margin or what's been invoiced.
  4. Ask of each tool: is it bad at its own job, or just disconnected?
  5. If most tools are fine but disconnected, connect them. If several are genuinely failing at their own job, an ERP selection may be worth it.

How we help at Lephlo

We build the connected alternative: focused internal tools and integrations that join up the accounting, CRM, shop and operations tools you already use, around one shared record and one view of the business. We'll also tell you honestly when a proper ERP is the better route.

It starts with a free consultation where we map how an order flows through your business today. We scope the first piece, give you a fixed price for it, and build it in short steps. You own the code and the data, fixes are free during the fix period after launch, and we stay on hand as it grows.

Related reading: system integration for small businesses and internal tools: the apps you already use, and how to connect them. To size a first version, try the Build Scope Planner, or book a free consultation.

Frequently asked questions

Does a small business need an ERP? Only some do. If inventory, purchasing and finance are tightly linked and your processes are standard, an ERP can be worth it. If your tools are good but disconnected, connecting them usually costs less and disrupts less.

What is the difference between an ERP and accounting software? Accounting software handles the books: invoices, bills, bank and reports. An ERP adds operations like inventory, purchasing, manufacturing and projects on the same database as the books.

Can Xero or QuickBooks work as an ERP? Not on their own, but connected to inventory, order and job tools they can cover much of what a small business would use an ERP for.

What is a custom ERP? Usually a set of custom tools covering the operations an off-the-shelf ERP doesn't fit, connected to standard accounting. Building a whole ERP from scratch is rarely the right answer for a small business.

Sources