Zero RFI
Ask your architect if they’re using AI. They’ll probably say yes. They have a ChatGPT license for the office.
Then ask them which parts of your project it touched. Watch what happens.
The “not ready yet” trap
There’s a line you’ll hear from a lot of design and construction firms when you push on AI adoption: “We’re evaluating it, but it’s not mature enough for our work yet.”
It’s a reasonable-sounding position. It’s also how firms fall behind.
The early internet was slow, unreliable, and full of broken promises. The firms that waited for it to be “ready” lost a decade of competitive positioning to the ones that figured it out while it was still awkward.
AI in AEC is at that same point right now. It’s imperfect. It makes mistakes. It requires human judgment to use well. None of that is a reason to wait. It’s a description of every new capability at the point when it matters most to adopt it.
The firms adopting AI today aren’t doing it because it’s perfect. They’re doing it because the learning curve is real, and the firms that start climbing it now will be meaningfully better than the ones who start in two years.
What “AI-first” actually means for your projects
When a firm says they’re AI-first, it shouldn’t mean they’ve added a chatbot to their website. It should mean the tool shapes how they approach the work.
For a design firm, that means AI is involved in coordination checking, clash detection, specification writing, RFI responses, not as a parlor trick, but as part of the actual production workflow. For a contractor, it means schedule analysis, cost risk flagging, and field reporting are happening faster and with better information than they were two years ago.
The practical question for you as an owner: is your design and construction team using AI to surface problems earlier, or are they surfacing the same problems at the same point in the project they always have?
If the answer is the latter, the tools may have changed but the outcomes haven’t.
The build-it-yourself illusion
Some owners hear “AI in construction” and think about building internal tools. Apps, dashboards, custom models. That’s a different conversation, and for most owners it’s a distraction.
Your building is a means to your core business: a hospital, a distribution center, a corporate campus. You don’t need to be an AI company. You need to work with partners who are.
The right question isn’t “should we build AI capabilities?” It’s “how do I evaluate whether my vendors have genuinely integrated AI into their work, versus just telling me they have?”
Three questions that separate real from theater
When you’re evaluating design and construction partners, these cut through the noise:
Show me a project where AI caught something that would have been missed otherwise. Not a demo. A real project, a real problem, a specific outcome.
What does your RFI process look like today versus eighteen months ago? If AI is genuinely in the workflow, the volume and speed of RFI resolution should have changed.
Who owns AI adoption at your firm, and what’s their budget? A firm that’s serious about this has someone accountable for it and resources behind it. “We have a committee looking at it” is not the same thing.
What changes for you when your partners get this right
The downstream effects of genuine AI adoption by your design and construction team are real and measurable.
Fewer RFIs means fewer coordination gaps reaching the field. Faster issue identification means problems get resolved before they affect schedule. Better documentation means your closeout package is actually useful rather than nominally complete.
None of this happens automatically just because a firm has an AI subscription. But firms that have genuinely rethought their workflow around these tools produce measurably different results.
The window to find those firms, before they’re universally recognized and their fees reflect it, is right now. Ask the questions. Look at the evidence. The ones doing the real work will have real answers.
