Home · Insights · Implementation
Speed to lead: the three tools we recommend, and how they connect
An enquiry that arrives while you are with a client is only a problem if nothing in your business can respond when you cannot. The fix is rarely a bigger team. It is three ordinary tools, connected so that the first reply, the record and the booking happen without anyone remembering to do them.
What a speed-to-lead system has to do
Strip away the vocabulary and the job is three things, in this order: catch the enquiry wherever it arrives, answer it and write it down without a person in the loop, and make the next step easy enough to take straight away. Everything else is detail. We covered what that looks like for a service business in our walkthrough of installing a speed-to-lead system. This post is the other half: which tools, and how they connect.
In our experience an enquiry rarely goes cold because someone was careless. It goes cold because it arrived at a moment nobody could act on it: during a treatment, on a job site, at ten at night. A system fixes that by being available at the moments you are not.
The three tools
We are not selling a platform. These are ordinary tools, each of which a small business can already pay for, and the value is almost entirely in how they are joined.
| Tool | Its one job | What you stop doing |
|---|---|---|
| A booking page (we use Cal.com) | Lets a person pick a time themselves, and tells everything else the moment they have | Replying "when are you free?" by hand |
| A CRM (we use Attio) | Holds the person and the deal, so every enquiry has exactly one record and one stage | Keeping leads in an inbox, a spreadsheet and your head |
| A workflow tool (we use n8n) | Joins the other two, sends the first reply, and tells you | Being the person who copies information between tools |
Two small helpers sit alongside them on our own system. Claude drafts the first reply and the report, and Slack carries the alert to us. Swap any of them. A different CRM or booking page works as long as it can talk to the workflow tool, which is the part we would not compromise on, because it is the part that makes the other two behave like one system. Ours runs on our own server in Europe.
How an enquiry travels on our own site
When someone completes our audit, the workflow writes them into the CRM, drafts their report with Claude, and has a second pass check it before it is emailed. If the check fails it regenerates once, and if that still fails a shorter plain version goes out instead, so nobody waits on a technical fault. We describe that failure design in how we built our own audit system.
When someone books a call, a separate short workflow writes them into the CRM, creates the deal at a stage called Call Booked, and posts the booking to our Slack. When someone chats on the site, a reply goes back to them in the chat box, and if they leave contact details the same capture workflow picks them up.
The design choices that matter more than the tools
- One front door. Every source posts to the same capture workflow. There is one place to fix when something changes, and one record per person, however they arrived.
- The record comes first. Writing the enquiry to the CRM happens before anything clever. If a later step fails, the lead is already safe, and you find out from an alert rather than from a missing customer.
- The reply buys time, it does not promise a minute. "Shortly" and "in the next couple of hours" are honest and still fast. Promising a specific minute you might miss is worse than a slower, truthful line.
- Plain beats clever. The first reply is short, written in your voice, and offers one next step, usually a booking link. It does not try to close anything.
What it does not do
It does not replace the conversation. Its job is to make sure the person is acknowledged, recorded and offered a next step while you are busy. The sale still happens between people. We are also careful about what we claim for it: the volumes on our own site are small enough that we will not quote a conversion rate, and a post that does, without showing the work, should make you ask where the number came from.
What to do first, in order
- List every place an enquiry can arrive. Website form, phone, WhatsApp, email, social messages. Most owners find more doors than they expected.
- Connect the busiest door first. One door, fully working, beats four half-connected.
- Write the first reply in your own words. Decide what it says and what single next step it offers.
- Add the other doors one at a time. Each new door should end in the same record.
The outcome to aim for is simple to state: no enquiry waits for you to be free. How that gets built for a specific business is the work behind AI automation for service businesses on Mallorca, and it starts with the same question this post ends on: where does your next enquiry actually arrive?