You bought a CRM to support the growth plan. But have you decided what it actually needs to measure?

Most of the founder-led businesses I work with don't struggle with CRM because they picked the wrong software.

They struggle because the growth plan never got translated into something people can actually run day to day and something management can actually trust.

Here's what that looks like in practice. The business buys a CRM to "support growth." It builds a pipeline, imports contacts, adds fields, creates dashboards, asks the team to keep it updated.

Then a few months in, the same questions start doing the rounds:

-       Why does nobody trust the forecast?

-       Why are we still working from spreadsheets?

-       Why does every salesperson describe the pipeline differently?

-       Why are customers going quiet before anyone notices?

-       Why does the team seem busy, but revenue still feels unpredictable?

None of that's really a software problem. It's a commercial-design problem.

The question underneath all of it is this: how well has your business actually translated its growth plan into something people can operate and management can use?

Before you buy, replace, automate or integrate anything, start there.

The five questions to ask first

These aren't the usual CRM survey questions. They're about whether the business can actually make and act on the commercial decisions its growth plan depends on.

1. If your growth plan says you need another £500k of revenue, could you show today how much of that's expected to come from new customers, existing customers and re-engaged accounts?

I ask this a lot, because "grow revenue by £500k" isn't an operating plan, it's an arbitrary number - a wish list. It could come from new customers won through outbound activity, referrals, partnerships or marketing. It could come from existing customers buying more, renewing or adding new services. Or it could come from previously valuable customers being re-engaged through proper account management.

Each of those needs something different from the business. New-customer revenue needs enough qualified pipeline and a sales process that actually converts. Existing-customer growth needs proper account management and a clear reason to expand. Re-engagement needs a deliberate list of dormant accounts, a real reason to get back in touch and someone who owns doing it.

If your CRM can't show you the mix behind that £500k, you've got a target. Not yet a plan.

I like to see it laid out simply:

Revenue source	Annual target	Commercial requirement
New customers	£200,000	Qualified pipeline, conversion and onboarding capacity
Existing customers	£220,000	Retention, expansion and account plans
Re-engaged accounts	£80,000	Prioritised target list and win-back activity

The exact split will differ business to business. The discipline behind it shouldn't.

2. If one of your previously good customers started buying significantly less, would your CRM catch it and give someone a clear next step?

Most CRMs I see are built to record opportunities, not to watch customer health. They'll show you every detail of a quote that hasn't closed yet, but they won't tell you that a long-standing customers spend has quietly dropped by 30%, 50%, more. Nobody built that alert, so nobody sees it, until the order that used to arrive every month just... doesn't.

I like a simple rule here. If a top 20 customers spend over the past 90 days drops below half their normal average, flag it and give the account owner a task to review it within five working days.

The exact number matters less than the logic. Decide what "healthy" looks like for an account. Decide what counts as a warning. Give someone ownership of the next move. And write down what you learned so it isn't lost next time.

A CRM that only records what already happened is just like a filing cabinet. One that spots the change and prompts someone to act is actually managing the account.

3. How many times does the same customer or sales information get entered, copied or updated across your CRM, email, order system and spreadsheets?

There's a quiet kind of waste in a lot of growing businesses. It's rarely about the volume of admin. It's about the same information being handled two, three, four times before anyone acts on it. A lead comes in by email. Someone enters it into the CRM. The quote lives somewhere else. The order goes into another system. The account history's split between inboxes. And somewhere along the way, someone builds a spreadsheet because they've stopped trusting the CRM report altogether.

Not all admin is waste, to be clear. A good discovery note, a clear next step, an honest forecast, that's just doing the job properly. But typing the same detail into three places isn't. Neither is hunting across systems to work out whether a customers actually ordered.

My rule is simple: capture it once, use it wherever it's needed. Every time the same information gets entered twice, you lose time and you introduce variation, because no two people type the same thing the same way twice.

Sage's research suggests better digital processes, e-invoicing being one, could save small UK firms up to five hours forty minutes a week, worth around £11,300 a year. That's finance research rather than a CRM benchmark, but the principle holds everywhere: manual, fragmented processes eat capacity that should be going towards growth.

The goal isn't "integrate everything." It's finding the handful of handoffs causing the most friction and fixing those first.

4. If three people updated the same type of opportunity today, would they record it the same way and would the numbers actually mean the same thing?

