Process

How long does it take to automate your lead follow-up?

A realistic timeline from first call to a system that answers, qualifies and books, and what makes projects run late.

Process 24 July 2026 5 min read

The honest answer for a typical service business is weeks, not months, provided the decisions get made quickly. Here is where the time actually goes.

Week one: mapping

We work out where enquiries come from today, what happens to each one, and where they die. This usually involves reading real call logs and real inbox threads rather than a process diagram, because the diagram and the reality rarely match.

The output is a short list of the gaps worth closing first.

Weeks two to three: build

The site or landing pages, the assistant trained on your services and pricing, the CRM wired to every lead source, and the follow-up sequences. This runs in parallel, which is why it is weeks rather than months.

Your involvement here is mostly answering questions: what do you charge for this, what do you refuse, how far do you travel, what should it never say.

Week four: supervised live

The system goes live with every conversation visible to you. We read transcripts daily and correct the assistant where it is wrong, vague, or too eager. This week is not optional. It is where a generic bot becomes something that sounds like your business.

Then: tuning

After launch the work shifts to small adjustments: a question that keeps coming up, a follow-up that is landing badly, a booking rule that needs changing when you get busy.

What makes projects run late

• Pricing that has never been written down. The assistant cannot quote what nobody has defined.
• Waiting on access to the domain, the business profile, the ad accounts, the existing CRM.
• Content: photos of real jobs and a list of services in plain language.
• Too many approvers on small decisions.

None of those are technical. If you want the fast version of this, sort those four out before the build starts.

← All posts