AWS sells to the tribe, not the board

Other articles exploring a different angle of Top-down FinOps and personification

• When good top-down structure is on the other side
• When the human is the UI
• AWS sells to the tribe, not the board
• Borrowed leverage: partners, resellers, and the myth of ‘direct’

The context

• Audience: executives and FinOps leaders who wonder why procurement feels ‘late’ to cloud.
• Situation: technical teams make buying decisions by optimisation, not negotiation.
• Decision on the table: how to rebalance power without slowing delivery.

Cloud marketing is, on purpose, deeply technical.

It is written for people who like systems, clean abstractions, and the feeling of being competent. It is written for people who value ‘best practice’ and do not want to ask permission from procurement to do their job.

That is not an accident. Technical buyers are predictable.

They like rules. They like self-service. They like belonging to a tribe that speaks a shared language. They like certificates. They like being able to point at a badge and say, ‘I know what I’m doing.’

This tribe dynamic matters because it shapes how cloud buying happens.

If you are steeped in technical culture, negotiation can feel grubby. It can feel like a distraction. You want to build. You want to ship. You want to optimise what you have, not argue about what it costs.

So when someone says, ‘We can’t negotiate with AWS’, the sentence often means, ‘We do not think negotiation is part of our craft.’

That works out very well for AWS.

A procurement team might look at a core service and ask why it has not improved in price for nine years. In many industries, that would be unacceptable. Efficiency gains should show up as better commercial terms.

A technical team might respond, ‘It’s more complicated than that.’ And they might be right, technically. But they have also moved the debate away from the one place procurement is trained to hold the line: price and terms.

This is how procurement gets bypassed, not through malice, but through culture.

Engineers often prefer minimal human interaction. They like being in the zone. People are distractions. A clean interface is bliss.

There is a reason Amazon retail is so successful. Click, ship, done. No awkward small talk. No haggling. No explaining yourself.

Cloud self-service fits the same preference. It feels empowering.

‘Working direct’ becomes a status symbol inside the tribe, even when the ‘directness’ is mostly a fantasy. You are not working with a person. You are working with a product catalogue and a set of strict rules. The human, if present, is often there to guide you to a compliant choice, not to redesign the choices.

Meanwhile, AWS, like any strong business, has incentives.

Increasing margin is rational. Shareholders like it. Even customers benefit indirectly when that margin funds better products.

But customers do not pay bills with vibes. They pay them with cash.

Most companies are not startups. Most companies run a stable core business. That core could often run elsewhere, or at least could run with a very different cost posture. For these firms, procurement saying ‘pricing is not acceptable, we walk’ is not ignorance. It is discipline.

Top-down FinOps is the art of making both worlds true at once:

• the technical world gets speed, autonomy, and good engineering
• the business world gets negotiation posture, predictable cost, and leverage

The fix is not to shame engineers. It is to change the operating model.

Bring procurement into cloud early, not as a blocker, but as a design constraint.
Make commercial posture part of platform strategy.
Reward engineers for cost outcomes, not only technical elegance.
Treat ‘we can’t negotiate’ as a smell, not a principle.

Vendors sell to the tribe because the tribe is easier to move. Top-down FinOps exists to make sure the tribe does not accidentally sign away the company’s leverage.