CRM
One place every enquiry lands.
Most local businesses do not have a lead problem. They have a lead handling problem: calls in one person's phone, forms in an inbox, messages on a personal profile, and nobody with a complete picture of who is waiting for a reply.
What does setting up a CRM properly involve?
Four things. Capturing every enquiry from every channel into one place automatically, so nothing depends on somebody remembering to log it. Designing a pipeline with a small number of stages that match how your business actually works. Defining who owns what at each stage. And connecting outcomes back to the marketing that produced them.
The most common failure is not technical. It is building a system with fourteen fields and nine stages that nobody fills in, which leaves you with worse data than a notebook because it looks authoritative and is incomplete.
Start with the smallest system your team will actually use, and add to it only when somebody asks for something it cannot do.
What a CRM is actually for
Strip away the software marketing and a CRM does three things: it records who got in touch, it records what happened next, and it tells somebody when nothing has happened for too long.
Everything else is a refinement of those three. Reporting is derived from them. Automation triggers off them. Forecasting, where it is relevant at all, is arithmetic on top of them.
That framing matters because it sets the bar for a successful implementation. A CRM that records who got in touch and what happened next, and that everybody actually updates, is a success. One with detailed custom fields that half the team ignores is a failure regardless of what it cost.
It also explains why the implementation is mostly a process question rather than a software question. The hard part is agreeing who does what and when, not configuring the tool.
How an implementation actually runs
The order here is deliberate. Configuring software before agreeing the process produces a system that fits nobody.
Map what happens now, honestly
Every route an enquiry can arrive by, where each one currently lands, and who is responsible for it. This conversation usually surfaces at least one channel nobody was monitoring, and often a shared inbox with no owner.
Design the smallest pipeline that is useful
Four to six stages for most local businesses: new, contacted, qualified, quoted or booked, won, lost. Each stage should mean something anybody in the business can identify without a rulebook. Nine stages with ambiguous definitions produce inconsistent data that nobody trusts.
- Stages defined by what happened, not by how somebody feels about it
- A clear definition of when something moves and who moves it
- A lost reason, because that is where the most useful data is
Capture everything automatically
Web forms, phone calls, chat, messages and booking requests flowing in without manual entry. Anything that relies on somebody remembering to log it will be incomplete within a fortnight, and incomplete data is worse than none because it looks trustworthy.
See the remaining steps: How an implementation actually runsHide the remaining steps: How an implementation actually runs
Decide who owns what
Who responds to a new enquiry, within what window, and what happens if they do not. A CRM with no ownership rules is a filing cabinet that sends reminders to nobody in particular.
Connect outcomes back to marketing
The source of each enquiry recorded automatically, and the outcome sent back to the advertising platforms. This is what lets campaigns optimise toward customers rather than form fills, and it is the single highest value connection in the whole system.
Train on the version people will use
Short, practical, on the actual workflow, recorded so people can rewatch it. Then check a fortnight later whether it is actually being used, because that is when adoption either sticks or quietly fails.
We would rather ship a small system that everybody uses and expand it than deliver a complete one that half the team works around.
Where enquiries actually leak
Every item here is a process failure that a CRM can catch, and every one of them is common.
- Calls that ring out with no record that they happened, let alone a callback.
- Form submissions arriving at an address nobody checks, or silently failing since a plugin update.
- Messages on a social profile that only one person can see.
- Enquiries that got one attempt and then nothing, when most bookings in a considered category need more than one.
- No record of what was said, so the second conversation starts from the beginning and the customer notices.
See the full checklist: Where enquiries actually leakHide the full checklist: Where enquiries actually leak
- Quotes sent and never chased, which is the largest recoverable pool in most local businesses.
- Past customers never contacted again in a category with an obvious repeat cycle.
- No way to tell which channel produced any of it, so budget decisions are made on instinct.
- Two people contacting the same person, or nobody contacting them because each assumed the other had.
Fixing the first four typically changes more than any change to the marketing that produced the enquiries in the first place.
Migration, and what usually goes wrong
If you already have a system, moving is a real project rather than an export and an import, and it is worth being honest about the risks before starting.
Data quality is the first problem. Existing records almost always contain duplicates, people who have moved on, and fields that were used inconsistently over the years. Migrating that as it stands means importing the mess into a new tool and concluding the new tool is no better.
Read the full breakdown: Migration, and what usually goes wrongHide the full breakdown: Migration, and what usually goes wrong
Field mapping is the second. Systems structure information differently, and a decision has to be made about what to bring, what to archive and what to abandon. The instinct to bring everything is the reason many migrations produce a cluttered system nobody wants to use.
History is the third. Notes, emails and call records attached to a contact are often the most valuable part of a CRM and the hardest to move. Sometimes the right answer is to migrate active records and keep the old system readable for a period rather than attempting a complete transfer.
And the practical one: run both in parallel briefly, with a clear switch date. A hard cutover on a Monday with no fallback is how a fortnight of enquiries goes missing.
Choosing a system
Feature comparison tables are close to useless for this decision. These are the questions that decide whether it works.
| Item | Ask this | Because |
|---|---|---|
| Can it capture every channel automatically? | Yes for calls, forms, chat, messages | Manual entry always decays |
| Will your team actually use it? | Simple enough for the least technical person | Adoption is the only real measure |
| Does it connect to what you already run? | Practice or job management, phone, calendar | Duplicate systems cause duplicate work |
| Can you get your data out? | A full export including notes and history | Otherwise you are locked in |
| Does it meet your sector's requirements? | A business associate agreement in healthcare | Not optional, and not all vendors offer one |
The healthcare row rules out a number of otherwise capable products. It is worth establishing at the start rather than after a trial.
The data questions worth answering first
A CRM holds the most sensitive information most local businesses keep: who your customers are, how to reach them, and often why they contacted you.
Three questions belong in the decision. Where is the data stored and who can access it. What happens to it if you stop paying. And in a regulated sector, does the vendor offer the contractual terms you are required to have, which in healthcare means a business associate agreement.
Read the full breakdown: The data questions worth answering firstHide the full breakdown: The data questions worth answering first
Internally there are two more. Who in your team should be able to see everything, and who should not. And how long records are kept, which is a decision worth making deliberately rather than by default accumulation.
We set these up with access limited by role, with a documented retention position, and with the export route tested rather than assumed. A system you cannot leave is a system that will eventually cost you more than it should.
We do not publish a price for this piece of work on its own, because the right scope depends on what already exists. What is published is the bundle pricing: 2,400, 3,600 or 4,800 dollars a month depending on which channels are running. You can read the full breakdown on the pricing page, and you will get an exact number in writing before anything starts.
How to tell it worked
Adoption first, because nothing else is measurable without it. What share of enquiries appear in the system, and what share of records are actually being updated. If those are low, every other number is fiction.
Response time to new enquiries, which is the operational number automation and ownership rules exist to move.
Contact attempts per enquiry, since most bookings in a considered category come after more than one and most businesses make exactly one.
Conversion rate from enquiry to customer, by source, which is the number that changes how a marketing budget should be allocated.
Lost reasons, aggregated. This is the most underused report in any CRM and it will tell you whether you are losing on price, on availability, on speed of response, or on something you can fix this month.
What to ignore: total records, which grows regardless of whether anything is working.
How this connects to the rest
The CRM is the foundation under marketing automation, which triggers off what the CRM records, and it is close to pointless to build automation without it.
It is what makes conversion tracking complete. Once the CRM knows which enquiries became customers, that signal can go back to the advertising platforms so they optimise toward outcomes rather than form fills.
It connects to call tracking, since calls are the majority of enquiries for many local businesses and are invisible without it.
And it is the reason we can answer the question every acquisition service is judged on: which channel produced the customers, not which channel produced the leads.
Find your last ten enquiries in one place.
If you cannot, that is the problem. Not the software you do not have, the ten enquiries you cannot currently see in one list.
Straight answers.
Do we need a CRM at all?
If you can list every enquiry from the last month with what happened to each one, and nothing was missed, then not urgently.
Most businesses that try that exercise discover they cannot, which is the answer.
Do we have to replace our current software?
Usually not. Most practice management and job management systems can be connected rather than replaced, and replacing something your team already knows carries costs that never appear on the invoice.
Where a replacement genuinely is right, we will make the case rather than assume it.
How long does an implementation take?
The configuration is usually days to a couple of weeks. Agreeing the process, and getting the team actually using it, is where the time goes and it is measured in weeks.
Anyone quoting an implementation purely on configuration time has not accounted for the part that decides whether it works.
What if our team will not use it?
Then the system is too complicated or the process was never agreed, and both are fixable. The usual cause is too many required fields and too many stages.
We would rather ship something small that everybody uses and grow it than deliver something complete that half the team works around.
Is our customer data safe?
That depends on the system and on how access is set up, which is why we answer it before choosing rather than after. We limit access by role, document where data is held, and test the export route.
In healthcare, any vendor handling patient information needs a business associate agreement, and that requirement rules out several otherwise capable products.
Can we get our data out if we leave?
You should be able to, including notes and history, and it is worth testing that before you depend on the system rather than at the point you want to leave.
A platform that makes export difficult is a platform that will eventually cost you more than its subscription.
Where this comes from.
Primary documentation and published research behind the guidance on this page.
- HHS guidance on HIPAA and online tracking technologies (opens in a new tab)
- HIPAA and marketing, U.S. Department of Health and Human Services (opens in a new tab)
- CAN-SPAM Act compliance guide, FTC (opens in a new tab)
- Data security guidance for business, FTC (opens in a new tab)
- Google Tag Manager Help (opens in a new tab)
Talk to the team
A short call, a look at how the business currently shows up, and a straight answer on what we would do first.