“We’ve got a CRM but nobody really uses it.” We hear this constantly, and in our experience it’s one of the most telling indicators of where a consultancy actually is commercially. Sometimes it’s HubSpot, sometimes Salesforce, sometimes Pipedrive or something bespoke.
Occasionally it’s a shared spreadsheet that someone gave a grand name to. But the complaint is always the same: the system exists, the adoption doesn’t, and at some point the conversation turns to whether switching to a different platform would finally fix things.
It wouldn’t. Because the platform is almost never the problem.
What a CRM actually does and doesn’t do
A CRM is a database. It stores information about contacts, companies, conversations and deals. It can surface reminders, generate pipeline reports and help you see where revenue is likely to come from over the next quarter. These are genuinely useful things, but there’s a long list of things a CRM cannot do. It can’t create pipeline. It can’t have commercial conversations on your behalf. It can’t decide which deals to prioritise, when to walk away from an opportunity, or how to position your firm against a competitor. And it can’t make your team disciplined, consistent or commercially motivated.
A CRM is only as useful as the information that goes into it and the quality of decisions that come out of it. Information only goes in if there’s a process that requires it, and that process only gets followed if there’s accountability around it. This is where most businesses go wrong.
They implement the platform, configure the fields, sit through a training session and then wonder six months later why adoption has fallen away. The answer is that there was nothing meaningful to put in it. No agreed definition of what a qualified lead looks like. No shared understanding of what the pipeline stages actually represent. No expectation that deals will be logged when they open, updated when they move and reviewed when they close or die. The CRM isn’t the problem. The absence of the process and accountability behind it is.
Bad data is a symptom, not a cause
Every underperforming CRM has the same profile. Deals logged at the wrong stage, or logged weeks after the first conversation happened. Contacts marked as active despite no interaction in months. Close dates that passed without anyone updating them. Deal values that bear no relationship to what was actually discussed. Notes so sparse they tell you nothing useful when you look back at them six months later.
This data doesn’t become bad by accident. It becomes bad through habits: logging a deal only when you’re feeling confident about it, updating stages when you remember to rather than when something actually changed, skipping the lost deal record because it feels like publicly acknowledging a failure. These habits, repeated across a team over time, produce a CRM that nobody trusts. And when nobody trusts it, it gets used even less, which makes the data worse, which reduces the trust further. It’s a completely self-reinforcing cycle, and the only way out of it is through the process and expectations that sit upstream, not through the software itself.
Reporting should lead behaviour, not lag behind it
The most common mistake we see with CRM reporting is treating it as a rearview mirror: something you look at to understand what happened last quarter, a way of telling a story after the fact for management or board purposes. That’s not what good reporting does. Good reporting is a forward-looking management tool. It surfaces what’s in pipeline right now, identifies which deals are stalling and need active intervention, shows which team members have healthy activity levels and which are running thin, and gives you enough early warning of a revenue shortfall to actually do something about it before it lands.
But it can only do that if the underlying data is accurate, which brings us back, always, to the process. The reports and dashboards you set up should be designed to drive the behaviour you want to see. If new business conversations started per week matters to you, there needs to be a field for it and it needs to feature in your weekly review. If proposal conversion rate matters, every proposal sent needs to be logged and every outcome recorded. If average sales cycle is a lever you want to manage, stage dates need to be accurate.
What the metrics should actually cover
For most consultancies, the reporting that genuinely drives commercial decisions needs to cover five things: new pipeline added each month (not deals being moved around within an existing pipeline, but genuinely new opportunity being identified); pipeline distribution by stage (too much concentration at early stages suggests a conversion problem; too little at early stages is a forward revenue warning); time in stage (deals that stay in the same stage beyond your normal cycle have usually stalled, and that’s almost invisible without a CRM tracking it); proposal conversion rate (of everything you formally put in front of a client, what percentage converts to a win); and average deal size, because changes here often signal something important about positioning or the type of client you’re attracting.
What good CRM use actually looks like in practice
In the consultancies where this works well, the CRM isn’t an administrative logging exercise that happens somewhere in the background. It’s the centrepiece of a short weekly commercial conversation where the whole team reviews pipeline together, challenges deals that haven’t moved, updates close dates that have passed and makes decisions about what needs to happen to move the priority opportunities forward. That conversation typically takes no more than thirty minutes, and it produces real decisions.
Over time, it produces the habit of keeping the CRM current because everyone knows it’s going to be looked at and discussed. The tool becomes useful because it’s used, it’s used because there’s accountability, and the accountability holds because leadership takes the weekly rhythm seriously.
What to do with this
If your CRM isn’t working, resist the urge to change the platform. Instead, answer three questions honestly: do you have a clearly defined sales process with stages that everyone understands and agrees on? Do you have a shared, specific definition of what a qualified opportunity looks like? And do you review pipeline together as a team on a regular basis and use the CRM as the actual basis for that conversation? If the answer to any of those is no, that’s where to start. Fix the process, build the habit, establish the accountability. Then reassess whether the platform still needs changing. In most cases, you’ll find it doesn’t.