Routing

Your speed to lead is worse than you think

Ask a sales leader how fast inbound gets contacted and you will hear a number. Measure it and you will get a different one.

The short answerThe gap between believed and actual response time is almost always caused by mechanics rather than effort. Nightly sync jobs, round robins that assign to people who are away, notifications nobody reads, and a queue that only gets worked at set times. None of those are visible to a leader looking at a weekly average.

Measure the median, not the average

One lead contacted in four minutes and one in four days averages to a reassuring two days. The median tells you what normally happens, and the ninetieth percentile tells you how bad the tail is. Both matter more than the mean.

The usual mechanical causes

A routing rule that depends on an overnight job. Assignment to a round robin without an out of office check. Notification going to an inbox rather than the place the rep actually works. A lead that lands in a queue nobody owns over a weekend.

Why it compounds

A buyer filling in a form is usually filling in several. The first credible response frames the evaluation. A day of delay does not cost you a day, it costs you the position of incumbent in a comparison you never saw.

What good looks like mechanically

Routing that fires on record creation rather than on a schedule. Assignment that checks availability. Notification in the tool the rep already has open. And a visible queue with a named owner, so nothing sits without somebody accountable for it.

Where the hours actually go

The usual causes, and the fix
CauseWhat happensFix
Scheduled routing jobsA nightly job sets a floor no coaching can beatRoute on record creation
No availability checkLeads go to people who are outCheck calendars or status first
Notification goes nowhere usefulAn inbox checked twice a dayPush to the tool the rep has open
Weekend and holiday gapsUsually the largest single bucketA rota, not software
Two ownership modelsScheduler and CRM disagree on the ownerOne ruleset for both
No fallback ownerA lead matching no rule belongs to nobodyAlways name one

In one engagement, moving from an overnight job to event driven assignment on record creation took first contact from five days to twelve hours without anyone working harder.

Want your own number? The free speed to lead checker reads a lead export in your browser and gives you the median, the ninetieth percentile and the weekend gap.

Measure it this week

  • Median hours from creation to first logged activity, last 90 days
  • The same figure at the ninetieth percentile
  • How many leads were created on a Friday and first touched on a Monday
  • Whether routing runs on creation or on a schedule

Questions

What is a good speed to lead?

Faster is better and the useful target is hours rather than days. The number that matters is your own median over time, and whether the tail is getting shorter.

How do I measure speed to lead in HubSpot or Salesforce?

Compare record creation timestamp to the first logged activity on that record, then report the median and the ninetieth percentile rather than the average.

Does speed to lead still matter for long sales cycles?

Yes, though for a different reason. In a long cycle the first credible conversation sets the frame for the evaluation, even if the decision is months away.

What usually causes slow response?

Scheduled rather than event driven routing, assignment without availability checks, and notifications landing somewhere the rep does not work.

Why do inbound leads go cold before anyone calls?

Usually mechanical: routing on a scheduled job, round robins that ignore availability, and notifications arriving somewhere nobody checks often.

Do we need a lead routing tool?

Not always. Native assignment rules handle most straightforward cases. Tools earn their place on complex matching or instant scheduling.

Why do inbound leads go cold before anyone calls?

Usually mechanical: routing that runs on a scheduled job, round robins that ignore availability, and notifications arriving somewhere nobody checks often.

How should we measure speed to lead?

Compare record creation to the first logged activity, and report the median and ninetieth percentile. Averages hide the tail, which is where the problem lives.

Do we need a routing tool?

Not always. Native assignment rules handle most straightforward cases. Tools earn their place on complex matching or instant scheduling.

Want to talk it through?

Leave an email and I will reply myself, usually the same day. No sequence, and no calendar link unless you ask for one.

One reply from a person. Nothing else.

Got it. You will hear from hello@sapwood.io.

Would rather just book time? Here is the calendar.