In this article
- Readiness: what the checklist assumes
- 1–5: data fragmentation, missed follow-up and visibility gaps
- 6–8: separate CRM needs from broader process problems
- 9–10: assess readiness, users and the minimum scope
- Do we need a CRM yet?
- Mistakes, and what a CRM changes when it is the right answer
- Questions owners ask
Readiness: what the checklist assumes
That you have, or will write, a sales process — because a CRM holds a process, and without one it holds noise. That at least one person will be responsible for the system’s discipline: the queue, the fields, the follow-ups. And that the owner will use it to look, rather than only to inspect — a CRM that exists so the owner can check on people is abandoned by the people within a quarter.
Count first: enquiries per month, open deals, active customers, people who touch them. Two salespeople and forty deals is already past what a spreadsheet manages honestly.
1–5: data fragmentation, missed follow-up and visibility gaps
1. Customer details live in individual phones, notebooks and inboxes, and when a salesperson left last year their customers went with them. 2. Two people have called the same enquiry, or nobody has, because the enquiry went to an inbox everyone can see and nobody owns. 3. Follow-ups happen when someone remembers; a proposal sent three weeks ago has not been chased because nothing reminded anyone. 4. The owner learns about a lost deal from the accounts ledger, or about a complaint from the customer, and asks for the pipeline by messaging each salesperson on Sunday night. 5. Nobody can say, without a day of work, how many enquiries came last month, from where, and how many became customers — so the marketing budget is judged on feeling.
Any three of the five, in a business with more than one person selling, is a CRM problem. All five is a business running on memory.
6–8: separate CRM needs from broader process problems
6. Salespeople do not follow up because they do not know they should — no written standard, no sequence — and a CRM will schedule follow-ups nobody has agreed to make; write the standard first, then the CRM enforces it. 7. Deals stall because discovery is weak or proposals are slow — a skills and process problem the CRM will record faithfully and not fix. 8. The owner wants a dashboard of activity — calls made, emails sent — to manage the team by counting; a CRM will produce it and the team will produce the activity, and neither will produce customers. In each of these, the CRM is a mirror, and the reflection is the process.
The honest test: if the process and the discipline existed, would a spreadsheet be enough? For a very small team, sometimes yes. The CRM is worth buying when the process exists and the spreadsheet cannot carry it — the assignment, the reminders, the integrations, the shared view.
9–10: assess readiness, users and the minimum scope
9. Users: who will enter and use data daily — the salespeople, the coordinator, the owner — and are they willing? A team told about the CRM on the day it launches resists it; a team that helped write the process and piloted the tool adopts it. Name a champion among the salespeople, not only among the managers. 10. Minimum scope: the smallest implementation that fixes the five signs — contacts and companies, a pipeline with your stages, tasks with reminders, the website form and WhatsApp writing in, and two views for the owner. Not the marketing automation, the quoting module, the customer portal or the AI assistant — those come after the basics have been used for a quarter.
A CRM bought at minimum scope, configured to the process and used daily, is worth more than the full suite configured by a consultant and used by nobody.
Checklist · use it here or print it
Do we need a CRM yet?
Tick what is true. Five or more in the first two groups means a CRM will pay for itself; the last group tells you whether you are ready to implement one, or whether a process has to be written first.
0 of 14 done
If the first two groups are ticked and the third is not, the problem is process before software: write the stages and the response standard, then implement the CRM to hold them.
What you enter stays in this browser and is not sent to us.
Mistakes, and what a CRM changes when it is the right answer
The mistakes: buying a CRM to fix a process that does not exist; buying it for the reports; launching on everyone at once with sixty fields; the owner never opening it; no champion in the team; and confusing an unused CRM with a wrong CRM, when it was simply never configured. A safeguard: before buying, write the sales process on one page and ask whether the current tools could run it if people used them.
When it is the right answer, a CRM changes three things within a quarter: every enquiry has an owner and a next action, the owner sees the pipeline on a phone without asking, and the marketing money is judged on customers by source. This is the CRM requirements work we do with SMEs — the process page, the signs audit, the readiness and user assessment, the minimum scope, and the selection that follows — and the free audit starts by counting how many of the ten checks your business fails today.
Questions owners ask
At what size does a business need a CRM?
When more than one person sells, or when one person has more open deals and enquiries than they can hold in their head — roughly forty deals or a few dozen enquiries a month. It is about volume and shared work, not headcount.
Can a spreadsheet be enough?
For one salesperson with a written process and discipline, for a while. It fails at assignment, reminders, integrations and a shared view — the moment a second person needs to see the same deal.
Will a CRM make my team follow up?
It will remind them, assign them, and show the owner who did not. It will not create the standard or the will; those come from the process and the manager. A CRM enforces a discipline that already exists.
We bought one and nobody uses it. Do we need a different one?
Usually not. Check whether it can run your process and your five daily scenarios; most abandoned CRMs were never configured to the process, and a fortnight of setup with the team revives them.
What should the first version include?
Contacts, companies, your pipeline stages, tasks with reminders, the website and WhatsApp writing in, and two owner views. Everything else after a quarter of daily use.
What does GullySales do?
The signs audit, the process page, the readiness and user assessment, the minimum scope, and then the selection and implementation if a CRM is the answer — with an honest note when the fix is the process instead. Scoped in the free audit and priced in writing.