Deal

Origin & evolution

The deal as a managed object comes from the formalisation of selling into a repeatable process. The lineage runs through the funnel⬇️FunnelGrowthA conversion funnel tracking user progressionView reference → model attributed to E. St. Elmo Lewis around 1898, and through the pipeline metaphor that recast selling as a sequence of stages a prospect passes through. The arrival of customer relationship🫶Customer RelationshipBusiness ModelA type of customer relationshipView reference → management software in the 1990s turned the abstraction into a record. Salesforce, founded in 1999, made the "opportunity🚪OpportunityDiscoveryA validated gap worth solvingView reference →" object central: a row with a value, a stage, an owner, and a close date that the whole organisation could see and forecast🔮ForecastSales & RevenueA revenue forecastView reference → against.

Stage definitions converged on a recognisable shape. Most pipelines run some version of prospecting, qualification, proposal or demo, negotiation, and close, with the deal advancing or dying at each gate. Cirrus Insight and most modern sales guidance describe this five-to-seven stage progression, and the discipline of pipeline management grew up around keeping those stages honest so that forecasts mean something.

The evolution that matters for product teams is win/loss analysis. A deal marked Closed Lost is not just a missing number; it is intelligence. When the loss reason is logged consistently, patterns emerge across many deals: a competitor🥊CompetitorMarket IntelligenceA competing product or companyView reference → that keeps winning on one capability💪CapabilityStrategyAn ability that enables value deliveryView reference →, a price objection🚧ObjectionGo-To-MarketA common sales objectionView reference → that clusters in one segment, a feature⭐FeatureProduct SpecificationA product capability or featureView reference → gap that kills deals at the demo stage. Enterpret and others treat the lost deal as a source of product and positioning🎪PositioningGo-To-MarketProduct positioning statementView reference → signal, which is how a sales-pipeline object becomes a product input.

How it works in practice

A B2B security product runs 60 deals through its pipeline in a quarter and closes 18, a 30 percent win rate. The revenue number is fine, so leadership is content. The product team looks instead at the 42 losses and the reasons attached to each.

A pattern appears at the demo stage. Eleven deals died there, and nine of the eleven loss notes mention the same missing capability: single sign-on with a specific identity provider that larger buyers mandate. These nine were the biggest deals in the pipeline by value, all targeting the enterprise ideal customer profile👤Ideal Customer ProfileGo-To-MarketThe ideal customer profile (ICP)View reference →. The smaller losses were scattered across price and timing with no pattern. The deal records turned a vague "we should win more enterprise" into a specific, costed claim: one integration is blocking the nine largest opportunities at a single, identifiable stage. That is a roadmap🛣️RoadmapProduct SpecificationA strategic plan of features and milestonesView reference → input no amount of survey work would have produced as cleanly, because the deals carried the money, the stage, and the reason together.

Deal vs. its neighbours

• Account is the company you are selling to or already serve, a durable entity that persists across many deals. A deal is one time-boxed opportunity within that relationship. An account can host a first sale, a renewal, and three expansions, each its own deal. The account is the who; the deal is the each-time.
• Ideal customer profile describes the kind of account most worth pursuing, a definition. A deal is a concrete instance that may or may not match that profile. Comparing won deals against the profile tells you whether your targeting is right; the profile is the theory, the deal is the test.
• Opportunity is, in most CRM vocabularies, the same object under a different name, the qualified deal worth forecasting. The distinction is mostly tooling convention: a lead becomes an opportunity once it clears qualification, and from there the terms are used interchangeably for the thing moving through stages.

In the graph

In the Unified Product Graph, deal💼DealSales & RevenueAn active sales opportunity sits in the Sales region as the unit of pipeline progress. The inbound account_negotiates_dealAccountnegotiatesDealhierarchy ties it to the company on the other side, separating the durable relationship from the time-boxed sale. deal_quoted_via_quote_documentDealquoted viaQuote Documenthierarchy connects it to the commercial paperwork, and deal_references_ideal_customer_profileDealreferencesIdeal Customer Profilecross-domain lets a team check real deals against the account they meant to chase. The stage edge deal_at_pipeline_stageDealat stagePipeline Stagecross-domain records where the deal sits in its progression, which is what makes win/loss analysis queryable: aggregate the loss reasons by stage and the product signal falls out. That structure is why a sales object earns a place in a product graph, because a lost deal connected to a stage and a reason is a roadmap input, not just a missed quota.