Classify Demand and Admit One Agreement Attempt

On July 8, HarborWorks has a Northline inquiry, not an opportunity. The facilities director's name and message identify a possible customer, but the record does not yet establish a specific agreement attempt, a forecastable amount, or a buyer decision. This chapter turns that captured signal into a dated intake decision and permits opportunity HW-104 only after the required evidence exists.

Demand Intake and Qualification Boundaries

Apply the qualification boundary to every captured demand signal before it can enter opportunity pipeline.

A business can receive demand through inbound inquiries, referrals, outbound responses, partner introductions, or internal handoffs. The Sales Operations owner gives each signal a defined outcome instead of allowing activity alone to imply acceptance.

Classification means assigning each incoming signal to an outcome category using rules that can be applied consistently and checked later. The outcome determines whether the organization will activate an opportunity, perform bounded pre-opportunity work, defer the signal, or decline pursuit.

Without a recorded classification, the owner cannot distinguish work Sales accepted from signals that were merely captured.

Store an incoming demand signal as a lead until the qualification owner accepts or rejects it.

Use the lead record to identify a person or company and capture the contact event. It supports response and evaluation, not forecasting; at this point, no agreement or buying process has been confirmed.

Treat every new lead as uncommitted by default. This is a status rule, not a judgment about quality. Until the published gate is met, the record remains outside opportunity and forecast measures.

Outside opportunity does not mean outside tracking. If evaluation requires seller effort before the gate is met, attach a tracked work item or pre-opportunity state to the lead or account. Give it an owner, next review date, evidence, and disposition, and report its workload separately from opportunity pipeline.

Configure every new lead to enter one initial state that means "not yet evaluated." Exclude that state from pipeline views and forecasting logic, assign an evaluation owner, and keep it visibly separate until classification is complete.

Accept, Defer, or Reject Each Signal

Qualification is the decision that a lead satisfies the applicable gate for entry into opportunity pipeline as a potential agreement.

Once a lead is qualified, the organization treats it differently. The record becomes eligible for activation as an opportunity, management may plan against its published state, and opportunity reporting begins to count it. Earlier evaluation work can still consume capacity, but it remains separately labeled.

In practical terms, use an explicit "accepted" or "rejected" outcome. States such as "working," "contacted," or "in progress" are interim states; treating them as terminal postpones the decision and hides indecision inside activity.

Record qualification in a dedicated status field at a specific moment in time. Do not let activity alone imply acceptance.

A lead cannot be accepted unless the organization has enough information to justify pursuit.

That information falls into three categories. Record each in a form that allows later review.

The first category is fit: the stated need maps to something the company currently sells. Capture the mapped offering or use-case category and allow an explicit unresolved outcome while the operator investigates; do not force a guessed fit value to pass the gate.

The second category is the buying path: how the buyer expects to make a decision. At qualification, it can be incomplete, but the available evidence needs to support a plausible path. Record known participants, approvals, and expected procurement or legal review. These inputs help the owner judge whether a proposed timeframe is credible.

The third category is a buyer-committed next step. Under this book's default gate, a next step qualifies only if it requires buyer effort. Buyer effort means the buyer must involve others, produce information, or initiate an internal process. Seller actions, such as sending materials or scheduling follow-ups, do not count. In the default model, the qualifying buyer action marks entry into the opportunity cohort.

Some motions do not expose direct buyer effort at this point. A public tender, channel-led pursuit, or complex account-development motion may use an approved alternate gate with motion-specific evidence, an owner, a version, and separate cohort reporting. Until either gate is satisfied, keep the work recorded but outside opportunity pipeline.

To apply the default gate, a validation rule should block or route acceptance when fit, buying path, or next-step evidence is missing. Where that is not technically or operationally appropriate, a recorded reviewer attestation and exception queue can perform the check. An approved alternate gate uses its own substitute-evidence schema at the acceptance decision, not as later backfill.

Qualification does not always result in acceptance. Rejection is a valid recorded outcome.

Rejection is the recorded decision not to pursue the lead as a deal. Its reason and evidence preserve the record for demand-quality and qualification analysis.

Record rejection explicitly and categorize it. If a rejected lead disappears or remains unlabeled, reporting cannot include it in rejection-rate or reason-distribution measures.

For every rejected lead, capture a reason from a controlled list. Give each reason a distinct meaning. Free-text notes may add context, but they do not replace the standardized category.

