Sales Intel
Deal Blockers
Deals stuck behind missing features. Revenue-quantified, priority-ranked, and linked to the features that would unblock them.
The Deal Blockers page is the revenue-quantified input from sales to product. Each row is a deal stuck behind something product needs to build.
What you'll see
- List view: title, ID, status (
open | resolved | lost), priority (critical | high | medium | low), revenue impact ($), account, blocked-on features (the first title plus a count; hover for the full list), created - Sort options: default sort by revenue impact descending
- Filter bar: status, priority
- Blocker pipeline strip: open / resolved / lost counts; click a stage to filter the list to it
Row drawer
- Title (e.g. "ACME stuck on missing SAML")
- Account (one per blocker: a blocker is about one deal at one account)
- Features (every feature that would have to ship to unblock the deal, since a deal is routinely stuck on more than one)
- Description, revenue impact, priority
- Resolution notes (free text; fill it in when status → resolved or lost)
Common actions
- Add Deal Blocker button in the toolbar
- Resolve: set status to
resolvedin the drawer and write up the resolution notes - Mark lost: set status to
lost; if you want the loss in Win/Loss, add the record there (nothing is created automatically) - Open a row to change its account or the features it is blocked on; the list columns themselves are not links
- ProductSense in the toolbar: AI reviews open blockers and proposes edits
How this drives prioritization
Deal blockers are one of the sources in the workspace knowledge block, so ProductSense and Copilot can weigh revenue at risk when they rank work; a blocker waiting on three features counts for all three. The Sales Canvas totals the revenue at risk; the Features page doesn't read blockers directly.