Working with a CRM consultant: what to expect and how to choose one
There's a particular moment most business owners reach. They've tried setting up a CRM themselves, or they've tried for the second time, and it's still not working. The question becomes whether to keep pushing or hire someone in.
I'm in the business of being hired in, so you should weight my opinion accordingly. I'm also going to be honest about when hiring a CRM consultant is the right move and when it isn't. There are situations where the answer is "do it yourself for now, come back to me in six months if it still hasn't stuck". I'd rather lose a fee than sell someone a service they don't need.
This guide is for the moment you're sitting at the decision point. It covers what a CRM consultant does, when hiring one makes sense, what a good engagement looks like, what to watch out for, what it should cost, and what to ask before you sign anything.
What a CRM consultant does
The honest version: a CRM consultant does three things.
The first is the thinking that comes before the clicking. Choosing the right tool for your specific business, mapping your sales process and project delivery in a way that survives contact with reality, deciding what to track and what to leave out. That's the bit most business owners can't easily do from inside the business looking out. There's a step-by-step guide to setting up Capsule yourself if you want to attempt this without help, and a piece on the common mistakes I see if you've already tried.
The second is the build itself. Configuring the system, importing data, setting up pipelines and Tracks and custom fields, integrating with the rest of your stack (accounts, email, marketing tools, calendars). Technically this isn't difficult work, but doing it well requires having done it many times before, so you know which decisions matter and which don't.
The third is the bit that determines whether the project succeeds or fails: getting your team to use it. Training, documentation, troubleshooting in the first few weeks, and being available when someone says "but how do I..." for the seventh time. The best CRM in the world goes cold within a month if the team doesn't take to it. A good consultant builds the system in a way the team can use, then helps the transition.
What a CRM consultant shouldn't do, just as importantly. Make decisions on your behalf about how your business should work. Pick a tool because it's the one they always sell. Build something elaborate that needs them to maintain it forever. Disappear once the invoice is paid.
When hiring help is worth it
A few specific situations where the maths works out.
When you've tried CRMs before and they haven't stuck. The pattern usually means there's something in the setup that doesn't match how the business works, and that's hard to spot from inside. An outside perspective tends to find it quickly.
When your business is more complex than the templates handle. Multiple pipelines, multiple service lines, project delivery as well as sales, integrations with niche industry tools. The standard "follow the wizard" approach was designed for the simple case and gets brittle quickly outside it.
When the team is too small to dedicate someone to setting it up. If the founder is also the sales lead and the operations manager, asking them to also become the CRM administrator is the recipe for it never quite happening.
When you want it running well in weeks rather than months. DIY setup is doable but slow if you're learning as you go. A consultant who's done it a hundred times moves faster, and the saved time has a real cost.
When you're migrating from an existing CRM. Data migration is where most projects go wrong, and the consequences of getting it wrong are permanent. Worth paying for the experience.
If your situation specifically involves Capsule, there's a separate piece on what a Capsule Certified Partner does that goes into the specifics.
When DIY is the right call
Equally specific situations where I'd tell you to do it yourself.
When the business is genuinely simple. One pipeline, a small handful of clients, no project delivery to track. A CRM trial and an afternoon of patient setup will get you most of the way.
When you're early enough that you should be living inside the CRM yourself for a few months to learn what it needs to do. Spending money on a consultant before you've used a CRM at all is buying advice you don't yet have the context to evaluate.
When the budget genuinely isn't there. A good consultant should help, not be the thing that breaks the business. If you can't comfortably spend the fee, the fee isn't right for you right now.
When you want to learn the tool deeply because you're going to be the person running it ongoing. There's value in setting your own CRM up if you'll be in there every day. The understanding sticks.
What a good engagement looks like
The shape of a CRM consultancy engagement, in my experience, runs roughly like this.
A first conversation, usually free, where the consultant listens more than they talk. They're trying to understand your business, your current setup (or lack of one), what's not working, and what you're trying to fix. If they spend most of this conversation pitching their package, that's a red flag.
An audit or discovery phase, paid but light. They go deeper into your business, look at your current systems, talk to a few people, and come back with a clear written view of what they think you need and what a project to get you there would look like. This is where most of the strategic thinking happens, and it should produce real value even if you don't go on to engage further.
A setup phase, where they do the build. Length depends on complexity, but for a typical small business it's a few weeks rather than a few months. They should be communicating throughout, not vanishing for two weeks and reappearing with a finished system.
A training and handover phase. They show your team how to use it, write or provide documentation, and remain available for the inevitable questions in the first few weeks.
A check-in window after launch. The first month is when things wobble. A good consultant doesn't disappear at launch. They build in some hours for the post-launch period because they know what happens.
If the engagement you're being offered doesn't include those phases, ask why. There's a separate piece on what's included in a CRM setup service that goes into more detail on what each phase should cover.
Red flags to watch for
A few specific things worth being wary of.
The consultant who has one tool and recommends it to everyone. If they're a Capsule specialist they'll recommend Capsule, if they're a HubSpot partner they'll recommend HubSpot. That's not necessarily bad (I'm a Capsule specialist myself), but the good ones will tell you honestly when you'd be better served by something else. The ones who recommend their tool to everyone are doing sales rather than consulting.
The fixed-price total package with no detail. "CRM setup, £4,000" tells you nothing about what you're buying. A reasonable consultant should be able to break that down into discovery, configuration, integration, training, and post-launch support, with hours and costs against each.
The engagement that requires you to keep paying forever. Some consultants build systems that only they can maintain. Your CRM should be something your team can run after the consultant leaves, with occasional return visits for new requirements rather than ongoing dependency.
The very cheap quote. Good CRM consultancy involves real thinking, not just clicking through a setup wizard. If the quote is much lower than the others, the work behind it usually is too.
The very expensive quote with no clear value. Equally, a six-figure project for a five-person consultancy is often the consultant trying to make their target client size work for them rather than the other way around.
There's a longer piece on how to find a CRM implementation consultant who delivers which goes into more of the detail on what separates good ones from bad ones.
What it should cost
Honest numbers from the UK market in 2026.
A discovery audit, where someone competent looks at your situation and tells you what you need, runs roughly £100 to £300 depending on the consultant and the depth. Mine sits at £149.
A full CRM setup project for a typical UK small business, including discovery, build, integration, training, and post-launch support, runs somewhere between £1,500 and £6,000 depending on complexity. For most service businesses with up to ten people, expect a number towards the middle of that range.
Hourly rates for ongoing support, when you need it after launch, run between £75 and £200 depending on the consultant. Mine is £175 for ongoing work after the initial setup.
Anything significantly below those numbers is either inexperienced help or a stripped-down service. Anything significantly above is either an enterprise-scale consultant working with small businesses (a poor fit) or someone overpricing for the work.
What to ask before you commit
Five questions worth asking before you sign anything.
How many businesses like mine have you set up? Specifics matter. "A lot" is not an answer. You want a number and you want to hear about the patterns they've seen.
Which CRMs do you work with, and how do you decide which one to recommend? If the answer is "one CRM and we recommend it to everyone", you've learned something useful.
What happens if it doesn't stick? A confident consultant has a view on this. They've seen it happen, they know why it happens, and they have a process for catching the warning signs early.
Can I speak to a recent client? Anyone who's done good work has clients who'll vouch for them. Anyone who can't put you in touch with one is a question mark.
What does the work after launch look like? You're not just hiring for the build, you're hiring for the first few months of the system being alive. Get clarity on what that includes.
The audit as a low-risk first step
If you're not sure whether to commit to a full project, an audit is the sensible place to start.
The shape of a good audit is roughly: an hour-long conversation about your current setup and what's working and not, followed by a written assessment with concrete recommendations. You should walk away with a clear view of what you need (and possibly that you don't need anything yet). It should be self-contained, in the sense that the value doesn't depend on hiring the same consultant for the build.
That last bit matters. An audit that's really a sales pitch in disguise isn't an audit, it's marketing. A real audit produces value even if you take the recommendations elsewhere.
My own CRM Audit sits at £149 and runs to that shape. An hour together, a written summary with what I'd suggest and why, and no obligation to engage further. Some clients go on to a setup project. Others take the recommendations and run with them. Both are fine outcomes.
What to do next
If you've read this far and you're thinking about hiring help, the practical next step is probably one of two things.
A discovery call is the no-pressure first conversation. We talk for half an hour about your business, your current setup, and whether anything I do would help. If it would, we talk about what that might look like. If it wouldn't, I'll tell you that, and where else to look.
A CRM Audit is the next step up. If you already know roughly what you need and you'd like a second opinion before you commit to a setup, the audit gives you a structured hour with me and a written summary you can act on.
Either way, the right time to have the conversation is when you're considering it. The wrong time is six months further down a setup that's not working.