A customer calls about a quote you're working on. You say you'll check and come back — then spend ten minutes in your inbox reconstructing where it stands.
The ten minutes isn't the cost. The cost is that until they called, you didn't know either.
What that answer requires
To answer honestly you need four things at once: which suppliers you asked, which have come back, how old the outstanding ones are, and whether anything is now late.
In an email-and-spreadsheet setup none of those are facts you hold. They're facts you derive — by searching, opening and remembering. Which is why the answer takes ten minutes, and why nobody checks unprompted.
The two bad outcomes
You guess optimistically. "Should have it by end of week" — based on nothing, because you haven't checked whether the supplier who owes you a number has even opened the request. Sometimes that's right. When it isn't, you've spent credibility you'll want later.
You go quiet. Rather than admit you're unsure, you say you're chasing it. The customer hears nothing concrete, follows up in three days, and the relationship acquires a friction that has nothing to do with your capability.
Both come from the same place: the status genuinely isn't known.
What good looks like
You open one screen and read it out: two of three quotes are in, the third was asked for on Monday and is due tomorrow, and here's the range so far.
Ten seconds, and it changes the conversation. You've given them something to plan around, you sound in control of your own process, and you've told them the truth.
Customers tolerate "one supplier is late, I'll have it Thursday" far better than "still chasing" twice. Specifics read as control; vagueness reads as chaos, even when the underlying situation is identical.
The version of this that costs you jobs
The same gap shows up before the customer ever calls.
If you can't see that a quote is late, you can't tell your customer early. If you can't tell them early, you can't ask for two more days while they still have flexibility — you're asking at the deadline, when the answer is no.
Late information is what turns a small supplier delay into a missed bid. Not the delay itself.
What to actually change
You don't need software to improve this. You need those four facts recorded rather than derived:
Write down, per RFQ, the date you sent it and the date you asked for. Two dates turn "is this late?" from a memory question into arithmetic.
Record replies in the same place as the requests. A quote that exists only in an inbox isn't visible to anyone who didn't send the RFQ.
Have somewhere that answers "what's open" without opening anything else.
If a tool does this for you, good. If it's a shared sheet with four columns, that works too. What doesn't work is knowing it well enough today and assuming you'll know it well enough on the day somebody asks about a job from three weeks ago.
The test
Have someone who didn't send it try to answer "where are we on the Henderson quote?" without asking you.
If they can, you have a process. If they can't, you have a person — and that person is answering from memory, which works until the week it doesn't.