A stage within the sales pipeline
A pipeline stage is one discrete step a deal occupies on its way to closing, such as qualified, demo, proposal, or closed won. Each stage is defined by what must be true for a deal to sit there, and the sequence of stages turns a vague sense of progress into a measurable position. The value lives in the exit criteria: a stage that any deal can enter on a salesperson's optimism forecastsForecastSales & RevenueA revenue forecastView reference → nothing.
The staged view of buying descends from the same 1898 sketch that gave us the funnelFunnelGrowthA conversion funnel tracking user progressionView reference →. E. St. Elmo Lewis described a buyer moving through attention, interest, desire, and action, later named the AIDA model and traced to *Printers' Ink*). Sales teams borrowed that progression and inverted its purpose, using the stages to forecast revenue rather than to describe a buyer's mind.
The modern pipeline stage hardened as customer relationshipCustomer RelationshipBusiness ModelA type of customer relationshipView reference → management software made stages into fields. Once a stage was a value in a database, it could be counted, and once it could be counted, the conversion rate between consecutive stages became the central diagnostic of a sales process. Methodologies layered on top: BANT and its successors supplied the questions that decide whether a deal has earned its way out of qualification and into the next stage.
The lasting refinement was the move from activity-defined stages to evidenceEvidenceValidationData supporting or refuting a hypothesisView reference →-defined ones. A stage named "demo given" records what the seller did; a stage named "buyer confirmed the problem is worth solving" records what the buyer did. The second kind forecasts; the first kind flatters. Mature pipelines write exit criteria as buyer actions, which is why two companies with identical stage names can have wildly different forecast accuracy.
A sales operations lead audits a five-stage pipeline: Qualified, Demo, Proposal, Negotiation, Closed. Three hundred deals entered Qualified last quarter. Stage-to-stage rates read 300 to 180 to 95 to 70 to 42. The largest drop sits between Qualified and Demo, where nearly half evaporate.
Reading the exit criteria explains it. Deals were entering Qualified on a single replied email, with no confirmed budget owner. The fix is not more demos; it is a tighter exit rule for Qualified, requiring a named economic buyer before a deal advances. The next quarter the Qualified count falls to 190, the Qualified-to-Demo rate climbs to 78 percent, and the forecast finally tracks reality. The stage definition, not the selling, moved the number.
deal_at_pipeline_stageDealat stagePipeline Stagecross-domain is the live pointer, and a deal occupies exactly one stage at a time.pipeline_sales_contains_pipeline_stagePipeline SalescontainsPipeline Stagehierarchy holds that composition, which is what lets the same deal flow be reused across teams.In the Unified Product Graph, a pipeline stage is a structural component of the sales pipeline, held by Pipeline SalescontainsPipeline Stagehierarchy, with each deal pinned to its current step through pipeline_sales_contains_pipeline_stageDealat stagePipeline Stagecross-domain. Separating the stage from the deal means conversion rates fall out of the structure for free: count the deals at each stage, compare to the next, and the leak shows itself. That structure also keeps the sales pipeline distinct from the marketing funnel in the graph, so a product team can read where qualified demand stalls without mistaking a buyer's attention for a seller's forecast.deal_at_pipeline_stage
Type-specific fields on BaseNode
stage_ordernumberPosition of this stage in the pipeline sequence
conversion_ratenumberPercentage of deals that advance from this stage
avg_days_in_stagenumberAverage number of days deals spend in this stage
idstringrequiredUnique identifier (UUID)
typeNodeTyperequiredDiscriminator for the entity type
titlestringrequiredDisplay name
descriptionstringOptional detailed description
statusstringLifecycle status
tagsstring[]Freeform tags for filtering
2 edge types connected to this entity.
pipeline_sales_contains_pipeline_stagedeal_at_pipeline_stage