01What You Actually See
What it looks like from the manager's chair
The Short Version
The real sales pipeline lives in a notebook, a personal spreadsheet and a phone. The system holds a version of it that is two weeks old, and everybody knows it.
The symptoms are always the same in a Brazilian manufacturer. Cards sitting in the same stage for 60 days while the rep says on Monday that the deal is progressing. Opportunity values rounded to fifty thousand because nobody updated after the quote went out. Interaction history that stops in March. And, the giveaway, the manager asking for the forecast by WhatsApp instead of opening the screen that was bought to show exactly that. The system is not wrong — it is empty, and everybody has already routed around it.
It is worth saying out loud what the rep is doing, because the usual reading is wrong. He is not sabotaging anything. He has eleven live quotes, a customer complaining about a delivery date, and a plant manager asking him to confirm a spec by four o'clock. Filling in a card takes seven minutes and returns him nothing today. Calling the buyer takes four minutes and might return an order this month. He is optimizing correctly against the incentives he was given. Fix the arithmetic and the behaviour follows; argue with the person and nothing moves.
A rep who does not fill in the CRM is answering a question nobody asked out loud: what does this cost me today, and what does it give me back today. The answer is usually seven minutes against nothing.
02The Five Real Causes
The five causes, and how each one shows up
Most manufacturers have two of these five at once, and they need different answers. Read the description and match it against what you saw last week:
Cause 01
Typing Costs More Than It Returns
Recording one interaction takes seven minutes because there are 23 required fields, four of which the rep cannot answer until the second call. The tell: cards get filled in bulk on Friday afternoon, all with the same wording. Recording has to cost under three minutes or it will always lose to a phone call.
Most Common
Cause 02
There Is No Written Sales Process
The stages in the system came from the vendor's default template, so nobody knows what has to be true for a card to advance. Two reps put the same deal in different stages and both are right. The tell: ask three reps what "negotiation" means and get three answers.
Structural
Cause 03
The System Gives Nothing Back
It is a reporting device pointed at the rep, not a tool that helps him sell. It does not remind him to follow up, does not show which buyer opened the quote, does not carry the technical drawing history. The tell: reps only open it on the day before the sales meeting.
Decisive
Cause 04
Commission Does Not Read the System
Pay is calculated from the ERP invoice, the meeting runs off a spreadsheet, and the card changes nothing about either. Whatever is not tied to money or to the Monday conversation stops being filled in within one quarter. The tell: the forecast in the system and the one the manager quotes to the board are different numbers.
Incentive
Cause 05
The Same Data, Typed Twice
Customer registration, price table and order status already live in the ERP. Asking the rep to retype any of it into a second screen guarantees one of the two goes stale, and it will be the one that does not issue invoices. The tell: company names spelled three different ways across the two systems.
Duplication
Cause 02 is the one that deserves a separate reading, because it is not really about the tool: a system on top of a sales operation with no written process only records disagreement faster. That argument is made in full in an industrial CRM without a process is an expensive spreadsheet.
03A One-Week Diagnosis
How to find out which cause is yours in five days
Every number below is already inside the account. None of it requires a survey, a consultant or a meeting — pull it yourself in an afternoon and the cause usually names itself:
Four Measurements, in Order
Measure 1: Next-Action Coverage
What share of open opportunities carries a next-action date in the future. Healthy is above 80%. Below 40% the pipeline is not being worked in the system at all, and every forecast built on it is fiction.
→
Measure 2: Update Lag
Median days between an interaction happening and it being recorded. Under one day is fine. If the distribution clusters on Fridays, you have Cause 01 — the cost of recording is too high and reps are batching it to survive.
→
Measure 3: Field Fill Rate
Percentage of records with each field filled. Any field under 30% is either useless or unanswerable at that stage — both mean delete it. Manufacturers routinely find they are requiring fields that only make sense after the plant visit.
Measure 4: the login question:
How many days in the last 30 each rep opened the system, and on which days. If access concentrates on the day before the sales meeting, the cause is 03 or 04 — the tool is a reporting obligation, not a work surface. If access is spread out but records are thin, the cause is 01 or 05.
Do the reading with the sales manager in the room and without naming individuals. The moment the exercise turns into a list of who filled in the least, you stop measuring the system and start measuring who is willing to look busy — and the numbers stop being usable for the rest of the year.
04What Does Not Fix It
Three things managers try first, and why they fail
These are worth naming because they consume a quarter each and leave the operation slightly worse than before — the team learns that the initiative passes if you wait it out.
Three Dead Ends
One More Training Session
Training solves not knowing how. None of the five causes is not knowing how — the reps understand the screen perfectly and have decided it is not worth the minutes. A second training session changes usage for about two weeks and then the arithmetic reasserts itself.
→
More Required Fields
Making fields mandatory does not produce data, it produces "a combinar" typed into eleven boxes. You end up with a full-looking database that cannot be segmented, which is worse than an honestly empty one because now the reports look credible.
→
Swapping the Tool
A migration costs three to six months and carries all five causes across intact, because none of them lives in the software. Change tools when the tool genuinely cannot do what the process needs — which, for a manufacturer with 40 inquiries a month, is almost never the case.
What does move the needle:
Cut recording to under three minutes, make the system return something the rep wants today, and put the Monday meeting inside the screen so the pipeline in the tool becomes the only pipeline that exists. The step-by-step version of that is a page of its own, because it is a change to the sales routine and not a configuration change.
The practical sequel to this diagnosis is how to make reps actually use the CRM. If your reading pointed at Cause 02, the stage definitions are in building the RD Station pipeline for a manufacturer. If it pointed at Cause 05, the account was probably never organized — start at organizing RD Station from scratch.
05FAQ
FAQ
Why does the sales team not use the CRM? +
For five measurable reasons: recording costs more minutes than it returns, there is no written process for the stages to reflect, the system gives nothing back that helps the rep sell, commission does not read what is in there, and the same data already lives in the ERP. It is arithmetic, not resistance to technology.
Is the sales rep sabotaging the CRM on purpose? +
Almost never. A rep with eleven live quotes chooses a four-minute call that might close this month over a seven-minute form that returns nothing today. That is a correct decision against the incentives he was given. Change the arithmetic and the behaviour changes; argue with the person and nothing does.
How do I know if the CRM is really abandoned? +
Measure what share of open opportunities carries a next-action date in the future. Above 80% is healthy; below 40% the pipeline is not being worked in the system and any forecast built on it is fiction. Then check the median lag between an interaction happening and being recorded — over three days means abandoned in practice.
Does more training make reps use the CRM? +
No, because none of the five causes is not knowing how. Reps understand the screen and have concluded it is not worth the minutes. A second training session lifts usage for about two weeks, then the same arithmetic takes over and the team learns that these initiatives pass if you wait them out.
Should I make more fields mandatory to force the data in? +
No. Mandatory fields produce filler text, not data — you get a database that looks full and cannot be segmented, which is worse than an honestly empty one because the reports now look credible. Go the other way: any field filled in under 30% of records should be deleted or moved to a later stage.
Will changing to another CRM solve it? +
A migration costs three to six months and carries all five causes across intact, because none of them lives in the software. Switch only when the tool genuinely cannot do what your process requires — for a manufacturer handling 40 inquiries a month, that is almost never the real constraint.
Does the sales rep need to use the CRM if the ERP already has everything? +
The ERP holds what already became an order; the CRM holds what has not become one yet — the eleven live quotes, who has not answered, what to do next. Both are needed, but never ask the rep to type the same record twice. Customer data should flow from the ERP, not be retyped.
How long does it take to get a sales team back into the CRM? +
Five days for the diagnosis and roughly 60 days to see next-action coverage move, provided you cut recording to under three minutes and run the Monday meeting inside the screen. Usage that returns only through pressure falls back within one quarter, so measure at day 90 rather than day 30.
Want to know which of the five causes is yours?
We run the four measurements on your own account, tell you which causes are active, and hand back the smallest change that moves next-action coverage — without a migration and without another training session.
