Anatomy of an inbound engine: capture to dashboard

An inbound engine is the fixed path an enquiry travels from first contact to reported number: capture, response, triage, CRM record, nurture, dashboard. Six stages, and each one is a point where a lead either moves forward or leaks. Build each stage deliberately once, and every enquiry after that gets handled the same way — whether it arrives at 9am on a Tuesday or 11pm on a Friday.

What are the six stages?

1. Capture — the form, booking link, phone line or shared inbox where the enquiry lands.
2. Response — the acknowledgement and the first human contact.
3. Triage — deciding whether this is a buyer, a browser or a mismatch.
4. CRM record — the enquiry becomes a pipeline entity with an owner, a source and a next action.
5. Nurture — structured follow-up for everyone who does not book straight away.
6. Dashboard — the numbers that tell you whether the five stages above are working.

Most firms have stage one and a loose version of stage four, and improvise the rest. The 90-Day Follow-Up Framework sets out what disciplined follow-up looks like over a quarter; this article describes the machinery that makes it automatic. It is also, in outline, what we install as the Inbound Engine.

How should capture work?

Capture should be short, specific and singular. Short: every field you add to a form costs you completions, so ask only what triage genuinely needs — name, company, email, and one qualifying question such as "roughly how many staff?" or "what are you trying to fix?". Specific: a booking link beside the form lets the ready-to-talk minority skip the queue entirely. Singular: every capture point — form, booking tool, phone note, inbox — must write to the same CRM, because an enquiry that lives only in someone's mailbox is invisible to the rest of the engine.

What happens in the first five minutes?

The first five minutes decide more than the next five weeks. As an industry rule of thumb, contact rates drop roughly 8x once five minutes have passed since an enquiry — the prospect who was on your website, thinking about the problem, has moved on to something else. No team answers everything within five minutes by effort alone, which is why the response layer is automated: an instant, specific acknowledgement to the prospect and an instant alert to whoever owns new enquiries. How to do that without sounding canned is covered in instant response without sounding like a robot.

How does an enquiry become a pipeline record?

This is the mechanism at the engine's centre. When a form is submitted, then a CRM record is created automatically, carrying the source and the answers given — no retyping, no judgement calls. When the record is created, then one routing rule assigns an owner and sets a first-response deadline. When the deadline passes without a logged contact, then the task escalates rather than expires. When the prospect books a call, then the record moves stage on its own; when they go quiet, then a follow-up sequence starts without anyone deciding to start it.

The point of "then" in every clause: nothing depends on somebody remembering. Memory is the component that fails first under load.

What happens to the leads who do not book?

Usually most of them — and this is where the engine earns its keep, because these are the leads that die of neglect rather than rejection. Two nurture tracks cover almost every case. Leads with a stated future timeline go into slow-cadence, CRM-triggered follow-up, which we detail in staying present through a nine-month buying cycle. Everyone else goes onto a regular letter — one asset, sent on schedule, that keeps you present at near-zero marginal cost, as described in the newsletter as a nurture system.

Nurture is email, so the sending layer matters. A new or neglected domain will put your carefully designed follow-up in junk folders; a properly warmed and authenticated mailbox will not — what a 91/100 warm-up score actually means covers that layer.

What belongs on the dashboard?

Four numbers, updated without anyone compiling them: enquiries by source, median time to first response, conversion rate by stage, and the count of leads with no next action set. That last one is the leak detector — any record without an owner and a next step is a lead in the process of dying quietly. If the dashboard needs a spreadsheet and an afternoon to produce, it will stop being produced; it has to fall out of the CRM the engine already writes to.

---

Next step: the Growth System Audit — £450, seven days, credited against any build — maps where your growth system leaks and what to build first.