The right CRM, chosen well. Value you keep.

Most failed CRM projects were lost at the start, not the finish. A platform got bought on a slick demo and a long feature list, then it was bent to fit a process nobody had written down, and within two quarters the team had quietly gone back to spreadsheets and memory. The software was rarely the problem. The choice, and the thinking behind it, was. That is what CRM consulting is for: deciding what you actually need, picking the platform that fits, and making sure the thing gets used.

This page sets out what a CRM consultant does, why the selection decision matters more than the build, and how I help founder-led and SaaS teams choose well. It is deliberately about the choosing. The configuration and build that follow a decision are a separate piece of work, covered on my CRM implementation page, and the two are best kept distinct so you implement the right thing rather than the wrong thing efficiently.

What CRM consulting actually is

A CRM consultant is an independent adviser who helps you choose and get value from a customer relationship management system. The word independent matters. A good CRM consultancy is not paid by a vendor and is not trying to sell you a particular logo. The job is to understand your business, translate that into clear requirements, and recommend the platform that fits, even when the honest answer is the cheaper one or the one you had not considered.

In practice the work covers a few distinct things:

• Requirements. Turning a vague wish for better organisation into a written list of what the CRM must do, must integrate with, and must report on.
• Selection. Shortlisting platforms against those requirements and your budget, then testing them on your real sales scenarios rather than on a generic demo.
• Fit and cost. Working out the true cost over a few years, including seats, add-ons and the effort to run it, not just the headline monthly price.
• Adoption planning. Deciding up front how you will get the team to use it, because a CRM nobody updates is worse than no CRM at all.

Notice what is not on that list: the build itself. Choosing the CRM and configuring it are different jobs, and confusing them is how teams end up locked into a platform they regret. Consulting is the thinking. The build comes after, once the decision is sound.

CRM consulting versus CRM implementation

People often use the two terms interchangeably, so it is worth being precise. CRM consulting decides what to buy and why. It produces a recommendation, a requirements document and a plan. CRM implementation takes that decision and makes it real: configuring stages and fields, importing and cleaning data, wiring up automation and training the team. You can think of consulting as choosing the right house and implementation as fitting it out. Get the first wrong and no amount of skill on the second will save you. If you already know which platform you are committing to and just need it built well, the implementation work is the better starting point.

Why the choice matters more than the build

A CRM is a long commitment. Once your data, your process and your team's habits live inside a platform, moving to another one is painful and expensive, so the decision you make in a few weeks shapes how you sell for years. That is why the consulting half is worth more than its modest cost. Three commercial reasons it pays for itself:

• Avoiding the wrong platform. The most expensive CRM is the one you buy, configure, half-fill with data and then abandon. Getting the choice right the first time saves the licence fees, the wasted setup and the lost momentum of a second attempt.
• Right-sizing the spend. Plenty of teams buy far more CRM than they need, paying enterprise prices for features they never switch on. Just as many buy too little and outgrow it in a year. Honest selection matches the tool to the stage you are at.
• Designing for adoption. The value of a CRM is entirely in whether people use it. A platform chosen with the team, that fits how they already work, gets adopted. One imposed on them does not, and the reporting built on top of it is fiction.

For SaaS and scaling teams the stakes are sharper, because the CRM is not a contact book. It is the spine of the whole revenue engine, feeding the pipeline, the forecast and customer success. Choosing it well is one of the first steps in proper revenue operations, and choosing it badly undermines everything that depends on it.

How I approach CRM selection

I start from how you sell, not from a list of products. The aim is a decision you can defend in two years, so the process is deliberately grounded in your reality rather than in vendor marketing. It usually moves through four stages.

Understand how you sell today

Before any platform is mentioned, I sit with the people who do the selling and the servicing and follow the real path a deal takes, from first enquiry to closed and beyond. Often this is captured as a set of process maps, because you cannot choose a tool to support a process you have never written down. This stage also surfaces the things that quietly decide the outcome: what the CRM has to connect to, who needs to see what, and where the current way of working actually hurts.

Write the requirements down

Next we turn that understanding into a short, honest requirements list, separated into what the CRM must do, what would be useful, and what is genuinely nice to have. Most selection mistakes come from skipping this and reacting to whichever demo looked shiniest. A written list keeps the decision anchored to your business rather than to a salesperson's strongest feature.

