A stage should describe buyer progress
I want a pipeline stage to describe something the buyer has done. That makes the review a conversation about evidence and remaining decisions, rather than optimism.
A demo completed or proposal sent is seller activity. It can support the purchase but does not establish agreement on problem, scope or approval. Choose a small set of stages that changes what the team does next.
A practical model includes problem validated, evaluation agreed, commercial decision active and executed agreement, with rejected or lost states. Keep research and meetings outside accepted value until your qualification rule is met. Each stage needs evidence, an owner and a remaining-decision field, not merely a color.
Define the exit evidence
For problem validation, record the buyer's workflow and consequence. For evaluation, agree standard scope, success criteria and relevant participants. For commercial decision, understand approval, risk and remaining terms. For agreement, use executed records under the relevant eligibility definition.
Keep unknowns visible when a stage advances. An evaluation can be active while finance authority remains unresolved; that risk should not disappear because a technical step was completed. Forecast probability requires your own calibrated history, not a generic stage percentage.
| Decision | Evidence to use | What changes next |
|---|---|---|
| Problem validated | Buyer-confirmed issue, fit and mutual next action | Clarify decision participants and feasibility |
| Evaluation agreed | Criteria, scope, technical owner and adoption limits | Resolve evaluation and committee risks |
| Commercial decision active | Approval process, accurate terms and remaining dependencies | Manage the mutual plan toward a real agreement |
Review a stalled opportunity
Illustrative deal: an engineering champion liked a demo six weeks ago. The seller has sent reminders and moved the close date, but no evaluation criteria or commercial owner is recorded. The last buyer evidence is interest, not a ready purchase.
Ask whether a change project exists and who would need to approve it. If the buyer confirms a migration must happen first, record that condition and a reasonable review. If there is no active decision, update the state. Do not keep a hopeful date merely to protect the dashboard.
Another deal is stalled because a security document is missing. That needs a named expert and accurate material, not a new outbound sequence. Separate authority, adoption, value and timing gaps so the next action addresses the real decision.
Make the mutual plan useful to the committee
List the buyer's decisions, not only the seller's preferred deadline. Engineering validates feasibility, product confirms workflow impact, security reviews risk and finance addresses the commercial case, where those roles apply. Give each action purpose, owner, dependency and buyer-agreed timing.
A concise sales room can hold the current summary, approved scope, success criteria, transparent assumptions and materials. Keep sensitive records access-appropriate. A plan is not mutual until the buyer confirms that it reflects how the company actually buys and implements.
Report four different economic measures
Pipeline is potential value under opportunity and forecast assumptions. Signed value is the eligible executed commitment. ARR is an annualized recurring run rate under finance definitions. Cash is payment received. Do not add them as if they are independent revenue streams.
Illustrative agreement: $36,000 annual subscription plus $8,000 implementation, paid quarterly for the subscription. First-year commitment, recurring component and cash received will differ. Finance should validate actual contract treatment, especially for usage, cancellation rights, multi-year terms and mixed services. Keep funding and booking-value metrics out of revenue claims.
Measure progression rather than activity alone
Use evidence-supported transitions, conversion by comparable cohort, stage age, unresolved decisions and won/lost reasons. State denominators and observation windows. A young cohort should not be compared with a mature one without explaining the difference.
Inspect whether value is assumed, scoped or executed. A higher guessed amount can grow pipeline without increasing buyer commitment. When history is sparse, describe scenarios and uncertainty rather than a precise probability model. The useful report identifies the next investigation or action.
Make integrations preserve the definitions
Define authoritative records and stable account identifiers before connecting outbound, calendar and CRM. Test duplicate, canceled, rescheduled and poor-fit events. A booking should not automatically become a valued accepted opportunity.
Check actual workflow and API behavior against current product documentation; interface rules may not apply identically to automated paths. Keep suppression and ownership consistent. For a failed synchronization, retain context, alert an owner and recover without duplicate outreach. The system is not ready merely because its happy path looks clean.
Use the worksheet as a review aid
The worksheet includes stage, evidence, missing decision, mutual action, owner, review date and value assumptions. Keep one authoritative operating record. A review date is not a promised close date.
Have another seller choose the next action from the row alone. If they need a verbal reconstruction, improve the context. The pipeline should make work more usable and reporting more truthful at the same time.
Advance stages when the buyer evidence changes
Use stage exits that a second person can inspect. “Demo delivered” describes seller activity; “the buyer agreed what the evaluation must prove” describes a buying decision. Keep an owner and next action on every active opportunity.
Review aging alongside context. A long legal review may be real progress; an apparently active deal without an accountable buyer may be stalled. Do not rely on stage probability alone to explain a forecast.
| Stage | Evidence to leave the stage | Next accountable decision |
|---|---|---|
| Discovery | The buyer confirms a relevant problem and consequence. | Agree who should evaluate a possible change. |
| Evaluation | The team agrees success criteria and reviews the result. | Accept the business case or stop. |
| Commercial alignment | Scope, value and decision participants are explicit. | Resolve remaining contract and risk requirements. |
| Approval | Authorized owners accept the relevant requirements. | Sign or give a specific reason not to proceed. |
| Handover | A delivery owner accepts scope and commitments. | Begin the agreed implementation. |
Connect this decision to the complete startup sales-motion plan.
Sources and research notes
- GitLabcommercial opportunity stages
Company operating handbook
- GitLabCommand Plan
Company operating handbook
- HubSpotPipeline rules
Product documentation
- Bessemer10 laws of cloud
Investor operating guidance
Primary sources reviewed October 6, 2026. The operating recommendations and worked scenarios are Daavid’s analysis. Illustrative numbers are assumptions, not measured client results. Company marks identify sources and prior experience; they do not imply a customer relationship or endorsement.

