Written CRM Decision Brief
What should improve, pipeline-led / relationship-led / hybrid, what CRM should own, what it only needs to see, missing prerequisites and requirements to take to vendors.
See the review →Before software selection, when the story is scattered, or when the result is visible but still unexplained.
You do not need to diagnose the root cause before choosing a route.
You are considering CRM because something should work better, but the business requirement is still broad or partly undefined.
The answer is scattered across CRM, delivery tools, spreadsheets, reports or people, so someone has to reconstruct the story.
A sensible change did not produce the expected result and several explanations still sound plausible.
Each product ends with a written artefact that makes the next decision explicit.
What should improve, pipeline-led / relationship-led / hybrid, what CRM should own, what it only needs to see, missing prerequisites and requirements to take to vendors.
See the review →What is already visible, what is missing, where the customer or revenue story breaks, and what management needs to recognise or record next.
See the review →What happened, which explanations the evidence supports, what remains unknown, and the smallest useful next test before the business changes more.
See the diagnostic →The review or diagnosis is not a pretext for a software project.
Opportunity, relationship, qualification, handover or account logic where the evidence shows the process is too implicit.
Define what the person responsible for the whole outcome needs to see before choosing the dashboard or implementation.
Configuration, fields, reports or workflow changes when the current representation no longer fits the business.
Connect tools or remove manual work only where the underlying definitions and process are already clear.
Specialist technical delivery where the required capability cannot be created sensibly with existing tools.
Sometimes the useful conclusion is that the proposed CRM, hiring, product or sales initiative is not the problem that needs solving.
These are three different questions. They should not be forced into one software or one diagnosis.