The CRO, not product marketing, is closest to the customer and knows what they will buy. The product roadmap should be a collaborative effort driven by the CRO, who can directly tie feature delivery to ICP expansion and revenue forecasts. This creates accountability and predictable growth.

Unlike simple B2C tests, B2B experiments require tight coordination with sales, customer success, and even legal. This alignment is crucial to manage customer expectations, contractual obligations, and prevent confusion for client-facing teams.

Instead of saying no to a sales request, show the financial trade-off. Frame current roadmap initiatives in monetary terms (e.g., "a $10M churn reduction project"). This forces a business decision: is one deal worth sacrificing the larger financial goal?

Focusing on individual enterprise client needs creates conflicting workflows that hinder scalability. A successful transition involves moving to a user research-driven approach, using data to justify a standardized product direction that serves the broader market, not just a few powerful clients.

A product roadmap's value is in the planning process and aligning the team on a vision, not in rigidly adhering to a delivery schedule. The co-founder of Artist argues that becoming a feature factory focused on checking boxes off a roadmap is a dangerous trap that distracts from solving real customer problems.

The tendency for sales to dictate product development is less about a company being B2B and more about its revenue concentration. A B2C app with a few "whale" customers spending 150x the average would face the exact same pressures. The dynamic is driven by the disproportionate value of individual large deals.

Don't view high-pressure sales requests as roadmap disruptions. Instead, see them as opportunities to pull forward planned features, co-design them with a committed customer, and provide the team with a motivating, tangible deadline. This turns external pressure into an accelerator for validated product development.

Post-IPO, sales-driven feature requests can derail the roadmap. Pendo's CPO advises creating a formal process, often with a dedicated program manager, to analyze commits for broad applicability and explicitly calculate the opportunity cost against the strategic roadmap before approving them.

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.