Why Product Managers Should Build Relationships with Customer Success
If product managers had to identify the single organizational function most consistently underutilized as a source of product intelligence, customer success would win by a significant margin. Customer success teams spend their working days in direct contact with users — understanding how they’re using the product, where they’re struggling, what they’re trying to accomplish, and what would make the difference between renewal and churn.
Yet in most product organizations, the relationship between product management and customer success is ad hoc at best: occasional escalations when a customer is upset about a missing feature, periodic NPS share-outs, and the occasional PM attending a customer call.
What Customer Success Knows That Product Doesn’t
The gap between usage and intention: Customer success teams discover the difference between how users say they use the product (in surveys, in interviews) and how they actually use it (in support conversations, in customer calls). This gap is often revealing: features that users say are important to them but that they don’t actually use, workflows that users say work well but that generate significant support volume.
Leading indicators of churn: Customer success conversations reveal churn signals weeks before they show up in retention metrics. The customer who is asking about specific missing features, whose usage has shifted to lower-frequency patterns, or who mentions they’ve been evaluating alternatives is on a path that product investment could change — but only if product management receives that signal.
The real adoption blockers: Support tickets and customer success call themes reveal the specific friction points that prevent users from adopting features and workflows that the product team thought were straightforward. These adoption blockers often point to onboarding problems, documentation gaps, or UX issues that are more addressable than the underlying feature gaps that get more PM attention.
Enterprise requirements patterns: For products with enterprise customers, customer success teams observe the specific compliance, integration, and administrative capability requirements that enterprise buyers require before fully deploying the product. These requirements often don’t surface in product research but are critical for renewal and expansion.
Building the Partnership
The most effective PM-customer success partnerships are systematic rather than ad hoc:
Weekly intelligence-sharing rituals: A standing weekly meeting where customer success shares the top themes from the previous week’s customer conversations — the most common questions, the most significant frustrations, the most encouraging adoption patterns.
Joined customer calls: PMs joining selected customer success calls (especially escalations and expansion conversations) to hear directly from users rather than receiving summaries.
Shared tagging taxonomy: A common framework for categorizing customer feedback that allows both teams to identify patterns across their respective channels.
Key Takeaways
Customer success teams hold real-time user intelligence that product managers need but rarely tap systematically. Building systematic intelligence-sharing partnerships — through regular meetings, joint calls, and shared categorization — converts this intelligence into the product decisions that improve retention, reduce churn, and drive expansion. The coffee meeting isn’t the investment; the systematic intelligence-sharing infrastructure it initiates is.
Making Intelligence Sharing Systematic
The intelligence that customer success teams hold is most valuable when it reaches product management systematically rather than episodically. The PM who attends customer calls occasionally and hears occasional themes gains much less than the PM who receives weekly structured intelligence about the patterns emerging across all customer interactions. Building the systematic infrastructure — the regular rituals, the shared tagging, the defined escalation paths for urgent signals — converts customer success knowledge from organizational capital that’s mostly wasted to product intelligence that’s consistently applied. The most productive way to structure PM-customer success intelligence sharing is to make it the default rather than the exception: the PM is informed about significant customer conversations by default, not by escalation only. This inversion — from reactive to proactive information flow — is what converts customer success intelligence from a resource the PM occasionally accesses to a continuous input into product decision-making.