What CRM software is, and who actually needs it

CRM is one of the most-bought and least-used categories of software. The reason is usually not a bad product choice; it is that the need was never defined.

When a company says "let's get a CRM," the sentence underneath is usually: "we are losing information about our customers." Those are not the same thing. The first is a product decision, the second is a process problem. A product bought without defining the process becomes a tab nobody opens within three months.

What a CRM actually does

At its core it does one job: it keeps the entire history with a customer in one place. Who called, what was discussed, which quote was sent, when to follow up.

Everything else sold alongside it, automation, reporting, email marketing, is built on top of that foundation. If the foundation is not working, neither is anything above it. Reports come out empty in a CRM where nobody records anything.

So evaluating by feature list is misleading. The only thing worth asking is: will the team actually enter records into this system?

Signs that you need one

• You have to ask more than one person to reconstruct a customer's history.
• When someone leaves the sales team, the customer knowledge goes with them.
• Two people send separate quotes to the same customer.
• Nobody can answer "how many quotes did we send last month?"
• Customers who need following up get forgotten.
• Only one person knows what stage a deal is at.

If most of these are true, you need a CRM. If none of them are, you can probably manage with a spreadsheet, and you should. How far can a spreadsheet take you covers when it stops being enough.

Why CRM projects go unused

Data entry is seen as overhead. For a salesperson, entering records is time taken away from selling. If putting data in does not return something to them quickly, the records do not get kept.

The fix is to minimise data entry and make what is entered come straight back as something useful: follow-up reminders, quote history, auto-filled fields. When a salesperson sees yesterday's entry making today's job easier, they keep entering.

Everyone's needs get crammed into one screen. Management reporting, sales follow-up, and collections all forced through the same screen means it works well for nobody. Salespeople skip the reporting fields, managers find the incomplete report untrustworthy, and the system is gradually abandoned.

It does not connect to the other systems. If customers entered in the CRM get typed into accounting by hand, you are keeping duplicate records and one of them will fall out of date. Before long the question becomes "which one is right?" and trust disappears.

Too many required fields. A form with fifteen mandatory fields is not something a salesperson wants to fill in after hanging up the phone. The more required fields, the lower the completion rate.

Old data was not migrated. If the new system opens empty, the team keeps looking at the old file and two sources live in parallel.

Off-the-shelf or custom?

Off-the-shelf is enough if your sales process runs a standard course: lead, meeting, quote, sale.

Custom development is warranted if:

• Your process includes sector-specific stages such as site survey, sampling, fabrication, or installation.
• Your pricing varies with product configuration.
• The CRM has to work closely with ERP or production planning.
• Per-user licence costs compound as the team grows.
• The data has to stay in-country and on your own servers.

There is a third path that suits most companies: leave the off-the-shelf CRM as it is and build only the missing piece. For example, write a quote calculation screen around your own rules and write the result back into the CRM. That keeps the ready-made infrastructure the licence gives you without forcing your process. The decision framework in ERP or custom software applies here too.

Multiply the licence cost by three years

CRM decisions usually get made by looking at the monthly per-user fee. The correct comparison is monthly fee times user count times thirty-six months, plus two more items: integration development and data migration.

The resulting figure is often comparable to a custom development budget. That does not mean off-the-shelf is wrong. It just means the decision gets made with a real number.

A practical suggestion: measure for two weeks first

Before buying anything, spend two weeks measuring how long your sales team spends finding a customer's history. How often does it happen, and how long does each instance take?

Add two more numbers: how many follow-ups were forgotten, and how many times two people approached the same customer separately.

Those four numbers tell you both whether a CRM is necessary and what budget makes sense. Without measurement, the loudest opinion in the room usually wins, and it is usually not the right one.

Get the order right when you implement

1. Write down the current sales process first. How many stages are there, and what moves a deal between them?
2. Decide the minimum information required at each stage.
3. Migrate the existing customer data. An empty system does not get used.
4. Start with one team, confirm it works, then roll out.
5. Connect accounting and quoting only once the foundation is settled.

---

Describe your sales process and we can work out whether an off-the-shelf solution is enough or custom development is warranted. Get in touch.