Set Opportunity Entry Criteria Without Inflating Pipeline

A prospect can fit your target market, reply politely and accept a useful resource without having a buying project. Creating an opportunity at each of those moments makes the pipeline larger without making it more informative. An entry gate should identify when there is enough evidence to track a particular commercial decision, not reward every sign of engagement.

Define the gate for your selling motion. A public tender, a self-service purchase and a consultative project will not produce identical evidence. The common requirement is that the record explains a specific potential purchase and why it belongs in the opportunity process now.

Separate system classification from business qualification

A CRM label may describe a record relationship rather than a judgment about buying readiness. For example, HubSpot: Use contact and company lifecycle stages defines its default Opportunity lifecycle stage through association with a deal. Creating the deal can therefore affect the label; the label is not independent proof that your qualification criteria were met.

Write the business gate outside that circular logic. Decide which evidence must exist before the team creates an active opportunity, who reviews it and where uncertain cases remain. Do not demand certainty about every late-stage detail at entry, but do not fill missing information with a speculative amount or deadline.

A useful entry decision can be “not yet.” Keep relevant research and accepted communication obligations in their proper records. Declining to create a deal does not require deleting the account, abandoning a requested answer or treating the person as unqualified for every future situation.

Build a five-part entry card

Record the proposed project boundary, the buyer-supported reason to investigate it, the plausible fit with your service, the accountable internal owner and the next decision that would clarify whether to proceed. Include known constraints that could make the project unsuitable.

Distinguish a next decision from a seller activity. Preparing a generic presentation is work, but it may not resolve any buying uncertainty. Reviewing whether the proposed service supports a named workflow is a decision-oriented step, provided the relevant participants have actually agreed to the review or the purchasing process calls for it.

Do not make the entry gate a disguised guarantee. Budget, purchasing route and timing may remain unknown at an early stage. Record those gaps and the intended clarification rather than pretending an initial conversation established them.

Apply the gate to three fictional candidates

Candidate A is Birch Components, which announces a new site and appears to match your service area. No conversation or published buying process identifies a project for your service. The entry card contains a research hypothesis, not a buyer-supported initiative. Outcome: retain in the research queue; no active opportunity yet.

Candidate B is Cedar Distribution. Its process owner describes a specific dispatch handoff problem and agrees to review an anonymized example with your specialist. Your service may address that workflow, and an internal owner accepts responsibility for the review. Outcome: create an early evaluation opportunity under the team's definitions, while leaving budget and purchasing timing explicitly unknown.

Candidate C is Elm Support. A contact requests a service requiring around-the-clock coverage that your organization cannot provide. The requirement is central, not optional. Outcome: do not create an active fit opportunity merely because the contact is ready to discuss price. Record the mismatch and any appropriate, authorized response separately.

Make exceptions visible and bounded

A formal procurement process might prohibit discovery meetings before submission. That does not automatically prevent an opportunity from meeting the gate. Use the published requirement, permitted clarification route and documented bid decision as relevant evidence. Record why that evidence substitutes for a direct conversation rather than silently waiving the gate.

Have the reviewer identify the exact exception, its owner and its limits. An exception to the discovery format is not an exception to truthful capability claims, delivery feasibility or required commercial approval. A larger potential amount should not reduce the evidence standard.

Audit the gate without rewarding rejection

Review a small set of recently created opportunities and some cases kept outside the pipeline. Ask whether each decision can be reconstructed from the evidence available at the time. Look for both false positives and projects excluded by unnecessarily rigid rules.

If entry records repeatedly lack a project boundary, improve intake before tightening forecast targets. If legitimate buying processes do not fit the gate, revise the definitions with examples. The goal is a pipeline whose entries represent explainable commercial possibilities, not the smallest possible list or the largest possible number.

Continue with Create a Weekly Pipeline Review That Ends with Decisions or Keep Research Notes Separate from Customer Commitments.