Ask three salespeople what "proposal sent" means and you'll often get three different answers. One means "I emailed the document." Another means "the decision-makers confirmed they'll review it." A third means "we've presented it and agreed when we'll follow up." All three might be acting perfectly reasonably. But none of them are describing the same commercial reality and if all three show up in the CRM under the same stage, your forecast's misleading before anyone's even opened the dashboard.

The same thing happens with lead sources, lost reasons, opportunity values, probability, close dates, account status, wherever people are left to interpret a field their own way.

This isn't really a data-quality problem. It's a shared-definition problem. The business needs to agree, very early on,  what has to be true before an opportunity moves stage, what counts as qualified, what a realistic close date actually means and what should happen when a deal stalls.

You don't need a rulebook for this. You need enough consistency that management's looking at one version of reality rather than a set of personal habits. Constrain the fields where consistency matters. Leave the free text open where judgement and relationship context genuinely belong. Get that balance right and the CRM stops being a compliance exercise and starts being useful.

5. When you look at your CRM dashboard, how many of those numbers actually change what you or your team do next?

This is probably the sharpest of the five, because it separates real management information from what I'd call dashboard furniture. Most CRM dashboards are busy: activity counts, contact totals, total pipeline, charts that look reassuring in a monthly meeting. But busy isn't the same as useful. The real test isn't whether a number's visible. It's whether it's ever changed a decision.

Ask, for every measure: if this moved materially next month, would we actually do something differently? Who owns that decision? Does it connect to pipeline, revenue, retention, margin or risk? Is the data behind it good enough to trust? Would anyone notice if it vanished?

If you can't answer those, it's probably furniture.

A useful founder dashboard is usually smaller than people expect. Something closer to: qualified pipeline against target, revenue mix across new, existing and re-engaged, where deals are getting stuck, which accounts are at risk and whether you can trust the forecast. That's enough to run a proper conversation.

The most useful CRM isn't the one with the most reports. It's the one that makes the next decision easier to see and harder to ignore.

The eight numbers actually worth tracking

Startups and growing SMEs don't need forty KPIs. They need a small set that tells them whether revenue's likely to arrive, from where, at what pace and how confidently.

-       Qualified pipeline coverage. The value of properly qualified opportunities against your revenue target. A big pipeline full of uncommitted or ageing deals doesn't give you confidence, it gives you false confidence.

-       Pipeline velocity. How fast potential revenue turns into closed revenue: number of opportunities, multiplied by average deal value and win rate, divided by average sales-cycle length. It tells you whether enough is moving through the system fast enough to hit the plan.

-       Stage-to-stage conversion. Overall win rate hides the real story. Track conversion from enquiry to qualified, qualified to proposal, proposal to negotiation, negotiation to close. You'll see exactly where deals are being lost or stalling.

-       Win rate by segment. A blended win rate can hide a lot. You might convert referrals brilliantly and struggle with paid leads, win fast in one sector and grind through long, low-margin cycles in another. Segment by whatever should actually inform your decisions, customer type, source, product, geography or deal size.

-       Sales-cycle length and deal age. Cycle length tells you how long revenue takes to arrive. Deal age tells you which live opportunities have gone quiet. If the cycle's lengthening, there's a revenue gap forming even if the pipeline still looks healthy.

-       Forecast accuracy. Compare what you expected to close against what actually closed. This isn't about catching people out, it's about finding out whether your categories, close dates and probabilities mean anything in practice.

-       Revenue mix. New, existing and re-engaged, this is where the growth plan gets tested against reality. If new business is underperforming, is existing-account growth picking up the slack, or are you just not noticing yet?

-       Retention, contraction and expansion. For any recurring or relationship-led business, new sales are only half the story. Track renewals, repeat orders, lost accounts and expansion, whatever that looks like for your model.

The right metric depends on the business. The principle doesn't: growth's more robust when you're protecting and expanding what you've already got, not just replacing it.

Three things that look like progress and aren't

Total activity logged. Calls, emails, meetings, tasks, they're useful for spotting whether a process is being followed. But activity's rarely a reliable predictor of revenue. Someone can send a hundred low-quality emails and create nothing. Someone else can move a valuable account forward with three good conversations. Only track activity when it connects to an outcome, qualified opportunities created, next steps secured, at-risk accounts contacted. Activity should explain performance. It shouldn't be mistaken for it.

