CRM Consulting

A CRM is only as good as the process it encodes. Most of what looks like a CRM problem is an undefined process problem.

Book a call

Companies rarely have a CRM problem. They have a process problem that the CRM is faithfully reflecting back at them.

Symptoms are consistent: reps do not update it, the data cannot be trusted, reporting requires a spreadsheet export, and someone is quietly running the real pipeline somewhere else.

What a CRM consultant should do first

  • The process, before the tool. What are your actual stages? What has to be true to move between them? Who owns a record at each point? Most CRM projects skip this and end up automating an undefined process.
  • Then the configuration. Objects, fields, stages, automation, permissions — matched to how the business sells now.
  • Then the data. Deduplication, field normalisation, ownership assignment. Unglamorous, and the reason most CRM projects fail to change anything.
  • Then adoption. A CRM that reps route around is worse than none, because it produces confident reporting on incomplete data.

How a CRM implementation runs

The sequence matters more than the tooling. Every stage below assumes the previous one produced a decision somebody is willing to defend.

StageWhat happensTypical duration
AuditCurrent data quality, process fit, adoption, integrations. Ends in a prioritised list.1–2 weeks
Process designStage definitions with exit criteria, ownership, the fields reporting depends on.1–2 weeks
Platform selectionOnly if you are genuinely undecided. Often the shortest step of the project.Days
ConfigurationObjects, pipelines, automation, permissions, reporting built to the process.2–4 weeks
Data migration and cleanupMapping, de-duplication, normalisation, deciding what does not come across.Highly variable
AdoptionTraining against real deals, manager routines, then removing what nobody uses.A quarter, not a week

Data cleanup is the line item that decides whether the project changes anything. It is also the one most implementation quotes leave deliberately vague.

Engagement types

EngagementTypical scope
CRM auditA read on data quality, process fit and adoption, with what to fix first
ImplementationNew CRM, process design, migration, adoption
MigrationMoving platforms without losing history or momentum
CleanupDeduplication, normalisation, restoring trust in the data
OptimisationExisting CRM, poor adoption or poor reporting
Ongoing ownershipCRM as part of a fractional operating engagement

Where CRM work is one part of a wider operational problem, it usually becomes a revenue operations engagement or a fractional operating role instead. Where the pricing and approval side is the bottleneck rather than the pipeline, it becomes a deal desk.

Choosing between HubSpot, Salesforce, Zoho and Dynamics

PlatformFits best atBreaks down when
HubSpot$2M–$50M, sales and marketing on one recordDeal structures get genuinely complex
Salesforce$25M and up, or genuinely unusual processNobody owns it internally
ZohoCost-sensitive teams under $10MReporting demands outgrow it
Microsoft DynamicsBusinesses already committed to the Microsoft estateBought for integration that never gets built
PipedriveSmall sales teams that want a pipeline and nothing elseMarketing or service needs the same record

We hold no reseller margin on any of these, which is why the answer is sometimes “keep what you have”. If HubSpot is already the direction, see HubSpot consulting and HubSpot implementation for what that engagement looks like specifically.

Field service businesses — HVAC, plumbing, electrical, and the trades generally — are the exception to most of this. A general CRM will not dispatch a technician or price a job, so the operating system is usually a vertical platform instead. That work is ServiceTitan consulting, not general CRM consulting, and the process discipline is the same either way.

When a CRM project is worth doing

Good fit

  • Reporting is rebuilt in a spreadsheet before anyone trusts it
  • Reps maintain a parallel pipeline outside the CRM
  • The system was configured by someone who has since left
  • Two teams disagree on what a stage means
  • Moving off spreadsheets, or off a CRM that never took

Poor fit

  • ×You want a specific integration built — that is a contractor job, not a consulting engagement
  • ×The CRM is fine and the real problem is that nobody has defined how you sell
  • ×A platform has already been bought and the decision is not reopenable

The second one is a warning rather than a disqualification. If the sales process is genuinely undefined, no configuration fixes it, and the work is process improvement that happens to end in a CRM.

Get a straight read on your CRM

A short audit covering data quality, process fit and adoption, with a prioritised list of what to fix first. Findings are yours whether or not we continue.

Book a call

Common questions

What does a CRM consultant actually do?
The useful ones define how you sell before touching the software: stages, exit criteria, ownership, and the handful of fields that reporting genuinely depends on. Configuration, data migration and training follow from that. A CRM consultant who opens with a platform recommendation is selling a platform.
Which CRM should we use?
For a $5M–$20M company the platform matters much less than the process discipline around it. A well-run HubSpot beats a badly-run Salesforce, and costs a fraction as much. Zoho and Pipedrive are credible at the smaller end; Microsoft Dynamics usually makes sense only where the rest of the business already runs on Microsoft.
Are you a reseller or an implementation partner?
Neither. We work with HubSpot, Salesforce, Zoho, Microsoft Dynamics and Pipedrive, and hold no partner margin on any of them, so the recommendation is not shaped by a commission. Ask any CRM consultant this before you take their platform advice.
Do you work in Zoho, Microsoft Dynamics and Salesforce, or only HubSpot?
All of them. Most of our work lands in HubSpot because that is where companies this size are best served, but a Zoho or Dynamics estate that already works is rarely worth replacing. Migrating platforms to solve a process problem just moves the problem.
How much does a CRM implementation cost?
The services cost usually runs to a multiple of the first-year licence, and the variable is almost never the configuration. Data cleanup and integrations move the number; seat count barely does. We scope as a fixed piece of work or a monthly retainer rather than an hourly rate, because hourly billing rewards the wrong things on a project like this.
How long does a CRM implementation take?
Process design and configuration is typically four to eight weeks. Data cleanup varies enormously with the state of what you have, and adoption is measured over a quarter rather than a fortnight.
Why do CRM implementations fail?
Three causes, in order of frequency: the process was never defined, so the configuration automated an ambiguity; the data was migrated rather than cleaned, so nobody trusts the reporting; nobody owned the system after go-live. None of these is a software problem, which is why buying a different CRM rarely fixes them.
Can you migrate us to another CRM without losing history?
Yes. A CRM migration is mostly a mapping and de-duplication exercise — deciding which records deserve to come across, what the fields mean on the other side, and what gets archived rather than imported. Moving everything is the mistake most migrations make.
Our reps will not use the CRM. Can that be fixed?
Usually, but not by adding features. Low adoption is nearly always a sign the CRM encodes a process that does not match how the team actually sells, so reps route around it and the real pipeline lives in a spreadsheet.