Why quote requests wait overnight

A quote request arrives before lunch. The list looks manageable, but the person who knows the account is serving at the counter, two product codes need checking, and the prices have to be confirmed. By the time someone can finish it, the branch is closing. The customer gets the quote tomorrow.

That delay is rarely one big problem. It is a chain of small jobs, each waiting for the right person or information. If you want to improve slow quote turnaround for builders, start by finding where the list pauses, not by telling staff to type faster.

Follow one request from inbox to quote

Pick a recent request and write down each step, who handled it, and when it moved on. Include waiting time as well as hands-on work. A list may take only a short time to price, yet sit untouched while the estimator finishes another job or waits for an account check.

A typical route might look like this:

1. Open the email and work out which attachment is the current list.
2. Retype or copy the requested lines into a quote screen or working sheet.
3. Find product codes for descriptions that do not include them.
4. Check the customer’s account pricing and any quantity breaks.
5. Resolve missing prices, unclear units or uncertain product matches.
6. Review the draft, format it and send it to the customer.

The useful question is not simply, “How long does quoting take?” Ask which step is being done twice, which step needs judgement, and which step is waiting for one person.

Retyping turns a list into a second job

A spreadsheet can look ready to use but still need tidying. Descriptions may be split across columns, quantities may sit under an unfamiliar heading, or the customer may have added notes between the lines. A PDF can be harder to work from if staff have to copy each item manually.

Set a simple intake rule for regular customers. Ask for one item per row, with a product code where known, a clear description, quantity and unit. Keep notes in a separate column. If a customer sends a different layout, save a clean example and agree how the branch will read it next time.

Also decide who checks that the attachment is complete. A missing page or a second version buried in the email can create more delay than the actual pricing. A short inbox checklist helps: confirm the customer, identify the latest list, check that all pages are present, and record any deadline or delivery note before work starts.

Code lookups need a clear stopping point

A line with a supplier product code is usually straightforward to identify. A line written as “white basin waste” or “treated timber, cut length” may need a search and a decision. Staff can lose time comparing near matches, especially when the request leaves out a size, finish or specification.

Make the decision rule explicit. If the description does not identify a safe match, flag the line and ask for clarification rather than choosing the closest-looking item. Keep a record of common customer terms and the catalogue descriptions they refer to. That gives the next person a useful starting point without turning a past guess into a rule.

For a regular account, note who can confirm unusual product choices and what information they need to make that call. If only one estimator knows the customer’s shorthand, capture the shorthand in a shared reference, not just in that person’s memory.

Price checks are not all the same

A price lookup can involve more than finding a figure in a list. The customer may have account-specific pricing, a group price, a quantity break or a price that applies only for a set period. A missing price or a conflict between possible prices needs attention, not a quick assumption.

Separate routine checks from exceptions. Make sure staff know which price source takes priority for each account, where to check quantity breaks, and who can resolve a missing or conflicting price. If the answer depends on a customer agreement, keep the relevant note accessible to the people who prepare quotes.

This is also where a single account expert becomes a bottleneck. Give a named backup access to the account rules and a clear route for escalating exceptions. The aim is not to remove judgement. It is to stop ordinary checks waiting behind one person’s other work.

Move the waiting, not the approval

Some steps can be prepared earlier. A branch can keep customer layouts, account rules and common product aliases in one place. Staff can check incoming lists for missing details as soon as they arrive, then ask the customer while the estimator is working on other quotes. A queue with an owner and a next action is more useful than an inbox full of unread messages.

QuoteClerk AI reads material lists from XLSX, CSV and TSV spreadsheets of up to 5,000 rows, PDFs of up to 10 pages, plain text and the body of an email, then matches each line to the supplier’s own catalogue and prices it from the supplier’s own prices. It flags uncertain lines, missing prices and price ties rather than guessing. A person on the supplier’s team approves every draft before anything reaches a customer. The working process and limits are set out in how an email quote request becomes a draft.

That does not remove the need for a person to check account exceptions or unclear specifications. It can, however, give the team a draft to review instead of making someone start by retyping every line. Keep the approval step visible, and agree who covers it when the usual estimator is away.