A formal price quote sent to a prospect
A quote document is the formal price proposal a seller hands a buyer: the configured product, the agreed line items, the discounts, and the terms, captured in one approved artefact. It is an offer, generally not yet binding, and the quote is where a deal's commercial shape gets pinned down before anyone signs.
Quoting predates software; the priced proposal is as old as trade. The discipline that surrounds the modern quote is younger. As products grew configurable, with options, bundles, and rules that made some combinations invalid, manual quoting became error-prone, and a category emerged to govern it: Configure, Price, Quote, or CPQ. BigMachines, founded in 2000 by Godard Abel and Christopher Shutts and acquired by Oracle in 2013, moved CPQ to the browser, so configuration rules, pricing logic, and approval routing lived in one system, work that had previously scattered across a sales engineer's spreadsheets.
What CPQ added to the bare quote was governance. A configured quote validates that the chosen options actually work together; a pricing engine applies the right rate and currency; an approval workflow routes any discount past its guardrail to a manager before the document can reach the customer. The quote stopped being a document a rep typed and became the output of a controlled process, which is how organisations stop margin leaking through unchecked discounting.
Salesforce's CPQ documentation codifies exactly these mechanics as the operational baseline for a controlled quoting process: configuration rules that block invalid combinations, tiered approval thresholds keyed to discount depth, and versioned quote records that preserve the full approval trail. That treatment reinforces the point that a quote's governance value comes from the system enforcing the rules, not from the document itself.
A rep configures a £140k annual subscriptionSubscriptionSales & RevenueA recurring subscriptionView reference →: 200 seats, a premium support tier, and a data-residency add-on. The CPQ tool blocks an invalid pairing, the add-on requires the premium tier, so the rep cannot quote a broken bundle. To win the deal the rep applies a 22% discount. Policy auto-approves discounts up to 15%; anything beyond routes to the regional sales director. The quote sits in pending-approval until she signs off, then generates as a versioned document with a 30-day validity window. The buyer accepts in writing, and only at that point does the quote acquire contractual force.
Tracy's writing on sales closes treats the written proposal as a deliberate commitment device: putting terms on paper with a defined expiry date moves the buyer from open-ended discussion to a concrete decisionDecisionStrategyA recorded decision with context, rationale, and consequencesView reference →. By that reading, the 30-day validity window and the requirement for written acceptance are not merely administrative conventions but the mechanism by which a quote converts commercial intent into a closing moment.
In the Unified Product Graph, Quote DocumentSales & RevenueA formal quote document sits in the sales domain of the Business, GTM & Growth region, and it attaches to the deal it prices through quote_documentDealquoted viaQuote Documenthierarchy. Keeping the quote distinct from the deal matters: a single deal can carry several quote versions as terms are renegotiated, and the edge preserves that the deal is the ongoing negotiation while each quote is a dated, approved snapshot of where the commercials stood. That separation is what lets the graph trace how a price moved, and who approved each step, on the way to a signature.deal_quoted_via_quote_document
Type-specific fields on BaseNode
quote_statusenumCurrent status of the quote
total_amountnumberTotal monetary amount of the quote
valid_untilstringExpiration date of the quote (ISO format)
currencystringCurrency code (e.g. "USD", "EUR")
idstringrequiredUnique identifier (UUID)
typeNodeTyperequiredDiscriminator for the entity type
titlestringrequiredDisplay name
descriptionstringOptional detailed description
statusstringLifecycle status
tagsstring[]Freeform tags for filtering
5 phases, initial: proposed · template: APPROVAL
2 edge types connected to this entity.
deal_quoted_via_quote_documentquote_document_advances_deal