When good top-down structure is on the other side

Satellite articles

• 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’

People say, ‘I’m talking with AWS’, the same way they say, ‘I’m talking with the bank’ or ‘I’m talking with the NHS’.

It sounds grown-up. It also hides the only thing that matters: you are talking with a human being who has a job title, a quota, and a limited amount of power.

Personification is when we turn an institution into a character. A single mind. A single intention. A single promise. We then negotiate with that character as if it can choose to be generous, flexible, or loyal.

That is not how large companies work. The best ones are not based around people. They are based around systems.

AWS is one of the cleanest examples we have of that design. It is not ‘a company’ in the way our brains like to imagine. It is an industrial machine: products, policies, queues, guardrails, pricing structures, and contracts that are meant to scale. It is built to treat customers consistently, not sentimentally.

From the inside, that looks like efficiency. From the outside, it can look like a brick wall with a smile.

When you personify AWS, you do two expensive things at once.

First, you overestimate how much influence you have.

You assume there is ‘room’ because you are talking to a person. But the person is often the interface. The decision is elsewhere. Sometimes the decision is in a policy. Sometimes it is in a model. Sometimes it is in a set of commercial rules that only move when you are big enough to bend the spreadsheet.

You can escalate. You can ask. You can negotiate. You cannot will the machine to behave like a small supplier who can decide on the spot.

Second, you misunderstand incentives.

Account managers are in sales. Sales exists to drive revenue. That does not make account managers malicious. It makes their objectives different from yours.

You want lower run-rate, lower unit cost, more predictability, fewer surprises. They want expansion, retention, and spend growth. Occasionally those align. Often they do not.

If your internal story is ‘AWS will help us optimise’, you should translate it into something more accurate: ‘A sales organisation will support optimisation when it helps retention or creates room for a new product sale.’

That difference is not cynicism. It is literacy.

Then there is the third trap, the one people do not like admitting out loud.

‘Going direct’ is sometimes an ego call.

It is a status signal. It sounds like you have access. It sounds like you are important. It sounds like you are not ‘stuck with a middleman’.

But top-down FinOps is not a popularity contest with vendor logos. It is an operating model: decision rights, budgets, accountability, and a feedback loop between technology choices and financial outcomes.

If you want a human who cares about you specifically, you pay for attention. Dedicated, high-touch support is not a vibe. It is a line item. In many organisations, a named person who will coordinate, chase, and treat your issues as their job can easily cost £15,000 a month or more.

That number matters because it forces a question.

Are you buying support, or buying the feeling of support?

If you are not paying, you are not buying a dedicated person. You are buying a place in a system.

This is why personification is dangerous in executive rooms. It turns a structural question into a relational one.

Instead of asking ‘Which operating model gives us leverage and predictable outcomes?’, you ask ‘Do we have a good relationship with AWS?’

A relationship is vague. Leverage is measurable.

Here is the more adult version of the conversation.

• Who are we actually speaking to, and what can they approve?
• What does success look like for them, inside their company?
• What would we need to pay for, if we want higher-touch support?
• Where does procurement sit in this, and what is our walk-away position?
• Which parts of our spend are genuinely strategic, and which are stable utility?

Given that context, what changes?

You stop trying to persuade a company to care. You start designing a system of your own: commercial strategy, support strategy, architecture strategy, and governance, with decision rights that live inside your organisation.

That is top-down FinOps. Not because it is aggressive, but because it is real.