BlogChoosing an ERP
ERP or CRM: which do you need first.
A CRM helps you win the customer; an ERP helps you deliver their order. Which one comes first depends on where you lose more: before the order or after it.
The difference in one sentence
A CRM (Customer Relationship Management) manages your relationships with customers: contacts, conversations, quotes, next steps. Its goal is more and better deals.
An ERP manages delivery: orders, stock, production, purchasing, invoices. Its goal is for the order to reach the customer on time, in the right quantity and at a known cost.
One ends roughly where the other begins: at the confirmed order.
Think of it as a relay. The CRM carries the baton from the first contact to “yes, we’ll order”. The ERP takes it from there to delivery and payment. If the handover is manual, that is where details get lost.
What a CRM does
- Keeps contacts and the history of conversations with each customer.
- Shows deals by stage: enquiry, quote, negotiation, won.
- Reminds you of next steps and follow-up calls.
- Forecasts sales by salesperson.
A CRM makes the most sense when the sale is long, with many contacts and quotes, and when you have several salespeople.
The main question a CRM answers is: “Who should we talk to this week, and why?”. If your salespeople keep notes in notebooks and on personal phones, a CRM brings that knowledge back to the company.
What an ERP does
- Turns the accepted quote into an order with a date and a status.
- Reserves stock and shows what is missing.
- Plans production and consumes materials.
- Suggests what to order from suppliers.
- Issues the invoice from the actual order.
An ERP makes the most sense when delivery is complex: a warehouse with many items, production, suppliers with different lead times.
The main question an ERP answers is: “Can we deliver this, when, and at what cost to us?”. If a salesperson has to walk round the warehouse and the shop floor to promise a date, that answer is missing.
Where they overlap
Both systems have customers and quotes. That is why it often looks like you must pick one. In fact the question is which process hurts more.
Many ERP systems have a basic customer area: contacts, quotes, order history. For a company that sells to repeat customers, that is often enough. A full CRM becomes necessary when the sale itself is a project.
The reverse is also true. Some CRM systems have simple orders and invoices. They work for services without stock, but rarely suffice once there are materials, batches or production.
So don’t compare feature lists. Compare which question costs you more every week: “who should we call” or “can we deliver it”.
If your customers email you for the same items every month, your problem is probably not selling. It is delivering.
Example: two companies with different needs
Company A sells industrial equipment by project. One deal takes, for example, three months, five meetings and three versions of the quote. Orders are few but large. Here a CRM pays off more: most time is lost tracking deals.
Company B is a print shop with, for example, 40 orders a week from repeat customers. Customers order on their own, by email or phone. The problems are deadlines, materials and machines. Here an ERP pays off more: most time is lost in delivery.
If Company B implements a CRM first, it will have tidy contacts, but orders will keep running late. If Company A implements an ERP first, it will have a tidy warehouse, but deals will keep slipping away.
Notice that the difference is not the size of the companies but where the complexity sits. For Company A it is in the conversation with the customer. For Company B it is on the shop floor.
Over time, both companies may end up with both systems. The difference is the order. The right order pays off from the first stage and funds the next one.
How to decide which comes first
- Take the last ten customer problems you know about.
- Split them into two groups: before the order was confirmed and after.
- Next to each problem, note what it cost in time or money, even roughly.
- The group with the bigger total tells you where to start.
If most problems are “we forgot to call back” and “the quote was late”, start with a CRM. If they are “we had no material”, “we promised the wrong date” and “the invoice was wrong”, start with an ERP.
For example, ten problems might split into three before the order and seven after. If those seven include two returned shipments and one late-delivery penalty, the answer is clear before you add anything up.
Ask both sales and the warehouse. Each sees their half of the problems, and you need the whole picture to decide.
If you need both
Then the most important thing is that data is never entered twice. A deal won in the CRM should become an order in the ERP without retyping.
The other direction matters just as much. Salespeople should see in the CRM whether the order has shipped and whether the customer has an overdue payment. Otherwise they will keep phoning the warehouse and accounts.
Settle these questions before you sign for the second system, not after people have started working in it.
If any of these points is missing, the link between the systems will be maintained by people copying and pasting. That is the same problem you set out to solve.
How systems connect is described on the integrations page.
How we approach it
Our strength is delivery: orders, stock, planning and invoices. The orders module already has a customer base: import from Excel or CSV, duplicates found and merged, tags, contacts, a communication log and credit limits. That is often enough for repeat customers. If you already use a CRM, we discuss connecting to it rather than replacing it.