A customer asks what it would cost. Three days later, you send them a number.
Nobody in your business spent three days on it. The actual work — looking at the job, deciding the price, writing it down — took about twenty minutes. The other two days and seven hours, the quote was sitting somewhere.
Ask where, and you get a shrug and a reasonable answer: it has been busy. That answer is true and it is also the reason the same thing will happen next week.
Where the three days actually go
Follow one quote through your business and it stops in the same places every time.
- Waiting to be noticed. The request arrives in an inbox, a form, a voicemail, or a text to someone’s personal phone. It waits there until a human happens to look.
- Waiting for the details. Whoever picks it up does not have enough to price it, so they ask a question and wait for the answer.
- Waiting for the person who knows. One person can price a job like this. They are on site, in a meeting, or on leave.
- Waiting to be written up. The price is decided. Now somebody has to open the template, re-type the customer’s details, and put it into a document.
- Waiting for a check. It sits with you for approval, which takes ninety seconds of attention and half a day of elapsed time.
Five stops. Twenty minutes of work. Three days of calendar. That gap is not a performance problem — it is the shape of the process.
What each day of delay costs
Run this with your own figures. I am not going to hand you an industry statistic, because the only number that means anything here is yours.
Take the quotes you sent last month and split them into ones that went out same day and ones that took more than two days. Compare the win rates. Then ask the customers you lost when they made the decision — some of them will tell you they went with whoever answered first, and that answer will be uncomfortable and useful.
Then the second cost, which is the one people forget. Every quote sitting in the middle of that process is also occupying somebody’s memory. They are holding a mental list of what has gone out, what has not, and who needs chasing. That list is doing real damage to their week and it never appears anywhere as a cost.
The chase is a second job
The quote goes out. Then what?
In most businesses, then nothing, until somebody remembers. The follow-up on day three, the second one on day ten, the decision to give up around week three — all of it held by a person who is also doing their actual job.
Which means your win rate is partly a measure of how good one person’s memory was that month. When they are busy, quotes go cold that would have closed. Nobody sees it happen, because a quote that was never chased leaves no trace at all.
What quoting software fixes, and what it doesn’t
Worth being fair here. Quoting software genuinely helps with the writing-up stop — templates, line items, a tidy PDF, a customer who can accept online. If your only problem is that quotes look scrappy and take an hour to type, buy the software. It is cheap and it works.
What it does not do is start. It waits for someone to open it and begin a quote. It does not read the inquiry that arrived at 7pm, pull the customer’s details out of it, notice that this is the third time this customer has asked, price the standard parts, flag the one line that needs your judgement, and have a draft waiting when you sit down.
It is a better place to write a quote. It is still a place a person has to go.
What I learned writing quotes for a living
I spent years as a project manager writing scopes and quotes before I moved into architecture, so the three days is a process I have personally been the bottleneck in.
Here is the part that surprised me and might save you a wrong conclusion: I was not slow at pricing. I was slow at starting. Every quote required me to go and gather the same six things from four places before I could think about the number at all, and that gathering is what I put off. Once the information was in front of me the quote took minutes.
So if you are about to solve this by telling someone to be quicker, check first whether the delay is the thinking or the gathering. In my case, and in most cases I have looked at since, it was the gathering — and nobody has ever fixed a gathering problem by trying harder.
Find your own bottleneck this week
- Take the last ten quotes you sent. For each one, write the date the request arrived and the date the quote went out.
- For the three slowest, reconstruct the timeline — when did it get noticed, when was the price decided, when was it written, when was it sent.
- Mark which gap is biggest. It is usually the same gap for all three, and that is your bottleneck.
- Ask what information was missing at the point it stalled. That list is what an intake step would need to collect up front.
- Check the chase. Of those ten, how many were followed up at all, and by whom? If the honest answer is “whoever remembered”, you have found a second bottleneck downstream of the first.
If all ten went out the same day and every one was chased on schedule, you do not have a quoting problem. Go and count a different flow — and do not let anyone sell you a fix for a process that is already working.
What to do next
Reconstruct three timelines this week and find the gap. If it is gathering rather than deciding, no amount of pressure on the person doing it will change the number.
When you are ready to compare a tool against the thing that would actually remove the stops, the honest comparison is here. For the wider picture, count the stops across the whole flow.
If you want the whole picture instead of one workflow: tell us what’s still manual. You get a map of every point where your business stops and waits for a person, what that costs you in hours, and which of those an engine would take over first. Free, yours to keep, and useful even if you never hire us — including on the days the honest answer is that you should not build anything yet.
Common questions
Would hiring an admin fix this faster than software?
Sometimes, and it is a fair comparison to make honestly. A person can absolutely close the gathering gap, and if your volume is low that may be the cheaper answer this year. What a person does not do is scale without cost or remember perfectly on a bad week — you are buying capacity, not removing the stop. Price both against the same thing: the number of quotes per month and what each day of delay is worth to you.
Our quotes need judgement. Doesn’t that rule out automating them?
It rules out automating the judgement, which nobody should be trying to do anyway. Most quotes are not one decision — they are twenty pieces of assembly and one or two real calls. The assembly is what moves on its own: pulling details out of the inquiry, applying your standard rates, drafting the document. The judgement stays yours, arriving with everything already prepared.
How fast is fast enough?
Ask your own customers rather than trusting a benchmark. Call three people who chose someone else recently and ask when they decided. Their answers tell you the window you are actually competing in, and it varies enormously between trades and deal sizes. Speed matters far more on small, comparable jobs than on large ones where the buyer is comparing detail.
What happens to quote history if we change how this works?
Ask that question before you buy anything, because it is the one that gets discovered late. Your past quotes are a pricing record — what you charged, who accepted, what you discounted. Whoever proposes a change should say in writing where that history ends up and how you get it out again. If nobody can answer, that is information about the proposal.