We Bought a CRM and Nobody Uses It

The CRM that went in a few months ago is sitting empty. The sales team still keeps its own spreadsheets, and management still asks for files to add the numbers up.

We see this often, and the reason is rarely that the software falls short.

The real reason, the system makes the work harder

A salesperson has ten conversations a day. If logging one takes three clicks, they log it. If it takes seven clicks and two mandatory fields, they do not.

And once they stop, the system empties out within weeks. Then management looks at the reports, the numbers do not match reality, and trust is gone.

So the first thing we look at is the most frequent task. Putting that on the shortest path comes before every other feature.

Second reason, the stages do not belong to the company

An off-the-shelf CRM brings its own stages. Quoted, negotiating, won. When those do not line up with how you actually work, the team has to file every record in the wrong box.

Before long everyone interprets it their own way, and the same stage means two different things to two salespeople. That is the point where the reporting stops meaning anything.

We take the stages from how the company actually sells. This is not something ready-made tools cannot do, but on most rollouts nobody does that configuration.

Third reason, records with no owner

Every enquiry needs an owner. An enquiry that belongs to nobody gets picked up by nobody, and that is usually the one that disappears.

Assignment can be manual or driven by a rule. What matters is not which, but that it is never left empty.

Fourth reason, follow-up depends on somebody remembering

Calling a customer back in two weeks does not happen unless it is written somewhere. Putting that on a person is unfair, because tracking thirty open records at once is not something a human does well.

Follow-up has to become a record. A dated task is opened, it surfaces on the day, and it stays on the list until it is actually done.

Fifth reason, there is no history

When someone new takes over an account and cannot see what was last discussed, they make the customer explain it a second time. The customer notices.

A conversation history gathering under one record turns a handover from a meeting into something you can read.

Off-the-shelf or custom

The honest answer is this. If your process is standard, the ready-made tool is cheaper and faster, and we say so plainly. You pay monthly and skip the build entirely.

If your process is what makes you different, a custom build protects that difference. Where pricing varies by customer, where a sale passes through more than one team, or where your quote comes out of a complicated calculation, bending a ready-made system into that shape usually costs more in the end.

What we do during the build

First we watch how the company actually sells. The process as described and the process as performed are rarely the same, and we build for the second one.

Then we put the most frequent task on the shortest path. Everything else is arranged around it.

A customer list is the easiest asset in a company to walk out of the door, so who can see what, and the logging of exports, are defined from the start.

Sixth reason, too many mandatory fields

Mandatory fields go in with good intentions, so that data does not end up incomplete. In practice they do the opposite.

When a salesperson has to fill five fields they do not know the answers to just to open a record, they either do not open it or they type something made up. The second is worse, because the system looks full while the data inside it is wrong.

We keep mandatory fields to a minimum. The record opens first and the detail is added later. An incomplete record beats a record that never existed.

Seventh reason, management does not look at the system

This might be the decisive one. If managers still ask for the numbers out loud in a meeting, the team learns that entering them serves no purpose.

A system only gets used when it becomes the source of decisions. Run the weekly meeting off the screen and everyone starts entering their records. That is not a software feature, it is a habit, but it is what determines whether the software survives.

You cannot manage what you do not measure

The most concrete benefit of a CRM is turning the conversion rate from a guess into a measurement. How many enquiries came in, how many were quoted, how many turned into work.

A company that knows those three numbers knows where it is losing. Are too few enquiries arriving, or are most of the ones arriving never reaching a quote? Those are very different problems needing very different fixes.

Source tracking belongs here too. If you do not know which channel produces enquiries that convert, you are deciding where to put the advertising budget blind.

The first month after go-live

The first month is the one that matters. Whether the system gets used is decided there.

During that month we watch where the team gets stuck. Which screen they hesitate on, which field they leave empty. Then we fix those points.

Most of what people try to solve with training is actually a design problem. If a screen takes half an hour to explain, the problem is the screen, not the user.