Secure AI deployment for AEC firms. Connects to SharePoint, Google Drive, and local archives. Human-approved outputs by default
← Blog

AI Adoption

The AI Tools Your AEC Firm Is Probably Already Paying For (And Not Using)

Microsoft Copilot, Adobe AI, and project management integrations sit unused inside most AEC software stacks. Here is an honest audit of where the actual value lives, and why adoption stalls without a connected workflow layer.

A

Alice Wong

June 19, 2026 · 5 min read


You already bought the AI. It is sitting in your license seats.

Walk into most AEC firms and ask what they are "doing about AI," and you will hear about pilots, committees, and a line item in next year's budget. Then look at what the firm already pays for every month. Microsoft 365. An Autodesk subscription. Bluebeam. Adobe Acrobat. A project management platform. Every one of those now ships with AI built in, and at most firms almost nobody is using it.

This is the quiet part of the AEC AI conversation. The barrier usually is not budget. It is that the tools you have already licensed are doing a fraction of what they could, and no one has connected them to how the work actually moves.

Where the value is hiding

Here is an honest audit of the AI you are likely already paying for:

  • Microsoft 365 Copilot drafts and summarizes inside Outlook, Word, Teams, and Excel. For a firm that lives in email threads and meeting notes, this is the highest-frequency, lowest-glamour win available.
  • Autodesk Assistant is now expanding across Revit, AutoCAD, and Civil 3D as part of the broader Forma push. Firms like DPR, HOK, Stantec, and Arcadis are already wiring it into design and construction work.
  • Bluebeam automates markups, takeoffs, and repetitive review actions you are probably still doing by hand.
  • Adobe Acrobat AI Assistant lets you query long PDFs in natural language. Point it at a 200-page geotech report, a spec section, or an inbound RFP and ask instead of scroll.
  • Your PM platform's copilot (Procore and others) surfaces RFIs, submittals, and schedule risk without a manual dig through the log.

Notice the pattern: none of these require a procurement cycle. They are features inside seats you renew anyway.

So why does it sit unused?

Microsoft's own numbers tell the story. Copilot has roughly 15 million paid seats against 450 million Microsoft 365 commercial subscribers, about 3.3% of the people who could be using it, two years in. And when employees have both Copilot and ChatGPT available, only 18% reach for Copilot while 76% reach for ChatGPT.

Read that again. The problem is not that people will not touch AI. It is that they default to whatever is easiest to reach and ignore the capable tool already embedded in their workflow.

A 2025 survey of around 1,000 AEC professionals found only 27% use AI in their operations at all, though 94% of those who do plan to use it more in 2026. The firms holding back consistently name the same three obstacles, and cost is not one of them: complexity, culture, and connection.

The biggest barrier to getting value from AI is not the technology or the people. It is the organization around them.

That is the conclusion of a Microsoft study of 20,000 workplace AI users, and it matches what we see in AEC: licenses bought, training skipped, tools never wired into the proposal, the report, or the submittal: the moments where the senior hours actually go.

What actually moves adoption

The firms getting real value did not buy more AI. They changed how they introduced it.

Kimley-Horn, a large multidisciplinary AEC firm, rolled out Microsoft 365 Copilot not with a launch email but with what they called an "AI workout": recurring, short sessions where teams practiced small, repeatable Copilot tasks until they became second nature. They met people inside the workflows they already had instead of asking them to adopt a new one.

That is the whole trick. Adoption follows the work, not the org chart. A principal will use AI to clean up a fee proposal if it lives where she writes the proposal. She will not log into a separate tool, paste in confidential project data, and learn a new interface between deadlines.

The audit worth running this week

Before approving a new AI line item, run the inventory you already own:

  1. List every subscription with AI included: M365, Autodesk, Bluebeam, Adobe, your PM platform.
  2. Count actual active users of each AI feature, not license seats. The gap is your real opportunity.
  3. Pick one repeatable task per tool, meeting recaps, spec lookups, drawing markups, and make it a habit, Kimley-Horn style.
  4. Find the disconnects. Wherever someone copies data out of one tool to feed another by hand, that seam is where embedded AI quietly fails and where a connected layer earns its keep.

The real cost of shelfware

Unused AI seats are not free. You pay the subscription and you pay again in the senior hours spent doing what the tool could have drafted. For 2026, the line that keeps showing up in industry forecasts is that AI has shifted from "future trend" to "industry baseline". The firms that fall behind will not lose on technology budgets, they will lose bids to competitors who deliver faster.

The good news is that catching up rarely starts with a purchase. It starts with using what you already bought, and connecting those tools to the workflows where proposals, reports, and submittals actually get made. That connective layer, not another standalone app, is where the next round of AEC productivity is going to come from.

Related posts

See all posts →