Do I need a CRM?
A guided check that separates the broad goal - often “improve sales” - from the commercial model, system boundary and prerequisites underneath it.
Start the free checkCRM & systems
Start with what the business needs to keep track of.
If you are choosing CRM, define the requirement before the vendor. If you already have CRM, decide what should live there, what only needs to be visible there, and what may belong somewhere else.
CONSIDERING CRMI have not chosen a CRM yet.
Work out what should improve, whether CRM is the right system, and what requirements to take to vendors.
Start before vendor selection →ALREADY USING CRMI already have a CRM.Look at adoption, visibility, pipeline logic, data and the gap between the system and the business.
See CRM problems →Before CRM selection
Thinking about CRM does not mean CRM is already the answer.
Start with what you expect to improve, how revenue actually appears in the business, and what the system would need to own or see.
CRM Decision Review
Turn the idea of “we need CRM” into a written brief: what should change, pipeline-led or relationship-led, what CRM should own, what it should see, and what must exist first.
See the reviewCRM environments
Different CRMs make different parts of the business easier to see.
That is useful. It also means the platform can shape what management notices first - and what stays outside the picture.
HubSpotLifecycle / marketing-sales
Watch for lifecycle logic and processes that outlive the teams they were designed for.
PipedriveDeal pipelineExcellent sales visibility can make the commercial process look as though it ends at Won.
SalesforceFlexible business modelFlexibility allows old objects, fields, flows and definitions to survive long after their original reason has expired.
Zoho CRMApplication suiteConnected apps do not automatically become one commercial model. Meaning can still change across app boundaries.
Dynamics 365Microsoft ecosystemConnected context across Sales, Power BI, Finance and other tools does not by itself create one management model.
monday CRMWorkflow / work visibilityVisible work and visible commercial state are not necessarily the same thing.
A common pattern
The software may be current. The operating logic inside it may not be.
Teams change. Offers change. Customer journeys change. Ownership changes. The CRM can keep running while stages, fields, workflows and reports continue to represent an earlier version of the business.
That is not automatically a rebuild. The first job is to establish which parts still describe the business and which no longer do.
Across the stack
The important connection may be outside the CRM.
A customer can exist simultaneously as a sales record, a delivery workload and a changing commercial relationship.
Commercial change→Operational demand→Economic result
Review whether your current systems can trace that connection →
When it looks like a CRM problem
Adoption, dirty data and reporting problems can be symptoms.
The CRM may be broken. Or it may be faithfully recording definitions and processes that are no longer useful.
See the CRM problem map →When it looks like a systems problem
Integration is not the same as visibility.
Moving data between tools does not guarantee that the same business event means the same thing on both sides.
See Revenue Visibility Review →Where systems fit
The platform is not the starting product.
Choose the business question first.
COMMERCIAL FLOW£1,950
Commercial Diagnostic
Use when something changed in the business, the expected result did not follow, and several explanations still seem possible.
See diagnosticVISIBILITY£595
Revenue Visibility Review
Use when the systems exist but someone still has to piece the customer story together manually.
See reviewKeep the platform unless there is a reason not to.