What people usually mean when they say “we need an ERP”
When a business owner tells me they need an ERP, they’re rarely describing the software. They’re describing a feeling. The same customer exists in four places with four slightly different addresses. Nobody trusts the stock figure. Month-end means someone exporting three spreadsheets and stitching them together. Every new hire takes weeks to learn which system holds which truth.
An ERP (enterprise resource planning) system promises to fix all of that by putting everything in one place: sales, purchasing, stock, finance, often HR and project costing too. For some businesses, that’s exactly right. For many smaller ones, it’s a very large answer to a narrower question.
The real problem is usually the gaps between systems
Most established SMEs already have reasonable tools. A CRM the sales team actually likes. An accounts package the bookkeeper knows inside out. A booking or job system that fits the way the work is done. Each one is fine on its own.
The pain lives in the gaps. A won deal doesn’t create the job. A finished job doesn’t raise the invoice. A paid invoice doesn’t update the customer record. People fill those gaps by re-typing, and re-typing is where errors, delays and the “which number is right?” arguments come from.
If that sounds familiar, replacing every system at once is one option. Connecting the ones you have is another, and it’s usually faster, cheaper and far less disruptive.
When an ERP genuinely makes sense
There are good reasons to go the ERP route:
- Stock is central to the business. If you hold inventory across locations, manufacture, or need tight landed-cost tracking, an ERP’s joined-up stock and finance model is hard to replicate with connections alone.
- Your current tools are the problem, not just the gaps. If the CRM, accounts and job system are each being outgrown in their own right, you may be replacing them anyway.
- You need one audit trail. Regulated work, complex multi-entity accounts or strict traceability can tip the balance.
- You have the capacity to change. An ERP rollout changes how almost everyone works. It needs time, internal ownership and patience through the dip that follows go-live.
If two or three of those apply, an ERP deserves a serious look.
When connecting what you have is the better move
Integration tends to win when:
- People are broadly happy with their own tools. Forcing a sales team off a CRM they like to get “one system” can cost more in lost adoption than it saves.
- The pain is in a few specific handovers. Deal to job, job to invoice, invoice to customer record. Those are well-understood connections.
- You need results this quarter, not next year. A focused integration can be live in weeks. Most ERP projects take months.
- The budget is real but finite. Connecting systems is usually a fraction of the cost of licensing, configuring and migrating to an ERP.
The honest trade-off is that connected systems need looking after. Software providers change their APIs, and a connection that’s never monitored will eventually fail quietly. Building it properly means logging, alerts and someone who knows how it works. I’ve written more about that in why CRM automation keeps breaking.
A simple way to decide
Before talking to any vendor, map the handful of journeys that matter most. For most businesses that’s enquiry to sale, sale to delivery, and delivery to payment. For each step, note which system holds the information and where someone re-types it.
Then ask two questions:
- Are the systems themselves failing, or just the handovers between them? If it’s the handovers, connect them.
- Would the business still need to change how it works, even with perfect software? If yes, fix the process first. Neither an ERP nor an integration will rescue a process nobody agrees on.
That map is also the most useful thing you can hand any supplier, because it turns “we need an ERP” into a specific list of problems with a specific cost attached.
Where I’d start
If you’re weighing this up, a Transformation Day is designed for exactly this decision. It’s a fixed-price day, often on site, at £600. I look at how the work actually moves through the business and you leave with a prioritised roadmap, with no obligation to go further. Sometimes that roadmap says “buy an ERP”. More often it says “connect these three things first and see how far that gets you”.
Read what a Transformation Day looks like, or get in touch. The first call costs nothing.
