Lead Time: Why Faster Work Did Not Shorten It

Ask a business how long a job takes and you get the hours of work. Ask a customer how long it took and you get the calendar. Those two numbers are frequently different by a factor of five, and the gap between them is where almost every lead time promise goes wrong.

The arithmetic that catches people out

A custom quotation involves perhaps ninety minutes of genuine work: reading the request, pricing it, writing it, checking it. The quoted lead time is five business days. Both of those are true at the same time, and the ninety minutes is not the interesting number.

The five days contain a day before anyone opens the request, half a day waiting for a measurement from the customer, two days in a queue behind other quotes, and an overnight wait for a signature. Cut the ninety minutes of work to thirty with better tooling and the quote still goes out on day five.

This is the most common reason an automation project produces no visible customer benefit. The saving is real and it lands in capacity rather than in speed, which is worth having and is not what anyone was promised. Finding where the elapsed time actually goes is the subject of locating the bottleneck after it moves.

Measure the calendar, not the clock

Pull your last thirty completed jobs. Record two dates for each: when the request arrived, and when the customer received the result. Not when work started. Not when it was marked complete internally.

Sort those durations from shortest to longest and look at the spread. Most businesses discover a distribution rather than a number: a cluster of fast jobs, a long middle, and a tail of outliers that nobody remembers until a customer brings one up. The tail is where the complaints live and the average conceals it entirely.

Then split each duration into working time and waiting time. If waiting is under half of the total, the process is unusual and your work genuinely is the constraint. Above that, which is the normal case, your lead time is a queueing problem wearing a capacity costume.

Where the waiting actually accumulates

Missing information is the delay businesses treat as the customer's fault, and usually it is not. Discovering on day three that you need a measurement, a file or an account number resets the clock while you wait for a reply. Asking for the full set at intake moves that wait to a point where it costs nothing, and a well-built intake form does more for lead time than most software purchases.

Handoffs are the largest total in most processes because they multiply. Four handoffs at half a day each is two days of pure queue, invisible on any individual person's timesheet and plainly visible on the customer's calendar.

Quote a number you beat

Half of all jobs are slower than the average, so quoting the average means missing about half your promises. The figure worth quoting is one that eight or nine jobs in ten comfortably beat, which usually sits well above the average and feels uncomfortably long to say out loud.

Saying it anyway is the better commercial trade. A customer told nine days and served in six is pleased. A customer told five days and served in six makes a phone call, and that call costs you time as well as goodwill. Reliability compounds in a way a short headline number does not.

Where the spread between your fast and slow jobs is wide, the honest move is to quote by category rather than quoting one number for everything. Simple jobs in three days, complex ones in ten, with a stated rule for which is which.

Where AI genuinely helps

Three uses move lead time rather than just processing time. Intake completeness, where a form or assistant checks the request has everything before it enters the queue. Triage, where incoming items get sorted and routed immediately rather than waiting for someone to look. And chasing, where follow-ups on missing information go out on a schedule instead of when somebody remembers.

Each of those attacks waiting time directly. Faster drafting, by contrast, attacks the smallest component, which is why it is the most common project and the least visible result. Generating the document quickly still matters once the queue is gone, and the quoting mechanics are in building a quote template.

Where physical fulfilment is involved, lead time also depends on whether your stock numbers are true, since promising from an inaccurate count produces the worst kind of delay. That dependency runs through cycle counting and demand forecasting.

What shorter lead time is worth

Faster responses win work that would otherwise go elsewhere, and the effect is largest at the quotation stage where customers are actively comparing. Shorter lead times also shorten the gap between doing work and being paid for it, which is a cash position improvement rather than a service improvement.

Both of those are easier to put in a business case than a vague faster, and the second one connects directly to collections, covered in what AI can chase for you. Tracking the distribution month to month, rather than a single average, is what keeps the improvement from quietly eroding.

Frequently Asked Questions