"Speed to Lead: how fast a new lead gets a first response"

What Speed to Lead measures

Speed to lead is the oldest rule in sales: the operator who replies first usually wins the job. Speed to Lead is Verinode reading how well you actually do that, from your own logged lead activity, not a survey or a self-reported estimate.

Every lead in your pipeline has, at most, three dated milestones: Received (the lead came in), First response (someone on your team replied), and Converted (the lead became a signed job). Verinode reads the ordered pairs of those dates across your leads and mines the typical gap between them. Speed to Lead is the headline half of that: the median time from Received to First response. It sits on the Explore row of the Sales & Marketing home page as its own tile, alongside the six benchmark tiles that make up the rest of the row.

There is deliberately no "quoted" stage in this mining. Verinode tracks whether a lead is in the quoted status, but there is no dated quote milestone to mine a duration from, so quoting stays a status, not a stage in this pace.

Where to find it

Open Sales & Marketing from the sidebar, under the Revenue group alongside Jobs, Clients, and Reputation, at iq.verinode.ai/growth. Scroll past the hero panel and the Take Action row to the Explore row near the bottom of the page. Speed to Lead is the last tile in that row, after Average Job Value, Close Rate, Marketing % of Revenue, Cost per Job, Return on Marketing $, and Referral Share. It carries a green accent stripe.

Tapping it opens the same overlay deck the other Explore tiles use, on the Getting Leads tab: the acquisition-economics benchmark cards for Marketing % of Revenue, Cost per Job, Return on Marketing $, and Referral Share. Speed to Lead itself does not get a separate card inside that deck. Its number, its pace strip, and its peer comparison live entirely on the home tile; the tap is there to put you next to the rest of the acquisition picture while you think about what the pace number means.

Reading the tile

1. 1The headline number. A day count: how many days typically pass between a lead landing and your team's first reply, read as the median across your mineable leads (half your leads get a faster first reply than this, half get a slower one). A gap under a full day reads as "<1d" rather than a bare "0d," so a same-day response doesn't look like missing data.
2. 2The sub-line. Reads "median days to first response" once there is a number to show.
3. 3The pace strip. A row of small dots beneath the number, one per stage-to-stage gap Verinode was able to mine in your lead funnel, with the Speed to Lead dot lit to mark which one the headline number belongs to. This strip only appears once at least two gaps are mineable, meaning you have enough leads with dated conversions as well as dated first responses. With only received-to-response dates on file, you get the headline number with no strip yet; the strip fills in once converted dates start accumulating too.
4. 4The "vs Peer" line. When it appears, it reads something like "+1d vs Peer" or "-1d vs Peer". A plus means you are slower than the peer median for this same gap; a minus means you are faster. Slower is shown in Ember Red, faster in Deere Green, because for a response-time gap, fewer days is always the win.

The "vs Peer" line: what it needs to appear

The peer comparison on this tile is not always there, and its absence is not a bug. It needs two things at once:

• Your access. Peer comparisons on Verinode are part of the paid platform, or unlock through contributing your own anonymized data back to the benchmark. Until one of those is true, the line is simply absent, not blurred or ghosted, because a placeholder would leak that a comparison exists before you've earned the right to see it.
• A peer cohort for this specific gap. Verinode only shows a peer median once enough operators like you have contributed mineable data for the same received-to-response transition. Before that cohort has formed, the line stays off the tile even for operators with full peer access. As more operators like you contribute lead-timing data, this fills in on its own; you don't have to do anything to unlock it beyond keeping your own leads flowing in.

Verinode also hides the line if the gap between your number and the peer median rounds to nothing meaningful (under half a day), so the tile never wastes your attention on noise it can't actually distinguish from your own normal week-to-week variation.

The warming-up state

If Verinode cannot mine a received-to-first-response gap at all, yet, the tile shows a dash for its number and reads:

Log lead responses to map your speed to lead

This is the honest empty state, not an error. It appears when there is no lead data at all, when the leads on file don't have both a received date and a first-response date, or when none of your response gaps are in valid date order. As your lead source (a CRM connection, a forwarded intake inbox, or manual entry) starts capturing both timestamps on real leads, the tile fills in on its own the next time you open the section. No dashboard needs building, no report needs running.

Data quality behind the number

A couple of guardrails run underneath this tile so one bad date entry can't swing the number you see:

• Out-of-order dates don't count. If a lead's recorded first-response date somehow lands before its received date (a data-entry slip, most often), that pair is left out of the median entirely rather than producing a nonsense negative duration.
• Extreme outliers are capped, not dropped. A single lead where the received date is a year off from a typo would otherwise be able to drag a small sample's median or its longest-tail reading far out of line with reality. Verinode caps values that fall well outside your normal spread before computing the stats, so the case still counts toward your volume, but one bad date can't define your typical pace.

Neither of these requires anything from you. They just mean the number on the tile is a trustworthy typical pace, not whatever your messiest single data entry happened to say.

How Speed to Lead relates to the rest of the section

Speed to Lead is the pace half of your lead funnel; the Lead Pipeline tile above the Explore row is the volume half, how many leads came in and how many currently need a follow-up. Read them together: a fast Speed to Lead number with a Lead Pipeline tile flagging several leads needing attention usually means your first-response habit is good but something is stalling leads after that first reply, worth a look at the Pipeline view before assuming the funnel itself is the problem. A slow Speed to Lead number is the more direct fix: it points straight at how quickly your team (or your after-hours process) gets to a new lead, independent of anything else in the funnel.

For how the other six Explore tiles are built and what each one measures, see Explore tiles: the Sales & Marketing metric catalog. For the four numbers in the hero panel above the Take Action row, see the four Sales & Marketing vitals. For what the Take Action row does with what Verinode finds here, see Take Action: growth decisions, agent activation, and unlock and the decision workspace. For how peer comparisons are computed and gated across the whole platform, see how benchmarks work and reading a benchmark.

Best-practice example

Say your tile reads 2d, sub-line "median days to first response," a lit pace dot on the first of two, and "+1d vs Peer" in red. That means half your leads wait two days before anyone replies, a day slower than operators your size on the same gap. Open the Getting Leads tab to check whether a slow response is showing up anywhere else (a lower close rate, a lower referral share), then look at the Lead Pipeline tile for which open leads are actually sitting unworked right now. Fixing this one is rarely about spending more on marketing, it is almost always about who covers the phone, and when, between the moment a lead lands and the moment someone calls back.

Data sources