How to Choose a CRM - A Comprehensive guide for small business
Up to 70% of CRM rollouts fail to deliver what was promised.
I’ve sat across the table from enough businesses to know the real cause: nobody worked out what they actually needed before they bought anything.
If you’re running a business with 5 to 50 staff, you’ve probably had this conversation. Someone says “we need a CRM.” Everyone nods. A salesperson demos something shiny. Six months later half the team is still working off a spreadsheet because the new system was too fiddly to bother with. I see this constantly on Full Systems Audits, and when we break things down it becomes clear that the tool you chose is almost never the problem. The decision process that got you there is to blame.
The post below explains the exact framework I use with clients. Getting the cost, requirements, and simplicity right, and the specific platform you pick actually matters much much less than the sales pages would have you think.
Why most CRM choices go wrong first
Gartner puts CRM implementation failure at around 50%. Forbes puts it higher, in the 55 to 75% range. Whichever number you trust, the pattern behind it is consistent: over 60% of failures come down to people, not technology. Poor adoption is the single biggest cause. Only 6 to 10% of failures are genuinely down to a technical problem with the software itself.
Gartner puts CRM implementation failure at around 50%.
Forbes puts it higher, in the 55 to 75% range.
Over 60% of failures come down to people, not technology.
Only 6 to 10% of failures are with the software itself.
Translate that into plain English: your team decides in the first two weeks whether they’re going to use the new system properly or quietly keep their own workaround running alongside it. If the CRM is harder than the habit it’s replacing, they’ll use the habit. Every time.
That’s why simplicity sits in this framework as a first-class criterion, not an afterthought. A CRM with every feature under the sun is worthless if your sales team never opens it.
1. Cost: look at the total, not the sticker price
List prices for UK CRMs run from around £7 per user per month at the cheap end (Freshsales) up past £140 for Salesforce Enterprise. Zoho’s standard plan sits around £12. Microsoft Dynamics 365 is closer to £80 a user. On paper, that looks like a simple decision between a £10 tool and a £100 tool.
It isn’t. The subscription is the smallest number in the whole exercise. Budget two to three times the annual subscription cost for implementation, data migration, integrations and training in year one. A CRM priced at £30 a month can easily cost £2,000 or more once it’s actually set up and your team is trained on it. We’ve seen businesses pick the “cheap” option and end up spending more than the “expensive” one once setup is factored in, because the cheap tool needed far more manual configuration to do what they needed.
Before you compare prices, ask for the real number: subscription, setup, migration of your existing customer data, and the integrations you already know you’ll need (accounts package, email, website forms). That’s the figure that predicts your actual first-year spend.
2. Requirements: write down what you need before you look at what's available
Most CRM shopping happens backwards. Someone books three demos, gets dazzled by features they didn’t know existed, and picks based on which salesperson was most convincing. That’s how you end up paying for AI lead scoring when what you actually needed was a shared inbox and a pipeline view.
Before you book a single demo, get specific answers to these:
- Is this primarily for sales pipeline, customer service, or the full lifecycle from lead to repeat business?
- What does it need to talk to? Your accounts package, your website, your email, your ecommerce platform if you have one.
- Who’s actually using it day to day, and what’s their technical comfort level?
- What does “success” look like in six months? Fewer missed follow-ups? Faster quote turnaround? One place to see customer history instead of three?
Lack of integration with existing tools accounts for a meaningful share of CRM failures on its own. If your CRM doesn’t talk to your accounts software, someone is retyping data by hand within a month, and you’re back to the exact problem you were trying to fix. Rank your requirements before you compare vendors, and be honest about which ones are must-haves versus nice-to-haves.
3. Simplicity: the best CRM is the one your team actually opens
This is the criterion most businesses skip, and it’s the one that determines whether the other two decisions were worth making at all. A CRM only creates value once data is in it. If entering a new contact or logging a call takes ten clicks and two minutes, your team will stop doing it within a fortnight.
Run a proper trial before committing, not a fifteen-minute sales demo. Get two or three actual team members to use it for a real task, not the salesperson’s cherry-picked example. Time how long common tasks take. If your least technical team member struggles in the trial, they’ll struggle in production, and that’s the person whose adoption determines whether the whole project succeeds.
Complexity of use is a documented cause of CRM failure in its own right, separate from cost and separate from missing features. A simpler tool that gets used beats a powerful one that doesn’t.
Where Krayin Fits
One option worth knowing about, particularly if budget is tight or you want more control over how the system works: Krayin. It’s an open source CRM built on Laravel, free under the MIT licence with no per-user fees and no feature gates on the core system. You pay for hosting (typically £5 to £15 a month at starter usage) rather than a licence, and it covers the essentials: contact and pipeline management, email integration, workflow automation, and a REST API if you need it to talk to other systems.
It’s not the right fit for everyone. Being open source, it needs someone comfortable setting up and maintaining hosting, which is exactly the kind of thing we handle for clients who want the cost benefits of open source without taking on the technical overhead themselves. For a business that’s outgrown spreadsheets but doesn’t want an ongoing per-user bill that scales with headcount, it’s a genuinely strong option, not a compromise.
The Framework in one Sentence
Work out the real total cost, write your requirements down before you take a single demo, and pick the option your actual team will use without a fight. In that order. Do that and the specific platform becomes a much smaller decision than it feels like right now.
If you want a second pair of eyes on this before you commit, our Full Systems Audit (£695) reviews what you’re already using, where the gaps are, and what actually needs fixing before you spend money on a new tool. Find out more here.
FAQ
How much does a CRM cost for a UK business?
Subscriptions typically range from around £7 to £140 per user per month depending on the platform. The real first-year cost is usually two to three times the annual subscription once implementation, data migration and training are included, so a £30 a month CRM can cost £2,000 or more to actually get running.
Why do most CRM implementations fail?
Studies from Gartner and Forbes put CRM failure rates between 50% and 75%. Over 60% of those failures are down to poor user adoption, not the software itself. Only 6 to 10% of failures are genuinely technical problems.
What’s the best CRM for a small team?
There isn’t a single best option. The right choice depends on your team size, whether you need sales pipeline tracking or full customer lifecycle management, and how technically confident your team is. Simplicity and actual adoption matter more than feature count.
Is Krayin CRM actually free?
Yes. Krayin is open source under the MIT licence with no per-user fees on the core system. You pay for hosting, typically £5 to £15 a month at starter usage, plus any setup and maintenance if you don’t manage the hosting yourself.
Does my CRM need to integrate with my accounts software?
If your CRM doesn’t connect to your accounts package, someone ends up retyping customer and order data by hand, which recreates the exact manual admin problem a CRM is meant to solve. Integration with existing tools should be on your requirements list from day one.