An ERP (enterprise resource planning) system is one shared database and set of workflows covering finance, inventory, purchasing, sales and often HR, so each transaction is entered once and everyone works from the same numbers. A small business needs one when its disconnected tools cost more in rework, errors and slow decisions than a single system would cost to run.
That test matters more than headcount or revenue. A ten-person distributor with three warehouses and thousands of stock items may need an ERP long before a fifty-person consultancy that sells time and sends a few invoices a month. This guide gives you a scored test, the realistic alternatives, and a way to put a number on the cost of waiting, so the decision rests on your operations rather than on a sales pitch. If you want the basics first, start with what ERP software is.
What problem does an ERP actually solve?
An ERP removes the gaps between departments: the re-keying, the spreadsheet that reconciles two systems, and the question nobody can answer without a day of work. It does not make a business more profitable on its own; it makes the business easier to see and harder to get wrong.
The symptoms usually look like this:
- The same order is typed into a sales tool, a stock spreadsheet and the accounting package.
- Stock figures in the warehouse and in the books disagree, and nobody knows which is right.
- Month-end close takes days because people are matching exports by hand.
- A simple question, such as margin by customer or by product line, needs a custom spreadsheet each time.
- Approvals happen in email, so nobody can prove who approved a purchase or a discount.
- One or two people hold the process in their heads, and holidays are a risk.
If none of these sound familiar, you probably do not need an ERP yet. If several do, the test below will tell you how urgent it is.
The 10-question test: does your business need an ERP now?
Score each question 0 (no), 1 (sometimes or partly) or 2 (yes, regularly). Be honest; the point is to find out, not to justify a purchase already decided.
| # | Question | Score 0 to 2 |
|---|---|---|
| 1 | Do staff re-enter the same transaction in two or more systems? | |
| 2 | Do you hold stock, and do stock counts regularly disagree with the records? | |
| 3 | Does month-end close depend on manual spreadsheet reconciliation? | |
| 4 | Do you trade through more than one legal entity, branch or warehouse? | |
| 5 | Do you need margin by product, customer, project or job, and struggle to get it? | |
| 6 | Are purchases and discounts approved informally, with no audit trail? | |
| 7 | Have you hit a limit in your accounting software (users, entities, stock features)? | |
| 8 | Do customers or auditors ask for traceability you cannot easily provide (batch, serial, approvals)? | |
| 9 | Are you planning growth (new site, new country, new channel) in the next 12 to 24 months? | |
| 10 | Would losing one key person stop a core process? |
How to read your score:
- 0 to 6: Your current tools are probably fine. Tidy up processes and integrations first.
- 7 to 12: You are in the grey zone. Look hard at the alternatives in the next section; a well-connected set of tools may carry you for a while.
- 13 to 20: The disconnected approach is likely costing you more than you see. Start scoping an ERP, packaged or custom.
Questions 2, 4 and 8 carry extra weight in practice. Stock, multiple entities and traceability are where spreadsheets fail first and most expensively. If your score is high and your processes are specific to how you trade, our custom ERP software page explains how a system built around your workflows is scoped and delivered.
What are the alternatives to an ERP for a small business?
The main alternative is a connected stack: accounting software plus a specialist inventory or job tool plus a CRM, linked by integrations. For many small businesses this is the right answer for years.
| Option | Good fit when | Watch out for |
|---|---|---|
| Accounting software only | Service business, few transactions, no stock | Stock, approvals and job costing live in spreadsheets |
| Accounting plus an inventory app | One or two warehouses, simple products | Two sources of truth for stock value; sync errors at month-end |
| Accounting plus inventory plus CRM, integrated | Clear separation between sales, stock and finance | Every integration is a point of failure that someone must monitor |
| Packaged ERP (Odoo, NetSuite, Business Central and similar) | Your processes are close to standard practice | Configuration effort, licence growth, workarounds where you differ |
| Custom ERP | Your processes are a competitive advantage or unusual | Needs a clear brief, a capable partner and ongoing support |
Two related comparisons may help: ERP versus accounting software covers when the accounting package stops being enough, and ERP versus CRM explains why a CRM does not replace an ERP, and vice versa.
When the connected stack stops working
The connected stack usually breaks in one of three places:
- Stock value. The inventory app and the general ledger drift apart, and someone posts a manual adjustment every month without knowing why.
- Multi-entity trading. Inter-company sales, transfers and consolidations become spreadsheet work.
- Cross-department workflow. A sales order should reserve stock, trigger a purchase, wait for approval and post to the ledger. When that chain crosses four tools, exceptions get lost.
What does it cost to wait?
The cost of not acting is real but hidden, because it is spread across salaries, write-offs and decisions made on stale numbers. You can estimate it with a simple worksheet.
Illustrative example (hypothetical figures, use your own): a wholesaler has three people who each spend about half a day a week reconciling orders, stock and invoices across tools. That is roughly a day and a half of skilled time every week, before counting the extra days at month-end, the stock written off because nobody noticed it expiring, and the customer orders delayed because availability was wrong.
Use this worksheet to build your own figure:
- Hours per week spent re-keying or reconciling data, multiplied by a loaded hourly cost
- Extra days of month-end close, multiplied by the people involved
- Stock write-offs and emergency purchases traced to bad stock data over the last year
- Revenue lost to stock-outs, late deliveries or pricing errors you can identify
- Audit, tax or customer queries that took days to answer
- The risk cost of key-person dependency (what happens if they leave?)
Compare that annual figure with the full cost of owning a system, not just the licence or build fee. Our sibling guide on signs you need a new ERP covers the warning signs for businesses that already have one and have outgrown it.
When is an ERP not the right move?
An ERP is the wrong move when the problem is process, not software, or when the business is too simple or too unsettled to benefit.
- Your processes are not agreed. If two branches do the same job in different ways and nobody has decided which is right, an ERP will encode the argument, not settle it.
- You have very few transactions. A consultancy issuing a handful of invoices a month gains little from inventory, purchasing and manufacturing modules.
- You are about to change the business model. If you are pivoting, merging or selling within months, wait until the shape is clear.
- Nobody can own it. An ERP needs an internal owner with authority and time. Without one, adoption fails whatever you buy.
- One integration would fix it. Sometimes a single link between the accounting package and the inventory app removes most of the pain. Try that first.
Packaged or custom ERP: which fits a small business?
Most small businesses with standard processes should start with a packaged product and configure it. Custom fits when the way you trade is what makes you different, or when packaged products force so many workarounds that you would be paying for software you then bypass.
We cover that trade-off in depth on ERP versus custom development, so this guide will not repeat it. A useful rule of thumb: if you can describe your core process in a page and it reads like a textbook, buy. If describing it takes ten pages of exceptions your customers value, consider building the parts that differ.
How to start: what to prepare before you talk to anyone
The best first step is a short written brief, not a vendor demo. A brief makes demos comparable and stops the loudest salesperson setting your requirements.
Preparation checklist:
- Your test score and the three questions that scored highest
- A one-page map of how an order flows from quote to cash today, including every tool it touches
- The reports you cannot produce now and who needs them
- Number of users by role, entities, sites and warehouses
- Systems that must stay (e-commerce, payroll, banking) and must integrate
- Your cost-of-waiting estimate from the worksheet above
- An internal owner who will make decisions
Our software requirements brief template gives you a structure for this. When it is ready, you are welcome to discuss the project with us. Timeline Digital builds 2 to 3 key modules as a free pilot before the full project starts, so you can judge the fit with your own data before committing.