CRM

Customer relationship management (CRM) capability is how reliably an organisation manages commercial data, customer context, opportunities and the next action on each of them. It is a question of adoption, data quality and governed workflow rather than of software. A capable CRM is one the organisation reads its forecast from, rather than one it rebuilds a forecast beside.

No, and the two are frequently confused. Platform choice decides what is possible. Capability decides what actually happens: whether records are maintained, whether context survives a handoff, and whether people have stopped keeping a second version in spreadsheets and inboxes. Replacing a platform without addressing adoption usually reproduces the same condition on new software.

Usually because the record is incomplete in the specific places decisions depend on: stage, owner and next action. Where those are missing, the pipeline is a list of opportunities rather than a statement about what is progressing, and a forecast has to be assembled beside it by somebody exercising judgement that nobody else can examine.

Adoption is the extent to which the people whose work the system describes actually use it. The clearest test is the absence of a parallel record. Where individuals maintain their real pipeline in a personal spreadsheet, or where reporting is rebuilt by hand each month, adoption has not happened regardless of how many licences are in use.

CRM is the commercial record. Revenue operations is a function that aligns marketing, sales and customer operations around one revenue process, and it exists largely to fix what weak CRM causes: broken handoffs, unreliable pipeline data and reporting nobody trusts. The Commercial Transformation Index assesses the underlying record condition, because that is what the function is working with.

Commercial records are split across inboxes, spreadsheets and individual memory. Customer context does not survive a handoff between teams. Open opportunities exist with no owner and no defined next action. Reporting is rebuilt manually because nobody fully trusts the system. These are observable characteristics rather than assessment criteria, which stay proprietary.

One record is treated as the commercial source of truth and is maintained as such. Context travels with the customer across marketing, sales, delivery and renewal. Every open opportunity has an owner, a stage and a next action. Forecasts are read from the system rather than assembled beside it.

Because CRM directly affects Marketing, Sales, Operations, Retention and Customer Success, and Automation, and none of them reports the record as the cause. A forecast assembled outside the system reads as a forecasting discipline issue. Renewal risk invisible until the renewal reads as a customer success issue. The record underneath all of it is rarely the thing examined.

It sets the ceiling. Almost every commercial automation reads from or writes to the commercial record, so automating on top of unreliable data distributes the unreliability at machine speed. This is the most common way an automation programme makes a situation worse while appearing to work, and it is why the Commercial Transformation Index reads the two domains together.

At lower maturity records are split across systems and memory, context is lost at handoff and reporting is rebuilt by hand. In the middle bands one record is the source of truth, stages and ownership are defined, and reporting is read from the system, though lifecycle coverage usually thins after the sale. At higher maturity the record carries the customer through delivery and renewal, and integrations have defined ownership.

A record people trust enough to stop keeping a second one. That is a governance and behaviour outcome rather than a configuration outcome. It requires that what the system asks for is what the work actually needs, that data arriving from the website and marketing is usable on arrival, and that reporting read from the system is accurate enough that nobody rebuilds it.

Not fully. Response times, follow-up and whether context survives a handoff are all visible to anybody who becomes a prospect, and they are a genuine partial reading. Establishing adoption, data quality and reporting integrity takes evidence from inside, so the Commercial Maturity Assessment covers those through self-reported evidence. The Full CTI Audit reviews the record itself against that description, and is the only route that produces a validated reading. This is the domain where description and reviewed evidence most often diverge.

With the three fields decisions actually depend on: stage, owner and next action. Establishing those reliably on open opportunities changes what the pipeline can tell you within one cycle, and it does so without a migration. Wider data quality work is worth doing afterwards, when there is a working record to improve rather than one to rescue.