Controlled rejection reasons allow the owner to form testable questions about audience fit, price expectations, buying access, or timing. The reason field records the seller's classification; it does not prove the upstream cause.

Give unresolved qualification decisions a deadline. The qualification owner sets a maximum window from captured demand. At expiry, route the record to a named exception owner, dated pre-opportunity queue, rejection, or deferred state. Automation must not invent a commercial rejection, and ambiguity must not remain in an undated hidden queue.

When an Opportunity May Enter Pipeline

An opportunity represents a potential agreement and enters pipeline only after the applicable qualification gate. A CRM may use one technical object for earlier work, but a pre-opportunity state must keep its amount and count outside pipeline measures.

Restrict opportunity activation to accepted leads and require the offering, opportunity amount basis and initial amount method, pricing unit or pricing method, buying entity, and either a buyer-grounded decision window or an explicit unbounded-timing state that is excluded from time-bounded forecasts.

Block activation until the default or approved alternate gate passes and the creation fields exist. Classify the opportunity as new business, renewal, expansion, or amendment because those types can use different stages, prices, and forecast rules. Keep an unresolved type in the qualification exception state rather than creating a persistent unknown opportunity.

Reviewing Qualification Decisions.

Audit a sample against the criteria and evidence effective when each decision was made. Here, drift means observed use departing from that published rule; it does not imply motive. Use supported findings to revise definitions, fields, or workflows prospectively rather than judging an earlier decision with a later rule (Anderson & Oliver, 1987; Oliver & Anderson, 1995).

If records that fail the gate are accepted, early-stage counts and amounts include a different population from the one the definition claims. Conversion and forecast reports then mix eligible opportunities with exceptions.

Report captured demand, accepted sales work, rejected demand, and unresolved exceptions separately. Every downstream conversion denominator must identify which admitted population it uses.

Test Four Outcomes From One Intake Queue

HarborWorks reviews four Monday signals. Northline is accepted after the facilities director supplies the eight-site list and schedules the scope review. A student requesting a school interview is rejected as ineligible. A facilities group considering next year's maintenance plan is deferred to a dated review because no current buyer step exists. A second Northline form is marked duplicate and linked to HW-104. The intake report preserves all four signals, while only Northline's accepted record may create new pipeline.

The qualification contract lists every permitted state, its evidence, decision clock, reason, fallback owner, opportunity gate, reporting treatment, and audit sample. Sales Operations maintains the rule; the sales leader decides cases that exceed the clock.

Completed HarborWorks intake decision

A reusable record needs the same fields: signal identifier, fit, buying path, buyer effort or approved substitute, decision, evidence links, actor, time, rule version, reporting treatment, and return route.

Turn the Intake Decision Into a Pipeline Claim

Acceptance permits HarborWorks to create HW-104; it does not make every later claim about stage, amount, timing, execution, or handoff true. Sales Operations must now state which claims about the admitted agreement attempt may enter planning records and what evidence each claim requires.

This book distinguishes two uses of commitment. A buyer commitment is an observable agreement to take a defined next step, such as involving procurement or reviewing commercial terms. A planning commitment is an internal forecast classification allowed only when the required buyer commitments, amount, timing evidence, and execution conditions exist. Neither term means a signed sale; only closed-won represents a binding agreement under the close policy.

Evidence means a recorded fact another operator can inspect later. A buyer email requesting contract review, a purchase order, and an executed agreement are evidence of different states. "They seemed ready" is an interpretation and cannot satisfy a gate without the fact that supports it.

Seller activity and buyer commitment are separate. A call, demo, or proposal records seller work; it becomes stage evidence only when the stage definition names the buyer response that must accompany it.

A reliable forecast, in this book, is one whose definition, horizon, error measure, and tolerance are explicit enough for a named business decision. The owner sets the tolerance from the consequence of error; no universal percentage fits hiring, cash planning, and staffing equally. Forecasting research supports structuring and documenting judgment rather than treating confidence as self-validating (Lawrence et al., 2006; Fildes & Goodwin, 2007).

Decisions Sales Operations Owns.

An opportunity enters pipeline only after the business's activation gate. Earlier research or pursuit work may remain in a pre-opportunity record, but it contributes neither opportunity count nor amount. The opportunity supports sales planning; it is not the contract.

A deal record becomes useful when it contains enough information to answer four questions in a consistent way:

