From Qualify to Handover is a twelve-stage operating framework beneath one parent Job. Opportunity moves through Qualify, Discover, Propose, Evaluate, Negotiate, and Close; Awarded creates Project; and Project moves through Intake, Validate, Procure, Deploy, Commission, and Handover.
1. One Job, two child workstreams, twelve decisions
The stages in this guide are an SMP operating framework, not a claim that every industry uses identical labels. Their purpose is to make the decisions, ownership, evidence, and next action visible while one Job moves from pursuit to execution.
Opportunity owns the pre-award work. Project owns the post-award work. Awarded is the controlled conversion between them, while Job preserves identity, participants, commitments, documents, Activities, and Notes across both workstreams.
That broader view is consistent with research that reconceptualizes B2B selling as a connected, multi-level process shaped by interpersonal, organizational, dyadic, and network relationships. The research is conceptual rather than a validation of these twelve specific stages, but it supports the need to manage more than a linear seller-to-buyer pipeline.1
SMP ↔ Third-party ERP
SMP owns the Job, workflow, context, and commitments. ERP owns inventory, transactions, and finance.
2. Qualify and Discover: decide whether the Job deserves pursuit
Qualify asks whether there is a credible problem, plausible fit, reachable decision path, responsible owner, and worthwhile next step. The output is not artificial certainty. It is an explicit decision to investigate, nurture, disqualify, or stop.
Discover replaces assumptions with evidence. The team identifies the operating need, success criteria, participants, constraints, timing, competing approaches, and consequences of inaction. Activities capture the work; Notes preserve what was learned and why it matters.
A meta-analysis of salesperson listening found that listening supports customer-oriented and adaptive selling and is associated with trust, satisfaction, relational performance, and sales performance. The practical implication for Discover is straightforward: a completed call is not evidence of discovery unless the customer’s requirements and reasoning become usable context.2
- Qualify output: pursue, nurture, disqualify, or stop
- Discover output: documented needs, participants, constraints, success criteria, and agreed next action
3. Propose and Evaluate: turn requirements into a defensible solution
Propose converts discovery into a solution position. In an engineered sale, that may include basis-of-design assistance, equipment selections, layouts, schedules, specifications, alternatives, budget guidance, and the first formal quote. The proposal should make assumptions and exclusions as visible as products and prices.
Evaluate is a joint test of fit. Technical stakeholders examine performance and compliance; commercial stakeholders examine price, risk, schedule, and terms; the selling team resolves exceptions and determines whether the solution can be delivered as represented.
ASHRAE’s current data-center framework traces work through planning, schematic design, design development, construction documents, bidding, commissioning, and operations. It demonstrates why a proposed equipment solution cannot be separated cleanly from the design and delivery context in which it must perform.3
G2’s CPQ category analysis and individual review excerpts emphasize configuration rules, pricing consistency, approval control, collaboration, and downstream handoffs. Review evidence is qualitative and product-specific, but it reinforces the operational importance of turning seller intent into an offer that finance and operations can fulfill.4
- Propose output: versioned solution, scope, assumptions, commercial position, and quote
- Evaluate output: confirmed fit, documented exceptions, required approvals, and a viable path to decision
4. Negotiate and Close: resolve the commercial record
Negotiate manages the differences between the proposed solution and an acceptable agreement. Price matters, but so do quantities, alternates, lead times, responsibilities, payment terms, exclusions, substitutions, warranties, and the consequences of change.
Close records an outcome. Lost should preserve the reason and what the team learned. Awarded should identify the accepted quote, scope, commercial terms, participants, dates, approvals, outstanding conditions, and first post-award action. A verbal win without a controlled commercial record is not ready for conversion.
A recent practitioner discussion among sales engineers described the post-sale reconstruction of a long technical engagement when promises were distributed across recordings, CRM, and email. The thread is anecdotal and cannot establish prevalence, but it illustrates the exact failure this stage is designed to prevent: execution should not begin with a scavenger hunt for what was agreed.5
- Negotiate output: resolved or explicitly open commercial differences
- Close output: Lost with learning, or Awarded with an authoritative accepted record
5. Awarded is the conversion—not the order
Awarded closes the Opportunity and creates the Project beneath the same Job. It does not erase the pursuit, flatten every note into one summary, or wait for an order to create an execution workspace.
The new Project should inherit the accepted quote and its revisions, approved scope, people and organizations, promised dates, commercial terms, design information, documents, risks, unresolved conditions, and accountable owners. Activities and Notes remain universally available, and Connected Communication keeps the Project conversation attached to the work so shared context can become coordinated action.
A practical conversion gate asks three questions: What exactly was awarded? What remains unresolved? Who owns the next action? If the system cannot answer all three without reconstructing the sale, the Job is not ready to move cleanly into execution.
6. Intake and Validate: make the awarded work executable
Intake establishes operational ownership. The project team confirms the customer and supplier participants, accepted scope, milestones, communication path, required documents, order dependencies, open risks, and immediate actions. Intake is complete when the receiving team can explain the Job without asking the customer to repeat the sale.
Validate tests whether the awarded record is complete enough to procure and deploy. The team verifies selections, quantities, compatibility, approvals, submittal requirements, lead times, site conditions, release constraints, and any difference between the quote, specification, and order intent.
USACE contractor-submittal guidance requires submittals to be prepared early enough for evaluation, approval, procurement, and delivery; it also requires registers, schedules, review results, action dates, and follow-up to be tracked. The regulation applies to its construction contracts, not every sale, but it provides a rigorous example of why validation must precede uncontrolled procurement or installation.6
- Intake output: accepted ownership, execution plan, open-item register, and first actions
- Validate output: approved or exception-managed basis for procurement and deployment
7. Procure and Deploy: manage the order as project work
Procure turns the validated commercial record into supplier commitments and customer orders. It tracks releases, acknowledgements, requested and promised dates, substitutions, price or scope variances, documentation requirements, and dependencies that could prevent fulfillment.
Deploy manages the movement from committed order to usable delivery. Depending on the Job, that can include submittal cycles, drawing approvals, manufacturing status, inspections, logistics, site readiness, delivery, installation coordination, startup preparation, and exception resolution.
G2 defines order-management products around quote or order conversion, fulfillment, inventory visibility, shipping preferences, and tracking from quote through delivery. Category pages are commercial marketplace material rather than independent performance research, but the documented workflow helps show why an order is an active execution object—not merely a number stored after the sale.7
- Procure output: acknowledged commitments, controlled exceptions, and current need dates
- Deploy output: delivered and installation-ready scope with issues resolved or assigned
8. Commission and Handover: prove readiness and transfer usable knowledge
Commission verifies that the delivered solution is installed, started, tested, documented, and capable of meeting the relevant requirements. The exact responsibility varies: a representative may coordinate manufacturer startup and documentation without serving as the project’s formal commissioning authority.
ASHRAE describes commissioning as a documented process involving stakeholder roles, design documents, specifications, procedures, training, systems manuals, and verification that systems meet the Owner’s Project Requirements. Its guidance makes clear that commissioning is not a ceremonial final check; it carries requirements and evidence forward into operation.8
Handover transfers a usable operational record: approved documents, startup and test results, training status, warranties, manuals, unresolved items, responsible contacts, and the next service obligations. Handover is complete when the receiving party can operate and support the result—not merely when files have been sent.
NIST’s General Buildings Information Handover Guide reports substantial historical costs associated with validating and reformatting facility information that should already have been usable. The cost estimates are based on 2002 activity and should not be treated as a current benchmark; their enduring relevance is the documented burden created when lifecycle information cannot be transferred reliably.9
- Commission output: verified performance, documented results, training, and resolved deficiencies
- Handover output: accepted operational record, warranty path, remaining obligations, and closeout readiness
9. What good lifecycle control looks like
A well-controlled process does not require every Job to be complicated. It requires every stage change to have an intelligible reason, a responsible owner, supporting evidence, and a visible next action. Teams may combine stages for simple work or add controls for regulated and engineered work without breaking the parent-child model.
Small samples of customer reviews for specialized manufacturers’ representative software highlight opportunities, quotes and revisions, bid calendars, orders, shipment dates, reporting, and project visibility in the same operating conversation. With only a handful of reviews on the cited profiles, this is a field signal—not representative proof—but it supports the need to evaluate continuity across the whole Job.10
The governing test is simple: can a new participant understand what the customer needs, what was decided, what was promised, what has happened, and what must happen next? From Qualify to Handover, the SMP should make that answer easier at every stage.
Qualify
The pursuit becomes a record. The Job is created as the durable parent, and its Opportunity opens with an explicit decision that the work deserves pursuit.
Where fragmented stacks break: Without a qualifying decision, every inquiry is chased and none is owned.
Frequently asked questions
Are these twelve stages an industry standard?
No. They are the SMP editorial framework for organizing the decisions between initial qualification and operational handover. Companies can adapt the labels while preserving clear ownership, evidence, and exit criteria.
Why does Awarded create the Project before the Order?
The Project needs to manage intake, validation, unresolved conditions, submittals, and procurement readiness. Waiting for an order can leave important post-award work without an accountable operating record.
Where do Activities, Notes, and Connected Communication belong?
Activities and Notes are universal across Leads, People and their Contacts or Users, Organizations and their Customers, Suppliers or Competitors, and Jobs with their Opportunities and Projects. Connected Communication keeps Email, SMS, Group Chat, and future channels connected throughout the system.
Does Handover automatically close the Job?
Not necessarily. Handover establishes operational transfer and closeout readiness. The Job closes when the Project’s remaining commercial, documentation, warranty, and administrative obligations are complete or explicitly assigned.
References
- Susanne Wiatr Borg and Louise Young, “Continuing the Evolution of the Selling Process: A Multi-Level Perspective,” Industrial Marketing Management 43, no. 4 (2014): 543–552. The article presents a conceptual framework of connected relationships in B2B selling; it does not validate the SMP stage names used here.
- Omar S. Itani, Emily A. Goad, and Fernando Jaramillo, “Building Customer Relationships While Achieving Sales Performance Results: Is Listening the Holy Grail of Sales?” Journal of Business Research 102 (2019): 120–130. Meta-analysis of salesperson listening, customer orientation, adaptive selling, and performance outcomes.
- ASHRAE, “AI Data Center Energy Performance Framework: Introduction and Purpose,” accessed August 12, 2026. The framework maps planning, design, construction documents, bidding, commissioning, and operations for this specific engineered-building context.
- G2, “Best CPQ Software,” accessed August 12, 2026. The page combines G2 category descriptions with selected individual review excerpts. It is a commercial marketplace source and is used only to document workflow themes and qualitative user experience.
- Reddit, r/salesengineers, “Had to recall everything that was promised to a client after a multi-month engagement. Help,” accessed August 12, 2026. This is an individual practitioner discussion and is treated as anecdotal evidence, not a representative industry finding.
- U.S. Army Corps of Engineers, ER 415-1-10, Contractor Submittal Procedures (April 30, 2012). The regulation connects submittal evaluation and approval to procurement, delivery, schedules, tracked actions, and quality control in USACE construction contracts.
- G2, “Best Order Management Software,” accessed August 12, 2026. Used to document common order-management workflow boundaries; marketplace category material is not treated as independent proof of performance.
- ASHRAE, “Commissioning,” accessed August 12, 2026. The resource describes Standard 202 and related guidelines covering roles, requirements, documentation, training, systems manuals, and verification against Owner’s Project Requirements.
- Kristine K. Fallon and Mark E. Palmer, General Buildings Information Handover Guide, NISTIR 7417 (2007). The historical cost estimates draw on 2002 activity and are presented with that limitation.
- G2, “Rep Order Management Reviews,” accessed August 12, 2026. The profile contained a small review sample and is used only as a qualitative field signal about opportunity, quote, order, shipment, reporting, and project workflows.
Source types are identified in the notes so peer-reviewed findings, commercial research, product reviews, and individual anecdotes are not presented as equivalent evidence.