The Enquiry That Never Became an Opportunity
Most enquiries die between hello and not interested, and nothing records that they died. What an opportunity has to be for a stage change to mean something, and why a dead enquiry should be recorded as dead.
Somebody sent you a message. You answered it. They told you, in the language people use when they want you to stop replying, that your business is not the kind of business they were looking for. Then the conversation ended, correctly, and nothing anywhere recorded that it ended.
That is the whole event. It took four messages and about eleven minutes, and it produced no line in any list, no stage, no note, no reason. Six weeks later the same person, or somebody from the same kind of company, writes to you with the same kind of question, and the whole conversation happens again from zero, because the record of the first one does not exist. The person asking does not know or care that you have answered this before. Your side of it does not know either, because the only trace of the first conversation is in one person's message history, and that history is not something a business can make decisions from.
This is the first of four articles on specific steps of the chain from a conversation to money in the bank. The others isolate the quote that was built and never sent, the order taken by phone with no document behind it, and the invoice that was issued and never arrived. The chain as a whole is covered separately in [Quote to Cash: What Each Step Has to Carry](/blog/quote-to-cash-what-each-step-has-to-carry); that article is about the transitions. This one is about the gap before the first transition, where an enquiry is supposed to become an opportunity and instead quietly stops existing.
The argument is narrow and it is not about pipeline features. It is that a stage change has to mean something for a stage to be worth having, and that recording a dead enquiry as dead is not bookkeeping for its own sake — it is the only thing that makes the surviving pipeline worth reading.
The distinctionAn enquiry is noise. An opportunity is a claim you have staked something on.
The most common way a small business handles an inbound enquiry is to let it become an opportunity immediately, because a stage is a place where you can see it and an inbox is not. This is a reasonable instinct and it produces a specific, quiet corruption. The pipeline fills with rows that are indistinguishable, at a glance, from rows where money is genuinely in play: same stage name, same probability, same colour, same number in the total at the top. Somebody is supposed to know which is which. Usually the person who typed it, and only for about a week.
The problem is not the volume. A hundred enquiries a month is a hundred enquiries a month, and a business that gets a hundred enquiries a month is doing well. The problem is that a pipeline of a hundred things that might happen is not a forecast, a workload plan, or a management view. It is an inbox with columns. And a manager looking at a hundred identical rows does something completely predictable: they stop looking, because the view has not distinguished itself from noise. This is the same failure that makes a wall of unread email unread, and it is not a discipline problem. A list that never distinguishes anything is a list people learn to ignore, and once they have learned to ignore it, the two real opportunities in there are ignored as well.
So the useful question is not how do I capture more enquiries. It is what is the difference between the row for somebody who said we are not interested in your business and the row for somebody who asked for a price, a timeline, and a reference for a similar project. Both arrived by message. Both have a name in them. Both are sitting in a list at the moment. The only difference is what has been established, and everything downstream depends on that difference being written down somewhere a person can act on.
An opportunity, defined properly, is not a contact and it is not a message. It is a record of something somebody has committed to that creates a cost to you if the business does not happen. They have given you a real scope. They have given you a date. They have told you who else is deciding. They have asked you to put a written price against a specific piece of work and to put a date on it. Those are commitments, and they are what makes the row a forecastable object rather than a memory. An opportunity is a promise somebody has made to you about their own future behaviour, and the reason to record it separately from an enquiry is that it is the only kind of row in your business that is a promise about somebody else's action.
There is a related point about who the record is for. An enquiry record serves the person who answered the message. An opportunity record serves the person who has to make a decision in three weeks about whether to hold capacity back. Those are different readers, and they need different fields. The first wants the transcript and a next action. The second wants scope, decision process, timing, and the name of the person who can actually say yes. A single row trying to serve both is why most CRMs end up with a notes field that is never read and a probability column nobody trusts.
Illustrative: the same message, read as an enquiry and read as an opportunity
Read as an enquiry
A person asked a question. Somebody answered it. The conversation ended without a decision. The only record of it is one person's message thread, and the only thing that thread can tell a business is that a question was asked and a reply was sent. It cannot tell anyone whether the business was ever real, whether the person has budget, or whether this is the fourth time the same scope has been quoted by four different suppliers.
Read as an opportunity
A named decision process exists. A specific scope has been described. A date has been stated, and the date came from the customer rather than from you. A written price has been requested against that scope. A person has asked what happens if the date slips. Every one of these is a statement about the customer's own intentions, made deliberately, and together they are enough to say what the work would involve and what would have to be true for it to happen.
The requirementFor a stage to be worth having, moving into it has to have changed what is known
A pipeline stage is usually understood as a label. It is better understood as a claim about how much is known, and the whole list is only useful if moving between stages means the amount known has genuinely changed. If two adjacent stages can be entered without learning anything new, they are one stage with two colours, and a manager reading the list has to do the analysis the system was supposed to do.
There is a useful test for this. Ask: what would a person have to know, that they could not know yesterday, in order for it to be honest to move the row? If the answer is a fact — they gave me a date, they confirmed who signs, they told me the scope is three sites — the stage is real and entering it is an event. If the answer is a judgement, a feeling, or an elapsed amount of time, the stage is decoration. Time-based stages are the worst offenders, because they convert a list of claims into a list of ages, and an age tells a manager nothing except that somebody is not moving it.
The same test applies in reverse, and this is the part that is usually missing. For a stage to be meaningful, there has to be a condition for leaving it that includes leaving it as a loss. If a row can only leave a stage by going forward, then the stage is an assumption rather than a measurement, and every number derived from the pipeline is a projection of a world where nothing is ever lost. That is the single most consequential structural flaw in a small sales process, because it does not make the pipeline look optimistic — it makes it look accurate.
Which brings us to the enquiry that died. If an opportunity cannot be marked as lost, then an enquiry that turns out not to be an opportunity has nowhere to go. It cannot be promoted, because promoting it is a lie. So it stays. And every dead enquiry sits in the same place as every live one, in the same stage, with the same probability weight, contributing the same value to whatever number is drawn from the top of the list. The list grows, the number grows, and the growth is composed entirely of things that were already known to be dead.
A stage with an entry condition and no exit condition is a queue. A stage with both is a measurement. Only the second one can be used to decide anything.
Illustrative: what a stage needs before a number can be read off it
| Question about the stage | Stage that is only a label | Stage that can carry a decision |
|---|---|---|
| What must be true to enter | Nothing in particular. A row appears when somebody types the name in | A specific fact is established that was not known before, and it is written on the record |
| What must be true to leave | The next stage is chosen. There is no losing move | Either a defined fact is established, or a person records a loss with a stated reason |
| What the age of a row means | That nobody has touched it. Time is the only signal available | That a condition has been outstanding since a stated date, and somebody owns chasing it |
| What happens to a bad enquiry | It sits in the same stage as a good one, adding weight to the same number | It is removed from the number, with the reason attached, and can be looked at later |
| What the total at the top means | Everything anyone ever typed in, weighted by an assumption | A claim about the future made by people who agreed what each stage was asserting |
| What a review can discover | That the list is too long and somebody should clean it | Which stage is where things actually stop, and whether the stage names are wrong |
A constructed pipeline, before and after the loss path exists. All figures constructed for this article. No conversion rate, win rate or average deal value is asserted anywhere in this piece; the amounts below are invented so the arithmetic is checkable.
Suppose a month produces four enquiries. Three of them turn into opportunities. Here they are with invented values, and no probability attached, because attaching a probability to a stage you have not measured is the thing this article is about.
| Row | What actually happened | Constructed value |
|---|---|---|
| A | Asked for a price and a timeline, gave a scope, named the person who signs, asked what happens if the date slips | 180,000.00 |
| B | Asked for a price, said it was for a board review next month, no scope given | 90,000.00 |
| C | Asked whether you handle a specific thing, then said your business is not a fit for this work | 0.00 — no opportunity ever existed |
| D | Replied to a general enquiry, asked one clarifying question, then stopped replying | 0.00 — no opportunity ever existed |
Pipeline as it stands in the system that cannot record a loss. Every row that was ever created is still there, in one stage, and the only number available is a sum.
| Reading | Arithmetic | Result |
|---|---|---|
| Sum of all rows in the pipeline | 180,000.00 + 90,000.00 + 0.00 + 0.00 | 270,000.00 |
| Rows in the pipeline | 4 | 4 |
| Rows that are claims about the future | 2 | 2 |
| Half the list is dead | 2 of 4 | 50% of the list |
Pipeline once the loss path exists. Rows C and D are closed as non-opportunities with a reason, and the reason is what makes the record useful later.
| Reading | Arithmetic | Result |
|---|---|---|
| Rows still open | A and B | 2 |
| Constructed value still open | 180,000.00 + 90,000.00 | 270,000.00 |
| Closed as not an opportunity, with a reason recorded | C: not a fit for our work. D: no reply after one clarifying question | 2 rows |
| Same month, a new enquiry arrives identical in shape to D | It can be compared against a recorded D | — |
What actually changed. Nothing about the sales process improved. No more messages were answered and nobody chased harder. The only change is that two rows stopped pretending to be futures. The sum is the same in both tables, and that is the point worth sitting with: the number did not move, so the number was never the problem. What moved is that the list can now be read, because a third of it has a name on it.
And the reason is the part that pays. Row C closed because the customer said it plainly: we do not handle this kind of work, thanks anyway — an illustration, not a quotation from anyone. Row D closed because one clarifying question went out and nothing came back. Those are two different reasons and they point in two different directions. One tells you the segment or the positioning is wrong. The other tells you the first reply is too slow, or too general. Without a reason recorded, both rows are simply absent from the pipeline and both lessons are lost. With a reason recorded, they are two entries in a list you can read in ten minutes, and that list will start telling you something about your business that no amount of pipeline hygiene gets you otherwise.
The argumentA closed enquiry is not a failure. It is the only measurement this step produces.
There is an obvious objection to all of this, and it deserves a straight answer. Marking a dead enquiry as dead is work, and dead enquiries pay nothing. Why spend a minute on something that produced nothing? The answer is that the work is not per-enquiry. It is per-pattern. The value of recording a loss is not in the row you closed; it is in the reason, and the reason only becomes information when there are several of them and they agree. One loss teaches you nothing. Nine losses with the same stated reason is a fact about your market, and you cannot get to the nine without closing the first eight.
The second reason is more practical and more uncomfortable. Every row you cannot close is a row somebody has to keep looking at, and the person keeping looking at it is usually the person who does not want to have the conversation that marks it dead. Marking a row as lost requires somebody to say, in a record, that this one is not happening. That is socially expensive in a small business, and it is exactly the reason the rows are not closed. The design implication is that closing has to be cheap enough to be done at the moment the customer says the thing, while the customer is still the reason it is obvious. A closure that takes four fields and a justification paragraph will not happen. A closure that takes a reason chosen from a short list and one sentence will happen most of the time.
The third reason is about the next enquiry, which is where this article started. When the same kind of person comes back, the useful question is not whether you have met them. It is whether you have already established that they are not a fit, and what you said. A record with a stated reason is a record you can read in fifteen seconds before deciding how to reply. Without it, the reply is written from nothing, and it is written the same way it was written the first time, which is how a business that has answered the same question forty times keeps producing the same answer.
There is a fourth, quieter benefit, and it is about the quality of what remains. A pipeline where closing is normal is a pipeline where the open rows are the ones somebody has actually thought about, because the unconsidered ones have been filtered out by the act of closing. A pipeline where closing is painful is a pipeline where every row has been considered by nobody, and the volume in it is a measure of how many messages the business receives rather than a measure of how much work might happen. Reducing the row count by closing honest losses is not pessimism. It is the thing that makes the number mean something.
And it is worth being clear about the boundary. Recording that an enquiry died is a claim about the past — this conversation happened, this person said that, on this date. It is not a prediction and it is not a score. A system that tried to infer quality from the shape of a message would be making a judgement about a person on the strength of a few words, and NoxOrigin does not do that. There is no lead scoring here and no marketing automation behind it: nothing reads your messages and assigns a number. The claim is recorded by a person who was in the conversation and knew what happened. That is a smaller, duller, and much more defensible thing than scoring, and it is the whole mechanism.
Illustrative: what to settle before your loss path means anything
- Name the stages in terms of what is known, not what the seller hopes. If you cannot say what a person would have to have told you to justify entry, the stage name is decoration.
- Write an exit condition for every stage, including the exit that is a loss. A stage you can only leave forwards is a queue.
- Keep a short list of loss reasons and keep it small. Around six is usually enough to be useful and small enough to be chosen without thinking.
- Require the reason to be the customer's stated reason where you have one, and your own reason where you do not. Do not merge the two, because they are different facts about different people.
- Separate enquiries from opportunities as different records. A message is an enquiry; a claim about the future is an opportunity.
- Give every open row one owner and one dated next action. An unowned row is a row that will be closed by nobody and lost by nobody.
- Do not attach a probability to a stage you have not yet measured. A number that has not been earned is worse than no number, because it will be quoted onward.
- Decide what happens to a dead enquiry's customer record. Usually the customer record survives as a customer; only the opportunity is closed.
- Review closed-as-non-opportunity reasons on a schedule. The value is in the pattern, and patterns need a date on them.
- Say plainly in your process that a non-opportunity is a normal outcome and not a performance issue, or the reasons will be written to look better than they are.
The next stepWhat has to survive the handover from an enquiry to a quote
The reason to get this step right is downstream, and it is worth being concrete about it. A quote is an expensive thing to produce: it takes somebody's time, it creates an expectation, and once it exists the customer has a document in their hand with a number on it. So the only question that matters at the end of the opportunity step is whether what was established during the conversation is available to the person who has to write that quote, without re-interviewing the customer.
That means the scope, as the customer described it, has to be on the record. Not a summary of a summary — the actual thing they said they needed, in their terms, with their quantities. Because when the quote comes back with a number in it that does not match what they expected, the cause is almost always a gap here, at the point where a conversation became a record and something was dropped. A scope recorded as internal needs to be scoped works. A scope recorded as a summary of what they said does not survive a third hand.
It also means the decision process has to be on the record while it is still known. Who signs, who else looks at it, whether a board is involved, whether there is a budget holder who has never appeared in the conversation. This is information you get for free during an enquiry and cannot get later, and it is the difference between a quote that gets decided and a quote that goes quiet. The record has to hold the fact that the price will be reviewed by someone you have never spoken to, because that person is the one who will object, and the objection will come as a surprise if you did not know they existed.
Finally, the date has to be captured as the customer's date and kept as such. Your own delivery estimate is a commitment you can make. Their internal deadline is a fact about them, and it is usually the thing that decides the deal. A quote that arrives the day after their board meeting is a lost quote, and the loss is almost invisible unless somebody recorded that the meeting was on the fourteenth.
None of this needs automation, and none of it needs a score. It needs a record that a person can fill in while the customer is still on the line, which is a completely different thing and a far more achievable one. The [Sales Pipeline and Forecast Software](/sales-pipeline-and-forecast-software) page sets out how NoxOrigin treats stages as claims about the future, and the [CRM Operating Guide for a Small Service Business](/blog/crm-basics-small-business-whatsapp-spreadsheets) covers the weekly review that keeps a list of claims honest.
Frequently asked questions
What is the difference between an enquiry and an opportunity?
An enquiry is a question somebody asked. An opportunity is a claim about the future that the customer has committed to: a described scope, a stated date, a named decision process, or a request for a written price against specific work. The distinction matters because only an opportunity carries a cost to you if the business does not happen, which is what makes it worth tracking as a separate record.
Why does a dead enquiry need to be recorded rather than just deleted?
Because the reason is the only output this step produces. A single closed enquiry teaches nothing, but several closures sharing a stated reason is a fact about your segment or your first reply, and it can only be found if each closure recorded why. Without the reason, the row is simply absent and the lesson goes with it.
Is a stage without a loss exit ever useful?
It is a queue. A stage that can only be left forwards assumes that everything in it will eventually convert, so any figure derived from it is a projection of a world where nothing is lost. Only a stage with both an entry condition and an exit condition — including a losing exit — can carry a number that means what it says.
Does NoxOrigin score or rank incoming enquiries?
No. There is no lead scoring, no marketing automation and no email sequence builder. Nothing reads a message and assigns a quality number. The stage, the owner and the loss reason are recorded by a person who was in the conversation, which is a smaller and more defensible claim than an inferred score.
What happens to the customer record when an opportunity is lost?
The opportunity is closed with a reason; the customer record normally stays. A customer who is not a fit for one piece of work may well be a fit for another, and the reason they are not a fit is worth keeping attached to the customer rather than discarding with the row.