Five years ago, the question was whether a company could afford to build its own software. AI coding agents have turned that into a different question: whether it should. That shift is what Wall Street briefly nicknamed the SaaSocalypse in early 2026, the fear that agentic AI would let companies build in-house what they used to buy, cheap and fast enough to make buying pointless. It didn't play out that cleanly, software stocks fell hard and then mostly recovered within months. The panic overshot. But the shift it was reacting to, AI genuinely lowering the cost of building, is real, and that's why build versus buy is worth asking again in facilities management too.
‍

That question lands just as directly inside FM, because software choices carry consequences the same way operational ones do. Facilities management is a business of compounding decisions. A maintenance choice made today can influence asset reliability, energy costs, and client satisfaction months later. Technology strategy works the same way. Whether a company chooses to build or buy rarely proves itself in the first year. The consequences compound over time, in engineering costs, operational capability, how quickly the business can adapt, and ultimately the competitive advantage it creates.
‍

What are you actually trying to become

Before getting to build or buy, it helps to ask something more basic: what do you actually want your technology to do?
‍

Some FM leaders mainly want fewer surprises, work orders that don't sit unassigned, an accurate record of what's actually been serviced, reporting that doesn't take three days to pull together. Others want technology to move numbers that matter well beyond daily operations, margins, contract retention, what the business looks like the day someone eventually values it. Neither answer is wrong, they're just different starting points, and the bar for good enough shifts depending on which one is actually being answered.
‍

If it's the first, that's a legitimate destination in itself. Plenty of FM businesses run well without wanting to be anything more than reliable. But if it's the second one, wanting technology to shape the operating model rather than merely support it, that ambition already has a name in the market. Being tech-native.
‍

Private equity has been paying close attention to FM, treating it as a sector worth scaling and consolidating rather than just holding steady. And within that activity, seemingly similar FM businesses have commanded very different revenue multiples. Smart Managed Solutions was reportedly valued at around 1.5 to 1.7 times revenue, while EMCOR UK's acquisition implied roughly 0.6 times. Those figures don't tell us why the difference exists, profitability, growth prospects, deal structure, and buyer motivation all matter, and technology embedded in the operating model is at most one input among many, not something these numbers can isolate or prove. But they do highlight something worth asking: what characteristics make one FM business fundamentally more valuable than another? Technology isn't the only answer, but it's becoming increasingly difficult to argue that it's not part of the conversation.
‍

What actually earns that difference isn't simply having AI. Access to powerful foundation models is becoming increasingly widespread across the industry. What separates FM companies is where that AI actually sits, bolted onto the side as a feature nobody quite uses, or built into how decisions actually get made and work actually gets dispatched. That's the real decision the rest of this comes down to, not whether to have technology, but where the advantage from it should live.
‍

What building in-house actually commits you to

Building your own platform is one way to try to own that advantage outright, nobody else has exactly what you built, by definition. Here's the part that usually gets skipped though. Building it properly doesn't stop once the first version ships. It means running a second business alongside the FM business, one with its own product managers, engineers, QA, security reviews, integrations, customer support, release management, and governance. None of those needs disappear once version one ships. They're recurring costs for as long as the platform exists.
‍

That's a bigger commitment than the budget line usually suggests. Large software projects have a long, well-documented history of running over budget and falling short of what they promised, and there's no real evidence yet that agentic AI has changed that. Building version one is the easy part. What comes after, patching, upgrading, keeping pace with new integrations, tends to cost more than what came before, for as long as the platform stays in use. AI-generated code still needs real oversight for quality and governance, the same as code written any other way, faster doesn't mean fewer things can go wrong. None of this makes building the wrong call.
‍

Where a company has a genuinely unique need or domain requirements no existing product fits, running that second business might be worth it.
‍

Buying only wins if it's genuinely ahead

Buying has an obvious rebuttal built into it, worth naming directly. If a competitor can buy the exact same platform, how does buying it make you different from them?
‍

The honest answer is that differentiation was never about exclusive ownership. It's about access to capabilities that would otherwise take years to build independently. When everyone can buy the same underlying platform, differentiation moves elsewhere, into how that capability actually gets implemented, how deeply it's embedded into daily decisions, and how quickly a company acts on what it learns. Two companies can buy the identical platform, and if one reaches real operational impact three years before the other is still building its own version, the advantage is real, even without being exclusive.
‍

Take predictive maintenance as an example. A specialist FM platform arrives having already solved many of the universal problems, integrating with common CMMS and BMS environments, reducing false alarms, refining fault detection logic, learning which patterns are generally worth investigating. What it doesn't arrive with is knowledge of a customer's own portfolio, that still has to be learned after deployment. The difference is that the customer starts by adapting the platform to its own portfolio, rather than first building a predictive maintenance platform from nothing. Building means solving both the universal problems and the portfolio-specific ones. Buying lets a specialist solve the first, so your team can focus on the second.
‍

That advantage only shows up under one condition though. The vendor has to be genuinely ahead of the market, not just present in it, and figuring that out deserves more diligence than most companies give it before signing. There's a real dependency cost too. Whoever a company buys from now has a hand in its roadmap, and where data sensitivity or deep customisation genuinely matters, that's a legitimate factor to weigh, not just a talking point.
‍

The real question was never build or buy

Buyers ultimately pay for capabilities a business's competitors can't easily reproduce, whether those capabilities live in owned software, in operational IP built around a bought platform, or in an operating model nobody else has matched.
‍

Build versus buy was never the real question. The real question is where competitive advantage should live, and whether the business is equipped to own and defend it there. Build only when the need is genuinely unique enough to justify running a second business indefinitely. Otherwise, the advantage usually comes faster from how fast and how deep a bought platform gets embedded.
‍

FAQs

What does it mean for an FM company to be "tech-native"?

It means technology shapes the operating model rather than just supporting it, moving numbers like margins, contract retention, and long-term valuation, not just fixing day-to-day operational friction. It's one possible destination, not the only legitimate one.
‍

What does building an in-house FM platform actually commit a company to?

More than a one-time project. It means running a second business alongside the FM business, with its own product managers, engineers, QA, security reviews, integrations, customer support, release management, and governance, all as recurring costs for as long as the platform exists.
‍

If a competitor can buy the same platform, how does buying create any advantage?

Not through the technology, since two companies buying the same platform have identical tools. The advantage comes from implementation, how deeply it gets embedded into daily decisions and how fast a company acts on what it learns.
‍

What's the catch with buying instead of building?

The advantage only holds if the vendor is genuinely ahead of the market, not just present in it, which deserves real diligence before signing. There's also a dependency to factor in, since the vendor now has a hand in the roadmap, which matters more where data sensitivity or deep customisation is involved.
‍

Does technology actually affect how an FM business gets valued?

Recent FM deals have shown wide gaps in valuation multiples between seemingly similar businesses, Smart Managed Solutions at roughly 1.5 to 1.7 times revenue versus EMCOR UK's acquisition at roughly 0.6 times. Many factors drive that gap, and technology is only one input among them, but it's increasingly hard to leave out of the conversation.