The Quote That Was Never Sent
A quote is built, priced, and never sent, then sits in a list that looks exactly like one that was sent and is waiting. What has to be recorded for a pipeline stage to be a fact about the future, and what a sent quote costs.
Somebody priced it. Somebody checked the arithmetic. Somebody formatted it, and it looked right, and it went into a folder — or a record, or a drafts list — and there it has been ever since. Nobody rejected it. Nobody accepted it. Nobody opened it. It is sitting in a list that looks exactly like a list of quotes that were sent and are waiting.
This is a specific and unusually clean kind of loss, because every fact about the quote is true. The scope was real. The price was calculated correctly. The total is right. The document is good. And none of that has any bearing on the outcome, because a quote that was never sent has not been refused and has not been accepted. It is in a third state that most systems have no way to name, and the naming problem is the entire problem.
A quote is the last point in the chain where the work is still negotiable. Once it is sent it becomes a position, and a position can be lost. Before it is sent it is a document with no position taken, and the number of such documents in a business has a way of becoming large enough that nobody can look at them any more. The quote is also, usually, the most expensive artefact the business produces per unit of revenue: somebody's time went into it, and the return on that time is entirely determined by whether it leaves the building.
This is the second of four articles on the weak points of the chain from conversation to money. The first was the enquiry that never became an opportunity. The third is the order taken by phone with no document behind it, and the fourth is the invoice that never reached the customer. The chain as a whole is covered in [Quote to Cash: What Each Step Has to Carry](/blog/quote-to-cash-what-each-step-has-to-carry). This one is about the gap between a document existing and a claim having been made.
The distinctionA quote that exists is a piece of work. A quote that was sent is a claim you made to somebody.
The reason unsent quotes accumulate is that the system treats them as if sending were a formality — the last click before the interesting part begins. It is not the last click. Sending is the moment the document stops being yours and becomes a statement addressed to another party, and everything difficult about a quote happens at that moment. The scope is now something the customer is expected to react to. The price is now a number they can refuse. The date, if there is one, is now an expectation rather than a note. Nothing about the internal version of the document had any of those properties.
So an unsent quote is not a quote in an early state. It is a different object: a piece of work in progress, with all the uncertainty that implies, and it competes for attention with every other piece of work in progress in the business. Nobody prioritises work in progress by value, because work in progress has no value yet. The most expensive document you have written this month is competing for a slot in a queue with drafts, half-written replies, and abandoned spreadsheets, and it is losing, because it is in the queue.
There is a second and less obvious cost, which is that an unsent quote corrupts the pipeline it sits in. If the quote is attached to an opportunity that is still open, then the opportunity looks live, and the pipeline value includes a document that has made no claim on anybody. A manager reading that view is counting a future that depends entirely on somebody remembering to do something. The pipeline and the quote list are usually the same list, which means the number that is supposed to tell you about the future is partly made of things that have not happened to anybody yet.
And a third cost, which is the one that hurts longest. An unsent quote contains a price you were prepared to accept. If the customer eventually comes back — sometimes months later, sometimes through a different person — you have no record that you ever quoted this, and you may well quote differently. Sometimes the difference is correct, because costs moved. Sometimes the difference is a person who has simply lost the document, and you have raised your price against a customer who has been entirely blameless. Both look identical from inside the business, and only one of them is a decision.
Illustrative: three quotes, three states, one list
Sent, waiting
A document exists, it was addressed, and it is in the customer's hands. The customer has not answered. The correct next action is a dated follow-up, and the correct internal state is a claim that has been made and not yet resolved. The cost of this state is time, and the thing you can act on is when to chase.
Not sent
A document exists and nobody outside the business has seen it. There is no customer obligation, no expectation, and no claim on anybody. It is invisible to the customer and it is occupying the same slot in the same list as the first state. The cost of this state is the time already spent plus the chance that the work was never worth finishing.
Sent, then revised
A document was sent and the scope or the price then changed. The revision is a second document, and if it is a change of scope it is a new quote on the same project rather than an edit to the old one, because the first version is already out in the world and the customer may still be holding it.
The requirementFor a pipeline stage to be a fact about the future, it has to be a promise with a date and a recipient
A stage on a quote is usually one of two things: a document status, or a claim about the customer's likely behaviour. The first is cheap and nearly useless for planning. The second is what a forecast needs, and it is only a fact if it can be interrogated. So the useful test is: can you look at the row and say who has it, when they were given it, and what has happened since? If you can, the row is a fact about the future in the sense that matters. If all you have is a name and a colour, you have a filing system.
Three things have to be on the record for that to work, and none of them are difficult. The first is the recipient: which named person the document went to, at which address, on what date. Not a company — a person, because a quote that reaches a company and never reaches the person who decides is the single most common reason a quote appears to have been ignored. The second is the state of the claim: sent, and since then either nothing, or a recorded response of some kind. The third is a dated next action with an owner, because a claim about the future that nobody owns is not a forecast, it is a hope with a value attached to it.
The distinction between a document status and a claim is where most pipelines get muddled, and it shows up in a very specific symptom: a list of quotes where everything says the same thing. If every row in your quote list reads the same, the list is carrying no information. It is not a pipeline. It is an inventory of documents, and an inventory of documents cannot tell you what to do on Thursday. The fix is not a new status to add. It is deciding, once, what a row in this list is a claim about, and refusing to have two different kinds of row in it.
The other requirement is that the record survives the failure. Which means a sent quote has to be more than a flag. It has to carry what was sent, when, and to whom, so that three months later when the customer comes back and asks what you quoted, the answer takes thirty seconds and is the number you actually said. Not a reconstruction, and not the current price. The number that was on the document.
This is also the point at which a scope change has to be handled as a new record rather than an edit, and it is worth being blunt about why. There is no change-request record, no milestone record, no deliverable record, no contract editor and no e-signature in NoxOrigin. A scope change is a new quote on the same project. This is not a limitation dressed up as a principle; it is the same principle. The moment the first version leaves the building it is a document that exists in the world independently of your database, and editing your copy of it does not un-send it. The customer's copy, and quite possibly a forwarded copy, is the version that matters when the two disagree. A new quote with its own number is the only thing that keeps the two apart, and it is the only thing that lets you answer a later question about what was agreed and when with a number rather than a reconstruction.
Illustrative: what the row tells you in each state
| Question | Quote that exists but was never sent | Quote that was sent |
|---|---|---|
| Who is holding this | Nobody. The document exists only inside your business | A named person at a named address, on a recorded date |
| What is being claimed | Nothing. No obligation exists on either side | A position on scope, price and date, waiting on a response |
| What the value in the pipeline means | A piece of work in progress, weighted by an assumption | A claim you made, with a date attached to when it was made |
| What the correct next action is | Decide whether to finish it, or delete it and keep the number for reference | A dated follow-up owned by a person, or a recorded close |
| What happens if the customer comes back in three months | You have no record of what you quoted, and may quote a different number | You can state the exact figure and the date it was given |
| What the cost of leaving it alone is | The time already spent, and a row inflating a pipeline it is not part of | Time only. The claim is real and does not decay by being ignored |
A constructed quote, followed through three states. All figures constructed for this article so the arithmetic can be checked by hand. The 18% GST rate appears only to make the invoice total checkable and is not a statement about the rate that applies to your business.
The quote, as built and priced:
| Line | Arithmetic | Result |
|---|---|---|
| Design and build, fixed fee | as stated on the quote | 150,000.00 |
| Two site visits, travel and accommodation | 2 x 12,000.00 | 24,000.00 |
| Line total before tax | 150,000.00 + 24,000.00 | 174,000.00 |
| Discount agreed in the conversation | as stated | -14,000.00 |
| Quoted value, tax exclusive | 174,000.00 - 14,000.00 | 160,000.00 |
| GST at 18%, for checkability only | 160,000.00 x 0.18 | 28,800.00 |
| Quoted total as it would appear on an invoice | 160,000.00 + 28,800.00 | 188,800.00 |
State one: the quote was never sent. Nothing in the business has been claimed. The only figure that exists anywhere is the total on the draft.
| What is known | Where it lives | Can it be produced later |
|---|---|---|
| The customer asked for this work | In one person's message thread | Only if that person still has it and still remembers it |
| The scope as discussed | In a draft and possibly in a colleague's head | Only from the draft |
| The price quoted | On the draft | Yes, from the draft |
| The date it was quoted | Nowhere, because there is no event | No |
| What the customer was told | Nothing | Not applicable |
State two: the quote was sent on a recorded date to a named person. Now there is a claim, and the same figures carry a different meaning.
| Reading | Arithmetic | Result |
|---|---|---|
| Quoted value, tax exclusive | as above | 160,000.00 |
| Quoted total including GST at 18% for checkability | 160,000.00 x 1.18 | 188,800.00 |
| Days the quote has been outstanding | recorded date to today | a real number |
| The number that can be stated to the customer later | the figure on the sent document | 188,800.00 |
State three: the customer asks for a change before the work starts. This is not an edit to the sent quote. It is a second quote on the same project.
| Line | Arithmetic | Result |
|---|---|---|
| Scope carried forward from the first quote | 160,000.00 | 160,000.00 |
| Additional work requested | as stated by the customer | 20,000.00 |
| Revised quoted value, tax exclusive | 160,000.00 + 20,000.00 | 180,000.00 |
| GST at 18%, for checkability only | 180,000.00 x 0.18 | 32,400.00 |
| Revised quoted total | 180,000.00 + 32,400.00 | 212,400.00 |
| Original quoted total still on record | 160,000.00 x 1.18 | 188,800.00 |
Check the difference. 212,400.00 minus 188,800.00 is 23,600.00, which is 20,000.00 plus 20,000.00 x 0.18 = 20,000.00 + 3,600.00. That is the whole of the change, and it is legible in one line because the first quote was a separate record with its own number and its own send date. Had the first quote been edited in place, the 188,800.00 would no longer exist anywhere, and the only answer available to the customer asking what they were originally quoted would be whatever the system could work backwards from — which is nothing at all.
Why it mattersA quote of unknown status is not slow. It is unpriced.
The usual complaint about quotes that stall is that they are slow to decide, and that is a real problem with a real cost. But slow-to-decide is only one of the states, and it is the least damaging one, because a slow decision still has a clock on it that everybody can see. The state this article is about is different: nobody knows the status, including the person who owns it. That is not slowness. It is the absence of a fact, and an absence of a fact cannot be managed at all.
Consider what a manager can ask about a claim. How many are out. How long have the oldest ones been out. Which of them had a reply. Which of them have been chased and which have not. Every one of those questions is a question about events, and every one of them is unanswerable about a document that was never sent — because there were no events. The document is in the list, and it will stay in the list, and the list will be reported on, and the report will carry a figure that is neither revenue nor a claim. It is an artefact count with a value attached, and treating it as pipeline is how a forecast ends up being a list of intentions.
The second cost is that the time was spent. This is worth being careful about, because there is a temptation to argue that the person who built the quote made a mistake. Usually they did not. They did the work because the work was worth doing on the information they had, and the information they had said to send it. The failure is not in the building. It is in there being no scheduled, boring, unremarkable point at which somebody says the obvious thing — has this gone out yet — and no consequence when the answer is no. A process that depends on a person having a thought is not a process. A list that is worked on a schedule is a process, and the difference between them is the difference between this failure happening and not happening.
The third cost is the one that lands on the customer relationship, and it is the least visible. A quote that was never sent is a quote the customer never received, which from their side is indistinguishable from a business that decided not to bid. If they come back in three months, the honest response — nothing was sent, here is a fresh quote, at a possibly different price — is a worse outcome for everyone than a follow-up in week two. And the quote they eventually do receive will be read, at least partly, through the fact that it took three months. Nobody is owed a quote. But the business that follows up is making a claim about itself that the one that goes quiet is not, and that difference is worth something at the moment a second supplier is also being slow.
The remedy is unglamorous. Decide, in advance and in writing, what happens to a quote that is not sent within a defined window. Usually: it is either sent or it is closed as not proceeding, with the number kept on the record so the next conversation can start from where the last one actually stopped. The important part is that both outcomes are recorded, because the second one is the one that saves the information. A deleted draft teaches nothing twice. A closed draft with a reason is the difference between a business that answered this question before and a business that answers it again from scratch, which is the same situation this series started with, one step further along the chain.
Illustrative: what a quote record has to carry for its status to be a fact
- The recipient: a named person and an address, not a company name. A quote that reached the company and not the decision maker is the most common silent failure.
- The send date. Without it there is no claim, only a document, and the difference is the whole subject of this article.
- The version, with each revision as a separate numbered quote rather than an edit to the previous one.
- A dated next action with an owner on every sent quote that is unanswered.
- An explicit state for a quote that was built and not sent, so those rows are distinguishable from the ones that are waiting.
- The scope as the customer described it, not as it was summarised internally. The summary is what goes wrong in the third hand.
- The customer's own stated date, kept separate from your delivery estimate.
- A rule, decided once, for what happens to an unsent quote after a defined period.
- A rule for what happens when a sent quote is superseded, so the first version is retained with its own number and send date.
- No edit path that would change a quote already sent. A new quote is the mechanism, and it is the only mechanism.
The handoverFrom a sent quote to an order, and the question that usually has no good answer
The next step in the chain is acceptance, and acceptance is where the whole record either holds or becomes a reconstruction. A customer says yes on a call, or by reply, or in a meeting, and the thing that has to exist afterwards is a record of the work and the price, on the same project, that both sides can point at.
The difficulty is that acceptance is nearly always verbal. It arrives as a phone call, a sentence in a meeting, a yes in a message that also contains three other things. Turning that into a record takes a person and a few minutes, and it takes them at the moment when the natural human instinct is to start work. The customer has said yes; the work is available; the instinct is to begin, because beginning feels like momentum and writing it down feels like delay. That is exactly the moment the record is most likely to be skipped, and it is the same structural problem as the counter sale, moved upstream.
So the question a sent-quote process has to answer is not really about the quote at all. It is: when the customer says yes, what is the first thing that happens? If the answer is a document, the chain holds. If the answer is a task that somebody remembers, the chain becomes a sequence of reconstructions, each of which is individually plausible and collectively unreliable. The [Quotation to Order Software](/quotation-to-order-software) page is about keeping the quote, the revision and the order as separate records, and the [Quote to Cash: What Each Step Has to Carry](/blog/quote-to-cash-what-each-step-has-to-carry) article covers the whole handover.
The steps either side of the quote fail in their own ways. the enquiry that never became an opportunity the invoice that never reached the customer the quote that was never a scope
Frequently asked questions
What is the difference between a draft quote and a sent quote?
A draft is a piece of work in progress: it exists only inside your business and no obligation exists on either side. A sent quote is a claim you made to a named person on a recorded date, and it carries a dated next action. Only the second one can carry a figure that means something in a forecast.
Why does an unsent quote corrupt the pipeline value?
Because the quote list and the pipeline are usually the same list. An unsent quote attached to an open opportunity looks live, so its value is counted in a number that is meant to describe the future — even though nothing has been claimed on anybody. The number then partly consists of intentions rather than commitments.
Should a sent quote ever be edited when the scope changes?
No. A scope change is a new quote on the same project. There is no change-request record, no contract editor and no e-signature in NoxOrigin, and that is the right behaviour: the first version is already out in the world and the customer's copy is the one that matters. Keeping both versions as separate numbered quotes is what lets you answer a later question about what was originally agreed.
Does NoxOrigin remind me to send a quote I have drafted?
No. There is no automated quote delivery, no PDF renderer and nothing sent to WhatsApp on send. What exists is a record with a dated next action and an owner, so the follow-up is a scheduled piece of work rather than something you have to think of. The discipline of working the list is still yours.
What should happen to a quote that is not sent within a defined period?
Decide once, in writing, whether it is sent or closed as not proceeding. Closing is the important half: the record keeps the number and the reason, so a later conversation can start from where the last one stopped rather than from nothing.