CRM adoption is the share of your sales team that records contacts, deals and next steps in the shared system as part of normal work, and it rises when the system saves reps effort instead of adding to it. Choosing the platform comes first, as the CRM software in South Africa guide explains; this post covers the harder part, which starts once the licence is paid and half the team is still running deals from a notebook.

The CRM adoption statistics post covers the numbers. This one is the playbook: a diagnosis table that separates the reasons reps skip the system, a field audit that cuts what they are asked to type, and a four-week schedule to make the new habit stick.

Quick Answer

To improve CRM adoption, find out why reps skip the system before you retrain anyone. The usual causes are too many mandatory fields, no payoff for the rep, a manager who still runs meetings from a spreadsheet, slow mobile use at client sites, and old habits nobody has reinforced. Cut every field that no report, automation or decision uses, run the weekly pipeline meeting from the system itself, and make the old spreadsheet read-only.

Reps ignoring the system you paid for?

Send us how your team records deals today and we will show you which steps are costing reps time for no return.

Request a free audit

CRM Adoption Is a Workload Problem Before It Is a Training Problem

CRM adoption stalls when keeping the system current costs a rep more time than it gives back. Salesforce's research gives context for the pressure: its sales survey, published in December 2022 with 7,775 responses, reported that reps spend just 28% of their week actually selling, with the majority of their time consumed by other tasks such as deal management and data entry.

It is a CRM vendor's global survey of sales professionals in 38 countries, not a South African measure, and it does not say how much of that time goes on updating a CRM or whether reps resist it. It shows how little selling time there is to spare.

Read that figure from the rep's side. A salesperson who sells for a little over a quarter of the week has good reason to treat every extra field as a tax on the part of the job that earns commission. If the tax is visible and the benefit goes to someone else, the rational response is to skip it or batch it on Friday afternoon, when the details are half-remembered.

That is why a training session on its own rarely fixes the problem. Training answers "how do I use this?", and most reps already know. The question they are actually asking is "what do I get for it?", and the answer has to come from how the system is configured and how managers use it.

Start with the workload, not the lecture

Low CRM adoption usually means the system asks for more effort than it returns to the person typing. Before scheduling more training, measure what each rep is asked to enter, and ask what they get back for it. Training fixes a knowledge gap; it does not fix a bad trade.

Why Do Reps Quietly Stop Updating the System?

Reps stop updating the system for several different reasons that look identical from a dashboard: stale deals, empty fields and a pipeline nobody trusts. Treat the symptom as a set of competing hypotheses and run the check that separates them, because the fix for a workload problem (cut fields) is the opposite of the fix for a knowledge problem (teach more).

SymptomPossible causesCheck that tells them apartBest for
Deals sit in the same stage for weeksReps are updating elsewhere (WhatsApp, a notebook); stage definitions are unclear; deals are genuinely stalledAsk two reps about three deals each and compare their answers to what the system showsTelling stale data from a stalled pipeline
Mandatory fields filled with placeholdersToo many required fields; the field means nothing to the rep; the required value is not known at that stageList the fields with the most placeholder values and ask whether anyone reads themTargeting the field audit
Records updated in bursts before the weekly meetingThe meeting is the only reason to update; entry is slow; reps see it as reporting upwardCheck record timestamps against the meeting calendarDeciding whether to change the meeting or the screens
Only some reps use itDifferent workloads or lead sources; a manager who exempts favourites; the tool fits one role and not anotherCompare the reps who do use it with the rest: lead source, territory, tenure, deviceSpotting a design problem versus a discipline problem
Usage drops after launch monthNo reinforcement; the spreadsheet still works; the novelty has worn offLook at the week-by-week activity trend and ask whether the old tracker is still circulatingSeparating launch fatigue from a flawed setup
Field reps update late or not at allPoor mobile signal; slow mobile screens; load-shedding; mobile data costHave a rep log a visit on their phone at a typical client site, then time itSouth African field and branch teams

The check is the point of the table. Two of these causes can sit behind one symptom, and one conversation with a rep can settle the question before anyone builds a new workflow. Where deals are negotiated in chat threads, part of the answer is connecting the channels: the WhatsApp CRM integration post covers how conversations can reach the record without retyping.

How Many Fields Should a Rep Have to Fill In?

A mandatory field earns its place only if you can name the report, automation or decision that uses it, so the right number of required fields is the number that survives that test. Every field with no named consumer is a toll that the rep pays and nobody collects.

Run the audit in an afternoon, with the sales manager and one or two of the reps who use the system the most:

Keep: "Lead source". It feeds the monthly report on which channel produces deals, and the owner reads that report when deciding where to spend.

Keep: "Next step and date". It drives the follow-up task and the weekly pipeline review, and a deal without it cannot be managed.

Cut or make optional: a detailed "Industry" picker nobody segments by. If no report or campaign uses it, it is a placeholder waiting to happen.

Cut or move: a field that can only be completed after the deal closes, but is marked required at the first stage. Make it required at the stage where the rep actually knows the answer.

