Sales Is the Favorite Child. Stop Negotiating Like You're Not.

Watch what happens in any product org when Sales wants something.

It gets built. Maybe not well, maybe not soon, but it gets built.

Now watch what happens when Product asks Sales to change how they sell. Silence, and a meeting that somehow never gets scheduled.

That's not a coincidence. That's the org chart telling you a truth nobody says out loud: Sales is the favorite child.

This isn't a complaint, it's a map — and most product leaders refuse to read it.

Why the favorite child gets fed

Sales sits closest to revenue. The CEO can see the number Sales moves this quarter, in dollars, while your number is slower and fuzzier and easier to wave off. So when Sales and Product disagree, the parent already has a favorite.

You know this in your gut. Then you walk into the room and negotiate like it isn't true.

You bring a roadmap; they bring a deal that closes Friday. You bring product logic; they bring a customer name and a revenue figure. It's Monopoly money at a poker table. You can hold the best hand in the room and still get cleaned out, because you're not even playing with the same chips.

It was never about politics. You brought the wrong currency.

The scar

My team once became a sales order desk, and I'm the one who signed off on it.

Scale-up, growing fast, hungry for logos. Sales would surface a feature a prospect "needed to close," and we'd build it. I told myself we were being customer-driven. Collaborative. (Mostly I told myself whatever let me dodge the fight.)

We were running an order desk. The product fractured into a Frankenstein suite nobody could explain. A junk drawer of features, each built for one account, none of them adding up to a platform.

Every yes made the next no harder. And the team learned the lesson I was quietly teaching: your job is to build what Sales sells. They stopped bringing judgment, because judgment wasn't on the menu.

What finally changed wasn't a stronger spine. It was better information. I started sitting in on sales calls — not to sell, but to hear what Sales actually got paid for. Logo count, deal size, time-to-close. Once I understood the number under the request, I could reshape it before it hardened into a promise my team inherited.

Empowerment isn't permission to say no

Here's the trap most leaders fall into. They think empowerment means earning the right to refuse. But by the time you're refusing, the promise is already made and you're just the obstacle standing in front of it.

Real empowerment is reshaping what gets committed before it ever reaches your team. Three moves make it possible.

Read the incentive, not the request. Sales isn't asking for a feature, they're asking to hit a number. Find the number and you'll usually find three ways to hit it that don't cost you a quarter.

Get in the room before the promise. The expensive commitments don't happen in roadmap reviews. They happen on the sales call, the second a rep says "yeah, we can do that." Be there, or inherit it.

Trade in their currency. Don't defend the roadmap with product logic. Frame it in revenue and risk: "that feature wins one logo and delays the integration three paying accounts are waiting on." Now you're a peer at the table, not a gatekeeper at the door.

Do this and your team stops being an order desk. They get a boundary to work inside and the room to use their own judgment, which is all an empowered team ever really was.

I watched this turn around at an enterprise where Product and Sales were at each other's throats. Neither understood what drove the other. So I stopped refereeing and put both teams in a room to map what each got rewarded for. Sales finally saw why Product kept resisting. Product saw the quota math under every "urgent" request. Nobody touched the org chart, but once the incentives were visible, the two sides started shaping work around each other instead of escalating through me.

The signal you can measure

Want a number? Count the roadmap items this quarter that started life as a sales promise you only heard about after it was made.

More than zero means you're not in the room early enough. If it's most of your roadmap, you're not running product — you're running an order desk with a nicer title.

The favorite child isn't going anywhere, and that's fine. The CEO needs Sales to hit the number, and honestly, so do you. The job was never to dethrone them. It's to stop pretending the table is level and start bringing chips that actually play.

So before the next deal-driven feature lands on your backlog, pick up the phone. Ask Sales one thing: what number are you chasing, and is this the only way to hit it?

When did you last get to ask that before the promise was made?