A question worth sitting with: how many software platforms are your project teams currently paying for? And of those, how many are actually delivering results you can measure?

For most building owners, the answer is a familiar one: many platforms, modest results, and project managers who will tell you privately that they run their actual work out of email and spreadsheets.

The grand promise that didn’t land

BIM was supposed to change everything. A single model that captured design intent, enabled coordination, surfaced conflicts before they became field problems, and handed over a rich digital record to the owner at closeout.

For owners specifically, the promise was a digital twin, a model so rich and accurate that it could serve as the foundation for facilities management, maintenance planning, and operational optimization for the life of the building.

What most owners actually received: a PDF. Maybe a 3D model in a format their facilities team has no software to open. A drawing set that was out of date before the paint dried.

BIM delivered value to designers, who use it to produce drawings. It delivered some value to contractors, who use it for coordination and clash detection. It delivered almost nothing to owners, who were the original intended beneficiary.

Why centralized software fails in a decentralized industry

The reason is structural, not accidental. Software products are built on the assumption of standardization: everyone using the same workflows, the same data structures, the same naming conventions. That’s how a database stays coherent.

But construction is the opposite of standardized. Every project is different. Every team assembles from different firms with different tool preferences and different process habits. The GC doesn’t use the architect’s software. The MEP subcontractor doesn’t use the GC’s project management platform. Everyone has their own system, and the “single source of truth” exists, in practice, in the email threads where actual decisions get made.

Forcing a decentralized, project-specific industry into centralized software is like trying to run a farmers market on a grocery store’s inventory management system. The metaphor doesn’t fit the reality.

Where project information actually lives

On your project right now, if you asked three different people where the most current version of the project schedule was, you’d probably get three different answers. Someone would say Procore. Someone would say the GC’s last email attachment. Someone would say they think the PM has an updated version but hasn’t shared it yet.

The “single source of truth” that software vendors sold you is a fiction sustained by the absence of time or incentive to challenge it.

This isn’t a failure of your team. It’s the predictable outcome of asking construction teams to conform to software logic that doesn’t match how projects actually work.

What actually creates value for owners

The question worth asking isn’t “which software platform should I mandate?” It’s: what information do I actually need, and how do I get it regardless of which tools each party is using?

That reframe points toward AI. Not as another platform to standardize on, but as a layer that ingests the chaos (the emails, the meeting transcripts, the field reports, the multiple versions of the schedule) and synthesizes it into coherent information for the owner’s decision-making.

Accurate, current information doesn’t need to live in one system. It needs to be findable across all the systems, surfaced in a form you can use.

The return on your software investment

Before your next project, ask every major team member to document what software they’re using and what decisions that software is informing. Not what features they have access to, what decisions.

The gap between “we have this capability” and “this capability is driving decisions” is where software ROI disappears.

Then ask whether AI-assisted synthesis of the information those tools generate could give you better visibility as an owner than any of the individual platforms. The answer is almost certainly yes.

Stop buying platforms and start demanding outcomes. The software vendors won’t like it. Your project results will.