Zero RFI
Every AEC conference has the same cast of characters. Architects talking about design excellence. Contractors talking about jobsite efficiency. Technology vendors talking about their platforms. And somewhere, almost as an afterthought, a building owner in the room wondering why the conversation has not yet turned to what they actually need.
That is not an accident. It is a structural problem, and it is why most AEC innovation lands with a thud.
Who the industry is actually building for
Buildings exist because owners need them. A hospital needs a place to treat patients. A manufacturer needs a facility to make things. A developer needs a building that generates returns. The building is a means to an end, and the owner is the one who understands that end better than anyone.
Yet when AEC firms and technology companies design their workflows, they optimize for their own processes. BIM tools were built for architects and contractors, not for owners. Project management software was built for design teams and GCs, not for the people signing the checks. The owner receives a PDF at closeout and is expected to be satisfied.
The feedback loop that was never built
The deeper problem is this: the owner is the one who knows whether the building actually worked. Did it operate the way the design intended? Did the maintenance costs match the projections? Did the layout support the business the way it was supposed to?
That feedback almost never returns to the design and construction team. The project ends, the team disperses, and the owner is left managing a building with a three-ring binder and an email address for the warranty department.
This is why the industry repeats the same mistakes. There is no closed loop between what owners experience operating buildings and what designers and builders learn from those outcomes. Every project begins largely from scratch, repeating errors that could have been avoided if anyone had asked the people living with the consequences.
What owners actually need from innovation
They do not need better-looking drawings. They need to understand what they are building before they commit to it, expressed in terms that connect to their business, not their architect’s workflow.
They need real-time information during construction. Not monthly reports already two weeks stale by the time they arrive. Not dashboards requiring a consultant to interpret. Actual clarity about what is happening on their project and what decisions they need to make.
They need the building to perform as promised after handover. Not performance backed only by a warranty that goes unread. Measurable outcomes, tracked against what was committed.
None of this is technologically difficult. What is difficult is getting an industry oriented toward its own internal complexity to reorient toward the person the whole endeavor is supposed to serve.
What changes when you center the owner
When you start from owner outcomes rather than industry workflows, the questions change. Instead of “how do we make design more efficient,” you ask “how does the owner know they are getting what they paid for?” Instead of “how do we reduce RFIs,” you ask “why did the owner lack enough information to define scope clearly before RFIs became necessary?”
These are not the same question. And the answers point toward meaningfully different solutions.
The AEC industry is full of capable people working to improve a broken system. The persistent challenge is that they keep improving the system they inherited rather than rebuilding it around the person it is supposed to serve. That is the gap. And it is larger than any software tool will resolve on its own.
The owners who recognize this are beginning to demand more, not from their vendors’ innovation roadmaps, but from the first conversation. That is the pressure the industry needs.
