# The Handoff No. 1: The lead that arrives late

> Canonical page: https://wayhatch.com/handoff/001-the-lead-that-arrives-late/
> Evidence label: Conceptual blueprint. Definitions: https://wayhatch.com/about/evidence-labels/
> Updated: 26 October 2026 (2026-10-26). Publisher: wayhatch, wayhatchai@gmail.com
> Published: Tuesday 27 October 2026. Author: Marcelo.

Why an inbound lead reaches Sales late and without the reason it qualified, and the routing workflow that closes the gap.

Someone fills in the demo form on a Tuesday afternoon. The lead lands in the CRM, waits in a queue and reaches a rep the next morning. The rep opens it, sees a name and a company, and starts the call by asking what they were interested in.

That is this issue’s leak. The lead arrived late, and it arrived without the reason it qualified. Both faults usually sit in the routing layer between the form and the rep. Most teams build that layer once and then leave it alone.

## Why it happens

There is rarely one broken rule. It is usually a few of these at once.

- The definition was never agreed. Marketing calls a lead an MQL on one set of criteria and Sales accepts it on another, so leads wait while someone decides whether they count.
- Matching is weak. Someone at an existing customer fills in the form, nothing links them to the account, and the lead goes into round robin instead of to the account owner.
- Nobody owns the rules. The routing logic was written by whoever set up the CRM, edited several times since and documented by nobody.
- There is no fallback owner. When no rule matches, for a new region or a rep on leave, the lead sits unassigned and nothing tells anyone.
- The reason does not travel. The form answer and the criterion the lead met stay in Marketing’s system, and the rep gets a name.

None of this appears on a dashboard as one number. It shows up as Sales saying the leads are poor and Marketing saying Sales is slow.

## The workflow in five lines

- Marketing and Sales agree in writing what makes a lead sales-ready and how quickly it gets a first response.
- Each lead is checked against that definition, and the criterion it met is written on the record.
- The lead is matched to its account. Uncertain matches go to review instead of creating a duplicate.
- Rules run in a fixed order, from customer owner and open opportunity owner to named accounts and territory round robin, and end with a named fallback owner.
- RevOps escalates any lead that misses the window and audits a sample of routed leads each week.

[Read the lead routing workflow and copy the rules template](https://wayhatch.com/workflows/lead-routing/)

## One thing to do this week

Export last month’s inbound leads to a spreadsheet. For each one, note whether it had a named owner, whether the first personal touch happened inside the window your team agreed, and whether the record carried the reason it qualified.

If your team never agreed a window, that is the first finding. Ask Sales leadership what they believe it is, then compare that with the timestamps.

One month done by hand is enough. It gives you something to bring to the definition conversation besides opinions.

## How far we tested it

Not far yet. The lead routing workflow is a conceptual workflow with a synthetic example built on invented leads, so you can see the inputs and the outputs. It has not been run on a live CRM, and we report no response times or conversion results from it.

If you run the audit and are willing to share what you found, anonymised, write to wayhatchai@gmail.com. It would be the first real data this workflow has seen.

Next issue in two weeks.

Marcelo