Zero RFI
In 2011, a textbook was published on Building Information Modeling for owners and developers. The premise was compelling: BIM would finally give building owners the rich, data-driven picture of their buildings that they’d always needed. A dynamic digital record. A foundation for facilities management. A tool for ongoing operational intelligence.
What most owners actually received at project closeout: a PDF set. Maybe a Revit file that their facilities team has no license or training to open.
The gap between that promise and that reality is worth sitting with, because AI is making the same promises now, and the question is whether history is going to repeat itself.
What BIM was actually built for
The pattern underlying BIM adoption is worth examining clearly. The tools were developed for architects and engineers, marketed to owners as the beneficiaries, and implemented in ways that served the design and construction community’s workflows.
Architects got better drawing production. Contractors got clash detection. Owners got documentation that lived in formats requiring expensive consultants to interpret, if it was maintained at all through construction.
The “as-built digital twin” that was supposed to transform facilities management became, in practice, a model that was accurate as of design completion and progressively less accurate as construction proceeded and changes were made in the field.
There was no deliberate deception. The industry built tools that solved the problems that were clearest and most immediate to the people using them daily. Owners, who only show up at the beginning and the end of most projects, weren’t the ones shaping the tools.
The lesson for what comes next
AI is being marketed to owners in language that sounds familiar. Real-time intelligence. Predictive analytics. Operational insights. Data-driven decision-making. These are the right outcomes. The question is whether the tools being sold will actually deliver them, or whether they’ll deliver value to the architects, contractors, and technology vendors who are closer to the development process.
The pattern to watch for: tools that require significant owner investment in adoption (training, process change, new workflows) while delivering most of their immediate value to the service providers using them daily. The owner benefits are real but distant, contingent on sustained use that rarely happens.
What would actually serve owners
The AI capabilities that genuinely benefit owners don’t require owners to learn new software, conform to new workflows, or maintain data disciplines that aren’t core to how they operate.
They work by ingesting what already exists (project documents, emails, field reports, meeting transcripts) and surfacing intelligence in forms that owners can actually use without becoming construction technology experts.
What did the project cost versus what was bid, and where did the gaps come from? What decisions were made during construction that affected long-term operating costs? What performance characteristics should the owner be tracking, and how does actual performance compare to design intent?
These are owner questions. Good AI tools for owners answer them. Bad AI tools for owners give owners another dashboard to maintain that gradually goes stale as project teams stop feeding it.
The question to ask any technology vendor
When someone pitches you on AI capabilities for your project, ask this: three years after this project closes, what will I actually be using from this system, and what will it cost me to maintain it?
The honest vendors will have a real answer. The others will talk about the richness of what they’re delivering at closeout without engaging with what happens next.
BIM failed owners not because 3D models are bad, but because the operational commitment required to capture the benefits wasn’t realistic for most owner organizations. AI can fail the same way, sophisticated at delivery, unused in operation.
The technology that actually changes things for owners will be the kind that requires almost nothing to maintain because it’s working continuously in the background. That’s the standard to hold new tools to. Don’t accept another beautiful system that goes dark six months after your project closes.
