Revenue pressure just hit your roadmap. Two product leaders share how they responded — one built a filter, one sprinted toward the fire.
You spent weeks getting alignment. You ran the strategy sessions. You got everyone in the room, made the hard tradeoffs, and walked out feeling good. Then, ten minutes later, your phone rings. It's the VP of Sales. There's a deal on the line, and the customer wants the exact feature your team just decided not to build.
This is one of the oldest tensions in product leadership. And it never fully goes away.
In Episode 6 of Product Leaders Lab, two product leaders share how they navigated this moment from completely different angles.
Francesca Negri Smedberg, CPO at Enento Group, was in the middle of a full product transformation when commercial pressure arrived. Aakash Gupta, formerly VP of Product at Apollo.io (now Founder of Product Growth), faced a version of this from a different direction: a new CRO walking in the door and questioning decisions his team had spent months building.
Neither of them chose the obvious response. And what they did instead is worth studying.
Most product leaders know the two bad options. You can hold the line and protect the roadmap, which risks losing the deal and your credibility with sales. Or you can give sales what they want, which sets a precedent that your roadmap is a suggestion, not a commitment.
What's less discussed is how much the pressure messes with your head before you even make a decision. The first instinct, Francesca said, is almost always an emotional one:
"You think, the people do not believe in the strategy."
That reaction makes sense. You did the work. You got the alignment. And now it feels like it's unraveling.
But that first instinct, if you act on it, tends to produce the worst outcomes. The leaders who navigate this well are the ones who catch that reaction and sit with it long enough to find a better frame.
Francesca was leading a product transformation at Enento Group, a company working to shift from reactive to strategic. Her team was still building the muscle of saying no.
When a sales request came in for a feature that had explicitly been deprioritized in the strategy, the stakes were high — not just for the deal, but for the transformation itself.
Her first move was a reframe. Instead of treating the sales request as a failure of alignment, she came back to something more grounded:
"They are actually doing their work. And from a sales perspective, your perspective is I have to close my deal. I have to hit the quarter."
That shift, from "they don't believe in the strategy" to "they're just doing their jobs," is where leadership actually lives.
From there, she applied a filter. Any request had to pass a set of conditions before she'd even consider saying yes.
The first condition was strategic fit: could you genuinely connect this to something already in the plan? Not a vague gesture at strategy, but a real connection to an ICP, a goal, a committed priority.
"I would always try to connect it to some part of the strategy, because then this can help you to build confidence."
The second condition was non-negotiable: something had to stop.
"To do this, we will still need to pause something. You cannot do both things at the same time."
The trade had to be visible to sales, to the team, to everyone. You can't just add.
The third condition was the most interesting: understand the actual problem before building anything. In the specific situation she described, the team went back to the customer before writing a line of spec. What they built in the end wasn't what the customer requested. It was something better.
"We tried to find a solution that was more... serving a broader amount of customers."
Most of the time, the filter returned a no. And Francesca had a deliberate way of delivering it. Not a bare refusal, but: here's why, here's what we're doing instead, and here's how we're capturing your feedback.
"It's about building the collaboration, a relationship rather than the conflict."
The filter wasn't just a prioritization tool. It was a relationship-maintenance tool.
The trade-off of this approach: it only works if you apply it consistently. One exception made without rigor, and you've taught sales that the filter is negotiable. It also requires a strategy clear enough to actually serve as a test. If your strategy is vague, it can't do the work.
Aakash's situation had a different dynamic. At Apollo.io, a new CRO joined who started surfacing concerns about the pricing model. Too many pricing plans were creating confusion for customers, for the sales team, and for customer support.
This wasn't sales asking for a feature. It was an executive with real organizational weight raising a problem that Aakash's team had been living with but underweighting.
His first move wasn't to defend. It was to learn.
"The very first thing I had to do was upgrade my knowledge."
He went directly to the IC PM responsible for pricing, requested all available documentation, and got into the active A/B tests himself. He didn't wait to see if the CRO was going to escalate. He sprinted toward the problem.
And what he found when he got there was that she was right.
"I start to realize that she's really narrowed in on a problem that exists for a lot of people within the company and our customer base."
He saw exactly where this was heading if he didn't move fast. So instead of bracing for conflict, he chose co-creation.
"I'm going to co-create with her how we're going to approach this plan. So actively bringing her into meetings about: these are the options, these are the trade-offs."
Not presenting a solution. Presenting options and inviting her into the decision.
His senior IC PM felt the heat. Felt questioned. Aakash handled that directly by connecting the work back to that person's own goals.
"If you explain to someone on your team why you're doing something, it helps disarm them."
He framed it in terms of OKRs, not politics.
The outcome wasn't just resolution. The CRO became an advocate, unlocking resources from marketing and ops that product couldn't have accessed alone.
"It turned into a co-effort where we end up getting more resources from more teams inside the company."
The trade-off of this approach: it requires genuinely believing the other person might be right. If you run toward co-creation but are secretly just trying to manage them down, they'll feel it. It also requires a particular kind of executive relationship. Aakash's approach worked in part because the CRO was open to product-led thinking. A different executive might not have responded the same way.
Francesca built a filter. Aakash ran toward the problem. On the surface, these look like opposite moves.
But the conditions were different. Francesca was operating in a transformation, where the team was still learning what strategic product work looked like. The filter wasn't just a tool for handling one request; it was a training mechanism for the whole org.
Aakash was operating at scale with an executive who had real organizational weight and a real point. His job wasn't to protect the roadmap. It was to move fast enough that conflict never had a chance to form.
What's the same in both cases is what they didn't do. Neither of them got defensive. Neither of them treated commercial pressure as an attack. And both of them, in their own way, stayed connected to the relationship, not just the decision.
The trap most product leaders fall into is treating this as a binary: either I hold the line or I give in. Both Francesca and Aakash found a third option. Not a compromise, not splitting the difference, but a deliberate move that kept the relationship intact while producing a better outcome than either side originally had in mind.
The quality of the "no" matters as much as the no itself.
Francesca said it plainly:
"We say no, but we're trying to say no in terms of: this is good feedback, but we are not prioritizing right now because we're doing this. And then connecting to the strategy."
A no with reasoning, with an alternative, with visible follow-through, is a relationship-builder. A bare no is a relationship-ender. Most product leaders skip the follow-through, and that's where the damage happens.
The revenue-versus-vision tension doesn't disappear as companies mature. If anything, it gets more complex: more stakeholders, bigger deals, more executive opinions about what product should be doing.
What changes for the leaders who navigate it well is their relationship to the pressure itself.
Francesca described it this way, reflecting on the moment she reframed that mid-transformation sales request:
"People have gone back to their daily work."
No betrayal. No failure of alignment. Just people doing their jobs in a system that creates competing incentives. The leaders who stay effective are the ones who can hold that frame under pressure, and find a path through it that doesn't leave bodies on the floor.
Want to hear the full conversation? Listen to Episode 6 of the Product Leaders Lab wherever you get your podcasts:
