“Nobody wants to run hardware again”

Head of Platform Engineering · Cloud infrastructure

A platform team that says it won't run hardware again is protecting how it works, not ruling out where workloads live. Don't sell boxes. Talk about operations: ask which parts of running infrastructure they'd happily hand over, and which they'd want to keep control of.

What the buyer says

My team's skills are all in public cloud now. Nobody wants to go back to running hardware.

How to handle it

Listen

Listen for the experience behind it: overnight hardware failures, slow procurement, skills the team has deliberately left behind. That's the pain you need to avoid recreating.

Acknowledge

Agree that nobody should have to rack servers to deliver a platform, and that their team's cloud skills are an asset.

Explore

Ask which parts of running infrastructure they'd happily hand over, which they want to control, and what their developers need from the platform. Ask whether any workloads they're responsible for already sit outside public cloud, and who looks after those.

Respond

Show how your offer works the way their team already works: the same tools, automation and self-service, with the hardware run for them. Keep the conversation on operations and outcomes, not on the equipment.

Say this
“That makes sense. Nobody wants to be racking servers to run a platform.”

Say this
“Which parts of running infrastructure would your team happily hand over?”

Say this
“If it worked the way your team already works, would where it runs matter as much?”

Variations

Head of DevOps: “We manage everything as code now. We don't touch hardware.”
CTO: “My engineers want to build products, not look after data centres.”

Questions people ask

How do you sell infrastructure to a platform team that only wants public cloud?

Talk about operations, not hardware. Ask what they'd hand over and what they want to control, then show how your offer fits their existing tools and ways of working, with the hardware run for them.

Why do platform engineering teams resist on-premises infrastructure?

Usually because of past experience: slow procurement, out-of-hours failures and manual work. The objection is about how infrastructure is run, which is something you can address.