An owner tells me leads keep slipping through the cracks. Someone calls, fills out a form, or gets referred, and then… nothing. Or something, but too late. They’ve tried two CRMs already. Now they’re looking at a third.
Before they sign up for the third one, I’d want to ask a different question: what’s supposed to happen after someone becomes a lead?
What the owner thinks is wrong
“We need a better CRM.” It’s a reasonable thought. The CRM is where leads live, and leads are getting lost, so the CRM must be the problem.
But a CRM is a container. It holds a process. If nobody has decided what the process is, the CRM is an expensive list of names.
What I’d investigate
I’d take a few recent leads, some that turned into work and some that didn’t, and walk through what actually happened to each:
- Where did it come in? Phone, form, email, referral, a text to the owner?
- Who saw it first?
- Who was supposed to respond, and how fast?
- What was the next step after the first conversation?
- Who owned that next step, and when was it due?
- At what point was it “sold”? What happened then?
Usually the answers get vague around the second or third question. “Whoever’s around.” “As soon as we can.” “We’d follow up.”
What’s probably underneath it
The missing piece isn’t software. It’s decisions:
- Stages. What are the steps a lead goes through, and what does each one mean? “Proposal Sent” should mean the formal proposal was delivered, not “we talked about pricing.”
- Ownership. Every lead has one person responsible for the next action.
- Follow-up expectations. How fast do we respond? How many times do we follow up? When do we close it out?
- The handoff. When a lead becomes a job, what transfers to operations? Scope, pricing, exclusions, promises made, schedule commitments, payment terms, special notes.
That last one is the piece almost everyone skips. A lot of businesses have a sales process and an operations process and no bridge between them. That’s where you hear, “Wait, they promised the customer that?”
What I’d change
I’d write the process down first, simply. Five or six stages with plain definitions. A rule that every open lead has an owner, a next action and a due date. Follow-up expectations. And a short list of what has to be handed to operations when something sells.
Then I’d set up the current CRM to match. Stages, required fields, reminders, the handoff. Only if the current CRM truly can’t hold that process would I recommend switching, and then you’d be shopping with a clear list of what it must do.
For a contractor, the handoff list might be scope, exclusions, allowances, schedule promises and anything the customer said on the walkthrough. For a service firm, it might be scope, rates, retainer terms, who the real decision maker is, and what was promised about turnaround. Different words, same idea: the person doing the work should never learn the promise from the customer.
What I’d leave alone
The current CRM, at least at first. Most of the popular ones can handle a small business’s sales process once the process is decided. Switching for the third time without deciding the process just gets you a third set of logins.
The tradeoff
Writing the process takes time, and it’s not exciting. A new tool feels like progress. A conversation about what “qualified” means feels like a meeting. But the conversation is the part that keeps leads from slipping, and you only have to have it once.
The pattern
The tool gets blamed for the decisions nobody made. A CRM can only hold a process you’ve already decided.
So try this: write down what should happen to a new lead in the first 48 hours. Who sees it, who responds, what they say, what happens next. If you can’t write it in a few sentences, the CRM was never going to save you.
If you want help turning that into a process your team will actually follow, bring it to a Systems Fit Call.
