Questions to ask a CRM consultant. Before you sign anything.

The short answer. Five questions that separate a good hire from an expensive one.

A CRM consultant's real value shows up months after the contract is signed, in whether the system actually gets used, so the questions worth asking are the ones a smooth-talking but shallow candidate cannot fake. Ask how they define project success, what their plan is for training and adoption rather than just configuration, what experience they have with the other tools your CRM needs to talk to, what support looks like after launch, and for references from a project that has been live long enough to show whether it stuck.

Most founders default to comparing quotes and timelines, which are the easiest things to compare and the least predictive of outcome. A consultant who promises a four-week go-live and a consultant who promises six weeks are not meaningfully different if neither has a plan for what happens when the sales team quietly stops logging deals in week seven. The questions below are designed to surface that difference before you have paid for it.

It helps to separate two different hires you might be making, since the questions differ slightly. One is a consultant to help you choose a platform in the first place, weighing HubSpot against Salesforce against Zoho against Pipedrive for your specific business. The other is a consultant, sometimes the same person, sometimes not, to implement the platform once it is chosen. Selection advice benefits from someone with no stake in which platform wins; implementation benefits from deep, specific expertise in the one you have picked. Knowing which hire you are making before the first call keeps the conversation focused on the right set of questions.

How it works in practice. What to actually ask, and what a good answer sounds like.

Push past the headline answer on each one. If a candidate says they handle training, ask what that training actually consists of: live sessions, role-specific guides, a recorded library, and who owns refresher training once new hires join after the consultant has left. If they cite integration experience, ask for the name of a comparable project rather than accepting "we've done integrations before" as sufficient, since connecting a CRM to a simple email tool is a different job entirely from connecting it to a bespoke billing system or an existing data warehouse.

Cost questions deserve the same scrutiny. Clarify whether pricing is fixed or hourly, whether packages differ by company size, and critically, what is excluded from the headline number, since ongoing support, additional user licences and future workflow changes are where budgets most often run over. A consultant who welcomes this level of questioning is usually confident in their own scope; one who becomes vague or defensive is telling you something about how the project will go once real complexity appears.

Also ask directly about their approach to integrating the CRM with the rest of your stack, marketing automation, an invoicing or ERP system, a booking engine if you are in hospitality. A consultant who has only ever configured a CRM in isolation will underestimate how long integration work genuinely takes, and that underestimate becomes your delay, not theirs, once the project is under way. A specific answer names the tools they have connected before and roughly how long that work took; a vague one talks only about the CRM's own features and skips past the harder question of how it will actually sit inside your existing systems.

What good looks like. Due diligence that actually reduces risk.

The businesses with the smoothest CRM projects are rarely the ones that moved fastest through selection, they are the ones that asked harder questions before signing. Research into CRM and membership-system selection found that organisations navigating the process without consultant guidance report markedly lower confidence across the tasks that matter most: writing an effective request for proposal, budgeting the implementation realistically, and negotiating the contract terms, compared with those who completed a properly guided selection. That confidence gap is not abstract, it is the same gap that later shows up as an unexpected invoice or a system that does not fit how the business actually sells.

A good consultant welcomes a working session before the contract is signed, not just a sales call. Ask them to walk through, in specific terms, how they would map one real process from your business, your lead intake, say, or your renewal workflow, onto the CRM you are considering. A consultant who can only speak in generic platform features has not yet done the harder work of understanding your business; one who asks you detailed questions back about how your team actually works today is doing the diligence that leads to a system people use rather than tolerate. For the wider selection framework this fits into, see our approach to CRM consulting and selection.

Compare shortlisted consultants against the same criteria table above rather than against each other's pitch decks, which are designed to look strong in isolation and rarely invite direct comparison. Two consultants who both say "we handle training" answer very differently once asked to specify what that training actually looks like week by week, and that specificity, not confidence on a call, is what predicts whether the system is still in daily use a year later.

Ask, too, how the consultant handles disagreement about scope once the project starts, since it always does. A CRM implementation surfaces process problems that had nothing to do with software, a sales team with three different definitions of "qualified lead," a renewal process that exists only in one person's head, and a consultant's response to that discovery tells you a great deal about how the rest of the project will go. A strong answer names it plainly as a process gap, proposes fixing the process first, and adjusts the timeline honestly. A weak one either ignores the gap and builds automation around a broken process anyway, or treats every discovery as a chargeable scope addition, which is a different problem but an expensive one.

Pitfalls to avoid. Where hiring a CRM consultant goes wrong.

The first pitfall is choosing on price alone. A cheaper quote that excludes training and post-launch support is not actually cheaper, it has simply moved the cost of adoption failure onto your team's frustration and a system nobody trusts. Weigh quotes against what is included, not the headline figure.

The second is skipping the reference check, or only speaking to a reference the consultant hand-picked from a project that finished last month. A project can look successful at go-live and be abandoned within a quarter; ask specifically for a reference from a project that has been live for six months or longer, and ask that reference directly whether the team still uses the system without being reminded to.

The third is hiring a consultant who is not platform-agnostic during the selection stage. A consultant who only implements one CRM has an obvious incentive to recommend that platform regardless of fit, which is a different conflict of interest to hiring a certified specialist once the platform decision is already made. Keep the two stages, choosing the platform and implementing it, separate in your mind, and be clear with yourself about which stage you are hiring for.

The fourth is treating the consultant relationship as finished at go-live. CRMs drift: fields get renamed, teams restructure, new integrations get bolted on without documentation. Ask upfront what an ongoing relationship looks like, whether that is a retainer, a fixed number of support hours per quarter, or simply an hourly rate for ad hoc help, so you are not negotiating support terms for the first time in a moment of frustration six months after the consultant has moved on to their next client.

The fifth is asking every question above and then not writing any of the answers down. A verbal promise on a discovery call about training or support is easy for both sides to remember differently three months later. Put the substantive answers, what training consists of, what post-launch support costs, what is and is not included in the quoted price, into the proposal or contract itself before signing. If a consultant is reluctant to commit an answer to writing that they were happy to give verbally, treat that reluctance as information in its own right, not as an oversight to smooth over.