A product manager's role extends beyond development. The customer stories and problem statements gathered during discovery are powerful sales assets. Packaging these insights and sharing them with the sales team helps them communicate the product's value more effectively.

Related Insights

The discovery phase of a sales call isn't a generic interrogation or a prelude to a demo. Its only goal is to understand the customer's PULL: their specific Project, its Urgency, the other Options they've considered, and the Limitations of those options. Only then can you effectively position your product.

The skill of storytelling isn't just for marketing or user narratives. Its most powerful application in product management is internal: convincing diverse stakeholders and team members to rally behind solving a specific problem. It's a tool for alignment and motivation before a single feature is built.

Buyers are not looking for a new vendor; they are looking to solve a problem. Instead of listing features, top salespeople frame conversations around the specific problems they solve. This approach builds immediate value and positions the seller as a strategic partner in the buyer's success, rather than just another pitch.

Vercel COO Jean Grosser's litmus test for a great salesperson is that engineers shouldn't be able to tell they aren't a PM for at least 10 minutes. This requires deep product knowledge, enabling sales to act as an R&D function by translating customer feedback into valuable product signals.

True product intuition isn't just from standard discovery calls. It's forged by directly engaging with customers' most urgent problems on escalation calls. This unfiltered feedback provides conviction and data-backed confidence for decision-making.

In the pre-product-market fit stage (the first ~20 deals), the sales leader's primary role is not just closing revenue, but acting as a product manager. They must be in every meeting to gather objections, find pockets of value, and translate raw market feedback into actionable insights for the engineering team.

Founders often rush discovery to save time for a long demo. This is backward. When you precisely understand a customer's 'pull' (their top blocked priority), your pitch becomes hyper-relevant and can be delivered in 90 seconds, making the entire sales process more efficient.

The 'CEO of the product' metaphor is misleading because product managers lack direct authority. A better analogy is 'the glue.' The PM's role is to connect different functions—engineering, sales, marketing—with strategy, data, and user problems to ensure the team works cohesively towards a shared goal.

The debate between being product-led vs. sales-led is a false dichotomy that creates friction. Instead, frame all functions as fundamentally 'customer-driven.' This reframing encourages product teams to view sales requests not as distractions, but as valuable, direct insights into customer needs.

Don't rely on recalling the right story in the moment. Proactively build and maintain a "story library" with dozens of categorized examples. While you may only use a few core stories regularly, having a deep, accessible catalog ensures you have a relevant narrative for any customer situation.