Where a quote request actually waits

Ask a tool shop how long it takes to answer a request for quotation and you'll usually hear about the estimate: the hours an engineer spends working out steel, cavities and cycle time. That work is real, but it isn't where most of the waiting happens.

Follow one request from the moment it arrives to the moment the client gets a first answer, and the estimate turns out to be a short stretch in the middle. Most of the time goes on waiting for someone to notice it, open the attachments, work out what's missing and find the person who can write back in the client's language.

The handoffs, one by one

• Noticed. The request lands in a shared inbox next to invoices, delivery notes and newsletters. Nobody owns the inbox, so it waits until someone has a gap.
• Opened. Someone opens the email, then the PDF, then the client's own form, then tries the STEP file. The details that matter are spread across all of them.
• Checked. Something is missing, or one thing contradicts another. The material on the drawing isn't the material in the spec. Nobody can quote until it's settled.
• Asked. The question has to go back to the client, in German or French, politely and precisely. That waits for the one person who writes it well.
• Answered. The client replies days later, and the request goes back to the top of the pile.

Each of these is a few minutes of work. Together, spread over a busy week, they're the difference between a first reply the same day and one the following week.

Measure your own

You don't need software to see this. Take the last ten requests your company received. For each one, note four times from the email history: when it arrived, when someone first replied to the client, when the quote went out, and how many messages went back and forth in between.

Then look at the gap between arrival and first reply. If it's measured in days and the first reply is a question, the time isn't going into the estimate. It's going into the handoffs before it.

What to change first

The quickest gain is usually the first reply. If every request is read the day it arrives, its gaps listed and the questions sent back in the client's language, the client starts answering while your engineers are still busy with yesterday's work. The estimate then starts from a complete request instead of a half-finished one.

That's the part we automate in the quote request assistant: reading the request and its attachments, listing only what blocks the quote, and drafting the questions for your team to send. The estimate stays with the people who know how to make it.