Choose a CRM by starting with your sales process, and leave the feature list till later. Write down the real decisions a customer makes between first enquiry and signed work, make those your pipeline stages, and then check which tools can hold that shape without custom hacks. After that, test three things. Who owns each record, what the CRM has to connect to, and whether you can export everything if you leave. Price comes last.
Start with the decisions your customer makes, not the stages your CRM suggests
Every CRM comes with default stages like New, Contacted, Qualified, Proposal, Won. They describe what your team did, and they say nothing about what the customer decided. That's why pipelines go stale. Deals sit in "Contacted" for nine weeks and nobody can tell you why.
Better stages match a decision only the customer can make. For a service business that usually looks like enquiry received, spoke to a human, agreed the problem is worth fixing, seen the price, made a decision. Each step forward needs proof, and hoping doesn't count.
Try this on your pipeline now. For each stage, ask what the customer did to get there. If the answer is "we sent them something", that's an activity and it shouldn't be a stage, so merge it or delete it.
Keep it between five and seven stages. Any fewer and you can't see where deals die. Any more and your team stops updating them, and that's worse than having no CRM at all.
The two stages most service businesses are missing
The first is a qualification stage with a written definition, so something you can check and not just a feeling. Something like "has a budget range, a timeline and authority to sign". Without it your close rate means nothing, because the number you're dividing by is full of junk.
The second is a stage between "won" and "started". The handoff from sales to delivery is where a lot of service businesses lose money without noticing, through missed context and slow starts. We went through the detail in the sales-to-delivery handoff checklist.
Decide who owns each record before you decide which tool
Ownership is what decides if a CRM stays accurate. Every contact, deal, task and note needs one named person who's responsible for it, and a whole team being responsible doesn't work.
Write it down before you buy. A simple version looks like this.
| Record | Owner | Who else can edit | Who must be notified |
|---|---|---|---|
| New enquiry | Whoever responds first | Sales manager | Sales manager, daily |
| Open deal | Salesperson named on it | Sales manager | Owner, weekly |
| Won deal / account | Delivery lead | Salesperson, read plus notes | Finance |
| Company record | Operations | Sales, restricted fields | Nobody |
Then check the tools on your shortlist can actually enforce it. Some let anyone edit anything. That sounds flexible, and then what ends up happening is you've got three versions of the same company and a deal nobody claims. You want permissions per field, or at least record ownership plus an audit history so you can see who changed what.
This is one of our build principles. Clear permissions, and human review wherever money, legal commitments or messages in your name are involved. On the MRM Group build, the agreement-before-payment flows and audit history were there for that reason, with human approval at sensitive financial-promotion decision points. You can read the MRM Group case study to see how it fits together.
Work out what must connect, and what only needs to be visible
Integration is where CRM choices get expensive. So split your list into two columns before you look at any tool.
Must write data both ways. Your website and enquiry forms. Your calendar and booking tool. Your phone system, if calls are a real channel for you. Your email, so replies land on the record automatically without anyone copying and pasting.
Only needs to be visible. Accounting, project delivery, support tickets. These often work better as a read-only view or a dashboard than as a two-way sync you spend six months fixing.
Speed to lead is the connection that pays for itself fastest. Harvard Business Review's "The Short Life of Online Sales Leads" found that firms trying to contact a web lead within an hour were nearly seven times as likely to qualify it as those who waited even an hour longer, and more than 60 times as likely as those waiting 24 hours or more. Of 2,241 US companies audited in that 2011 study, 23% never responded at all. If your form doesn't create a CRM record and an alert within seconds, nothing else on the feature list matters.
Watch the connector costs too. If you're planning to join everything up with Zapier, each successful action step counts as a task, triggers and filters don't, and when you hit your plan limit new runs are held until you pay for more. Ten automations across a busy pipeline add up quickly. We wrote about where it tips over in Zapier vs custom automation.
Score your options: a seven-point test
Give each CRM on your shortlist a score out of two for each line. Zero is no, one is partly, two is yes.
- Can the pipeline hold your real stages without renaming things into nonsense?
- Can you set record ownership and limit who edits sensitive fields?
- Does it connect both ways to your website forms, calendar and email?
- Can you export everything, including notes, activity history and messages, in a format you can use?
- Can someone new on the team log an enquiry properly after fifteen minutes of training?
- Does reporting answer your top five questions without a spreadsheet?
- Is the total yearly cost, including seats, add-ons and connector tasks, something you'd happily pay in year three?
Ten or above, it'll work. Below seven, keep looking. Question four is the one people skip and then regret, because how well a tool exports decides if leaving later costs you a weekend or three months.
The signs you have outgrown the CRM you have
Not every annoyance means you should move. Moving is disruptive, and the tool is hardly ever the whole problem. These are the signs that the tool really is what's holding you back.
- You pay for features you don't use, and the ones you need are locked in a higher tier or a separate product.
- Your team keeps a spreadsheet next to the CRM because the CRM can't hold something they need. One spreadsheet is a warning, and three means it's time to decide.
- You can't answer "how many enquiries came in last month and what happened to each one" without doing it by hand.
- Reporting means exporting to a spreadsheet every week, which we cover in the 9 numbers every service business dashboard needs.
- Permissions are all or nothing, so people can see client financial data they shouldn't.
- Adding a new service or role means fighting the way the tool thinks.
TMMB Academy came to us with a funnel in pieces, rising software subscriptions and no single system. What we built was one portal with its own workspace for admins, coaches, creators, sales, assistants and brands. The work ran for more than 60 days. The TMMB Academy case study sets out what that covered.
When not to move
If your stages aren't defined, nobody updates records and there's no agreed owner, a new CRM will fail the same way with a different logo. Fix the process in the tool you've got for three months first. If people stick to it and the tool still gets in the way, then move, and you'll have the proof.
The same goes the other way. If a well set up off-the-shelf CRM covers your process, use it. Our projects start at £4,500, and a custom build is only worth it when the tool really is the limit. Custom software vs SaaS sets out where that line is, honestly.
Plan the exit before you commit
We moved our own CRM out of GoHighLevel into a system we built, and that move is now complete. What it carried across was more than 1,600 contacts, around 100 deals with values, over 11,000 emails, over 1,000 text messages, nearly 200 calls and several thousand activity records. Those are the import counts, not what's in there today. We built the import so it could be run again, matched on the original IDs, carried do-not-contact settings across, and ran both systems side by side before switching anything off.
Two lessons apply to your choice. First, message history is the hardest thing to move and the easiest to lose, so check how a tool exports emails, texts and call records, and not just contacts. Second, do-not-contact and consent flags have to come through the move untouched. Under UK PECR guidance, automated marketing calls need specific prior consent, and general marketing consent is not enough. So losing those flags is a compliance problem, and much more than a hassle.
The step-by-step method is in CRM migration without losing data. When we do this for clients through CRM setup and migration, it's built in your own accounts, and you own the code and the data.
Do this week
Open your pipeline and list every stage. Next to each one, write the customer decision it stands for. Any stage where you can't name a decision gets merged or deleted.
Then pick one deal from each stage that's left and check the record has an owner, a next action and a date. If most don't, the problem is how the team uses it, and that's cheaper to fix than a new tool.
If the way your process works really won't fit the tool you've got, book a call. We'll map how enquiries come in and where work gets stuck before anyone talks about software.
