What a CRM Should Do for a Service Business

Operations

What a CRM Should Do for a Service Business

Open your CRM and pick five leads from the last month who never became clients. For each one, answer three questions without opening your inbox, your phone, or asking anybody: what was the last thing that happened, what is supposed to happen next, and whose job is that.

Most owners can answer the first question. The other two are usually a guess.

That is the whole problem, and it is not a software problem. Every one of those records exists. The contact is saved, the email is logged, the notes are in there somewhere. The system did exactly what it was asked to do. It just was not asked to do the thing that mattered.

Saving a contact is not following up

A lot of businesses use a CRM as a filing cabinet with a search box. Names go in, the drawer closes, and everyone feels organised.

Then two assumptions quietly form. The team assumes the software is handling it, because the record is clearly there and clearly logged. The owner assumes the team is handling it, because the tool was bought precisely so this would stop being their problem. Both are reasonable. Both are wrong at the same time, and while they are wrong the client is sitting in silence wondering whether anyone is going to get back to them.

Nobody dropped the ball on purpose. The record just never said whose ball it was.

A tool is not a result

Here is the part nobody selling software mentions. A tool is a capability. A result is a capability that someone has pointed at the right moment, connected to the next step, and checked when it drifts.

Buy ten tools and you have not removed ten jobs. You have added an eleventh, which is running the ten tools. That is why so many owners feel busier after a year of adding software, not freer. Capability was never the constraint. The constraint was that capability still has to be operated by somebody, and that somebody kept being you.

The distance between "I have a CRM that can send a follow-up" and "every lead reliably gets the right follow-up without me touching it" is the entire job. It is setup, rules, ownership, and oversight. It does not happen because the software is good.

The three things a record has to show

The test for whether your CRM is working is not how much it stores. It is whether a person who did not have the original conversation can open a record and know what to do.

That takes three fields, and they are the three most businesses leave blank.

Field	The question it answers	What "blank" actually means
Last event	What happened, and when	Nobody knows if this person has been contacted this week
Next action	What specifically happens next, and by when	The record is a hope, not a plan
Owner	Which named person does it	Everyone is responsible, so nobody is

Follow up soon is not a next action. It has no date, no method and no author. It is a note to nobody. A real next action reads like call Thursday morning to confirm the survey date -- and it has a name beside it.

That last field is the one people resist, because assigning it feels like blame. It is the opposite. An unowned record is the one that gets dropped, and the person it gets dropped on is the client.

Software cannot fix a rule you never wrote

Automation is very good at doing a defined thing on cue. It is useless at deciding what the thing should be.

If your team does not know how a new enquiry is meant to be handled, no amount of configuration will save them. They will clear notifications instead of solving problems, because clearing the notification is the part the system actually asks for. The board looks tidy. The work is not done.

So before you change any settings, write down what should happen. Who replies first. How fast. What that first reply has to contain. When it becomes a call. When it stops. Boring, specific answers -- the kind a new hire could follow on a bad Friday. Then set the software to enforce what you wrote.

This is the same failure that shows up at the front door. A fast reply is not the same as a handled enquiry -- speed only helps if someone owns what comes after it. And it is why your marketing report stops too early: it can tell you the lead arrived, and nothing about whether anyone carried it.

What you are actually buying back

You did not want a CRM. You wanted to stop being the person who remembers.

You wanted to not lie awake wondering whether the quote went out. You wanted to stop asking your team whether anyone got back to the Sandersons. That is a different purchase from software, and no feature list delivers it, because the thing you are buying is the operating layer above the tool -- the rules, the ownership and the checking that turn a capability into something that just runs.

That layer is what Bizi runs for owners who would rather not run it themselves. The software does the sending. Somebody still has to own the operation, and if that somebody is you, you have bought a job rather than a system.

Go and check five records

Open your CRM now. Take the last five enquiries that did not become clients.

For each one: does the record show the last thing that happened, with a date? Is there a specific next action with a deadline? Is there one named person against it?

Count the blanks. That number is not a measure of how disorganised your team is. It is a measure of how much of your business is still being held in your head -- and every blank is a client who is waiting on something nobody has decided to do.