Waggle Dance CRM vs Your Phone Contacts
- Apr 28
- 6 min read
If your "CRM" is your iPhone contacts, you're not alone; most owner-led service businesses start exactly there.
It works for a bit. You save a number, maybe tap in a name that's vaguely descriptive, and you move on. The problem doesn't show itself straight away. It creeps in somewhere around the point where you've got a dozen conversations on the go, and you're spending more time piecing things back together than actually doing the work.
Your phone keeps names. It doesn't keep track of what's happening with those names.
The contacts app was never built for this
There's nothing wrong with your phone; it's doing exactly what it was designed to do. Store contact details. Ring people. Send messages.
What it wasn't built to do is tell you that you promised to follow up with someone on Thursday, that a quote's been sitting unanswered for two weeks, or that a particular enquiry came from a referral and probably needs a bit more care than a cold lead would.
None of that lives in your contacts. It lives in your memory, your WhatsApp threads, a note you made in the car, maybe a voice memo you meant to transcribe. Spread across five or six places, none of which talk to each other.
That's the actual problem. Not disorganisation. Just friction, the kind that builds up quietly until something falls through.
Phone contacts store names and numbers. They don't capture what someone needs, where a lead came from, or what was supposed to happen next. That missing layer is where follow-ups go quiet and work gets lost.The bit that trips most people up
Say you take a call between jobs. You save the contact "Rob Conservatory" or something similar, and you tell yourself you'll call back on Thursday.
Thursday gets busy. You're pricing something, chasing an invoice, dealing with a supplier. Rob doesn't come up. Not because you forgot him exactly, but because nothing reminded you he existed.
That's not a memory problem. It's a structural one. There was no prompt, no visible reminder, nothing to surface Rob at the moment it mattered.
And here's the thing: Rob probably hasn't given up on you. He just hasn't heard back. So he's called someone else.
It happens constantly, in businesses that are otherwise running fine. Good tradespeople, decent consultants, small agencies doing solid work, losing jobs not because they're bad at what they do, but because the follow-up got buried under everything else.
It's not about being careless. New things are loud; older leads are quiet. Without something to surface them at the right moment, they drift, and so does the revenue attached to them.What the average day actually looks like
Most people using their contacts as a makeshift CRM aren't just using their contacts. They're bouncing between:
WhatsApp threads with clients that mix chat and business. Email chains that started months ago. The calendar app, which shows appointments but not context. Notes the app, a notebook, and random voice memos. And whatever they can pull from memory before a call.
Each of those things works on its own. Together, they create a lot of piecing together.
"Did I already quote this person?" "Have I followed up since that meeting?" "What did they say about the budget?" Those questions shouldn't take two minutes of digging to answer.
It's not one broken tool; it's six tools that don't connect. The result isn't chaos, it's a low-level tax on your time and attention that's easy to miss until you add it up.
What a CRM is actually supposed to do
There's a version of CRM software that adds work. Complicated pipelines, mandatory fields, and reporting dashboards nobody looks at. If you've tried one of those and abandoned it after three weeks, that's not a personal failure; it's the software's fault.
A useful CRM does something much simpler: it removes the effort of remembering.
You shouldn't have to remember that someone needs chasing. You shouldn't have to dig through a WhatsApp conversation to find out what you quoted. You shouldn't have to hold five active enquiries in your head while you're trying to price a job.
The right system holds that for you. Not by adding admin by making the thing you'd already be doing anyway slightly easier and more consistent.
Good CRM software doesn't add a process on top of your work. It tidies up the one that's already happening in a scattered way across too many different places.A real-world example
One of the businesses we worked with was a consultancy, a small team, maybe twelve people, and the owner was still hands-on with sales.
They weren't struggling, exactly. Work was coming in. But there was a persistent feeling of being slightly behind proposals out that hadn't been followed up, a few leads that had "gone quiet" that nobody was quite sure about, and a general sense that the pipeline was harder to read than it should be.
We didn't rebuild anything from scratch. We mapped how their sales process actually worked, not how they thought it worked, but what was genuinely happening and built a simple structure around that. Three or four pipeline stages. A clear next action on every deal.
Automated nudges for things that had sat too long.
Within about a month, the difference wasn't a flood of new business. There were fewer things being missed. Leads that previously would have gone quiet got followed up. Proposals that might have been forgotten got a nudge at the right time. Small things, but they added up.
Today's Deep Dive
The three things that actually change
A timeline that makes sense
Instead of reconstructing a conversation from memory and three different apps, you can see the whole thread in one place: when they first got in touch, what they asked for, what you said, and what's outstanding.
A view of what needs doing
Not everything is just what's relevant today. Who's waiting on a response? Who needs a follow-up? Who's close to making a decision? Without having to dig for it.
Reminders that aren't in your head
You said you'd call on Thursday. The system knows that. If Thursday arrives and you haven't, it tells you. That's most of the job done.
If you want to start somewhere practical
You don't need to migrate years of contacts or map out a 10-stage pipeline on day one.
Pick one enquiry type, the one you handle most often, and trace it through from first contact to booked job. What are the three or four things that need to happen? Who moves it forward at each step? What's the most common point where it stalls?
That map, even on a single page, gives you somewhere to start building a 4-process that doesn't rely entirely on memory.
From there, it's about getting your tools to connect. Calls, messages, notes, calendar, when those live in one place rather than five, you stop losing time to piecing together and spend it on the actual work.
Tools like GoHighLevel (GHL) are built for exactly that. Not clever for the sake of it, just genuinely connected in a way that most standalone apps aren't.
How Waggle Dance CRM fits in
If you want something that's already configured for how UK service businesses actually run, rather than a blank canvas you have to build from scratch, Waggle Dance CRM (£149/month + VAT) is designed around that.
Already have a system that's technically set up but not quite landing? CRM optimisation can usually fix that without a full rebuild.
And if the deeper issue is that your business feels busy but slightly chaotic, not a tool problem so much as a process and habits problem, the coaching bundle (£499/month + VAT) works on both together.
FAQs
When does a contacts list stop being good enough?
Honestly, it depends on how much follow-up matters to you. For a lot of people, the tipping point isn't the total number of contacts, it's the point where you realise you've lost track of something that cost you real money.
Do I have to import everything and start from scratch?
Not at all. Starting fresh with new leads while leaving your existing contacts where they are is usually the most sensible approach. You get a working system without the paralysis of trying to organise five years of history before you can begin.
I've set up a CRM before and stopped using it within a month. What makes this different?
Usually, when that happens, it's because the system was built around what CRM software can do rather than what the business actually needed. Too many stages, too many required fields, too much friction to update on the go. The fix is normally in the setup, not the software, getting it to match how work actually moves in your business, not some textbook sales process.
Will it actually save me time or just move where the admin lives?
Done right, it reduces the mental load more than it changes the clock time. Less keeping track of. Less remembering. Fewer moments of "wait, where was I with this person?" That's the main shift; it feels calmer, even if the hours don't look radically different on paper.
If part of your sales process currently lives in your head, and if you're honest, quite a bit of it probably does, you're not doing anything wrong. That's just what grows up naturally when you're building a business and don't have time to stop and systematise everything. The point isn't that you need to work harder. It's that the work you're already doing could land more consistently with a bit of structure behind it. That's what a decent CRM is for. |
