Nobody sets out to run their business on a spreadsheet. It just happens. Someone makes a tab for enquiries, someone else adds a column for "follow-up date", and a year later there are four versions of the file, three of them called final.
We've been on the other side of this many times: a business owner opens a spreadsheet on a screen share, a little embarrassed, and says "I know, it's a mess." It isn't a character flaw. A spreadsheet is a genuinely good first CRM. The trouble is knowing when it has stopped being one.
The spreadsheet isn't the problem. Memory is.
A spreadsheet stores what happened. A CRM's real job is to remind people what should happen next. The moment your process depends on someone remembering to scroll to the right row on the right morning, you're using a filing cabinet to do a job that needs an assistant.
If a lead goes cold because nobody looked at row 214, that's not a people problem. It's a system problem.
Five signs it's time
- Two people have called the same customer this week, and neither knew. Shared context is the first thing to break.
- You can't answer "how many deals are in progress?" without an hour of filtering and a small prayer.
- Someone left, and half of what they knew about your customers left with them.
- Follow-ups live in people's heads, or in their phone reminders, or on sticky notes.
- Everyone has their own copy of the file, and you've stopped trusting any of them.
One of these is normal growing pain. Three or more and it's already costing you money, quietly, in the form of enquiries that never got a reply.
What a CRM should actually do for you
Forget the feature lists for a moment. For a growing business, a good CRM does a handful of things well:
- Keeps every conversation, quote and file attached to the customer, in one place anyone on the team can find.
- Shows a clear pipeline, so you can see at a glance what's new, what's waiting, and what's about to close.
- Reminds the right person at the right time, so follow-ups stop depending on memory.
- Reports on itself: where leads come from, where they drop off, what's worth your time.
Everything else is a bonus. If a tool makes those four things easy, it'll earn its place. If it makes them harder than the spreadsheet did, your team will quietly go back to the spreadsheet, and you'll have paid for the privilege.
Moving over without a revolt
The technical part of a migration is the easy bit. The hard part is people, who have habits and a job to do this week. Some things that help:
- Start with one process. Move new enquiries first. Leave historical data for a calmer week.
- Clean before you move. Merge duplicates and delete the ancient dead ends. Importing mess just gives you a more expensive mess.
- Ask the team what annoys them today, then check the new setup fixes it. Adoption follows relief.
- Keep the spreadsheet read-only for a month, then archive it. A clean cut-off beats a slow fade.
Off the shelf, or built for you?
For many businesses, a well-configured ready-made CRM is exactly right, and we'll happily tell you so. Custom makes sense when your process is genuinely unusual: multi-stage projects, supplier coordination, bookings tied to inventory, or approvals that don't fit a generic pipeline. If you're bending your business to fit the software, that's the signal to look at something shaped around you instead.
Whichever way you go, the goal is the same: fewer things living in people's heads, and more customers hearing back on time. That's most of what a CRM is for.
Once your customer data lives in one dependable place, the next question is what to hand off to software. We walk through that in our practical guide to automating your business with a CRM and AI. And if you're weighing a bespoke system, have a look at how we approach CRM development, or see how the same thinking applies in hospitality in our piece on hotel systems.
