For product managers · Sales-led feature requests
Sales already told Acme it’s on the roadmap. Rehearse Tuesday’s review first.
You have the RICE score. You don’t have muscle memory for when the VP of Sales says “I already promised them Q2” in front of the CEO.
You’re Sam, PM at a 90-person B2B SaaS shop. Friday Slack from Sales: Acme needs a custom Salesforce bi-directional sync — “table stakes, $280K ARR, we lose the logo if product blocks it.” You’ve read the LogRocket article and the One Knight in Product post. You know you should present tradeoffs, not reflexively say yes. What you haven’t practiced is the live roadmap review when Sales cites the deal you weren’t on, the CEO asks why revenue is “blocked,” and your instinct is to murmur “I’ll add it to the backlog.” Kommi puts you in that Zoom first.
Prioritization frameworks aren’t the hard part.
Every PM blog has the same advice: don’t say yes on the spot, ask what problem the customer is solving, present the tradeoff. You have the framework. What you don’t have is rehearsal for when Sales escalates from Slack to a leadership review and frames your “no” as blocking a named logo before quarter-end.
-
What’s at stake
One rushed “fine, we’ll fit it in Q2” becomes six months of one-off integration debt, an angry engineering lead, and a roadmap that only serves the loudest deal — not your strategy.
-
Why you procrastinate
You update the intake form instead of visualizing the review. You hope Sales will drop it. They won’t — Acme’s champion already told their CFO the sync ships in May.
-
What scripts can’t do
Aha.io and ideaplan give you the tradeoff frame on paper. They can’t simulate the VP pivoting from “it’s table stakes” to “the CEO wants this closed” while you decide whether to cave or hold the line.
-
What courses cost
Reforge runs $1,500+ and teaches stakeholder strategy over weeks. You need three reps tonight — after the Slack ping, before Tuesday’s review — not a module on prioritization theory.
Sample roleplay · 3 minutes
“I already told them it’s on the Q2 roadmap.”
You’re Sam. Tuesday roadmap review. You’ve scored the Acme sync request against strategy — it pulls you off the platform initiative for six weeks. The VP of Sales opens.
VP of Sales
“Acme is $280K ARR and a named logo in financial services. They need bi-directional Salesforce sync — it’s table stakes. I already told their champion it’s on the Q2 roadmap. Why is product blocking revenue?”
You (Sam)
“I want to make sure we close Acme — and I also need to protect the platform work we committed to the board. Can we walk through what problem the sync solves and whether our existing webhook covers it?”
VP of Sales
“They don’t care about webhooks. Their CFO asked specifically about Salesforce. The CEO wants this closed before quarter-end. Can you just commit to Q2?”
Your move
- → Present the tradeoff without sounding like you’re blocking revenue
- → Address the “I already promised them” trap without throwing Sales under the bus
- → Offer a path forward — workaround, phased scope, or premium custom work — without reflexive yes
Each choice changes how Sales responds — more CEO escalation, a request to join the Acme call, or a genuine tradeoff conversation. You practice holding strategy under live pressure instead of retreating into backlog jargon.
Then the coach reads you back to yourself.
Not a prioritization quiz. Not seventeen stakeholder tips. One observation about what you did, one adjustment for next time, one sentence you can carry into Tuesday’s review.
Sample coach debrief
“You opened with alignment — you want Acme closed too. When Sales said ‘I already promised them Q2,’ you asked about webhooks instead of acknowledging the promise trap first. That made it sound like you were dodging the commitment Sales made.
Try next time: Name it directly: ‘I hear you committed Q2 — let’s figure out what we can actually deliver and what Acme needs to hear this week.’ Then present the tradeoff: six weeks off platform work vs. a phased webhook + manual export that unblocks their CFO review.
Carry into Tuesday: ‘We can prioritize a scoped sync for Acme in Q2, but it delays the reporting overhaul by three weeks. Which outcome matters more for the board commit this quarter?’”
Questions before your roadmap review
- Is this different from pushback on unrealistic deadlines?
- Yes. Engineer deadline pushback is about scope and capacity with your PM. This scenario is built for product managers defending roadmap strategy when Sales invokes ARR, named logos, and promises already made to prospects. Different room, different pressure tactics.
- I’m a senior PM. Is this too basic?
- The scenario scales. Run it with a VP who cites CEO escalation, a sales rep who Slack-pings before you’ve scored the request, or a CS leader who bundles three customer asks into one urgent thread. The pressure tactics change; the rehearsal need doesn’t.
- Can I practice saying yes with guardrails?
- Yes. Not every sales request should be a hard no. Run the scenario where you commit to a phased scope, charge for custom work, or propose a workaround — and practice articulating the tradeoff so engineering and leadership back you up.
- What about feature requests from Customer Success?
- This scenario focuses on sales-led deal pressure — ARR, named logos, promises to prospects. CS-driven requests use similar stakeholder frames but different stakes. Run both; the pushback muscle memory transfers.
$11.99 a month.
A coach with a calendar runs two hundred dollars an hour. Kommi runs roughly forty cents a day — and is awake when you can't sleep, which is when most of these conversations are actually being rehearsed anyway.
We don't have a free tier, a team plan, or a premium upsell. One price, no pricing page riddle. If we add tiers later, we'll do it because users asked — not because a growth deck did.
About forty cents a day.
- Two free sessions before billing starts
- Then $11.99 a month — about forty cents a day
- Unlimited sessions — any conversation you can describe
- A coaching read after every session, and your progress over time
- Cancel in two taps; 7-day refund if you change your mind
One conversation you’d have talked yourself out of is worth years of this. Or just sleep better on Wednesday. Either way.
Run your first rehearsal — free →US only at launch. We'll get to the rest of the world.
The conversation is on Thursday. Begin tonight.
Three minutes. Two free. 7-day money back after that.