Why Your Team Doesn't Update the CRM: 5 Causes and Fixes for Small Sales Teams in 2027
Teams skip the CRM when it makes them retype what's in their inbox. Five causes, a day-by-day fix for each and what to do if it still isn't updated.
Contents8 sections
In 2019, BCG gave a name to salespeople who quietly stop logging their client interactions: "passive disobedience". The sellers it described saw the CRM's data rules as admin that took time from selling. When your sales team doesn't update the CRM, a stricter rule hands them more of that admin, so ask for less typing, give each seller something back and keep the rule for last.
This is for the owner who still sells, with up to five salespeople and a CRM where many deals have no next step. You'll find your cause and a one-day fix for it.
How we put this together. We read BCG's 2019 analysis, published sales surveys and official labour statistics between 15 and 19 November 2026; the causes, tests, fixes and monthly check are ours.
Why doesn't your team update the CRM? Remove before you enforce
Because updating it costs the seller more than it gives back. People skip a form that makes them retype their mailbox, asks for fields nobody reads and never comes up in a meeting. Remove before you enforce: find which of five causes you have, take out the retyping and extra fields, and add a rule only at the end.
We'd set a rule last, because it asks for more of the admin people already skip. BCG wrote in 2019, about large companies, that sales teams often see only a narrow part of what a CRM can do for them. Its advice: show salespeople the payoff, agree one sales process for the whole firm and audit the data regularly. The steps below do that for a small team.
| Step | When | What you do | What you get | Cost |
|---|---|---|---|---|
| 1 | Day 0 | Run five one-question tests | The cause you have | Free |
| 2 | Day 1 | Cut the retyping, fields and stages | A deal that saves in fewer steps | Free |
| 3 | Days 2 to 7 | Review from the CRM, one next step per deal | A record each seller uses | Free |
All three use the CRM you already have, so they cost nothing but the owner's time.
See Saga, the CRM that comes with HAL, gethal.ai's AI sales agent, fill each account's timeline on its own. See the timeline fill
Step 1, day 0: which of the five causes is yours?
Run five one-question tests, one per cause, before you change anything. Each cause has a sentence you'll hear from the team and a question you answer by opening a few records. With more than one hit, start with the cause highest in the table: the order runs from the cheapest fix to the dearest.
| Cause | What you hear | The one-question test | It's this cause if |
|---|---|---|---|
| 1. Retyping | "It's all in my email anyway." | Does logging a call or email mean typing what's already in a mailbox or calendar? | Yes |
| 2. Too many fields | "I'll put it in on Friday." | Can a seller save a new deal with only a company, a contact and a next step? | No |
| 3. Nothing in it for the seller | "The CRM is for the boss." | What does a seller get from the CRM on Monday that their inbox doesn't give them? | Nothing |
| 4. Nobody reads it | "Nobody looks at it anyway." | Did your last pipeline review run from the CRM screen? | No |
| 5. No shared stages or next step | "Where do I put a deal that's gone quiet?" | Would two sellers put the same deal in the same stage, with a dated next step? | No |
Run the tests yourself on five open deals, then put the same questions to the team at the next sales meeting. The seller who skips the form knows which part they skip.
Watch for side spreadsheets too. If a seller keeps their own list of deals, ask what it holds that the CRM doesn't. BCG warned that when a few reps work around the CRM with spreadsheets, others may follow, so ask about the first one.
Step 2, day 1: what can you cut?
Cut anything a seller types that the CRM could fill in itself, every required field nobody read last month, and any stage that doesn't change what the seller does next. A day in the CRM's settings is enough. Make a field optional before you delete it, so nothing is lost while you find out who needs it.
Stop the retyping first. Our research into published surveys found that 38% of 1,000 US sales and marketing professionals, asked in June 2026, say most of their time goes on logging calls, emails and meetings (self-reported, US only). If your CRM can connect to the mailbox and calendar, connect them, and drop any rule to log emails or meetings by hand. Our article on time spent updating the CRM prices what's left, using Eurostat's 2025 EU average labour cost of €34.9 an hour (all jobs, firms with 10 or more staff).
Cut the fields nobody reads. List every required field on a deal and a contact, and write beside each who read it last month. A field with no name beside it becomes optional today and goes at the monthly check if it's still empty.
Merge stages that lead to the same next action. A stage earns its place when it changes what the seller does next: send a proposal, book a demo, chase a signature. Write one line per stage saying when a deal enters it.
Use HAL when you'd rather nobody typed it: in Saga, the CRM, every email, reply and meeting lands in the account's timeline on its own, and a reply or booked meeting moves the deal on the board.
Step 3, days 2 to 7: how do you make the record pay the seller back?
Use the CRM where the seller needs it. Run the weekly pipeline review from the CRM screen, and give every open deal one next step with a date and an owner. The record then becomes the seller's call list and their notes for the meeting, so what they type on Tuesday is what they use the next Monday.
Run the review from the screen. Open the deal board at the weekly sales meeting and go through it deal by deal. When a seller talks about a deal that isn't on the board, add it there and then, together.
Give each deal one next step. An action, a date and the person who does it, written so a colleague could do it: "call Anna on Thursday about the price for 200 units" (an invented example), where "follow up" would leave them guessing. On Monday, each seller filters the CRM by their own next steps and has the week's list.
Show each seller what they get. Say it once, at the meeting: the CRM keeps each buyer's last email beside the deal, and puts the week's calls in one list. The owner's weekly counts come from the same records, and the free outbound scorecard (Excel) turns them into rates.
What if the team still doesn't update it?
Escalate in four stages, each a little firmer: ask again, remove another field, automate the logging, and only then set one rule. Give each stage a week and run the five tests again before moving on. Stage 1 finds the reason the first tests missed.
Stage 1: ask each seller what they skip
Sit with each seller for ten minutes, ask which entry they skip and why, and match their words to the causes table. "The phone app takes too long" points to cause 2; "we never look at it" points to cause 4.
Stage 2: remove one more field
Take out the field they named, or make it optional for a month. If nobody misses it, it stays out.
Stage 3: automate the logging
Let the CRM record emails, replies and meetings itself, as a self-updating CRM does. For what only the seller knows after a call, updating the CRM by chat turns one sentence into a contact and a dated call.
Stage 4: set one rule
Make it about what you read: a deal without a dated next step isn't discussed at the weekly review, so its seller adds the step before the meeting. Check it at every review.
Watch a reply or a booked meeting move a deal along the board in Saga, with nobody dragging the card. Watch a deal move
Which fix suits which cause?
Match the fix to the cause your test found. Cutting fields and stages is free and deals with causes 2 and 5. Automatic capture and chat updates take the retyping away. The pipeline review and one next step per deal make the record useful to the seller. A rule comes last, for whatever is still missing.
| Fix | Causes it fixes | What it takes | What the seller notices |
|---|---|---|---|
| Cut fields and stages | 2, 5 | A day in the settings | Fewer steps to save a deal |
| Automatic capture | 1 | A CRM that records emails and meetings, or a mailbox connection | Nothing to retype |
| Updates by chat | 1, 2 | A CRM with a chat that writes records | One sentence instead of a form |
| Pipeline review from the CRM | 3, 4 | The weekly meeting you already hold | Their deals discussed from their records |
| One next step per deal | 3, 5 | A required, dated next-step field | A call list every Monday |
| One rule | Whatever is left | The owner checking it weekly | One task before the meeting |
Start at the top. Automatic capture is the only fix that removes the typing rather than shortening it, which is why it comes before a rule.
How do you keep it updated next quarter?
Run a ten-minute check on the first Monday of each month. Open five deals, see whether their last email and next step are there, ask about side spreadsheets, look for contacts who changed jobs, and remove any field that stayed empty. It is BCG's regular data audit, at the scale of five deals and ten minutes.
- Minutes 0 to 3, five open deals. Pick five at random. Each should have a next step dated in the future.
- Minutes 3 to 5, the last email. Check that the last email or meeting with each buyer is in the timeline.
- Minutes 5 to 7, side spreadsheets. Ask whether anyone keeps deals anywhere else. A yes sends you back to step 1.
- Minutes 7 to 9, people who moved. Check that each main contact is still in that job. Eurostat counted 12.7% of employed people aged 20 to 64 in the EU in a job held 12 months or less in 2025, and the BLS put 20.6% of US wage and salary workers with their employer a year or less in January 2026. Both count every job, people new to work included, so they're a rough sign of how often contacts move, not a figure about the buyers in your CRM.
- Minutes 9 to 10, empty fields. Any optional field still empty after a month goes.
See Saga's Focus page list today's past-due activities and stalled deals before your monthly check starts. See the Focus page
Who this is for
- The owner who still sells: you run the sales meeting, so the review from the screen in step 3 and the monthly check are yours. Start both the week you run the tests.
- The salesperson next to the owner: you do most of the typing, so the step 1 tests and stage 1 are where you say which fields to cut and which entries you skip.
- Whoever set up the CRM: the fields and stages you added are the ones step 2 asks about. Keep those someone reads.
If two or three people share one CRM, run step 1 together, so everyone answers the same five questions.
FAQ
How do you get salespeople to update the CRM?
Make it cost them less typing and give them something back. Cut fields to the few someone reads, let emails and meetings land in the CRM on their own, and review the pipeline from the CRM screen. Add a rule only if those fail.
Why don't sales reps use the CRM?
Because it costs them more than it gives. BCG wrote in 2019 that salespeople who see data rules as extra admin may skip logging, which it called "passive disobedience".
What are the common CRM adoption problems in a small business?
Five: retyping what's already in the mailbox, too many required fields, nothing in it for the seller, nobody reading it, and no shared stages or next step. Each has a one-question test.
What do you do when the sales team won't log activities in the CRM?
Stop asking them to log what the CRM can capture: connect the mailbox and calendar, or use a CRM that records emails, replies and meetings on its own. Then ask each seller what they still skip and remove it.
Why is my CRM data incomplete?
Something in it costs the team more than it gives. Check five open deals: a missing last email points to retyping, empty fields to too many fields, and missing next steps to a review that isn't run from the CRM.
How do you make a CRM easier for salespeople?
Remove before you enforce: cut every field nobody read last month, merge stages that lead to the same next action, and let the CRM fill in emails and meetings itself. For the rest, a chat replaces the form.
Run the five tests before your next sales meeting
Open five deals, ask the five questions and fix the top cause this week. To see a CRM that fills its own timeline, book a demo. Saga is included with HAL, so HAL's prices cover it.
Keep reading: What is a self-updating CRM · How much time updating the CRM takes · How to update your CRM by chat


