The Lead That Was Never Really a Lead: Enquiries, Opportunities, and a Decision Somebody Has to Make
A price request is not an opportunity. What distinguishes an enquiry from a deal, why the distinction has to be a decision rather than a free field, and the case for letting some enquiries be counted as enquiries.
A price request arrives. Somebody forwards it to the sales person, who creates a record and puts it in the pipeline, because turning somebody away feels like losing a customer who might one day buy something else. Three weeks later the same queue contains a price request, a genuine project enquiry, and a customer's question about their existing order, and all three are sitting in the same stage of the same report.
This is a small administrative decision and it has a large downstream effect. An opportunity is supposed to be a claim that some money will arrive. If the pipeline also holds things that are not claims about money, then the pipeline total is not a statement about money, and every conversation that starts from that total — hiring, targets, hiring again — is resting on a category error.
The claim in one line
Not every enquiry is an opportunity, and the difference has to be a decision somebody makes with a stated reason, because a field that anybody can set at any moment records what somebody felt that afternoon rather than what is true about the enquiry.
A price request is not an opportunity, and it is not a lead either
The word lead has been stretched to cover at least four different measurements — an enquiry received, a conversation started, a need identified, and a thing that might be sold — and once one word carries all four, asking whether a lead converted becomes a question with no answer attached. The definition of the record at /glossary/crm-and-sales separates the terms for this reason.
The useful distinction for a sales team is between an enquiry and an opportunity, and it can be stated without any vocabulary at all. An enquiry is something that arrived. An opportunity is something you have decided you intend to win, at a value you have discussed, for work you have described.
A price request usually fails the second test in a specific, interesting way: nobody has decided anything. There is no project, no decision-maker identified, no scope, no date, and no number that was agreed by both sides. Somebody asked what it costs. That is a real event that deserves a reply, and it may become an opportunity next week. It is not an opportunity today, and the difference is not pedantry, it is that an opportunity in the queue obliges somebody to chase a number, and a price request does not.
What has to be true before an enquiry becomes an opportunity (illustrative)
There is a project, described in words
Not a product interest. Something the customer actually wants done, in enough detail that two people would describe it the same way. If the only shared content is a price list, there is no project yet.
There is a decision-maker, by name
Somebody who can say yes, and somebody whose agreement is required. An opportunity attached only to whoever sent an email is attached to a reader, not to a decision.
There is a number both sides have discussed
A figure that came from a conversation rather than a list. This is the test that most price requests fail, and it is a good test, because a number nobody has agreed to is a guess the customer did not make.
There is a next action with a date on it
Something specific that happens next, on a day, with a person. An opportunity with no dated next action is an optimism entry, and it will age quietly into a stale deal, which is the subject of the cleanup article in this set.
One week of enquiries (worked example, illustrative — every enquiry and figure is invented; arithmetic shown)
The table below is a constructed week. Fourteen enquiries arrive. Five of them are turned into opportunities with discussed values, and those five total 370,000. Then two of the five turn out not to be new opportunities at all: both are existing customers asking about work already in progress, which is a service question that belongs against the current project, not a new claim on the future.
Fourteen enquiries in a week, read honestly (worked example, illustrative — the enquiries and figures are invented; arithmetic shown)
| Enquiry | What actually arrived | Became an opportunity? | Value discussed |
|---|---|---|---|
| 1 | Price list request for a single item. | No | — |
| 2 | Price list request, three items, no scope discussed. | No | — |
| 3 | Described project, decision-maker identified, figure discussed. | Yes | 150,000 |
| 4 | General question about a service, no project named. | No | — |
| 5 | Existing customer asking about their current order. | No | — |
| 6 | Described project, verbal agreement to proceed, figure discussed. | Yes | 95,000 |
| 7 | Price list request forwarded with no message body. | No | — |
| 8 | Described project, decision-maker not yet identified. | No | — |
| 9 | Described project, figure discussed, existing customer asking about current work. | Yes, then reclassified | 60,000 |
| 10 | Spare parts enquiry, treated as a sale by the sender. | No | — |
| 11 | Described project, decision-maker identified, figure discussed. | Yes | 40,000 |
| 12 | Enquiry from a supplier, not a customer. | No | — |
| 13 | Described project, figure discussed, existing customer asking about current work. | Yes, then reclassified | 25,000 |
| 14 | Duplicate of enquiry 4, forwarded twice by two people. | No | — |
Checking the arithmetic.
- Enquiries received: 14.
- Opportunities created: enquiries 3, 6, 9, 11, 13 — that is 5.
- Value as first recorded: 150,000 + 95,000 + 60,000 + 40,000 + 25,000 = 370,000.
- Reclassified away as existing-customer questions about current work: enquiries 9 and 13, at 60,000 and 25,000.
- Value removed: 60,000 + 25,000 = 85,000.
- Value remaining: 370,000 - 85,000 = 285,000.
- Check from the individual deals: 150,000 + 95,000 + 40,000 = 285,000. Matches.
So a week that began with 14 items to handle and 370,000 of claimed opportunity value ended with 14 items to handle and 285,000. The work did not change. Fourteen enquiries still each owed a reply. Only the number that was allowed to sit in the pipeline as a claim about money changed, and it changed because two of the five had been classified by whoever forwarded them rather than by what was true about them.
Why the distinction has to be a decision, not a field somebody can set freely
The obvious design is a field called opportunity, ticked by whoever is handling the enquiry. It is quick, it requires no policy, and it produces exactly the number in the table above: a value that reflects how generous the week felt rather than what was established.
The problem is not that people tick it wrongly. Most of them tick it consistently, according to an unstated personal rule that formed years ago, and the rule is usually reasonable. The problem is that a freely settable field cannot answer the question a pipeline exists to answer, because it records an intention rather than a state. A tick says: at 4pm on Tuesday, this person believed this was worth pursuing. That is real information. It is not the same as: this is a project with a decision-maker and an agreed figure, and here is the date somebody will do the next thing about it.
Making the promotion a decision means somebody examines the enquiry against written conditions and records the outcome, including the outcome of no. That is slower, and the slowness is the point: the conditions are checked once, by a person, instead of being assumed fourteen times a week by whoever was quickest. A deal that fails the conditions is not a failure. It is an enquiry, and there is a separate and correct place to count it.
Enquiry and opportunity compared on their own terms (structural comparison — no measured outcomes)
| Enquiry | Opportunity | |
|---|---|---|
| What it is | Something that arrived and is owed a reply. | A project you have decided to win, with a figure discussed. |
| What must exist | A message from somebody, or a forwarded enquiry. | A described project, a named decision-maker, a discussed figure, a dated next action. |
| What may be counted | Enquiries received in a period. | Value of opportunities you intend to pursue. |
| What it obliges you to do | Reply, and record what was asked. | Chase, forecast, and eventually quote or lose. |
| What it is not | A deal that is quietly drifting to nothing. | A guaranteed sale, or a booked amount. |
| What kills it | Nobody replies, or it was never a customer. | A dated next action that passes without happening. |
The argument for letting some enquiries be counted as enquiries
The instinct is to promote everything, on the theory that a bigger pipeline feels safer. It is worth resisting, for a reason that has nothing to do with the pipeline total.
An enquiry is a unit of work. Somebody sent a message and a reply is owed, and that reply takes time whether or not the enquiry ever becomes a sale. If enquiries are not counted anywhere, that work is real and invisible. It gets absorbed into the gaps between real deals, it is never resourced, and the only symptom is that nobody has time to follow up on the things that are actually going to close.
Counting enquiries as enquiries makes the workload visible. It puts fourteen items in front of a manager as fourteen items, rather than as five opportunities and a vague sense of busyness. It also gives the business something it does not otherwise have: an honest answer to whether the effort of responding is worth it. A week of fourteen enquiries and three genuine opportunities is a real result. It is also a different week from fourteen enquiries and no opportunities, and without a separate count for enquiries you cannot tell those two weeks apart.
The counter-argument, that a separate count is more work, is true and small. It is also the work that makes the opportunity count mean something. If every item becomes an opportunity, the opportunity count is a measure of how many messages arrived, and the pipeline has stopped carrying information about whether any of them were real.
What to decide before the next enquiry arrives (illustrative)
- Write down the conditions an enquiry must meet to become an opportunity, in terms of things that exist
- Name the person who makes that call, so it is a decision rather than a mood at 4pm
- Create a place for enquiries that are still awaiting a reply, separate from the pipeline
- Decide what an enquiry count is used for — resourcing the reply, not padding a total
- Check whether any incoming enquiry is from an existing customer about current work, and route it to the project
- Look for the same enquiry arriving twice, and decide which copy survives
- Decide what happens to an opportunity when its dated next action passes without happening
Where this stops, honestly
NoxCRM keeps lead and opportunity records with owners, stages, dated activities, consent records, and the history of what happened to each one. That is the record layer for the decision described above, and it is where the conditions get written down and applied.
Several things people expect a lead-management system to contain are not in NoxCRM, and it is better to say so than to let you find out during an evaluation. There is no lead scoring engine, so no deal arrives with a score that argues for its own stage. There is no marketing automation and no email sequence builder, so nothing is enrolled in a drip campaign behind your back. There is no dialler. There is no territory management, so enquiries are not routed by geography, and if routing enquiries by pin code or region is how your business works, that is something you build during setup or handle outside the system. Finally, there is no CRM-native forecasting model, which is the subject of the previous article in this set.
This absence is coherent rather than accidental. A lead scoring engine and an email sequence builder both work by making claims on a person's behalf — that this enquiry is worth pursuing, and that this is the right message for it. The whole argument of this article is that those claims should be a person making a decision, with a reason recorded, which is why the system gives you the records and the review and leaves the judgement with the team.
The enquiry conditions, the routing and the review are agreed during setup for the dedicated NoxCRM deployment, which is scoped per business. The CRM records they sit on are part of every NoxOrigin plan. If you are still working out the basic lead record and ownership model, the longer version is at /blog/crm-basics-small-business-whatsapp-spreadsheets and the migration checklist is at /blog/crm-basics-small-business-whatsapp-spreadsheets. If you are moving contacts and consent records across from a spreadsheet, /templates/crm-migration-template has a sheet for the field mapping that has to be written before anything is imported.
What we have not measured
We have not measured how many enquiries typically become opportunities, and there is no honest version of that number that would apply to your business rather than to an invented one. The counts in the table are constructed, the arithmetic is checkable, and the conclusion does not depend on the counts being representative — it depends only on the two reclassified enquiries being correctly reclassified.
Your own version is a single evening of work: take the enquiries received in the last month, and mark each one as a project with a discussed figure or as something that was only a question. The number that surprises you is the one worth acting on, and it is derived entirely from your own records rather than from anybody's average.
Frequently asked questions
Should every enquiry become an opportunity so nothing falls through?
No, and the reason is not that enquiries are low value. It is that a pipeline which holds everything holds nothing in particular. If every enquiry is an opportunity, the opportunity count is a count of messages, and the value attached to them is the value of whoever forwarded them most enthusiastically. Nothing falls through because enquiries are still tracked and still owed a reply — they are just tracked as enquiries, which is what they are.
What is the difference between a lead and an opportunity?
A lead is something that arrived and might be worth pursuing. An opportunity is a project you have decided to pursue, with a described scope, a named decision-maker, a figure both sides have discussed, and a dated next action. The gap between the two is a decision rather than a delay, and it is the decision that gives an opportunity its value: the value on an opportunity is a number that came from a conversation, not a guess somebody made while forwarding an email.
How do we stop people creating junk opportunities?
Not by asking them to exercise more judgement, but by making the promotion cost something. Written conditions, a named person who applies them, and a recorded reason either way. When the conditions are checkable, most junk stops being created rather than cleaned up afterwards, and the cases that still slip through are visible because each one carries a decision somebody made. A field anyone can set at any time cannot do this, because it records a feeling rather than a check.
What about enquiries from existing customers?
They are usually not new opportunities, and treating them as one inflates the pipeline with money you were going to receive anyway. A question about an order already in progress belongs against that project. The check is simple: does this enquiry describe work that is not currently quoted or contracted? If it does not, it is a service question and it should be recorded where it can be answered, not added to the value of the month.
Does NoxCRM score leads or automate our follow-up?
No. There is no lead scoring engine, no marketing automation, no email sequence builder, and no dialler in NoxCRM, and there is no territory management for routing enquiries by region. What NoxCRM keeps is the record layer — leads and opportunities with owners, stages, dated activities, consent, and history — and the decision about whether an enquiry is worth pursuing stays with a person, which is the argument this article makes.