Every sales team says they follow up fast. Almost none of them can tell you their median minutes-to-first-touch, because almost none of them measure it. Here's why the number beats the belief.
Ask a sales team how fast they follow up on a new lead and you'll get an answer in adjectives. "Quickly." "Straight away." "Usually within the hour." Ask for the median minutes between a lead landing and the first real touch — a call placed, a message actually sent — and the room goes quiet. Not because the team is slow. Because nobody is measuring.
The research on this has been public for years: contact a lead within five minutes and your odds of qualifying them are on a different curve entirely than at thirty minutes, let alone the next morning. The decay isn't gentle. A lead is a person who was thinking about their problem at the exact moment they filled in your form. An hour later they're in a meeting, at dinner, or on a competitor's calendar. The intent doesn't fade — it relocates.
Most teams accept this in principle and then measure nothing, which means the principle is decoration. Here's what measuring it actually requires, and why "we use a CRM" isn't the same thing.
A start line. The clock starts when the lead record is created — not when a rep opens it, not when it's assigned. If your number starts at assignment, your routing delay is invisible, and routing delay is where most of the time goes.
A finish line that means contact. An automated welcome email is not a first touch; it's a receipt. The counter should stop at the first outbound event a human would recognise as follow-up: an SMS, a call, a voicemail. If your automation counts itself, your number is measuring your software, and your software is always fast.
A stored result, per lead. Not a dashboard average recalculated on demand — a number written onto each record when the first touch happens. Averages hide the tail, and the tail is the story: a team with a 4-minute median and a 9-hour 90th percentile doesn't have a speed problem, it has a weekend problem, or a specific-rep problem, or a specific-source problem. You can only see which if every lead carries its own number.
A definition that survives arguments. Does a missed call count? Does a Facebook lead that arrived at 2am start the clock at 2am or at opening? There are defensible answers either way — what's not defensible is not deciding, because then two people quoting "our speed to lead" are quoting different quantities and both defending them.
Once the number exists per lead, it stops being a slogan and starts being a diagnostic. Segment it by source and you find the ad platform whose leads sit unrouted. Segment it by weekday and you find the Saturday gap. Segment it by rep and the conversation gets specific in a way that "follow up faster, everyone" never does.
This is why speed-to-lead is built into every CRM we install as a stored field, filled automatically, on every lead, with the definition written down. Not because measurement is virtuous, but because an unmeasured five-minute rule is indistinguishable from no rule at all — and the leads it's losing don't file complaints. They just book with someone faster.