Sales KPI

Lead Response Time Formula

Learn what Lead Response Time means, how to calculate it in Excel, and how to recreate the same KPI as a Power BI DAX measure.

💡 Ideas for You

Resources related to this KPI and spreadsheet reporting.

4 useful links
📚 Step-by-step booksStart with beginner-friendly step-by-step books and learning resources from Create & Learn.📊 KPI dashboard resourcesBooks and templates for building sales KPI dashboards in spreadsheets.📈 Business metrics booksReferences for understanding sales metrics, definitions, and reporting habits.📘 Excel reporting guidesGuides for turning spreadsheet calculations into clear reports and dashboards.

Quick answer

Lead Response Time is calculated as:

Total Response Time / Number of Leads

Use this Excel version when your inputs are on row 2:

=IFERROR(B2 / C2,0)
Example result0.2 days/hours
FormatNumber with unit such as days, hours, or months
Typical chartLine chart for trend; column chart by queue, team, project, or location.

What is Lead Response Time?

Lead Response Time measures speed, delay, or duration. It helps show whether work is moving quickly enough and whether process changes are improving performance.

Sales KPIs show how efficiently the team turns leads and opportunities into revenue.

Beginner tip: A KPI is not just a formula. It is a number used to make a decision. Before adding it to a dashboard, write down the definition, time period, owner, target, and data source.

Real-life example

Imagine a sales manager reviewing the pipeline before a forecast meeting. The team adds the inputs for Lead Response Time to a sales performance dashboard, calculates the KPI for the current month, and compares it with the previous month and target. In the sample below, the result is 0.2 days/hours. That number becomes useful when everyone uses the same formula each month.

Excel cellInputWhat it meansSample value
B2Total Response Timethe total time measured using the same unit for every row100.0 days/hours
C2Number of Leadsthe input value used by the KPI formula500
ResultLead Response TimeOutput of the KPI formula0.2 days/hours

How to calculate Lead Response Time in Excel

  1. Create one row per reporting period, team, product, campaign, location, or customer segment.
  2. Add one input per column. Do not combine inputs in the same cell.
  3. Paste the Excel formula in the KPI result column.
  4. Format the result as Number with unit such as days, hours, or months.
  5. Copy the formula down the table and compare the result against target, previous period, and trend.
Quality check before publishing:
  • Use the same date range for every input.
  • Confirm that the denominator is not blank or zero.
  • Document whether the KPI is calculated before or after discounts, refunds, taxes, returns, or cancellations.
  • Keep the definition stable so reports remain comparable over time.

Power BI DAX measure

If you also report this KPI in Power BI, create a measure instead of hard-coding the calculation in a visual. Replace the measure names below with the names used in your model.

Lead Response Time = DIVIDE([Total Response Time], [Number of Leads], 0)

For best results, build base measures first, such as revenue, cost, customers, orders, or tickets, and then build the KPI measure from those base measures.

How to read the result

Lower is usually better, because this KPI often represents cost, waste, delay, risk, loss, or friction.

Do not read the KPI alone. A single value can be misleading without a target, trend, segment, and business context. For example, the same result may be good for one product line but poor for another.

Useful comparisons

  • Current month versus previous month.
  • Actual result versus target or budget.
  • By channel, product, customer segment, team, or location.
  • Rolling average over several periods to smooth one-off spikes.

Common mistakes

  • Mixing time periods, such as monthly cost with quarterly revenue.
  • Using a total when the KPI should be segmented.
  • Changing the formula definition after the dashboard is already in use.
  • Comparing two teams that collect the inputs differently.
  • Ignoring blanks, zeros, refunds, cancellations, or duplicate records.