PIVOT lives
in the CRM.
Five custom property groups - one per PIVOT stage. Exit criteria are verifiable. Deal confidence is calculated from buyer evidence, not rep optimism. Managers see the factual state of every deal without a story.
Works in HubSpot, Salesforce, and Pipedrive. The property names differ. The logic is the same.
Five PIVOT Property Groups
Each PIVOT stage becomes a property group in the CRM. The fields are specific - not free-text notes. Exit criteria are mandatory before a deal can advance to the next stage. Sellers fill them as the deal progresses.
| Stage | Property Group | Key Properties | Field Type | Exit Trigger |
|---|---|---|---|---|
| P · Pain | PIVOT Pain | pivot_symptoms · pivot_business_problem · pivot_root_cause | Multi-line · required for Discover | Root cause confirmed in buyer's own language |
| I · Impact | PIVOT Impact | pivot_neg_impact · pivot_impact_metric · pivot_future_state | Currency + dropdown + text | € leakage quantified from buyer's own data. EB confirmed the number. |
| V · Value | PIVOT Value | pivot_differentiator · pivot_value_design · pivot_proof | Multi-line + checkbox | PoC scorecard submitted or ICP-matched case study confirmed |
| O · Orchestration | PIVOT Orchestration | pivot_champion · pivot_economic_buyer · pivot_decision_process | Contact assoc. + text | EB access confirmed. Decision process documented. |
| T · Transaction | PIVOT Transaction | pivot_decision_criteria · pivot_close_plan · pivot_handoff_date | Text + date | Contract terms agreed. CS handoff date set. |
A stage cannot advance until its exit trigger is verified in the buyer's own words.
Confidence Score Logic
PIVOT Confidence % is a calculated field. It counts completed stages, not filled fields. The count drives the forecast category - no rep can manually override it.
Create five custom property groups
One group per PIVOT stage. Each group has defined input fields - not free-text notes. All mandatory fields must be marked required in the CRM field settings.
Map exit criteria to each group
Configure stage-exit rules: a deal cannot advance from Discover to Validate until pivot_root_cause and pivot_neg_impact are filled. Block the stage-move button, not just add a warning.
Wire Confidence % to forecast category
Build a calculated property: (completed_stages / 5) × 100. Map to forecast: 0–39% = Pipeline, 40–59% = Upside, 60–79% = Best Case, 80–99% = Best Case (O must be complete for Commit), 100% = Commit eligible.
Confidence is calculated, not declared. Reps cannot override the forecast category.
Example Deal View
3 of 5 stages complete = Best Case. Commit requires O verified — no exceptions.
Quick Reference - Property Names
| Property Name | Type | Stage | Required At |
|---|---|---|---|
pivot_symptoms | Multi-line text | P | Qualify exit |
pivot_business_problem | Multi-line text | P | Qualify exit |
pivot_root_cause | Single-line text | P | Qualify exit |
pivot_neg_impact | Currency | I | Discover exit |
pivot_impact_metric | Dropdown | I | Discover exit |
pivot_future_state | Multi-line text | I | Discover exit |
pivot_differentiator | Multi-line text | V | Validate exit |
pivot_value_design | Multi-line text | V | Validate exit |
pivot_proof | Checkbox | V | Validate exit |
pivot_champion | Contact association | O | Justify exit |
pivot_economic_buyer | Contact association | O | Justify exit |
pivot_decision_process | Single-line text | O | Justify exit |
pivot_decision_criteria | Multi-line text | T | Commit exit |
pivot_close_plan | Multi-line text | T | Commit exit |
pivot_confidence_pct | Calculated (read-only) | All | Drives forecast category |
Copy these exact field names — every formula and report downstream depends on them.
PIVOT Confidence % = stages complete ÷ 5. A deal at 66% (3 of 5 stages) sits in Best Case, not Commit. Commit requires O confirmed - Economic Buyer access documented and decision process mapped. No exceptions.