Measuring elapsed time rather than counts tells you more

3 days ago
3 min read

Introduction

Funnel measurement is nearly always presented as counting: how many arrived, how many converted, what proportion moved from one stage to the next. Those counts are useful and, in a small business, they are also noisy, seasonal and slow to reveal anything.

Time is the alternative and it behaves much better. How long between the enquiry arriving and somebody replying. How long between the site visit and the quote. How long between the quote and a decision. These are stable at low volume, they respond quickly to process changes, and they measure the thing most improvement work is actually about.

They are also easier to collect, because dates are already in your calendar, your inbox and your invoices.

1. Measuring elapsed time rather than counts gives a stable signal

The core advantage.

The median days between two stages barely moves from random variation, whereas a conversion rate on fifteen enquiries moves constantly. You can read a change in it honestly. That alone justifies the switch. Fifteen timings are enough to see a real shift.

2. Response time is the first one to take

The highest-value measure.

Hours between an enquiry arriving and a human replying, measured in working hours. It correlates with conversion more strongly than almost anything else you can control. Most businesses are much slower than they believe. Measure a week of it before deciding you are fast.

3. Time to quote is the second

The middle of the funnel.

Days between the conversation and the price being sent. This is where quiet delay accumulates in trades and professional services alike. It is also very often fixable without spending anything. Usually the delay is waiting for information you already have.

4. Time to decision is the third

The buyer's half.

Days between your quote and their answer. Long values here are a signal about the quote and the follow-up rather than about the buyer. Track it and the follow-up conversation gets easier. A number replaces the guesswork about when to chase.

5. Use the median, not the average

The statistical caution.

One job that dragged for four months distorts an average badly at small volumes. The median describes the typical experience. Report both only if you have a reason to. Outliers are worth reading individually rather than averaging away.

6. Measure in working hours where it matters

The precision that counts.

An enquiry arriving on Friday evening and answered Monday morning is either sixty hours or one, depending on the convention. Choose the one that reflects the buyer's experience. Then hold it.

7. Timings expose handover problems

The diagnostic use.

A long gap almost always sits at a point where the work moved between people or systems. Counts never show you this. This is the main reason the measure repays the effort.

8. Set a target you can actually see

The management application.

Reply within four working hours, quote within two working days. Those are checkable daily by anybody. Targets built on conversion rates are not.

9. Track it before and after a change

The evaluation use.

Because it is stable, elapsed time gives a readable answer within weeks rather than quarters. That makes it the best available measure for judging a fix. Record the baseline before you change anything.

Be careful about optimising speed at the expense of the content. A quote sent in an hour that omits half the job is worse than one sent the next morning, and the timing measure will happily record the faster version as an improvement.

Conclusion

Start measuring the gaps between stages rather than only the counts within them.

Take response time first, then time to quote, then time from quote to decision, use the median rather than the average, decide whether you count working hours or calendar hours and hold that convention, read long gaps as handover problems, set targets people can check daily, and record the baseline before any change so the improvement is readable within weeks.