Making Product Managers Responsible for Sales is Stupid
Making Product Managers responsible for sales is stupid.
Let me start with a conversation I had with a sales head some years back.
After he and his team attended a conference in a different city, I asked how he enjoyed the trip. He sighed and said he didn't even have time to eat. He was standing all day to avoid missing the people he had planned to meet.
I asked him more. He described how he had studied the layout of the conference hall and the schedule to position his sales team strategically. So they could talk to speakers after they stepped off stage. Catch them when they passed the booth. Even intercept them coming back from the washroom.
I was amazed at the meticulous planning and physical toil they endured just to have good conversations. They got some solid leads that day. Some of those converted into paying customers months later.
While we as a Product team did the best we could for the product, we can't take direct credit for those sales. Major credit should go to those folks who stood for hours, planned the interception routes, and closed the conversations.
TL;DR: Product can (and should) take accountability for enabling revenue: building the right features, at the right time, for the right customers. But making PM directly responsible for sales outcomes ignores the enormous contribution of sales, marketing, and customer success. Every department plays its role. Leadership should define clear boundaries, not leave teams to fight it out.
Why PM ≠ Sales responsibility
Whether B2B or B2C, the path from "product exists" to "revenue arrives" involves multiple teams doing specialized work:
In B2B: Sales teams do prospecting, demos, negotiations, contract discussions, and relationship building. Account managers handle renewals. Solutions engineers handle technical validation. Each of these steps requires expertise that's distinct from product management.
In B2C: Marketing teams drive awareness, acquisition, and positioning. Growth teams optimize funnels. Content teams build trust. Each conversion involves work that the product team doesn't do and shouldn't do.
The product is a necessary condition for sales. But it's not a sufficient one. A great product with terrible sales execution won't sell. A mediocre product with excellent sales execution might.
Making PM responsible for sales conflates "created something sellable" with "sold it." These are different skills, different activities, and different accountabilities.
What Product CAN take accountability for
Product can't be responsible for closing deals. But Product can absolutely be accountable for enabling sales:
- Building the right features at the right time to support the sales motion
- Understanding what customers need so the roadmap addresses real demand
- Collaborating with sales to understand objections and gaps
- Providing product positioning and enablement that sales teams can use
- Supporting upsell and expansion through features that grow account value
- Ensuring the product delivers on promises made during the sales process
Accountability for enabling revenue is different from responsibility for generating it. The first is appropriate. The second is unrealistic.
The terms and conditions
For this to work, some things need to be in place:
1. Leadership should align Product and other departments on goals and strategy.
Everyone should know: what's the company's revenue target? What's the product strategy supporting it? How does each department contribute? This alignment comes from the top, not from individual teams negotiating it.
2. Leadership should define clear roles for each department.
Don't leave it up to Product and Sales to fight it out. "Product builds. Sales sells. Marketing generates demand. CS retains." Clear boundaries prevent territorial conflicts.
3. No other department should dictate what goes on the roadmap.
Sales saying "build this feature or we'll lose the deal" is not collaboration. It's hijacking. Product should listen to sales input (it's valuable data about customer needs), but the roadmap decision should be Product's to make based on the full picture.
Basically: do not push for specific features to convert one customer. That's a recipe for a Frankenstein product built for individual deals rather than a market.
4. Collaboration is everyone's responsibility.
Everyone should actively participate in product discussions and not wait until the release to comment. Sales should share customer feedback early. Marketing should share positioning concerns during planning. Engineering should flag feasibility issues before commitments are made.
When the lines get blurred
The trouble starts when leadership says things like:
- "Product should own revenue metrics"
- "PM should be accountable for ARR growth"
- "Why aren't we hitting sales targets? Product isn't shipping fast enough"
Each of these statements puts Product in an impossible position. You can't control:
- Whether sales reps show up prepared for demos
- Whether marketing generates qualified leads
- Whether pricing is competitive
- Whether the sales cycle hits unexpected delays
- Whether a competitor drops their price
You can control: what gets built, how good it is, and whether it solves real customer problems. That's your domain.
The right framing
| Department | Responsible for | Accountable to Product for |
|---|---|---|
| Product | Features, roadmap, user value | Nothing (Product owns this) |
| Sales | Pipeline, deals, revenue | Sharing customer needs and objections |
| Marketing | Demand, positioning, awareness | Sharing market insights and positioning gaps |
| CS/Support | Retention, adoption, satisfaction | Sharing usage patterns and churn signals |
| Product | (Reverse accountability) | Building features that enable sales/retention |
Product's accountability goes both ways. Product owes other teams a product that's sellable, adoptable, and retainable. Other teams owe Product the information needed to make good roadmap decisions.
The bottom line
At the end of the day, people should understand that every department or team needs to play their role as an idea takes shape, is built, marketed, sold, and finally adds value to customers.
No single department creates revenue alone. It's a chain. Product builds something valuable. Marketing creates awareness. Sales closes the deal. CS ensures value delivery. Each link matters. Each link has its own expertise.
Making PM responsible for the entire chain is not just unfair. It's counterproductive. It dilutes focus, creates resentment, and ultimately slows everything down.
Build great products. Enable other teams to do their best work. That's PM's job. Let sales be sales.
How ProductResume helps
Understanding role boundaries and demonstrating cross-functional collaboration (not ownership of everything) is what hiring managers look for in PM resumes. Score your PM resume to see whether your experience signals healthy collaboration or overreach.