How to Choose a CRM Consultant

Consultant or implementer?

These are different purchases and conflating them is the most expensive mistake in this category. An implementer configures a system to a specification you provide. A consultant works out what the specification should be by diagnosing the business problem first.

If you can write the specification yourself, hire an implementer and pay implementer rates. If you cannot — and most companies cannot, because the specification requires deciding what a qualified lead means — you need the diagnosis first.

The eight questions

1. 01
   What will you recommend we stop using?

   The fastest way to separate the two categories. A consultant has a view on consolidation and will name something. An implementer will configure whatever you already own, because tool selection is outside their remit.

2. 02
   Walk me through a data model you designed and why

   Listen for whether they talk about how the business sells or about platform features. Someone who designs from the sales motion produces systems that survive; someone who designs from the feature list produces systems that fit the demo.

3. 03
   How do you decide what should be a required field?

   A deceptively good question. The right answer involves a decision that depends on the value. A weak answer is whatever the client asks for, which is how orgs accumulate forty required fields and a workaround culture.

4. 04
   What happens if we terminate at the halfway point?

   The answer reveals the dependency model. If mid-project termination leaves you with a half-migrated system and no documentation, the engagement is structured for lock-in.

5. 05
   Who is doing the delivery work, and what have they built?

   Get names. Senior sale, junior delivery is the most common failure in this category and it is invisible until implementation starts. Ask to meet the delivery lead before signing.

6. 06
   What does training cover, and for whom?

   Should be role-based and should cover the reasoning behind the design, not only the clicks. A team that knows which button to press but not why the stage criteria exist will erode the design within two quarters.

7. 07
   How do you handle data migration and what is excluded?

   Migration is where timelines break. You want a stated cutoff policy, a deduplication approach, and an explicit list of what is out of scope. Vagueness here means a change order later.

8. 08
   Show me documentation from a past project

   Redacted is fine. Documentation quality is the single best predictor of whether you will be able to operate the system yourself afterwards, and it is easy to inspect.

What training should actually cover

Post-implementation training is routinely scoped as a walkthrough of the new interface, which teaches people where things are and nothing about why. The design then decays because nobody understands what it is protecting.

The third row is the one that gets cut for budget and is the one that determines whether you need the consultant back in six months. An internal admin who understands the data model can maintain the design; one who only knows the configuration screens cannot.

Pricing models and what they incentivise

Phased fixed price is the structure worth pushing for: diagnosis, then build, then adoption, each with a defined output and a break clause. You keep optionality and they keep the incentive to complete each phase properly.

Five red flags

• A quote before a discovery call. They are pricing a template and padding for unknown risk you will pay for regardless.
• Certifications presented as the main credential. Certification proves platform knowledge, not judgement about your business. It is a floor, not a differentiator.
• No named delivery team. Staffing will be decided after you sign, usually downward.
• Reluctance to document. Almost always a dependency model. Ask for a sample and watch the response.
• Every recommendation requires more of their services. A good diagnosis includes things your own team can fix, with instructions.

The test that costs nothing

Give each shortlisted consultant the same real problem from your business — a forecast that missed, a report two teams disagree about — and ask how they would diagnose it. Not solve it. Diagnose it.

Consultants ask about definitions, stage criteria, and where the data lives. Implementers describe a configuration change. You will know within twenty minutes which you are talking to, and it costs you nothing but the call. The same principle applies when choosing a RevOps agency, and the implementation itself is covered in CRM implementation.