Naming matters as much as count. Fields that are labelled differently from how reps talk invite wrong entries, so settle the labels using the CRM field naming convention. For the properties a deal genuinely needs before it moves a stage, the required deal properties post shows how to stage the requirement rather than front-loading it. It is written for HubSpot, but the staging principle applies on any platform.

The consumer test, step by step

For each required field, write its name and then complete one sentence: "This is used by ___ to ___." If you cannot finish the sentence, the field becomes optional or is removed. If someone can finish it, ask when the rep first knows the answer, and require it from that stage and no earlier. Re-run the test every quarter, because fields collect faster than they are retired.

Every field needs a consumer

A required CRM field is justified only when a named report, automation or decision uses it. Cut fields with no consumer, and require the rest at the stage where the rep first knows the answer. Fewer, better-timed fields raise data quality because reps stop typing placeholders.

What Should Managers Do So the Data Actually Gets Used?

The fastest way to raise CRM user adoption is for the manager to run every pipeline conversation from the system and refuse to accept the same information any other way. Reps update what gets inspected. If the weekly meeting runs from a spreadsheet or a verbal round-robin, the system becomes a second job with no audience.

Four manager habits do most of the work:

  • Open the pipeline view, not a slide deck. Run the meeting from the live board, deal by deal, so an out-of-date record is visible to everyone in the room.
  • Stop accepting parallel trackers. Once the field audit is done, make the old spreadsheet read-only. Keeping both alive guarantees the less useful one wins.
  • Give back before you ask. Build one view per rep that shows their own follow-ups due today, so the first thing they see is help, not a compliance form. The CRM reporting for sales teams post covers the reports worth building first.
  • Decide what counts. Some businesses tie commission or recognition to deals that exist in the system. That is a policy choice with trade-offs for morale, so make it deliberately and announce it in advance, not after the fact.

The reverse also applies: if the system is used mainly to police activity, reps will feed it the minimum. Introduce it as the place where their pipeline, follow-ups and handovers live, and use the data in meetings to unblock deals, not to audit effort.

A shared record also protects the team when a rep is on leave or leaves, because the next person can pick up the account. A move away from spreadsheets makes that argument concrete, and the CRM versus spreadsheet comparison sets out when the switch pays for itself.

Use the system or lose the meeting

The best lever a manager has is to run the pipeline meeting from the live system and retire the parallel spreadsheet. Reps keep records current when the record is what gets inspected, and when the first thing they see in the morning is their own follow-ups, not a report for head office.

Not sure which fields and reports to keep?

Send us your current pipeline stages and required fields and we will mark which ones look like extra work for reps and which ones earn their place.

Book a free consultation

Which Change Steps Make a New Sales Habit Stick?

A new sales habit sticks when each person understands why, wants to change, knows how, can do it in practice, and has it reinforced afterwards. That sequence is the ADKAR model, developed by Prosci founder Jeff Hiatt, and it is a useful checklist for any CRM adoption strategy because it separates problems that need persuasion from problems that need practice.

Prosci's own description frames Awareness as ensuring team members understand the need for change, Knowledge as providing training and support, and Reinforcement as maintaining the change over time and preventing a return to the old ways. The mapping below is our reading of how those stages apply to a sales team, not a Prosci finding.

ADKAR stageWhat it looks like in a sales teamA practical moveBest for
AwarenessReps know why the business needs one shared recordShow a lost deal or missed follow-up that a shared record would have caughtTeams that see the system as head-office admin
DesireReps want it because it helps them, not just managementBuild the rep's own follow-up view first; involve two or three respected reps in the field auditReps who feel monitored
KnowledgeReps know how to log a call, move a deal and set the next stepShort, role-based walkthroughs on real deals, not a feature tourNew hires and mixed-ability teams
AbilityReps can do it quickly in their real working conditionsTime the common tasks; fix slow screens; test on mobile at a real siteField reps and branch teams
ReinforcementThe habit survives the first busy monthRun meetings from the system; retire the old tracker; review fields quarterlyManagers after launch

Most struggling rollouts have invested in Knowledge (a training day) and skipped Desire and Reinforcement. If your reps know how but do not, the gap is probably in the stages that training does not touch.

What Does a Four-Week CRM Adoption Plan Look Like?

A CRM adoption plan can be run as four weekly steps: cut, rebuild, move the meeting, retire the old tracker. The weeks below are a working schedule that suits a small team, not a researched benchmark, so stretch it if your team is larger or spread across branches.

WeekStepOutputBest for
Week 1Run the field audit and the diagnosis checksA shorter required-field list and a note of the likely causes of non-useUse first, before touching any configuration
Week 2Rebuild stages and views with a pair of willing repsA personal "today" view per rep and one manager reportUse when you need proof it helps before asking everyone to change
Week 3Move the pipeline meeting into the system and train on real dealsMeeting run from the live board, with short role-based walkthroughsUse once the pilot reps are logging reliably
Week 4Make the old tracker read-only; review what reps still work aroundOne source of truth and a list of remaining frictionUse only after reps have a better way to work than the old tracker

