Skip to content
PRESHaiPRESHaiPRESHos Platform

Deal types

Settings → Deals is the deal-type hub: each deal type maps to one workflow and one pipeline. Pick the type first; the stages, probabilities, and approvals follow the type, not the deal. Treat the product UI as the source of truth for the type rows your tenant offers.

One type, one pipeline

Section titled “One type, one pipeline”

Each deal type carries its own pipeline: stages with groups, statuses, and probability percents for weighted forecasting. The capture below shows one type’s table — the Opportunity Pipeline with Prospecting (10, Active, Open), Solution Design (40, Active, Open), Proposal Sent (50, Active, Open), Renewal (50, Active, Open), Decision Maker Bought-In (70, Active, Open), and Won stages at 100.

  • Probabilities weight the forecast: open stages carry partial credit, closed Won stages carry full credit. Change a probability when the team agrees the stage means something different, not per-deal.
  • The picker selects which type’s pipeline the table edits; stages, groups, and statuses belong to that type.
One deal type's pipeline table: Opportunity Pipeline stages with groups, statuses, and probability percents

Motion vs. deal type

Section titled “Motion vs. deal type”

Motion and deal type are different fields — do not mix them. The deal type selects the workflow and pipeline the deal runs; motion describes how the deal moves (the sales motion behind it). A deal with the right type and no motion is routable but undescribed; a deal with motion and the wrong type runs the wrong workflow.

Quote approvals per type

Section titled “Quote approvals per type”

Each deal type sets its own quote approvals: which quotes need a named approver role before they go out. Configure approvals on the type, not per quote — the quote inherits the gate from its deal’s type.

What next

Section titled “What next”