BlogGuide
CRM or ERP: which one you need
and in what order
Two different things that get confused constantly. One handles the money that has not arrived yet, the other what happens after. Which comes first depends on where you are losing money now.
The difference, in two sentences
A CRM handles everything before the order: who called, what they asked for, which quote went out, who needs a follow-up and when. It is the map of money that has not arrived yet.
An ERP handles what comes after: stock, purchasing, production, real costs, invoicing. It is the map of money already moving through the company.
How to tell which one you are missing
Do not look at what you have heard others use. Look at where you are losing money now. Every company leaks in a different place, and the right system is the one that plugs that particular leak.
- If enquiries get lost in email and nobody knows who was left without a reply, you are missing a CRM
- If quotes go out and nobody follows them up, you are missing a CRM
- If you cannot tell what is in stock without going to count it, you are missing an ERP
- If you only find out at the end that a job ran at a loss, you are missing an ERP
- If the same data gets retyped in three places, what you are missing is integration, not another system
Why the order matters
For most small and medium companies the CRM comes first. The reason is simple: it brings in money, not just order. An enquiry that does not get lost and a follow-up that happens by itself show up in revenue within the first month, and people adopt it because it makes their day easier immediately.
An ERP is harder to introduce, touches more people and pays off more slowly but more heavily. Put first, in a company that does not yet have data discipline, it usually ends up half used.
The exception is obvious: if the company lives on stock and production while sales are covered by long-standing relationships, the order flips.
Off the shelf or custom
An off-the-shelf system costs little per month and covers the general case. It is worth it when your process really is the general one and when you can adapt to it.
A custom one costs more at the start and is worth it when your process is your competitive advantage, or when the exceptions are so numerous that in a standard system they all end up in the notes field. A full notes field is the clearest sign the system does not fit.
Quick test: if you need a separate file, kept alongside the system, for the process to work — the system does not fit.
How it gets introduced, module by module
One process, the one that hurts
Not the whole company at once. Enquiries, or stock. Something that can go live in weeks and shows immediately.
Old data, migrated cleanly
Without real data nobody uses a new system. With dirty data, everybody loses faith in it.
Integration with what you have
Invoicing, accounting, the online store. This is where most time goes, so it gets checked before the quote.
The remaining modules, one at a time
Each one fully live before the next begins.
What this is about, in full
Frequently asked questions
Can we have both a CRM and an ERP without them clashing?
Yes, if they are connected. Usually the CRM sends the order to the ERP and gets its status back. The problem is two systems that do not talk, with somebody copying between them.
How long does a CRM implementation take?
The first slice used daily, in four to six weeks for a small company. An ERP is measured in months, because it touches more departments.
Is it worth it for a company of five people?
A CRM, almost always, because at five people every lost enquiry is felt. A full ERP, usually not; a management system built around the actual process serves better.
Does the data stay ours?
With a custom system, yes: the code and the database stay with the client, with documentation on handover. With off-the-shelf systems it depends on the provider contract, which is worth reading first.