Measure the plan with your own yardstick, set before you start: for example, the share of open deals with a next step and a date recorded. A measure you define yourself, applied to your own pipeline, tells you more than a borrowed benchmark. If duplicate or messy records are what reps complain about, fix those early using the duplicate contact clean-up guide, because nobody trusts a system full of double entries.

Does Data Safety Change How You Introduce the System?

Customer contact details held only in personal phones, private chats and individual spreadsheets are a foreseeable risk that a business has to account for under POPIA, and a shared system with controlled access is one way to answer it, so data safety gives you a second reason to introduce the system. Section 19 of the Act requires a responsible party to take appropriate, reasonable technical and organisational measures to prevent loss of personal information and unlawful access to it, and to identify the reasonably foreseeable internal and external risks.

The section does not name a CRM or any other tool, so a CRM does not make a business compliant by itself, and what counts as reasonable is a judgement. It does give you an honest reason, beyond management convenience, for reps to keep contacts in one controlled place: when a rep leaves, the customer data stays with the business.

Pair that with a short set of access rules, as set out in the CRM data governance checklist. This is not legal advice.

Be direct with the team about what the data will and will not be used for. Reps who suspect that every keystroke feeds a performance review will enter the minimum. Say what the system is for, what managers will look at in meetings, and what is not being tracked.

Want a second opinion on your rollout?

Send us your adoption plan and we will audit the sequence and flag where it is likely to stall. No obligation.

Request a free audit

Why South African Businesses Choose Growth Pulse Media

Growth Pulse Media is a Johannesburg-based agency founded by Dirk van Greuning, who built and scaled a large South African ecommerce business first, so the test applied throughout this post, whether a step earns the time it costs, is a commercial one. All work is executed in-house, with a limited client load for senior attention. Our digital strategy service is where the wider question sits: which pipeline and revenue numbers the business should steer by, and which channels feed them. A free consultation is available with no obligation.

Who This Is NOT For

This playbook is the wrong starting point for solo owner-operators, leaders who want mainly to monitor reps, teams with no agreed sales stages, and anyone hoping a platform swap alone will fix adoption.

Owner-operators selling alone. If you are the only person using the system, the problem is habit, not buy-in. A weekly review of your own pipeline will do more than a change programme.

Leaders who want the system mainly to monitor reps. Surveillance as the primary purpose is the quickest route to minimal, defensive data entry. This playbook assumes the rep gets something back.

Teams with no agreed sales stages. If nobody can say what separates a lead from a qualified deal, no configuration will help. Define the stages first, then return to the field audit.

Anyone planning to swap platforms to fix adoption. A new tool with the same required fields and the same spreadsheet-driven meeting recreates the same problem. Fix the process first and compare tools afterwards.

Frequently Asked Questions

How do you get your team to use the CRM?

Get your team to use the CRM by making it save them effort: cut the required fields to those a report or automation uses, give each rep a personal follow-up view, and run the weekly pipeline meeting from the live system. Then retire any parallel spreadsheet so there is one place where deals live.

Why do salespeople resist using a CRM?

Salespeople resist a CRM when it costs time they would otherwise spend selling and the benefit goes to management instead. Salesforce's survey, published in 2022, reported reps selling for 28% of their week, which shows how little selling time there is to spare, though it does not measure CRM entry itself. Check whether the cause is workload, unclear value, slow mobile use or lack of reinforcement before you decide on a fix.

How long does CRM adoption take?

There is no reliable universal figure for how long CRM adoption takes, because it depends on team size, the process and how many fields reps must complete. A small team can run a four-week working schedule: audit, rebuild, move the meeting, retire the old tracker. Set your own measure first, such as the share of open deals with a next step and a date.

Should commission depend on logging deals in the CRM?

It can, but it is a policy choice with trade-offs rather than a rule. Tying commission to deals that exist in the system gives reps a strong reason to log them, and it can feel punitive if the system is slow or the fields are excessive. Fix the workload first, announce the rule in advance, and apply it to everyone.

Does a CRM help with POPIA compliance?

A CRM does not make a business POPIA compliant on its own. Section 19 requires reasonable technical and organisational measures and a view of foreseeable internal and external risks, and it names no specific tool. A shared system with access controls is one way to reduce the risk of customer data living only on personal devices. This is not legal advice.

Get the system your team will actually open

Send us your current stages, required fields and weekly pipeline routine, and we will show you where reps are losing time and what to change first. No obligation — we'll get back to you within 24 hours.

Contact Growth Pulse Media

Dirk van Greuning — Founder, Growth Pulse Media
Dirk van Greuning Founder, Growth Pulse Media

Founder of Growth Pulse Media and a specialist in South African search dominance. Dirk translates his experience in scaling South African businesses into high-velocity digital strategies for B2B and retail leaders. He writes about SEO, lead generation, and paid media from an operator's perspective — prioritising pipeline value over impressions.

Connect on LinkedIn