Insights / Demand Generation
Why your CRM is not fixing your follow-up problem
The tool can only support a process you’ve actually designed. Map that first.
“We tried a CRM. It didn’t work.”
We hear it a lot, and the list that follows is usually the same. Nobody used it. The data was wrong. It didn’t talk to our other tools. It felt like more work, not less.
Those complaints are fair. But in most cases the software didn’t fail. The setup did. The CRM was installed like a junk drawer: everything goes in, nothing comes out when you need it.
Meanwhile the original problem is still there. Enquiries come in, sit for a day, get answered by whoever notices, and quietly go cold.
A CRM doesn’t fix follow-up. It supports a follow-up process. If there’s no process, there’s nothing to support.
Where CRM setups usually go wrong
Garbage in, garbage out. Duplicate contacts, half-filled fields and inconsistent stages mean nobody trusts what the system says, so they stop looking.
Too complex, poorly configured. Most CRMs can do almost anything, which means someone has to decide what yours should do. Skip that and people get overwhelmed and underwhelmed at the same time.
Logins aren’t onboarding. If the team doesn’t know how or why to use it, they work around it.
No defined process. A CRM can only track what you tell it to. Without a mapped lead lifecycle, it becomes a glorified contact list.
Tool overload. Forms in one place, email in another, quotes in a third. Without clean connections, someone is copying, pasting and hoping it synced.
No owner. When the CRM is everyone’s job, it’s no one’s. The data rots.
Map the process before you touch the tool
Take one enquiry and follow it, on paper, from the moment it arrives to the moment you know how it ended.
Capture every enquiry in one place.
Web forms, calls, emails, chat, referrals. If some arrive by text to the owner’s phone, that counts. List every door and decide where each one lands.
Give every enquiry an owner.
A named person, not a shared inbox. Decide the rule: by service, by area, by rotation. Decide who covers when that person is away.
Set a response standard.
How fast is a first response, and what does it say? Write the standard down. Then measure whether it happens.
Qualify with written criteria.
Fit, need, location, timing, budget. A few questions your team asks every time, so a good lead gets treated like one and a poor fit gets a polite, quick answer.
Always set a next action.
Every open contact has a dated next step and a person responsible. A record with no next action is a lead you’ve already started to lose.
Record the outcome.
Won, lost, not a fit, no response. And why. That’s what tells you which sources and campaigns produce real work, which matters more as you work out where lead generation breaks.
Once that map exists, configuring the CRM is mostly translation. Stages match the map. Fields match the qualification questions. Tasks match the next actions.
Where email automation fits
Automation should carry the steps people forget, not replace the conversation. Two principles matter more than any template.
Every email needs a job. Confirm the enquiry and set expectations. Frame the problem. Show proof. Explain your approach. Handle the common objection. Offer a clear next step. If two emails exist for the same reason, cut one. If a sequence needs a dozen emails to explain itself, the issue is clarity, not cadence.
Stop on reply. If someone replies and still gets the next automated email, the workflow is broken. Replies should pause the sequence and alert the owner. Buyers should be removed. Cold contacts should slow down or exit.
Say a prospect downloads a pricing guide. One illustrative sequence:
- Day 0: the guide, and what to expect next
- Day 2: the three questions most buyers should ask before choosing
- Day 5: a short example of how a similar project was approached
- Day 9: an invitation to reply with a question or book a call
That’s an example, not a rule. Length and timing depend on your sales cycle. Judge it by replies, booked conversations and qualified opportunities, not opens.
In Canada, commercial email is covered by CASL, so confirm what consent you have for each contact before they enter a sequence.
Improve, integrate or replace
Once the process is mapped, the tool decision gets clearer.
| Option | When it fits | Watch for |
|---|---|---|
| Improve what you have | The tool can do the job and the problem is setup, data or habits | Fixing configuration without fixing ownership |
| Integrate it | Each tool does its job well but information doesn’t move between them | Connections nobody monitors, duplicate records |
| Replace it | The tool can’t support the mapped process, or nobody will use it | Moving bad data and bad habits into a new system |
One system can be simpler. It isn’t required. A sound process across two well-connected tools beats a single platform nobody trusts. Confirm what any integration actually does before you depend on it. Here’s how we approach CRM and automation.
Four checks that keep it working
Adoption. Are the people who handle enquiries using it every day, or updating it on Friday from memory?
Data quality. Pull ten random records. Are they complete, current and not duplicated?
Responsibility. Does one person own the system, the rules and the clean-up?
Measurement. Can you see response time, enquiries without a next action, and outcomes by source?
If you can’t answer those four, the CRM isn’t the problem yet.
The tool doesn’t follow up.
People do.
The process tells them when.
The CRM makes sure nobody forgets.