ERP vs CRM: What Is the Difference and What Does an Agency Need?

The moment an agency grows from five to twelve people, someone says the word ERP. Usually the bookkeeper, sometimes an adviser. And when you go looking for "ERP system" or "ERP vs CRM", you mostly find explanations written by parties who sell ERP. They rarely reach the conclusion that you do not need one.

The short answer for most creative agencies, marketing agencies and freelancers: you do not need an ERP system. You need a grip on two things, and neither of those sits in the part an ERP is good at.

What is the difference between ERP and CRM?

The difference in one sentence: a CRM manages the money coming in, an ERP manages the money and the goods moving around inside the company.

A CRM is a system for everything to do with clients: leads, deals, proposals and follow-up. An ERP system is a system for the operations underneath: finance, purchasing, inventory, payroll and project administration, usually tied together in one database.

The rule of thumb advisers use is workable: choose CRM if you lack a grip on your revenue, choose ERP if you lack a grip on your process. The ERP names you will meet most often are NetSuite, SAP Business One, Microsoft Dynamics 365 Business Central and Odoo. If you are reading this in the Netherlands or Belgium, Exact and AFAS come up just as often, and Gripp, which turns up in a lot of agency lists, is now part of Exact.

ERP vs CRM: does an agency need an ERP system?

Rarely, and it is worth understanding why.

An ERP is built around the question of how something moves from purchasing to inventory to invoice. That is a beautiful problem if you make or trade products. An agency sells hours and thinking. There is no inventory, no purchase order and no production line. What an agency gets out of an ERP is the finance module and the project administration, and that is a fraction of what you pay for.

On top of that, implementing an ERP system is almost never a matter of switching it on. A project comes with it: configuration, migration and a consultant. For a ten-person agency that is out of proportion to what it delivers.

So why does it still feel like you need an ERP?

Because the feeling is right, but the diagnosis is not. What agencies experience at that moment is usually this:

• Nobody knows at a glance which clients are behind this month
• Agreements from a sales conversation live somewhere other than the project that came out of it
• There are six tools, and the answer to every question sits in two of them
• The bookkeeper asks things you can only answer by hand

That is not an ERP problem, that is a fragmentation problem. An ERP solves it by forcing everything into one system, and that is an expensive way to achieve something you can also get another way. How that fragmentation happens is something I wrote out in why agencies use too many tools.

What do you actually need instead?

Two things, and really nothing more:

• One place where client, deal and project live together. So nothing disappears between the moment you promise something and the moment someone carries it out.
• Accounting software sitting neatly next to it. Not integrated into it, just alongside, with a clear agreement about what belongs where.

That second point is where agencies often go wrong by trying to merge them. Bookkeeping is a well-defined problem that accounting software has solved well. The urge to have that in the same screen as your client projects is understandable, but in practice it rarely delivers what you expect. Packages that try to do both agency work and finance, like Gripp, Simplicate and Teamleader, I compared earlier in Gripp vs Simplicate vs Teamleader.

When is an ERP system the right choice?

There is a line, and it is reasonably sharp. An ERP becomes defensible if you have multiple locations or legal entities, if payroll administration for dozens of people comes into play, or if alongside services you also sell products and therefore do carry inventory. It also becomes a different conversation once external audit requirements demand one closed administration.

If you are not there, you are mainly buying complexity. And complexity is more expensive for an agency than software, because you pay for it in the time of people who should be doing client work.

Where does Wecooking fit in?

Wecooking is not an ERP and does not try to be one. It solves the first point: client, deal, proposal and project in one place, with a CRM where a won deal becomes a client project in one click, and a client portal where the client can follow along. From €19 per month, all included, currently free in beta.

What is not in it, and that matters for exactly this question: no bookkeeping, no invoicing, no time tracking and no payroll. If you are looking for one system that also holds your finances, you are looking at a different category of software and this is the wrong article to convince you.

Growing fast and mainly noticing that the overview is falling away? That diagnosis matters more than the tool you pick, and scaling an agency without chaos goes into it further. And if you simply want to see whether that one overview is already enough before starting an ERP project, trying it for free is a lot cheaper than a quote process with an implementation partner.