Zero RFI
Two years ago, “AI strategy” was something tech companies needed. Today, it’s something your architect, your GC, and your property manager need, and if they don’t have one, you should be asking why.
This isn’t about trends. It’s about competitive reality. The firms that are integrating AI into their workflows are delivering faster, catching more problems earlier, and producing better documentation. The ones that aren’t are falling behind, and eventually, the gap shows up in your project outcomes.
What “having an AI strategy” actually means
It doesn’t mean buying a subscription to ChatGPT and calling it innovation. It means systematically thinking through where AI can accelerate outcomes, and building the workflows to make that real.
For an AEC firm, that might look like: AI-assisted specification review that flags gaps before they become RFIs. Automated meeting summary generation that creates action item logs without someone having to spend three hours on notes. Schedule risk analysis that pulls patterns from historical project data rather than relying on one PM’s gut feel.
For a developer or owner, it might look like: AI-powered market analysis at the front end of a project. Automated tracking of deliverables and milestones so you don’t have to chase status updates. Real-time cost benchmarking against comparable projects.
None of this requires building technology. It requires your vendors and partners to have done the work of integrating available tools into their processes. The question you should be asking in every procurement conversation is: what specifically are you doing with AI, and how does it benefit my project?
The technology adoption gap is your risk
When a firm hasn’t thought through its AI integration, the risk lands on you.
They’re taking longer to produce deliverables that AI could accelerate. They’re missing coordination issues that AI-assisted review would catch. They’re giving you information on a lag when real-time synthesis is available. And because they’re behind on tooling, they’re competing on relationships and reputation rather than on measurable capability.
That’s fine if relationships and reputation are sufficient. But when your project has a hard opening date, a fixed budget, and no room for the standard 20 percent cost overrun. You need more than a firm with good relationships.
What the next five years look like
The AEC firms that build genuine AI capability now (not just licensed software, but actual workflows and institutional knowledge) are going to be delivering on a fundamentally different capability curve by 2028.
Projects that used to take 18 months of design might take 12. Coordination conflicts that used to surface in the field might get resolved in design. Handover documentation that used to take weeks to assemble might generate continuously throughout construction.
These outcomes are achievable with tools and approaches that exist today. The gap is adoption and workflow integration, not technology.
As the person writing the checks, you have more leverage over this than you might realize. You can require AI-enabled workflows in your procurement criteria. You can ask for documentation of AI use during project delivery. You can reward firms that demonstrate measurable improvements with repeat work.
The owners who do this will get better projects. The ones who don’t will keep getting the same results from an industry that has no particular reason to change its approach without the pressure.
The question isn’t whether AI matters. It’s whether you’re using your position to demand what it makes possible.
