Skip to content
LuminaBusiness Advisory

Answers · in depth

Why Follow-Up Fails Even When the CRM Works

The CRM did its job. Every inquiry is in there — logged, time-stamped, assigned a stage. And a striking number of them were never touched again. Across the records we read, the pattern repeats in shop after shop, firm after firm: the system faithfully documents the exact leak it was bought to fix. The software isn’t failing. The ownership around it never got built.

The CRM is keeping perfect records of the leak

Here is the pattern we keep meeting when we read a company’s records: the CRM was bought to stop leads from slipping, it was implemented properly, people mostly use it — and it now holds a faithful, time-stamped archive of every lead that slipped anyway. The system didn’t fail. It did something more uncomfortable: it documented the leak it was purchased to fix, in detail, for anyone who cared to look.

A few scenes — invented as illustrations, but typical of what the records show:

  • Home services: the quote went out of ServiceTitan the same afternoon as the site visit — itemized, photographed, professional. It was never touched again, and three weeks later the homeowner hired whoever called back first.
  • Law: the retainer letter sits in Clio at “sent.” Nobody’s dashboard distinguishes “sent” from “signed,” so “sent” is where the pipeline stops asking questions.
  • Repair and equipment shops: the estimate ages past thirty days in the shop system, drops into a bucket no one filters for, and quietly becomes archaeology.

Different software, different industries, same shape. And in every version of it, the software did exactly what it was configured to do. That is the first thing to accept before anything gets fixed: the CRM is the witness here, not the culprit.

Everyone’s job is nobody’s job

Ask who owns follow-up and you will usually hear “the team.” That answer is the problem. When follow-up belongs to everyone, each rep is locally rational to work the hot new lead in front of them instead of the eleven-day-old quote — and the aging pipeline becomes a commons nobody grazes. No one was negligent. There was simply never a name attached to the stage.

The reporting to catch it usually exists from day one. Most systems will happily show leads with no next activity, quotes with no follow-up date, matters parked at the same stage for a month. But a report only changes behavior when a specific person is expected to open it at a specific time and answer for what it says. A report nobody is paid to open is indistinguishable from no report.

Underneath both sits the quiet substitution that makes the whole thing invisible: “it’s in the system” gets heard as “it’s being handled.” Logging a lead and working a lead feel similar at the moment of data entry and could not be more different sixty days later. A record is not an action. The CRM never claimed otherwise — people did.

Automation without a map, and the hours nobody owns

The next reflex is automation: buy the sequence tool, wire up the drip, problem solved. Sometimes. But automation dropped onto a process nobody has mapped simply automates the chaos it finds. If no one can say what should happen on day two, day five, and day twelve after a quote — and who takes over when the emails run dry — then the sequence fires, replies land in an inbox with no owner, and the leak continues with better tooling. A broken process, automated, breaks faster and at scale.

There is also a gap on the clock that no feature closes. Inquiries arrive at 7:40 on a Tuesday evening and at ten on a Saturday morning; if no headcount covers that window, they wait for Monday triage — and Monday is a long time in a buyer’s life. The one lead-response study we consider worth citing — James B. Oldroyd’s Lead Response Management study (2007, leadresponsemanagement.org) — found the odds of making contact with a new lead dropping roughly 21x within the first 30 minutes. Whatever the exact figure looks like in your business, the direction is not in dispute: the after-hours inquiry that waits until Monday was often answered by somebody else on Saturday.

What actually fixes it

None of what fixes this is exotic, and almost none of it is software. It is ownership, made specific:

  • A named owner per stage. Not a team — a person. Someone whose week goes badly if quotes older than ten days exist, and who has the authority to reassign and escalate.
  • Cadences with escalation. A written rhythm for what happens after a quote or a consult — day one, day three, day seven — and a rule for where the lead goes when a step is missed, so a dropped ball changes hands instead of disappearing.
  • Numbers read weekly, by name. A short, fixed set — new inquiries, untouched leads, aging quotes, follow-ups completed — read aloud in the same meeting every week by the person who owns them. What gets read aloud gets worked.
  • Diagnosis before any new tool. Map how a lead actually moves, nights and weekends included, before buying anything. Often the finding is that the current system is sufficient and the ownership around it is what is missing.

Notice what is absent from that list: a new CRM. In our experience the migration conversation is usually a way to postpone the ownership conversation — and the leak survives the migration intact.

Put a number on the leak before you touch the process

Start with arithmetic, not with software. Our free Leak Calculator takes four numbers you already know — inquiries per month, the share that never gets a real follow-up, close rate, and average job or matter value — and shows what the gap between “logged” and “worked” costs per year. It takes about two minutes.

If the number is small, you have your answer and it cost you nothing. If it isn’t, The Revenue Review is the diagnosis step: $4,500, fixed, two weeks. We read twelve months of your own records — the same ServiceTitan, Clio, or shop-system data described above — name where the money leaves, and hand you a 90-day fix list in priority order with the arithmetic behind every line. You keep your CRM. What changes is that, for the first time, every stage of follow-up has a name on it.

Run the calculator, then book the call. Twenty minutes is enough to tell whether the pattern above is your pattern.

Asked right after

We already run automated follow-up sequences. Why are leads still slipping?
Because a sequence is a step in a process, not an owner of one. Sequences fire, replies land, and the question is the same as before the tool: whose name is on what happens next? If nobody owns the reply, the exception, and the escalation when a step is missed, the automation runs flawlessly around a hole. Map the process first — nights and weekends included — then decide which gaps deserve software, which deserve a checklist, and which deserve a named human.
Should we switch CRMs?
Almost never as a first move. The uncomfortable evidence in your current system — every logged lead that was never touched again — is proof the software captures reality just fine. A migration resets the tooling and carries the ownership gap across intact, at the cost of months of disruption. Diagnose first: if twelve months of records show the leak lives in unowned stages rather than missing features, a new system will faithfully log the same leak in a nicer interface.

The next step

Bring us the process that keeps getting stuck.

A 20-minute conversation about the workflow, the teams and the systems involved — and a straight answer on whether The Revenue Review is the right next step. If it is not, we say that on the call.

Book the 20-minute call