Raw lead volume. More leads look like progress while quietly creating more noise and a worse pipeline. The question was never "how many leads did we generate." It's how many became genuinely qualified and what revenue did they actually create. A high volume of poorly matched leads isn't a marketing win; it's usually a targeting problem.

CRM usage and record completion. Login counts, contact totals, how complete the database looks, these are adoption indicators at best. They're not commercial outcomes. A full database isn't a healthy customer base. Frequent logins aren't evidence of good decisions. Fields filled in under pressure just because they're mandatory often create data nobody should trust.

Ask instead whether opportunities are current and have a next action, whether forecasts are getting more accurate, whether at-risk customers are being caught earlier and whether the team's spending less time reconciling systems and more time with customers.

The part nobody puts a number on

It's not just that poor CRM design produces bad data. It quietly eats commercial capacity too.

One UK field-sales study found reps spend just 27% of their time actually selling, administrative burden was the main reason cited. I wouldn't treat that as gospel, but it's worth checking against your own numbers rather than dismissing it.

Here's what that looks like in cash terms. Take a business with twelve people across sales, account management and commercial admin. If each of them loses just forty-five minutes a day to duplicated entry, switching systems, chasing missing information and correcting records, that's 45 hours a week. Across a working year, that's 2,070 hours. At a conservative £30 an hour fully loaded, that's £62,100.

That's not automatically £62,100 of lost revenue. It's £62,100 of capacity tied up in friction that didn't need to exist, time that could have gone into responding faster to inbound opportunities, holding better discovery conversations, protecting accounts showing early signs of decline, or building expansion with the customers you've already got.

There are around 1.37 million UK private-sector businesses with somewhere between one and 49 people. Plenty of them are big enough to feel the weight of running several disconnected systems, but too small to have anyone whose job it is to fix it. That's usually where the friction gets normalised: "that's just how we do it." It shouldn't be.

How you actually fix it

The answer isn't necessarily a more expensive CRM. It's clearer commercial design.

Scope before you shop. Start with the operating questions, not the demo. Map how an enquiry becomes a customer, how an order becomes visible, how a renewal gets managed, how you'd know a customers at risk. Work out what management actually needs to decide and the minimum information needed to decide it.

Design the data around the decisions. For every field, report or automation, ask what decision it actually supports. If you can't answer that, don't make it mandatory. Agree your critical terms properly, what counts as qualified, what each stage means, what triggers intervention.

Capture once, standardise where it matters. Automate wherever a reliable system can already provide the answer. Constrain choices where consistency genuinely matters. Don't make people copy data between systems or guess at vague fields. But leave real room for judgement where a dropdown can't capture what's actually going on.

Integrate the handoffs that matter most. You don't need a fully automated tech stack on day one, just fix the handoffs causing the most repeated work or customer risk first: enquiry into CRM, CRM into quotation, order status back to the account, activity captured against the customer, spend changes flagged for follow-up. Buy for the workflow, not the feature list.

Treat adoption as change, not training. Nobody adopts a system because they were sent a guide. Show people what's actually in it for them. If the redesign saves an account manager four hours a week, say so and mean it. Train by role and real workflow, not by feature. Make the essentials non-negotiable, keep them lean enough that people can see the point, then actually use the data yourself. The moment leaders go back to spreadsheets, the team learns exactly how much the CRM really matters.

The commercial truth

A CRM shouldn't be somewhere salespeople deposit information for management to look at later.

It should be a shared view of where growth's actually coming from, which customers need attention, where revenue's getting stuck and whether the growth plan's still credible.

Before you invest in another tool, another dashboard, another implementation project, go back to the five questions. If you can't answer them clearly, more functionalities won't fix it. Define the commercial logic first. Then build the system around it.

If your CRM gives your people selling time back, makes risk visible earlier and helps everyone make better decisions, it's doing its job. If it just gives the business more fields to fill in, it's part of the friction.

Not sure where the friction sits?

If your CRM feels like more administration than commercial support, a 30-minute diagnostic call can help clarify what's actually going on today and what "good" would look like for your business.

We'll look at where information's being duplicated, lost or manually reconciled, whether your CRM's measuring what your growth plan actually depends on, what your management information needs to support and the quickest wins to give the team time back.

You don't need a perfect brief or a ready-made solution to book one. In 30 minutes, I can usually see the main commercial and process issues and outline some practical next steps.

Book a free 30-minute CRM and commercial-process diagnostic call.