Pipedrive weighted value: stage and deal probability explained

SOURCE-BASED ANALYSIS · NO HANDS-ON RATING

Distinguish deal value from weighted value

Pipedrive documents stage probability and deal-specific probability. When a deal has its own probability, it takes priority over the stage probability. Weighted value multiplies deal value by the applicable probability; the percentages are not multiplied together. An unadjusted stage probability defaults to 100%. Inspect those settings before assuming a weighted total reflects calibrated closing expectations.

Our recommendation is to treat the resulting number as an assumption-based planning view. A weighted amount is not a booked sale, a bank balance or a promise that a fraction of each opportunity will be paid.

A three-deal arithmetic example

Assume three fictional deals in one currency: A has value 10,000 and stage probability 40%; B has value 6,000, stage probability 40% and an overriding deal probability 75%; C has value 4,000 and applicable probability 25%. Under those assumptions:

For B, multiplying 6,000 by 40% and then 75% would give 1,800, which does not follow the documented override rule. The figures are illustrative calculations, not actual pipeline data, measured win rates or a forecast for your company.

Reconcile your view

1. Record the filter, pipeline, currency and expected-close period defining the view.
2. Inspect the stage probability for each included opportunity.
3. Check whether any deal-specific probability overrides it.
4. Recalculate a small sample using the applicable percentage.
5. Compare the resulting sample with the displayed weighted values.
6. Investigate missing deals or differing scope separately from arithmetic errors.

Document the source of each percentage

Our planning advice is to label whether a probability comes from historical outcomes, a management assumption or a specific opportunity assessment. Do not present an invented percentage as a measured conversion rate. If you lack comparable historical data, retain that limitation next to the planning view.

A mature procurement process and an early inbound enquiry may require different assumptions even when their nominal values match. Establish review responsibility so deal-specific overrides do not become unexplained optimism that nobody revisits.

Keep timing and uncertainty visible

Suppose deal A slips outside the reviewed period. The percentage may remain unchanged while the period's expected value changes. Verify expected-close scope when comparing two screenshots. Similarly, do not combine differently denominated amounts into an unlabeled total without checking the view's currency handling.

Accept a reporting view when another reviewer can reproduce the arithmetic, identify the assumptions and explain its date scope. Compare forecasts with later outcomes to improve the process, but do not claim accuracy from this example. This guide is a mathematical walkthrough of a documented CRM feature, not financial advice, an account test or a sales guarantee.