When does a small business need a CRM?
How to decide between a spreadsheet, an existing CRM and a custom system—starting with the work your team actually needs to manage.
By Bozman Horizon ·
Start with the missed handoff, not the software
A small business needs a better customer-management system when important customer work is becoming difficult to see, assign or follow through. That does not automatically mean it needs a custom application. A shared spreadsheet with clear ownership may solve the immediate problem.
Look at recent enquiries. Can you tell who replied, what the customer needs, what was promised and when the next action is due? If those answers live across someone's memory, a text conversation and an inbox, the first job is to define one dependable process.
Five signs your current process needs attention
Watch for enquiries that receive no follow-up, two people contacting the same prospect without knowing it, quotes with no next action, incomplete handoffs after a sale, and reports that require rebuilding the same information each week. These are workflow problems before they are software problems.
For a week, record each missed or duplicated action and what caused it. Distinguish a missing tool from a missing habit: buying software will not fix a process nobody is responsible for maintaining.
When a spreadsheet is enough
A spreadsheet can be a sensible starting point when a small team has straightforward stages, manageable record volume and limited access-control needs. Each lead needs a name, source, owner, stage, last contact, next action and due date. Use consistent stage names rather than free-text descriptions that nobody else understands.
A practical test is whether another person can open the tracker and identify today's follow-ups without asking you. If they can, a simple system may be doing its job. If you need granular permissions, complex relationships or reliable automated workflows, assess those requirements before stretching a workbook further.
When to improve an existing CRM
An existing CRM is worth assessing when you need shared customer history, repeatable handoffs, reminders or integrations. First check whether the platform you already have can meet the requirement with better configuration and cleaner data.
Write down your stages and the evidence required to move between them. For example, 'quote sent' means the customer has actually received a quote; 'won' means your agreed acceptance condition has been met. Assign responsibility for stale records and test the process with a small set of real work before importing everything.
When a custom system deserves a closer look
Custom development may make sense when important requirements cannot reasonably be handled by established tools. Examples might include a distinctive estimating workflow, unusual approval rules or a specific client portal. The requirement needs to be concrete—not simply a preference to own a CRM.
Before committing, define the users, permissions, data export, integrations, backup arrangements, maintenance responsibilities and acceptance tests. Include ongoing support in the decision. A custom build is not automatically cheaper or more secure than an established platform.
Your next step: map one enquiry from start to finish
Take one typical customer enquiry and trace it through first response, qualification, quote, follow-up, acceptance and delivery. Note every handoff and where information is entered twice. Choose the smallest change that removes a real point of failure.
Bozman Horizon starts with that workflow, then assesses whether a workbook, a better-configured platform or a scoped custom system fits. We work remotely with small businesses internationally. A short enquiry helps establish the problem and whether our service is a fit; it is not a commitment to a build.
Not sure where to begin? Tell us what you want to improve.
Keep reading
Why website enquiries get missed between your form, inbox and CRM →