Sales Pipeline

Origin & evolution

The pipeline descends from the sales funnel⬇️FunnelGrowthA conversion funnel tracking user progressionView reference →, which E. St. Elmo Lewis sketched in 1898 as the AIDA sequence (attention, interest, desire, action). William Townsend gave it the funnel shape in 1924, modelling how a wide pool of prospects narrows toward purchase. That early model described aggregate flow.

The pipeline reframed the same stages around the individual deal. The funnel asks what fraction of a cohort👥CohortGrowthA group of users sharing a common characteristicView reference → converts; the pipeline asks where each specific opportunity🚪OpportunityDiscoveryA validated gap worth solvingView reference → stands and what has to happen next. CRM made this concrete: stages became database states, and a deal's position became a fact you could report on. The structured-stage discipline hardened further with qualification methodologies. MEDDIC, built at PTC in 1996, tied stage progression to evidence🔎EvidenceValidationData supporting or refuting a hypothesisView reference →, so a deal could not slide forward on a salesperson's good feeling alone.

How it works in practice

A SaaS team runs a five-stage pipeline: Discovery, Demo, Proposal, Negotiation, Closed. Their quarterly target is £500k. Finance asks the obvious question, do we have enough in flight to hit it. The team sums every open deal's value and gets £1.6m, a coverage ratio of 3.2:1, comfortably inside the 3:1 to 5:1 band that healthy organisations hold. Coverage answers whether the queue is full. It says nothing about speed, so they also track velocity: deal count times average value times win rate, divided by average cycle length. Velocity exposes the bottleneck that coverage hides, deals piling up in Negotiation because legal review takes three weeks. Two metrics🔢MetricStrategyA unified metric that measures progress, health, or behaviour across the productView reference →, two different questions.

Sales Pipeline vs. its neighbours

• Marketing funnel measures conversion rates across a cohort: how many of this month's leads became opportunities. The pipeline tracks named deals as discrete objects you can forecast🔮ForecastSales & RevenueA revenue forecastView reference → and act on. The funnel is a percentage; the pipeline is a list with owners.
• Pipeline stage🧽Pipeline StageSales & RevenueA stage in the sales pipelineView reference → is one position within the pipeline. The pipeline is the ordered whole; a stage is a single step, with its own entry and exit criteria.
• Forecast is a judgement made about the pipeline: which open deals will actually close this period. The pipeline is the full inventory of possibility; the forecast is the subset the team will commit to.

In the graph

In the Unified Product Graph, pipeline_sales🪈Pipeline SalesSales & RevenueA sales pipeline sits in the sales domain of the Business, GTM & Growth region. A product reaches its market through it via product_sold_via_pipeline_salesProductsold viaPipeline Saleshierarchy, and the pipeline owns its ordered steps through pipeline_sales_contains_pipeline_stagePipeline SalescontainsPipeline Stagehierarchy. It also qualifies inbound interest with pipeline_sales_qualifies_leadPipeline SalesqualifiesLeadhierarchy, the edge that turns a raw lead into a tracked deal. Modelling the pipeline as a container of stages, where a flat field would store only a single label, is what lets the graph reason about progression, coverage, and where revenue is genuinely at risk🎲RiskComplianceA risk to the product or businessView reference →.