1. 01What is being sold.
2. 02What economic amount and amount basis the company is planning against.
3. 03When the agreement is expected to be finalized.
4. 04What must occur next for the deal to advance.

If a reviewer must reconstruct one of these answers from memory or side messages, the record is not ready for the decision that consumes it. Stages group opportunities by observable buyer decisions—such as agreeing to evaluate a defined scope, involving procurement, or reviewing commercial terms—not by seller activity alone. No stage name carries an intrinsic probability; the business measures outcomes for records that met the same versioned rule.

How a Record Enters Opportunity Pipeline.

Meeting a lead does not create pipeline. A lead becomes an opportunity only when it satisfies the published gate for an active agreement attempt. The Sales Operations owner maintains the gate; the commercial owner approves its meaning and any alternate path.

This book's default gate includes:

• —There is a defined buyer problem that matches what the company sells.
• —There is an identified buying process, even if it is incomplete.
• —There is an agreed next step that requires buyer effort.

Retain the fact that supports each condition. A checked box without a source or reviewer cannot establish that the gate was met.

The gate controls pipeline, not whether legitimate work may occur. Research, discovery, account mapping, request-for-proposal review, and technical scoping can remain in a tracked pre-opportunity item.

At minimum, that item needs a buying-entity or account link, source and work type, owner, current request or hypothesis, next action, next review date, evidence links, and disposition. It may consume capacity, but it carries no opportunity stage, probability, or forecast amount.

When the gate is met, activate the opportunity and preserve the earlier record link. Otherwise defer, decline, or close the item with a reason. A formal public tender may need an approved alternate gate because direct buyer effort is unavailable; version its substitute evidence and report the cohort separately.

What a Stage Must Contain.

A stage contract contains:

• —The buyer decision that defines the stage.
• —The evidence that supports the buyer decision recorded.
• —The fields required when the deal enters the stage.

Required fields should be limited to inputs consumed at or after that stage. If proposal review implies a defined offer, require scope and proposed term there—not at initial activation and not after signature. Audit a sample against the applicable stage-contract version and report the evidence and field results, exceptions, and repair owner.

Advance the record only when the next stage's evidence and required fields exist. Preserve prior stage, new stage, actor, event time, evidence, and rule version. A manual override also records the missing condition, reason, approver, and expiration.

Time spent in stage is stage age: the elapsed time between stage entry and exit, or between entry and the measurement date for an open deal. Compare age with the business's own historical distribution for the same deal type and stage. An outlier is an investigation trigger, not proof that the deal will slip or be lost.

The pipeline owner may use a stage-age outlier as a candidate risk signal after testing its relationship with slippage and loss. Slippage means an expected close window moving into a later forecast period.

Some named-deal forecasts use a stage or category base rate; other forecasts use aggregate cohorts, scenarios, order states, or structured judgment. Publish the method and decision. Keep manual judgment separate from the observed rate so both can be evaluated.

A conversion rate is the share of a defined starting cohort that reaches a named later state within a stated window.

For example, if 30 of 50 comparable deals that entered a defined stage closed-won within 90 days, the observed cohort rate is 60 percent. That is a historical base rate, not a promise that the next deal has a known 60 percent chance. The forecast policy states how the base rate is used, what minimum cohort is acceptable, and how any judgmental adjustment is documented.

If the same stage label used different gates across teams or periods, calculate separate cohorts or mark the series non-comparable. Use only comparable cohorts in the forecast method and calibration tests.

An expected close window is the period in which the current agreement attempt is expected to resolve as won or lost. It is a planning claim, not a follow-up reminder. Set it only when buyer or procurement timing evidence exists, and require a controlled reason whenever it moves.

Controlled categories can include procurement, legal review, budget approval, buyer priority, and internal pricing approval; retain only distinctions that route a different investigation. Before timing evidence exists, keep the record outside time-bounded forecast categories rather than using a placeholder date.

The stage contract also states when scope and terms become required. Scope identifies the offering, service level, quantity, and options. Terms include duration, billing frequency, payment timing, cancellation provisions, and other material obligations. Treat those fields as stage evidence when the asserted buyer decision depends on them; Chapters 8–10 specify their pricing, approval, and execution treatment.

Closing and Transfer.

A deal closes when it reaches one of two terminal outcomes: closed-won or closed-lost.

