Your CRM is not wrong. It is empty.

One week in four

Ask a salesperson why their client record is out of date. They will not tell you they do not care. They will tell you they have just come out of a meeting, they are running to the next one, and that filling in seven fields to record a forty-minute conversation costs them more than it gives back.

They are right. CRM entry is work whose benefit goes to someone else: to the owner who wants a view, to the colleague who will pick the account up, to a successor two years from now. Whoever types gets nothing back straight away. It is a tax, and like every poorly understood tax it is paid as late and as little as possible.

You know the result: accounts with no last contact, opportunities stuck at a stage they left long ago, risk fields never filled in. The CRM shows nothing false. It shows almost nothing at all.

What a copilot that invents does

For two years every vendor has been selling the same remedy: a copilot plugged into the CRM that types for you. On paper it is exactly the right idea. In practice most of these copilots have one flaw that cancels the whole benefit: they assert without checking.

Two sentences are enough to break a sales team’s trust.

• “It has been saved.” It has not. The write failed, the assistant did not notice, and nobody finds out before next month’s pipeline review.
• “That client does not exist.” They do. The CRM was unreachable at the moment of the query, and the assistant read an absence of response as an absence of data.

These are not display bugs. They make the tool unusable, because they force you to check behind it. And once you check everything behind it, you have lost the time you came for. The team stops using it after three weeks, and the story ends with “we tried AI, it gave us nothing”.

The three guardrails

An assistant plugged into commercial data does not need to be brilliant. It needs to be verifiable. Three rules are enough, and each one can be checked in use.

• It never says an action is done when it is not. Write confirmed, or write reported as failed. No third possibility, no ambiguous wording.
• It never cites a record absent from your data. If the CRM does not answer, it says “I cannot look this up”. The difference between “I do not know” and “it does not exist” is the whole difference between a tool and a trap.
• Nothing is written until a human says yes. Every creation or change goes through an approval card, and stays reversible afterwards.

These three rules can be tested in ten minutes: cut the CRM connection and ask it a question about an account. If it invents an answer rather than announcing the outage, you know where you stand. It is the test we run ourselves in a demo, in front of the client, on their own data.

When typing disappears

The day recording a meeting costs one dictated sentence instead of seven fields, the tax falls away. What matters is not the promise but the order of operations: first remove the cost of entry, then hope the base fills up.

What that gives, once the team really uses it:

• The meeting note is dictated in the car, and it lands on the right record.
• The question “where are we with this client” gets an answer that cites its sources, with the date of each item, and states what is missing.
• The follow-up to prepare comes out of the schedule on its own, drafted, waiting for a green light.

None of those three is spectacular. Put end to end, they are the difference between a base that empties and a base that holds. And a base that holds is the only condition under which everything else, forecasting included, means anything.