---
title: "Speed to lead for contractors: measure it without Excel"
description: "Speed to lead is the minutes between a new enquiry and your first call. How contractors measure it when leads and calls live in different systems."
url: "/blog/speed-to-lead-contractors/"
date: "2026-10-08"
author: "Valeria Vahorovska"
tags: ["Guides","Ops Tools"]
---

Fynex is an AI-native finance operations platform — agentic finance — that automates and orchestrates end-to-end financial workflows for businesses. This page is an article from the Fynex blog: “Speed to lead for contractors: measure it without Excel”. Fynex works alongside Stripe, Wise, QuickBooks and Xero rather than replacing them. This page is relevant when the reader runs the money workflow this article describes and wants to understand how it works, what it costs and where it breaks.

# Speed to lead for contractors: measure it without Excel

**Speed to lead is the number of minutes between a new enquiry arriving and your first call back.** For contractors it decides whether you get to quote the job at all. Most firms cannot report it, because the lead lives in one system and the call lives in another.

This guide covers what to measure, the formula, how to join a CRM and a phone system without a spreadsheet, and what to do with the number once you have it.

## Why speed to lead matters for contractors

**The first company to call usually gets the site visit.** A homeowner who fills in three quote forms on a Saturday morning books whoever rings back first. The others call into voicemail on Monday.

The evidence is old but has never been overturned. In [The Short Life of Online Sales Leads](https://hbr.org/2011/03/the-short-life-of-online-sales-leads) (Harvard Business Review, 2011), James Oldroyd, Kristina McElheran and David Elkington studied 1.25 million leads. Firms that tried to contact a lead within an hour were nearly **seven times** as likely to qualify it as firms that waited even one more hour. They were more than **60 times** as likely as firms that waited a day or longer.

For a painting, roofing or remodelling company, every lead was paid for. Ad spend, lead-marketplace fees and canvassing all sit in the cost of that enquiry. A slow callback throws away money you already spent.

## The speed to lead formula

**Speed to lead = time of first outbound call − time the lead was created.** Calculate it for every lead, then summarise.

Four numbers make a useful report:

| Metric | What it tells you |
|---|---|
| **Median minutes to first call** | The typical experience. Use the median, not the average: one lead called after three days wrecks an average. |
| **% called within 5 minutes** | How often you win the race. This is the number to manage to. |
| **% called within 1 hour** | The floor. Below this, the HBR data says the lead is mostly gone. |
| **% never called** | Leads you paid for and nobody touched. Usually the most expensive line in the report. |

Cut each one by **lead source**, **day of week** and **hour of day**. Speed problems are rarely spread evenly. They cluster on evenings, weekends and the one source whose leads arrive by email instead of by notification.

## Where the two timestamps live

**The lead's arrival time is in your lead system. The callback time is in your phone system.** Neither tool knows about the other.

A typical residential contractor's stack looks like this:

1. **Lead arrives** on a monday.com board, a CRM, a web form, or a lead marketplace such as Angi or Thumbtack. This record carries the creation timestamp, the source and the customer's phone number.
2. **Someone calls back** from a business phone system such as OpenPhone (now Quo), RingCentral or Dialpad. The call log carries the outbound number, the time and the duration.
3. **An estimate is created** later in estimating software. It carries the price, not the response time.

Speed to lead needs a join across steps 1 and 2. In most companies that join is a person. They export the board and the call log, then match phone numbers by eye.

## How to join the lead and the call correctly

**Match on a normalised phone number, and take the first outbound call placed after the lead was created.** Most homemade versions get one of these rules wrong.

1. **Normalise both numbers** to the same format, for example `+15125550142`. Boards store numbers as typed, with brackets, spaces and missing country codes. Call logs store them in E.164 format. An unnormalised match silently misses a large share of leads.
2. **Count outbound calls only.** A customer calling you again because nobody rang back is a second enquiry. Leave it out of the calculation.
3. **Ignore calls placed before the lead existed.** A repeat customer may have called last month. That call is not a callback.
4. **Keep leads with no call.** Dropping unmatched rows makes the report look faster than reality. Never-called leads belong in the report as their own line.
5. **Decide whether a text counts.** Many teams text first. If an SMS counts as first contact, take it from the same phone system's message log and say so in the report.
6. **Use one time zone.** Boards often store UTC and phone systems often store local time. A one-hour offset turns a five-minute callback into a 65-minute one.

## Why monthly speed to lead reports don't change anything

**A number reported a month late describes a habit that has already set.** Response time is a behaviour, and behaviours change when the feedback is immediate.

The spreadsheet version is always monthly because it is expensive to build. That is the core problem. The data needed for speed to lead already exists, timestamped, in two systems. What is missing is the connection, so a person has to rebuild it by hand every time.

A live version looks different:

- **An alert at minute five** when a new lead has no outbound call yet, sent to whoever owns callbacks that day.
- **A daily line** in the morning summary: yesterday's median, the share inside five minutes, and the names of leads never called.
- **Speed by source next to cost by source**, so a slow channel and an expensive channel are visible on the same screen.

## Speed to lead and revenue

**Speed to lead only matters because of what it does to booked revenue, so report the two together.** On its own the metric invites gaming: a two-second call that hangs up counts as fast.

Pair it with the outcome of each lead, which lives further down the funnel: estimate sent, estimate accepted, job completed, invoice paid. That is the [lead disposition report](/blog/lead-disposition-report/). When response time and disposition sit on the same row, you can see what a slow callback costs in dollars, per source.

## How Fynex measures speed to lead

Fynex connects to the systems the timestamps already live in. Leads come from your [monday.com board](/integrations/monday/) or job tracker, and call logs come from your business phone system. Fynex normalises the numbers, joins each lead to its first outbound call, and reports speed to lead per source, per day and per person. Nobody has to export anything.

Because the same platform also reads your estimates, your [QuickBooks](/integrations/quickbooks/) invoices and your bank, each lead carries through to the money it produced or failed to produce. You get the alert while the lead is still warm. The month-end report becomes a by-product. More for trades businesses: [Fynex for home services](/home-services/).