Shortlist and test on your own scenarios

With requirements agreed, I shortlist two or three platforms that genuinely fit, then we test them against your scenarios, not the vendor's. We run your actual sales stages, your reporting questions and your awkward edge cases through each one. This is where the differences that matter show up, the ones a polished demo is designed to hide.

Recommend, with the costs and the trade-offs

Finally I give you a clear recommendation: which platform, why, what it will cost over a sensible horizon, and what you are trading away by choosing it. No option is perfect, and you should know the compromises going in. The output is a decision you understand and own, not a verdict handed down.

Choosing the best CRM for a small business

The question I am asked most is some version of "what is the best CRM for a small business?" The honest answer is that there is no single best one, because the right CRM depends entirely on how you sell and what you need it to do. A two-person consultancy and a thirty-person SaaS team have almost nothing in common in their requirements, even though both are small.

That said, there are sensible questions that point you towards the right shortlist:

• How do you sell? A simple, mostly linear pipeline suits a lighter tool. Complex deals with many stakeholders and long cycles justify something heavier.
• How many people will use it? Per-seat pricing adds up, and a tool that is generous at five users can be punishing at twenty-five.
• What must it connect to? Your email, your accounting, your support inbox, your website forms. Integration is where many small-business choices succeed or fail.
• Who will own it? If no one will administer a powerful platform, you will get more value from a simpler one that runs itself.
• What is the real budget? Including add-ons and the time to run it, not just the advertised monthly figure.

For many small and founder-led teams, a lighter platform such as Pipedrive or HubSpot fits better than the full weight of Salesforce, which can be more than a small team can use or maintain. But that is a starting hypothesis, not a rule. The point of a selection process is to test it against your answers above rather than to assume it. The work is platform-led, not platform-locked, and not paid for by any vendor, so the recommendation follows your needs.

What a consulting engagement includes

Engagements are shaped around your situation, but a CRM consulting and selection piece usually includes some mix of the following. It sits naturally within the wider growth consulting I do, so the tool you choose connects to the commercial plan rather than standing apart from it.

Stage	What you get
Discovery	A clear read of how you sell and service today, including the data flows and integrations the CRM has to support.
Requirements	A written, prioritised list of must-haves, useful-to-haves and nice-to-haves to anchor the decision.
Platform shortlist	Two or three platforms that genuinely fit, with the reasoning for each and the ones ruled out.
Scenario testing	Structured demos run against your own sales and reporting scenarios, not generic vendor scripts.
Recommendation	A single recommended platform with total cost of ownership, trade-offs and the case for it set out plainly.
Adoption plan	How the team will be brought onto the tool, and how it hands over cleanly into a build.

Throughout, the test I hold the work to is whether your team will trust the result. A technically ideal platform that the people doing the selling resent is a failed choice. I design the decision with the people who will live in the tool every day, because their buy-in is the difference between a CRM that holds and one that quietly empties out.

From a good choice to a system people trust

Choosing the right CRM is the start, not the finish. A sound decision still has to become a working system, and that is where the engagement either hands over to a build or sets the plan for one. The pieces that turn a chosen platform into something a team relies on are the same ones I work on across my services: a clean CRM implementation that matches how you sell, sensible CRM automation so the routine work runs itself, and reporting through sales dashboards that leaders can act on.

The thread running through all of it is adoption. The work that makes a CRM stick is not technical, it is human: clear ways of working, light documentation, and a tool that genuinely makes someone's day easier rather than adding admin. Getting that right is a discipline of its own, which is why CRM adoption is something I treat as deliberate work rather than a hope. A consulting engagement is where that planning starts, by choosing a platform people will actually want to use.

A note on the Middle East

Much of my work is with founder-led and SaaS teams scaling across the Middle East, and CRM selection is often one of the first decisions a business entering the region has to get right. A new market can bring new data and privacy expectations, new languages, and integrations with local tools, all of which belong in the requirements rather than discovered after purchase. Whether you are expanding into the region or running a team out of Dubai, the principle holds: choose the CRM that fits how you actually sell, plan for adoption from the start, and you get a system your team trusts rather than another login they avoid.