Start with what you hope CRM will improve - not a feature list.
Tell me the company name, what made you start looking at CRM and what you use today. “Improve sales”, “get everything in one place” or “we are outgrowing spreadsheets” is enough to start.
I look at the business before we speak.
Offer, customers, commercial model and the systems you already appear to use.
We separate the outcome from the software.
What you expect CRM to improve, what is difficult today and whether the need is pipeline-led, relationship-led or something else.
We decide whether there is a useful next step.
CRM Decision Review, a clearer requirements exercise, another system first - or no CRM project yet.
You do not need to know your CRM requirements yet.
“We want to improve sales” is enough.
“Customer information is scattered across people and spreadsheets” is enough.
“We want to know what every customer has bought” is enough.
“We are growing and I do not want the current way of working to break” is enough.
The first job is to work out what those statements imply - and whether CRM is actually the system that needs to change.
Do not prepare a feature list for me.
If you already have notes, bring them. Otherwise the current software list and the reason CRM entered the conversation are enough.
“Not yet” is a valid answer.
The problem may sit in CRM, product or SKU structure, quoting, delivery, finance, or simply in an undefined commercial process. The call does not assume a CRM purchase is the right next move.
This page is for the decision before CRM.
If CRM is already in place and the issue is adoption, reporting, forecasting, customer visibility or the way the system represents the business, use the regular Discovery Call instead.
Tell me what you hope CRM will make better.
I research the company before we speak. You do not need to diagnose the problem first.