The quote that took four days to leave the building

Monday's enquiry, Thursday's quote

The enquiry lands on Monday morning and everyone agrees it is a good one. It goes to the person who prices things. He needs a figure from a supplier. The supplier answers on Tuesday afternoon. The discount needs a nod from the owner, who is out of the city until Wednesday. The document gets typed on Wednesday evening and sent Thursday.

By then the customer has a quote from somebody else that arrived on Monday afternoon, and yours is being read as a comparison rather than as a proposal. Sometimes you win anyway. Often you never find out why you did not.

There is a second version of the same failure that costs even more. The quote goes out quickly, and it comes back wrong, because the specification was misunderstood at the start. Now the whole loop runs again, and this time the customer has watched you get it wrong once.

A quote is a chain of waits

Ask anyone how long it takes to produce a quote and they will describe the calculation, which is usually the shortest part of the whole thing. The time is spent waiting, and the waits are almost always the same five.

Waiting for the specification, because the enquiry arrived as a photograph and a sentence, so somebody has to go back and ask three questions and then wait for those answers. Waiting for a price from outside, from a supplier or a subcontractor who replies when he replies.

Waiting for permission, because the rate the customer wants is below the number the person quoting is allowed to give. Waiting for the document, because there is no template and each quote is composed from scratch. And waiting for attention, because the person who prices is also the person delivering last month's work.

Underneath all five is a structural problem. Quoting sits between sales and operations and belongs to neither, so no one is accountable for how long it takes. Work that lives in a gap between two departments moves at the speed of whoever happens to remember it.

• Waiting for a specification the enquiry never contained
• Waiting for a supplier or subcontractor to send a price
• Waiting for approval on a discount somebody could have been trusted with
• Waiting for a document to be composed rather than filled in
• Waiting for the attention of a person who is also delivering the work

Twenty quotes and two timestamps

Take your last twenty quotes. For each, write two times: when the enquiry arrived and when the quote left. Then write one word for where the longest single wait was, chosen from the five above.

The word column is the useful one. If most of the delay is specification, your fix is at intake and costs nothing. If most of it is approval, your fix is a written authority limit and also costs nothing. If most of it is supplier pricing, no internal change will help much and you need a different arrangement with your suppliers or a standing price list you are willing to quote from.

Businesses that run this exercise usually discover that the calculation, the part they thought of as quoting, accounts for a small share of the elapsed time. That single realisation changes what you fix first, which is the whole point of measuring instead of guessing.

The free fix: ask everything once, and pre approve the discount

Write down the facts you need before a quote can start. Most businesses land on six to eight: what exactly, how many, which specification or size, delivered where, needed by when, and anything about the site or the installation that changes the price. Number them and keep them on one card.

Send that numbered list as a single message at first contact. Not three questions now and two more tomorrow, which is what turns a two hour job into a two day one. A numbered list also gets answered in order, which makes the reply usable, and it signals competence to the customer at the exact moment they are deciding whether you are serious.

Then remove the approval wait with a sentence. Write down the discount any quoting person may give without asking, and the order value below which no approval is needed at all. Most owners find they are being consulted on decisions they would have approved in every single case, which means the consultation was pure delay.

Two more things that cost nothing. Build one quote template with your standard prices already in it, so quoting means filling in the variables rather than composing a document. And put a validity date on every quote, which protects you against a supplier price moving and gives the customer an honest reason to decide this week.

• A numbered intake list of the six to eight facts a quote requires
• One message containing all of them, sent at first contact
• A written discount band and a value threshold needing no approval
• A saved quote template with the standard price list already inside it
• A validity date on every quote issued

What automation adds, and when speed is the wrong goal

The automatable parts follow the measurement directly. The intake questions can be asked automatically the moment an enquiry arrives, so the specification is collected while the customer is still paying attention rather than the next morning. A quote for anything standard can be assembled from a maintained price list and sent as a proper document within minutes. The follow up can be scheduled the moment the quote goes out, which is the step most businesses lose entirely.

None of that helps if the enquiries were never worth quoting. Quoting faster on unqualified work simply produces more free work in less time, and a business drowning in quote requests that never convert has a demand quality problem rather than a speed problem. The intake list helps here as well, because a person who will not answer six questions was rarely going to buy.

Two more limits. If your prices genuinely move with the dollar or with a commodity, the honest fix is a short validity date rather than faster quoting, and speed without that just moves your losses forward. And where a quote depends on a site visit or an engineering judgement, the calculation is the thing you are being paid for. Automating around it produces confident numbers you are then contractually bound to, which is a considerably more expensive problem than a slow quote.

Ask all your questions in one message. The gap between question three and question four is where most of the four days actually went.

Who still prices it, and what the intake record is worth

Nothing here decides a price. The intake asks the six to eight facts the moment an enquiry arrives, chases the supplier whose figure is late, and assembles the document, and then it hands it to a person to price. A discount beyond the pre approved band waits for human approval. That boundary is what makes the speed safe, because a quote produced quickly and wrongly costs more than one produced slowly. It has to be withdrawn in front of a customer who has already started planning around it.

The intake record is the thing worth keeping. Every enquiry with its facts attached, the date it arrived, the date the quote left, and where the longest single wait sat, all in an account under your own logins. You own the system and, more usefully, you own the measurement, which turns the twenty quote exercise above into something you can read every month rather than an afternoon somebody has to volunteer for.

The pre approved discount band and the intake question list are both free, and both are worth doing in-house before anybody quotes for software. Most of the four days in the title disappears when the questions are asked once instead of three times, and your own team can make that change this week. What is harder to hold internally is the supplier chase, because it is the wait nobody owns and the one that comes straight back the moment the person doing it is busy.

The published work nearest this is Quillon, where the production pipeline behind audit-ready training packs became a single audited automation of 34 AI nodes at roughly four dollars of AI cost per full unit pack, and RM Gulistan Engineers in Karachi, where three purpose built ERP systems cover accounts, HR and inventory. Moiz Khan owns automation architecture at Wobble and decides what a system may say about a price, which on a quoting build means nothing at all.

Common questions

How fast should a quote go out?

Fast enough to be the first one the customer reads, which in most competitive categories means the same working day for anything standard. Rather than picking a target from an article, measure your last twenty and set a goal that halves your current typical time, because a target that far exceeds your process just gets ignored.

What should be on a quote intake checklist?

The facts without which you cannot price: what, how many, which specification, delivered where, needed by when, and any site or installation detail that changes the figure. Keep it to six to eight items. A longer list looks like a form and gets abandoned halfway through.

Should I let staff give discounts without asking me?

Within a written band, yes. It is usually the single fastest improvement available. Set the maximum discount and the order value below which no approval is needed, and review the exceptions monthly. Owners who do this commonly find they had been approving nearly everything anyway, which means the approval step was adding delay and no control.

Can quoting be fully automated?

For standard items with a maintained price list, most of it can, from collecting the specification to producing the document. For anything requiring a site visit, a measurement or a judgement about difficulty, the calculation is the value you are selling and it should stay with a person who will stand behind the number.

How long should a quote stay valid?

Long enough for a normal decision and short enough to protect you against a moving cost, which for most businesses here means somewhere between seven and thirty days depending on how volatile your inputs are. State the date on the document itself rather than in a covering message, because that is the page the customer keeps.