Construction AI: Schneider paid $22.6bn for PTC, and the engineering software you rely on keeps shrinking into fewer hands

Schneider Electric confirmed on 5 October that it is buying PTC, the American design and lifecycle software company, for $22.6bn in equity value, or $23.7bn once the debt is counted. The price works out at $205 a share, and the deal is expected to close in the third quarter of 2027 (reported by Bloomberg and the FT on 4 October, with Schneider confirming on 5 October). It's the largest software acquisition Schneider has made, and it doesn't stand on its own. The same company bought the AI firm Cognite in June, and it already owns AVEVA, the industrial-software business it took full control of back in 2024.

PTC isn't a name most site teams would recognise, but its tools sit under a lot of the work. Creo is design software, Windchill handles product lifecycle and the record of what got built and why. Schneider's pitch is that it can bolt that software onto its own hardware, the switchgear, the cooling, the power distribution, and sell the lot as one stack to the people building data centres, factories and large buildings. Read against the diesel-and-data-centre story from a few days ago, you can see why. The data-centre build-out is where the demand is, and Schneider wants to own more of the software layer that sits on top of its kit.

So why does a construction brief care about an industrial software merger. Because the tools a design office or a QS opens are drifting the same way. Fewer suppliers, bigger bundles, more of your stack owned by one firm. The procurement filter: when you next price a platform, put a line in the model for what it costs to leave it, not just what it costs to run. A $22.6bn deal three layers up is a long way from your site office, but the thing it's building, a small number of very large software estates you rent rather than own, lands on your desk in the end.

A week before the Schneider news, on 28 September, Arcadis said it was deepening its tie-up with Autodesk and connecting its own Model Context Protocol tooling to Autodesk Assistant, the firm's AI that's meant to read geometry, engineering intent and project history (Arcadis newsroom, 28 September; ENR). The headline the consultant led with was a number: automation had pulled its quality reviews down from five days to roughly half a day on live initiatives across North America and Europe. That figure is Arcadis's own, from existing projects, so treat it as a claim rather than a benchmark. The two chief executives, Heather Polinsky at Arcadis and Andrew Anagnost at Autodesk, both put their names to it, which tells you how much weight each side is putting on the pairing.

What Model Context Protocol does, in plain terms, is let one company's AI reach into another's tools and data in a structured way, so the agent chasing a checking task can actually see the project rather than guess at it. Arcadis is using it to pour its own know-how into Autodesk's platform rather than build a rival to it. There's a joint project too, which they've called See Through Walls, using sensors and predictive modelling to work out the condition of what's hidden inside existing buildings, aimed at material reuse and cutting carbon. That's the genuinely interesting bit for anyone doing retrofit, and it's the part I'd want to see stand up on a real job rather than in a press release.

But notice the shape of it. One of the biggest consultancies working on UK infrastructure has decided the smart move is to embed itself deep inside a single incumbent's platform. That's a reasonable bet for a firm that size. Worth doing: if you're a smaller practice watching this, don't try to copy it. The lesson isn't to pick a giant and marry it. It's that the review-and-check work is where the time actually goes, and that's the bit to go after first, whatever tool you use to do it.

Put the week together and it's one story told twice. Schneider is buying its way to a bigger software estate. Arcadis is wiring itself into one. Both are rational, both are big firms making big-firm bets, and both point the same way: the software that runs engineering and construction is settling into a few large, bundled, hard-to-leave stacks. That's the high street before the app banks, and the comparison only stretches so far, but the pressure it describes is real.

Which is where the challengers come in, the AI-first tools built to take on the incumbent suites the way the app banks took on the high street. Their whole case is the opposite of a merger. Published pricing instead of an annual negotiation. A self-serve start instead of a six-month rollout. And, the one that matters most this week, your data out the door with you if you decide to go. When the market consolidates above you, that promise stops being a nice-to-have and starts being the thing you check first.

For your board pack: add a single line to any software decision this quarter, the cost and the mechanics of leaving. Not because you're planning to, but because the people selling to you are busy making that harder, and the person who ends up stuck isn't the one who signed the deal. It's the site manager and the PM three years later, trying to get their own records out of a tool they can no longer afford. That's what it's about.