Closed-won means the agreement satisfies the organization's counsel-approved binding criteria. Closed-lost means the current agreement attempt has ended without satisfying closed-won and meets the owner's closure policy. Missing an expected close window is slippage, not loss.

The close policy requires a controlled closed-lost reason. Keep no decision separate from a named competitor, price, missing capability, timing, or internal priority, and route each category to its corresponding investigation.

Closed-lost reasons exist because pipeline learning requires classification. Classification means grouping outcomes into categories so patterns can be measured.

The close policy defines opportunity disposition. A separate handoff policy defines what must exist before a closed-won record can transfer to delivery.

A transfer record includes final scope, terms, constraints, and promises that affect delivery. If an item lives in another versioned document, link it. The receiving owner accepts or rejects the handoff against the checklist.

This is why Sales Operations work on the agreement does not end at signature. It ends at documented transfer, while the opportunity's closed-won timestamp remains the binding-outcome timestamp.

Audit four conditions before revising the policy: unsupported stage entry, placeholder timing, missing scope or terms, and an unaccepted transfer. Report exceptions separately from compliant records, preserve later corrections, and record any resulting rework or delay. The pattern identifies records for investigation; it does not establish motive or business effect.

Apply the Pipeline Gate to HW-104

HarborWorks logs Northline's July 8 inquiry in an account-linked pre-opportunity work item with an owner and review date. The item remains outside pipeline until July 10, when the facilities director confirms the eight-site problem, identifies Northline as the purchasing entity, supplies the site list, and schedules a scope review. The CRM then activates HW-104, preserves the work-item lineage, stores the message and site list as evidence, and records the direct-service rule version. A later proposal will not advance the opportunity by itself; the relevant stage will require Northline's defined response.

A pipeline charter is the controlled record of the opportunity-activation gate, pre-opportunity work-item rule, alternate-gate authority, stage-contract template, controlled close-window reasons, probability method, terminal-state rules, and separate handoff acceptance criteria. Name the commercial executive who approves the policy and the Sales Operations owner who maintains it.

Conclusion

You can now classify every captured signal, keep legitimate early work visible without calling it pipeline, and activate one agreement attempt only after the published gate passes. The completed qualification contract explains accepted, deferred, rejected, duplicate, and unresolved outcomes; the pipeline charter keeps buyer commitment, planning commitment, binding execution, and handoff acceptance separate. If HW-104 lacks fit, buying-path, or buyer-effort evidence, return it to the dated pre-opportunity queue instead of manufacturing an amount, stage, or close date.

Chapter glossary

• —Buyer commitment: An observable buyer agreement to take a defined next step that requires effort or coordination.
• —Planning commitment: An internal forecast classification permitted only when required buyer, amount, timing, and execution evidence exists.
• —Evidence: A recorded fact or source another operator can inspect to support or challenge a state claim.
• —Opportunity-activation gate: The published criteria and evidence required before one agreement attempt may enter opportunity pipeline.
• —Stage contract: The buyer commitment, accepted evidence, required fields, permitted transitions, and exception authority for one stage.
• —Stage age: Elapsed time between stage entry and exit, or between entry and the review date for an open opportunity.
• —Slippage: Movement of an expected close window into a later forecast period.
• —Conversion rate: The share of a defined starting cohort that reaches a named later state within a stated window.
• —Expected close window: The evidence-backed period in which the current agreement attempt is expected to resolve as won or lost.
• —Pipeline charter: The controlled record of pipeline admission, pre-opportunity work, stage, timing, probability, closure, and handoff rules.
• —Qualification boundary: The published rule separating captured or pre-opportunity work from opportunity pipeline.
• —Classification: Assignment of an incoming signal to an outcome category using rules that can be applied and checked consistently.
• —Lead: A record for a captured demand signal that supports response and evaluation but does not establish an agreement attempt or forecast.
• —Qualification: The decision that a lead satisfies the applicable gate for entry into opportunity pipeline.
• —Buying path: The buyer's expected decision process, including known participants, approvals, procurement, and legal steps.
• —Buyer effort: An action that requires the buyer to coordinate, approve, supply information, or initiate an internal process.
• —Qualification rejection: The recorded decision not to pursue a captured lead as a current agreement attempt, with reason and evidence retained.
• —Drift: Observed use that departs from the published rule without implying a motive.
• —Qualification contract: The record of permitted intake outcomes, evidence, decision clock, reasons, fallback owner, opportunity gate, reporting treatment, and audit method.