Questions we answerProcess and ownership
Is my business too small for a CRM?
Often yes, for now. A CRM solves a handoff problem, not a memory problem — and a half-adopted one is a worse record than the spreadsheet it replaced.
Free · a few minutes · starts from “Something in the team isn't working”
The short answer
Often yes, for now — and almost nobody writing about this will say so, because almost everybody writing about it sells one. A CRM solves a handoff problem, not a memory problem. You need one when more than one person touches the same customer, when things are being dropped between people, or when somebody leaving would take the pipeline with them. While one person holds the relationships and a shared sheet is current, it adds administration and removes nothing.
Search this question and every answer is no, you are not too small. That is worth noticing, because the pages saying it are written by the companies selling the software, and the answer was decided before the page was.
The honest version has a threshold in it. A CRM earns its keep when customer information has to survive being passed between people. Until that is true, it is a place to type things that one person already knows, maintained by people who do not yet need it — which is how a small team ends up with a database less accurate than the spreadsheet it was supposed to replace.
Is it really this?
Worth checking before you spend anything. These are the signals that tend to tell the two apart.
Signs it is
- Two or more people talk to the same customers and have to ask each other what was said.
- Follow-ups are being missed at the point where work passes between people.
- If one person were away for a fortnight, nobody could pick up their conversations.
Signs it's something else
- One person holds every relationship and has not dropped anything.
- The shared sheet is current, and everybody who needs it can find it.
- The real problem is that nobody has decided who follows up, which a tool will not settle.
What's usually behind it
- A growing customer list and a sense that a spreadsheet is unprofessional, rather than that it is failing.
- Something genuinely dropped — a follow-up missed, a renewal forgotten — which may or may not be a tooling problem.
- A new salesperson or account manager joining, which is the first moment a handoff exists.
What people usually get wrong
- Buying a CRM to fix a discipline problem. If follow-ups are not happening now, a new place to record them does not change that.
- Half-adopting one: three people using it differently, data rotting, and the spreadsheet quietly continuing in parallel.
- Choosing the tool before deciding who owns the record and what has to be in it.
The options, and when each one fits
In no particular order. Which of these fits depends on your situation, not on the question you typed.
Keep the shared sheet
One person owns the relationships, nothing is being dropped, and everybody can see it.
Fix the handoff first
Things are dropped where work passes between people. Decide who picks it up, then consider a tool to support that.
Use what you already pay for
A shared inbox, an accounts package or an existing product already holds most of this and is not switched on.
Adopt a CRM properly
Several people touch the same customers, and somebody owns making sure the record is true.
When doing nothing is the right call
If one person holds the relationships and nothing is being dropped, doing nothing is the correct answer rather than a deferral — and it stays correct until a second person needs the same information.
What the diagnostic asks
- What is actually going wrong and how long it has been happening.
- Who owns customer relationships today and how clear that is.
- How repeatable the work is and how much is written down.
- Whether software is already in place for it.
“I don't know” is always an answer. Nothing is assumed on your behalf.
The routes it weighs
Every diagnostic weighs all ten routes. These are the ones that tend to matter for this question — a description of the rules, not a promise about your answer.
Process improvement
Change how the work flows — remove steps, name an owner, fix the hand-offs.
Do nothing yet
Record the issue, set a revisit date, and decide what would change your mind.
Redistribute
Move ownership of the work to where it fits, and make that explicit.
AI Assist
Keep a person in charge and give them AI for drafting, summarising, checking or analysis.
Develop
Build the capability in someone already in the team, with time and support.
What changes the answer
- More than one person touching the same customer is the single strongest argument for a CRM.
- Nothing being dropped and one person holding everything is the strongest argument against, for now.
- A departure that would take the pipeline with it turns this from convenience into risk.
Get your own read
A handful of short questions, then the strongest route for your situation, what's also credible, what we still don't know and what would change our view. No account, no setup.
Related questions
- Nobody owns this work. What do I do?Give it an owner. That is almost always the first move, and it is faster and cheaper than anything else on the list.
- Too much depends on one person. What are my options?Reduce the fragility before it becomes a crisis: write the work down, develop a second person, move adjacent work off them, or decide it is acceptable for now with a date to look again.
- We have too many tools. What should we cut?Count problems, not tools. Ten tools each doing one job cleanly are fine; three holding the same customer list are not.
- How do I fix handoff problems?Work fails at the joins more often than in anyone's hands. Fixing it means agreeing what "ready" means at each boundary — and having someone own the outcome across it.
- Nobody has written our processes down. Is that a problem?Only where a process runs regularly and one person knows it. Documenting everything is a project small teams abandon; documenting a broken process makes the bad version official.
- Projects keep slipping — what should I do?Repeated slippage is information. What matters is where it slips: consistently in the same place is a process problem, everywhere at once is usually over-commitment.