How to Bridge the Gap Between Product and Sales Teams: Lenny & Jason

Lenny and SaaS investor Jason M. Lemkin discuss how to manage tension between product and sales teams. They recommend weekly VP-level meetings, structured rituals like force-ranking features on a whiteboard, and routing requests through hierarchy. Lemkin says some stress between teams is healthy, but process must contain it.
Chapters
we just need this one feature. Can we just get this on the roadmap? What's the best way to help that salesperson understand why it's not happening? Help them feel like, okay, I get it. Is it exactly what you said? Like, okay, we could change everything. Here's the story points you have this quarter.
Well, are you assuming, are you assuming that PM is the head of product or, or empowered enough to make the decisions?
I'd say yeah, that PM could put something on the roadmap if they think it's important.
The, the reason I'm a little confused, just because I want to get it right, is I'm hearing what I'm hearing, which maybe isn't what what you said. What I'm hearing is a, a jun— a junior IC rep is talking to kind of a more mid-level product person about the roadmap. That's a bro— as, as, and that's, you wanna have that. That's like one of the reasons we actually go to the office. 'Cause those discussions don't happen on Zoom, Lenny. They don't happen. And you want those discussions to happen, but you don't actually want them empowered. You want them to say, listen, I will talk to my boss. That's the right answer. It's too confusing. This stress between product and sales. Is a good thing. It's a, it's a sign of a well-run B2B company when there is stress between product and sales. It's a good sign. It is a good— if there's no stress, you're not, you're not in enough deals. You're not in enough deals if there's no stress, but the stress has to have enough process even in a startup that it doesn't break. Because as your question alludes to the fact it can break organizations again and again, right? People get, people resent it on either side, right? And so you, this is one thing where the answer has to be, look, we, we can chat about it over lunch. We can chat about this and. And, and, and actually you've got a good idea. You, you're an individual contributor. I'm going to tell my boss on Monday that I think we should do that. I'm going to, I'm going to use a little social capital to say we should do this, but you've got to push the decisions up. That's as far as you can go to make a recommendation. Otherwise, instead of that one, one stressful conversation at the VP level, you've got 100. You've got 10 times, 10 times 100. And again, they're fun lunch conversations, but they wreck you.
So the advice there is basically talk to your manager. I'll talk to my manager. They need to hash this out. It's not my call.
I think you gotta push it up and I think you gotta force the VP of sales and the VP of product to have this weekly meeting about the budget. And that will force them to have enough, just enough organization on their team so that it can all be surfaced up. 'Cause that means they each have to have a meeting with their team for 30 minutes each week and say, I'm gonna put it up on the whiteboard, guys, to my sales team. I'm gonna put up on the white, like the sales team's gonna say, look, and I've been in many of these meetings where you force the sales team to force rank what they want and you, you You end up, I can tell you, Lenny, 100% of the time in a sales meeting, when you force do a whiteboard force rank, you end up walking out with very different, uh, outputs than when you start the meeting in sales 100% of the time. On the product side, you need to do the converse. You just say, we owe sales 10% of our points. So we're gonna put in a weekly, uh, in our team meeting, we're gonna put in 15 minutes of our team meeting and we're gonna make sure we have the priorities right from the sales team. Let's go over what I got from Linda. This is what she says. Is she wrong? Should we do something? How can we help the sales team be even more successful? And what inputs is the team hearing? And they can raise their hand and they say, look, I just had this hallway conversation with Bobby, but honestly, Lenny, I can build the HubSpot integration in a day. What? I thought it, I thought it was really hard. No, I did it at my last company. And listen, actually, we can actually outsource it to Bob and Linda at this agency I know for $20 grand. They'll build it next week. I'm like, that's a magical moment, right? That's a magical moment. But you gotta each have these parallel meetings or it's just, it's just, it just that the good thing, that tension can become debilitating, right? When you've, we've all seen those fights, those almost fights that break out and they come from a place of passion, right? But you gotta have structure.
Great advice. Another trend I've been noticing is that product teams are taking on P&L responsibilities and revenue goals. What's your sense of, is that good? Is that bad? How do you think about that for product teams?
You want everyone to be aligned on the big picture with the revenue goal for the end of the year. Is the question, you mean having financial bonuses? Bonuses and stuff tied to hitting the plan?
More that their KPIs and their OKRs are essentially like this much revenue. You need to drive this much revenue from your experiments, from your product launches.
As you can see, I have a lot of opinions on, on things here that are data-driven. They're live experience. This one, I don't, I need another year in the oven and I'll tell you why. I'll tell you why. What happened the last 18 months is in customer success, which is a, which is, you know, In the old days, it was related to product. Now it's, it's less so, which is, I think is unfortunate. In customer success in the last 18 months, this happened all across the industry. 24 months ago, customer success's goal was happy customers measured in retention. Sometimes NRR, like net retention with upsells, sometimes with GRR, like just logos, how many logos stay. That was your only job. Happy customers, happy customers. Then things got harder in many areas of B2B and every customer success team last year, their goal was revenue. You need to bring in more revenue from existing base. And it destroyed customer relationships. It had, there is a leading public company. I will not name them. I'm a positive guy. I will tell you a company we all have used for years and loved. Okay. And they did this to their customer success team. And they came to us last year. We paid $299 a month for this product for our team. They asked us for $50,000 upfront or said they would turn it off that day, that week, maybe it was that week. $50,000. That's what happens when you weaponize. And so customer success, and I know this is going to trigger some people, but it is true when I talk to leaders, customer success got weaponized and I don't like it. Okay. I don't like it as a product, as if all founders are product people. I think I don't like it as a product because I think it's bad for customers. That experience I got was horrific, wasn't it? That $50,000 being told and it got walked back and
More from Jason

Why Your Next Hire Should Report to an AI, Tragedy Apps, and Too Many AI SDRs? | The Agents #004

Our Agents Drove Our Salesforce Bill Up 80%, Marketo Hates Agents, and We Stealth-Churned Off Notion

Managing 20+ AI Agents: Lazy Agents, Our $500K AI Bill, Stealth Churn & the Death of 60% Solutions







