CRM MVP
A record of what the customer is actually buying.
This changes over the life of an opportunity as much as the value does, and it is the field almost nobody ships properly. It does not have to be structured to count in part.
Two opportunities at the same value are indistinguishable at a glance. Afterwards nobody can say what was sold, so you cannot analyse what you win at, and a won opportunity cannot be handed to delivery without going back to the customer to ask what they bought.
In full where products or line items attach to the opportunity. In part where the only facility is a general description, a notes box, or a field the buyer creates. Not at all where there is nowhere to put it.
A Products and Services tab holding line items with name, item number, quantity, price and discount.
Only a generic description attribute; the vendor suggests tags or custom fields for what is sold.
Opportunity Products ship as line items with their own layout, driving the calculated Value.
Products attach as line items with per-deal quantity, price and currency, and can drive deal value.
Only a generic Deal Description box; no products or line items on the deal.
Only a generic note field; no scope or line-item facility on the opportunity.
Only a generic Notes box; no scope or line-items field survives in current documentation.
The opportunity ships only Summary, a general overview; products are line items on a Quote, a child record.
Only details, documented as a description, with no products or line-items facility.
Only a generic Description field; no products or line items on the opportunity.
The Opportunity Product table ships as line items associated with an opportunity.
A standard Products related list takes line items with quantity, sales price and discount.
The documented system attributes include no description, products or line items on Deals.
The default template supplies no description, scope or products field.
No description, deliverables or products column ships; the Products widget is added manually, is in beta and needs a connected catalogue board.
The API response ships Associated_Products, and products associate to pipeline records.
A Notes column ships in every pipeline, but it is generic free text, not a scope or line-items facility.
Only a generic Deal Description box; no products or line-items facility documented.
A Product field ships, and the API attaches products as line items on the deal.
Deal revenue line items hold the products and services being sold.
The only shipped descriptive facility is per-deal notes; no scope or line-item field.
Products attach to the lead through the Revenue widget with editable quantity, price and discount.
Line items ship on the deal record, taking library products or bespoke items.
A Products related list ships on the deal record alongside Quotes and Sales Orders.