Why Procurement Matters in Building Lifecycle

There is a fascinating character in the life of every commercial building. You’ll rarely see them in plant rooms. They don’t attend midnight breakdown calls. They are almost never blamed when occupants complain or energy bills spike or when systems don’t work. And yet, their influence quietly outlives almost everyone else involved.

The procurement manager.

Now let me be clear before anyone sharpens their knives: this is not a hit piece. Many procurement managers are smart, diligent, and genuinely trying to do the right thing (honestly). But the system they operate in has a curious curse – one that rewards the appearance of certainty over long-term intelligence. And buildings pay the price for it.

The curse usually begins with good intentions.

A project needs a BMS, an IBMS, a platform, a system – pick your acronym. The RFP is issued. Vendors respond with thick documents, colourful dashboards, long feature lists, and comforting phrases like “industry standard”, “proven deployments”, “open protocols” and “lowest total cost of ownership”

At this point, procurement does exactly what it is designed to do: compare, normalise, de-risk, and choose.

And this is where things quietly go sideways.

Because buildings are not laptops.

Procurement frameworks are excellent at buying things that are clearly defined, static, and comparable. Chairs, Servers, Software licences with neat SKUs. But buildings are living systems. They evolve, age, behave differently across seasons, and respond unpredictably to human use. The moment we try to buy them like commodities, nuance gets flattened.

So the safest vendor often wins. Not the most adaptable one. Not the one that understands how buildings actually behave. Just the one that fits the spreadsheet cleanly.

And once that decision is made, it becomes strangely permanent.

Most building technology decisions don’t last three years. They last ten, fifteen, sometimes twenty. Control logic hardens. Contracts renew quietly. Integrations become fragile folklore. Every future innovation is now prefaced with the sentence: “But will it work with what we already bought?”

The curse isn’t that procurement chose poorly.
It’s that procurement was asked to predict the future using yesterday’s evaluation criteria.

Here’s the uncomfortable irony: the vendor that demos best during procurement is often the least useful five years later. Shiny dashboards age quickly. Static rule engines don’t learn. Closed systems feel stable until you try to adapt them. And the buildings that looked “future-proof” in the tender meeting slowly become operational museums.

Operators feel this first.

They inherit systems chosen for compliance, not cognition. Systems that generate alerts but not insight. Systems that assume perfect data, perfect usage, and perfect humans. Over time, operators stop asking the system for answers and start working around it. Spreadsheets reappear. WhatsApp groups form. Tribal knowledge takes over. The building functions – but not because of the platform. In spite of it.

Owners feel it later.

They see rising OPEX without clear explanations. ESG narratives that require manual justification. Occupant feedback that never quite matches the dashboards. And when someone asks, “Can we optimise this across the portfolio?” the answer is usually a polite version of “Not easily.”

And yet, the procurement decision remains oddly untouchable. After all, it was signed off. It met requirements. It ticked boxes. It passed audits. The curse protects itself.

What makes this even more interesting is that AI exposes this gap brutally – but quietly.

AI doesn’t care about brand names or tender scores. It cares about data quality, openness, learning ability, and context. It quickly reveals whether a system can evolve or merely exist. And when AI is layered onto legacy procurement decisions, the limitations surface fast. Not as dramatic failures – but as ceilings you keep bumping into.

This is where the smartest procurement leaders are beginning to change their posture.

Instead of asking, “Which vendor meets all requirements today?”
They ask, “Which decision leaves us the most optionality tomorrow?”

Instead of freezing intelligence into a contract, they create room for learning layers, adaptive platforms, and systems that can sit above what already exists. They accept that intelligence is not something you fully specify upfront – it’s something you enable over time.

Ironically, this shift actually reduces risk. Buildings that can explain themselves, adapt themselves, and improve themselves are far less fragile than those locked into rigid certainty.

So no, the procurement manager is not the villain in this story. But the curse is real. And it shows up whenever long-lived, complex systems are bought using short-term certainty as the primary metric.

The good news? This curse is reversible.

The next generation of procurement decisions won’t be about picking the vendor. They’ll be about choosing architectures that allow intelligence to grow. They’ll reward openness over polish, learning over rules, and outcomes over features. And the procurement managers who lead this shift will quietly become some of the most influential stewards of asset value in the room.

Because in the end, the most dangerous thing a building can be is not inefficient or outdated.

It’s confidently locked into yesterday’s idea of “good enough.”