How to Prioritise Features Using Salesforce CRM Data
Most PMs prioritise features based on gut feel or whoever shouts loudest in Slack. Meanwhile, your Salesforce instance holds the actual data: which accounts are asking for what, how much revenue is at stake, and which deals are blocked by missing features.
This guide shows how to connect Salesforce to your product workflow so prioritisation decisions are grounded in real customer and revenue data — not opinions.
Step-by-step guide
Connect Salesforce to Vantage
In workspace settings, connect your Salesforce account via OAuth. Vantage indexes accounts, open opportunities, and support cases. No data leaves your Salesforce instance — Vantage reads it for context.
Identify revenue-weighted requests
When customers request features, Vantage traces the request back to the Salesforce account: ARR, deal stage, account tier, industry. A feature request from a $500K enterprise account carries different weight than one from a free trial.
Cluster requests into themes
Multiple customers asking for similar things get clustered automatically. "5 enterprise accounts worth $2.1M combined asked for SSO this quarter" is more actionable than "some people want SSO."
Score themes by configurable signals
Each theme gets a priority score: request frequency × customer segment × revenue impact × strategic alignment. You configure the weights — some teams weight revenue heavily, others weight frequency.
Turn a theme into a project
When you decide to act on a theme, the customer quotes, account data, and deal context become the project context. Requirements are grounded in what customers actually said, not what you remember them saying.
Close the loop when it ships
When tickets ship via Linear/Jira sync, Vantage traces back: this ticket → this requirement → this theme → these 8 Salesforce accounts. Surface who to notify and update deal notes.
Common mistakes
Prioritising by volume instead of value
100 free users asking for dark mode is not worth more than 3 enterprise accounts asking for SSO. Without revenue weighting, you build for the loudest crowd, not the most valuable one.
Disconnecting CRM from product
When sales and product use different tools with no connection, feature requests get lost in Slack threads and meeting notes. The CRM has the data — connect it.
Not closing the loop
Building a feature customers asked for and not telling them is a missed opportunity. Closing the loop drives expansion revenue and reduces churn.
Tips
Start with open opportunities — features blocking active deals have the clearest ROI
Weight by account tier, not just deal size — a strategic account request may be worth more than its ARR
Review themes monthly, not quarterly — customer needs shift faster than planning cycles
Use Salesforce case data alongside opportunity data for a complete demand picture
How Vantage helps
Vantage connects to Salesforce and indexes your accounts, opportunities, and cases. When you generate a PRD, the AI grounds it in real customer data — not generic advice. Feature requests trace back to specific accounts with revenue attached. When tickets ship, Vantage tells you which customers to notify. The demand side and build side are one workflow.