What is CRM support and training?
CRM support and training for SMEs is the work that happens around the software: mapping how your business operates, configuring the platform to match it, migrating and cleaning your data, teaching your team on real scenarios rather than a demo account, and staying reachable once it goes live. It’s the difference between owning a CRM licence and running a CRM.
We’ve been putting CRMs into UK small businesses for years, and the pattern barely changes. The firms that get value out of one are rarely the firms that picked the cleverest platform. They’re the ones who treated the rollout as a project with an owner, instead of a purchase with a login.
If you’re still deciding which platform to use, read how to choose a CRM first. This guide is for businesses that have already picked one, or are close to it.
Contents
- Why do CRM projects fail?
- What does CRM support actually include?
- What does a CRM implementation involve?
- How much does CRM training and support cost?
- Common mistakes to avoid
- Five questions to ask a CRM consultant
- TL;DR
Why do CRM projects fail?
CRM projects fail on adoption, not on software. The failure rate is high at every business size, but it lands hardest on SMEs because there’s rarely a dedicated IT person to own the rollout, and rarely anyone whose job it is to notice when the team quietly goes back to the spreadsheet.
Johnny Grow’s research puts the CRM failure rate at 55 percent, measured as deployments that didn’t achieve their planned objectives. The same report found budget overruns in roughly two-thirds of projects, with a median overrun between 30 and 49 percent. Those are enterprise-weighted numbers, but the causes are identical at ten people.
Four causes come up again and again: the CRM was configured around vendor defaults rather than the business’s real process; data was imported once and never cleaned, so staff kept trusting the old spreadsheet; training was one webinar with no hands-on practice; and nobody was named as the internal CRM owner after go-live. Every one of those is preventable, and none of them is a software problem.
What does CRM support actually include?
Proper CRM support covers six connected pieces of work: an initial health check, discovery and process mapping, configuration, data migration, user training, and go-live support. Vendor onboarding packages typically deliver two or three of them, which is the gap most small businesses discover about a month in.
Initial health check. Before committing to a new platform or a major reconfiguration, a good consultant assesses what you already have. Is your current system salvageable with better configuration, or would a fresh start serve you better? A consultant who never answers “keep what you have” is selling rather than assessing.
Discovery and process mapping. Mapping your existing sales or client management process before any configuration happens. This is the step vendors skip, and skipping it is how you end up with generic pipelines that don’t reflect how the business works.
CRM configuration. Setting up pipelines, custom fields, tags, user roles and permissions, and views, so the CRM matches the process you mapped.
Data migration. Moving contacts, companies, and history across from spreadsheets or a previous CRM. Done badly it produces duplicates, missing history, and a team that doesn’t trust the data. Done well it gives you a clean foundation.
User training. Hands-on sessions using your actual data, your actual pipelines, and the situations your team meets daily. The test is whether staff can finish their normal work in the CRM afterwards without reaching for a manual.
Go-live support. The first fortnight after launch decides whether adoption holds. A support window over that period catches problems before habits form around them.
What does a CRM implementation involve?
A CRM implementation runs from health check to go-live in a fixed sequence, and the order matters more than the pace. Configuring before discovery is the most common way to end up rebuilding, because every field you create is a guess until someone has mapped the process it serves.
Most of our small business rollouts follow the same seven steps.
A typical small business CRM implementation
Initial health check
We assess what you already have before recommending a change. If switching is the right call, we identify which data is worth bringing across so the history isn't lost.
Discovery and process mapping
We map your current sales or client management process, identify the data points you track day to day, and agree the pipeline stages and custom fields the CRM needs to reflect. Usually one or two sessions.
CRM configuration
We configure the platform to the agreed process: pipelines, fields, tags, and user permissions. Then we connect and test the integrations with your email, calendar, or accounting tools.
Data migration and cleaning
We import, deduplicate, and tag your existing contacts and companies, flagging gaps before they enter the system. You send the export; we hand back a clean import ready to upload.
Staff training
Hands-on sessions in your live CRM, using your data and your team's daily tasks, never a generic demo. Usually 90 minutes to half a day depending on team size and complexity.
Go-live and early support
The CRM goes live and we watch for adoption problems over the first fortnight, handling the configuration adjustments that only surface under real use.
Ongoing check-in (optional)
Monthly or quarterly, depending on how fast the business is changing. Covers configuration updates, new user onboarding, and any reporting or automation you want to add later.
Discovery through go-live typically takes one to four weeks for a team of 5 to 15, and data complexity moves that number far more than headcount does. A clean 2,000-row spreadsheet imports in an afternoon; three overlapping exports with inconsistent company names can absorb several days on their own. For a worked example at this scale, the training operations case study shows an international training organisation moving off spreadsheets and a legacy CRM in a single project.
How much does CRM training and support cost?
Standalone CRM training costs around £150 a session for a UK small business, covering one new user or a refresher for a small group. Ongoing support retainers typically cost £150 to £400 a month, scaling with how much configuration change the business generates, not headcount.
| Support type | Typical cost range | What you get |
|---|---|---|
| Ongoing support retainer | £150-400 per month | Configuration updates, user support, reporting changes |
| Additional training session | £150 per session | One new user, or a refresher for a small group |
These are UK market rates at the time of writing, for a team of roughly 5 to 15 people on a mainstream small business CRM. In a consultant-led project, training is normally bundled into the project fee rather than billed separately, so a quote that itemises it is worth querying.
What changes the outcome is whether training uses your data or a demo account. Sessions built on your live pipelines and your own records cost the same to deliver and produce a completely different adoption rate. A generic product walkthrough is cheap because the same session works for every client.
Setting the CRM up in the first place is priced as a project rather than a session, and what implementation costs at UK SME scale is a separate question from what support costs afterwards. The software licence is separate again: our CRM pricing breakdown covers what the subscription itself costs across the UK market. If you’re weighing up HubSpot specifically, what UK SMEs actually pay for HubSpot sets out the tier structure and the onboarding fees.
Common mistakes to avoid
These are the patterns we meet most often in small businesses that come to us after a first CRM attempt didn’t work out. All five are cheap to avoid in advance and expensive to unpick afterwards.
Buying the licence, skipping the setup. Signing up and expecting staff to work it out from tutorials. Fine for one person. It rarely survives a team.
Importing dirty data. Migrating contacts straight from a spreadsheet with no deduplication or tagging. The CRM inherits every problem the spreadsheet had, and the team notices almost immediately.
Training too early. If you train before the CRM is configured for your process, staff learn a version of the tool that doesn’t match what they’ll use day to day.
No internal owner. Nobody is named as responsible for the CRM at launch, so when the questions come there’s nobody to ask.
Treating go-live as the finish line. Stopping support the moment the CRM launches. The first four weeks of real use are where adoption either sticks or collapses.
Five questions to ask a CRM consultant
Ask these five before you sign anything. The answers tell you quickly whether a consultant works from your process or from a template.
1. Do you start with a discovery session, or with configuration? Going straight to configuration generally means working from a generic template. Discovery comes first for us, every time.
2. What does your training involve? Product walkthroughs aren’t training. Ask whether sessions are tailored to your use case, and optionally use your actual data and your actual pipelines. If the answer is no, it’s less likely to stick.
3. What happens after go-live? Find out whether a support window is included in the project, and what ongoing options look like afterwards. For most teams that window isn’t optional, but it does come at a cost.
4. Can you walk through a data migration you’ve run? Data migration is a specialist skill. Ask for a worked example, or a reference from a client whose migration they handled.
5. Have you worked with businesses similar to ours? Sector matters less than business model and team size. Setting up a five-person professional services firm is a different job from a 20-person e-commerce operation, so check the reference points are relevant.
Running this sequence for clients is what our CRM setup, migration and training work covers day to day, and the questions above are the ones we’d want asked of us.
TL;DR
- CRM projects fail on adoption, not software. Johnny Grow puts the failure rate at 55 percent of deployments that missed their objectives, with budget overruns in two-thirds of projects.
- Proper CRM support and training covers six things: health check, discovery, configuration, data migration, hands-on training, and a go-live support window. Vendor onboarding packages usually cover two or three.
- Standalone training costs around £150 a session and ongoing retainers £150 to £400 a month. Setup itself is priced as a project, and the software licence is separate again.
- Training built on your own data rather than a demo account costs the same to deliver and produces a completely different adoption rate.
- Avoid the five common mistakes: skipping setup, importing dirty data, training too early, naming no internal owner, and treating go-live as the finish line.
- Ask five questions before hiring: discovery process, training method, post-go-live support, migration experience, and relevant client references.
Is your team using the CRM you already pay for?
If your CRM went in without proper training, or the team has drifted back to spreadsheets since launch, that’s usually fixable without changing platform. Tell us what’s happening and we’ll say honestly whether it needs reconfiguring, retraining, or leaving alone.