CRM implementation: stages, cost, and why half of them fail to stick
A CRM is bought to stop losing enquiries and to see what is happening in sales. Buying it is the easy part. The real work starts after: mapping the process, migrating data, training people, and getting them to actually run deals in the system rather than in a parallel notebook.
Three options to choose between
An off-the-shelf CRM with basic configuration. Take a ready system, set up the pipeline and fields, connect email and telephony. Fast and cheap, but you live inside the vendor's logic.
Off-the-shelf with deep customisation. The same plus custom modules, integrations and automation for your process. More flexible, but you are tied to the platform and its updates, and customisations sometimes break on upgrade.
A custom system. Needed when the process fundamentally does not fit standard pipelines: complex calculations, unusual roles, industry specifics, integrations nobody offers.
Start the custom CRM conversation only after establishing that a ready product will not do. It costs more and takes longer, and only wins where the process really is non-standard.
Implementation stages
The order this normally happens in:
- Describe the sales process as it is: stages, who does what, where enquiries are lost.
- Decide what to change in the process and what to carry over. Automating a mess is pointless.
- Configure the pipeline, fields, permissions and roles.
- Connect enquiry sources: website, email, telephony, messengers, ads.
- Migrate customer and deal data.
- Train the team and write down the rules of use.
- Adjust based on actual use — the first weeks always reveal mismatches.
What the cost includes besides licences
Licences are usually the smaller part. The rest gets forgotten:
- Mapping the process and designing the pipeline.
- Integrations: telephony, email, website, accounting, messengers. Each counted separately.
- Data migration. If current data lives in scattered, incomplete spreadsheets, this is the heaviest part.
- Training and written guidance for staff.
- Support through the first months: adjustments based on real use.
- Monthly per-user fees, which grow with the team.
Why implementations fail to stick
The most common cause of failure is not technical. Salespeople go back to spreadsheets because the CRM became extra work rather than help.
The usual roots:
- Too many required fields: filling in a deal takes longer than making the sale.
- The system was rolled out without the people who use it and does not match the real process.
- The manager reads reports but never opens the system — so nobody else has to either.
- Data was migrated partially, leaving some customers in old spreadsheets. Now people check two places.
- Nobody owns the system after go-live.
A practical test: ask a salesperson to run a deal through the new system while you time it. If it takes longer than before, the rollout will not stick however well configured it is.
Where to start so you do not redo it
Start with one pipeline and a minimal set of fields. Adding a field later is easy; removing one already filled in is not.
Connect enquiry sources first: that produces the fast visible effect and explains to the team why this was done at all. Reports and automation come later, once real data is in the system.
And assign an owner before go-live. A CRM without one drifts from the process within months.
How to tell it worked
Not by how many modules are configured but by three things: every enquiry lands in the system automatically, salespeople run deals there without reminders, and the manager makes decisions from CRM reports rather than verbal updates.
If any one of those is missing, the implementation is not finished, however many features are switched on.
Questions people ask
How much does CRM implementation cost?
Licences are usually the smaller part. The bulk is process mapping, integrations with telephony, email and accounting, data migration, training and first-months support. Price depends mostly on integration count and the state of your current data.
How long does CRM implementation take?
Basic configuration of one pipeline with enquiry sources is quick. Data migration and post-launch adjustments take longest — and are most often underestimated.
Off-the-shelf CRM or custom?
Off-the-shelf suits a near-standard sales process. Custom is justified by unusual calculations, industry specifics or integrations platforms do not offer. Start by checking whether a ready product suffices.
Can data be migrated from spreadsheets and an old CRM?
Yes, it is a standard part of the project. Difficulty depends on how cleanly current data is filled in: incomplete and duplicated records cost more to move than tidy ones.
Why do staff avoid using the CRM?
Usually because working in it costs more time than it saves: too many required fields, a process that does not match reality, partially migrated data. The fix is simplification, not supervision.
