Articles · 6 November 2026 · Paulina Grzegorzek

The CRM nobody updates. What to do about it

A company buys a CRM, the implementation takes months, and six months later the salespeople still keep their contacts in Excel and in their heads. The data in the system is incomplete, so nobody trusts it, and since nobody trusts it, nobody updates it. There is a way out, but it usually isn’t another training session.

Too many fields

Every mandatory field takes a few seconds, and across hundreds of contacts that adds up to hours. A salesperson quickly works out that the system is eating time they don’t have, and starts working around it.

A good place to start is a simple question: which information does anyone actually use to make decisions? Everything else can wait or go. It usually turns out that a handful of fields is enough and the rest were added “just in case”.

The system doesn’t answer the salesperson’s questions

A CRM is very often built around a report for management rather than around a salesperson’s daily work. Yet a salesperson wants to know a few simple things: who to write to today, who has replied, and whether anyone on the team has already contacted this company.

If the system shows them this faster than Excel, they will start using it of their own accord, without reminders. The management report then comes as a by-product.

The pipeline stages don’t match how you sell

Stages copied from the vendor’s template rarely match the path a client actually takes in a given company. Salespeople don’t know when to move a card forward, so everyone does it differently and the numbers stop meaning anything.

It is better to map out, together with the team, what a client really goes through, and to name the stages the way the salespeople talk about them. Four to seven stages are usually enough, each with a clear rule for when a company moves on to the next one.

Re-keying data by hand

Every piece of information that has to be copied from an email or a spreadsheet is a chance that nobody will do it. The more happens automatically, the more complete the data: importing contact lists, automatically logging sent emails and replies, flagging companies someone has already spoken to and people who have asked not to be contacted.

A report assembled by hand before every meeting

If someone copies numbers from the system into a presentation before every meeting, the CRM is not the source of truth, just one of many places where data lives.

A dashboard that pulls the data itself does two things at once: it saves time and shows the team that what they enter is actually used. When meetings revolve around numbers from the system, keeping it up to date stops being an unpleasant chore.

An implementation without the team

A system designed without the salespeople usually misses their needs. It works much better to show a mock-up before building anything and gather feedback from the people who will use it every day.

A phased rollout also helps: for a few weeks the new system runs in parallel with the existing tool, the numbers are compared, and only then does the team switch over completely.

Replace the system or simplify it?

Most problems can be solved in the system the company already has: remove unnecessary fields, tidy up the stages, add imports and an automatic report. Switching makes sense only when the system can’t handle the basics or the licences cost more than the company gets out of it.

How I can help

I implement simple CRMs tailored to how your team really works: with a few fields, list imports and a dashboard that calculates the results by itself. Before I build anything, I show a mock-up to the salespeople, so they have a say in the system from day one. You can see what this might look like in the CRM demo, and I describe the whole process on the CRM implementation and dashboards page.

All articles · Checklist: 10 questions about your pipeline