AI can now work across construction software. But should it?

• OpenAI and Anthropic document computer-use tools that inspect browser or desktop state and return actions for an application to execute.
• Both providers recommend isolated environments, restricted access, and human confirmation for consequential actions.
• MCP standardizes how an AI host can discover resources and invoke tools, but each server still has to validate inputs and enforce authorization.
• Procore and Autodesk document APIs and webhook mechanisms that can expose supported construction records and events without screen operation.
• No cited source claims that an agent automatically understands a contractor's commercial rules, contractual authority, project context, or operating responsibilities.

A recorded demonstration proves that an interface action worked in that case. It does not prove repeatable identity, authorization, recovery, business correctness, or acceptable operating cost across a contractor's live workload.

1. 01

   Invitation

   An RFQ arrives in a personal or shared inbox with attachments and a deadline in the message body.

2. 02

   Portal

   A coordinator signs into a bid portal to confirm addenda, download files, and inspect changed listings.

3. 03

   Files

   Documents move into a project folder where names, revisions, and ownership may differ from the portal.

4. 04

   Spreadsheet

   Opportunity details and qualification notes are copied into a tracker maintained by one team.

5. 05

   Project system

   A project or estimate is created later, often with another identifier and incomplete source history.

6. 06

   Decision

   Estimator capacity, bid or no-bid reasoning, clarifications, and submission approval remain spread across messages and meetings.

Schedule approved check
  -> open allowlisted portal in isolated browser
  -> confirm account, project and page context
  -> apply approved filters
  -> compare listing IDs and fingerprints with prior state
  -> download permitted files
  -> validate file identity, size and completeness
  -> create or update source-linked opportunity record
  -> route new, changed or uncertain items to owner
  -> stop before reply, acceptance, bid decision or submission

Capture approved RFQ email and attachments
  -> preserve sender, recipients, message ID and received time
  -> match company, contact, project and opportunity
  -> classify documents and extract candidate fields
  -> validate deadline, attachment integrity and required information
  -> create visible exceptions
  -> assign estimator and require acknowledgement
  -> draft source-linked bid-decision brief
  -> authorized person records bid or no-bid decision
  -> pricing, approval and submission remain separate controlled stages

1. 01

   Boundary

   One source workflow, defined users, allowed systems, read and write actions, prohibited actions, and named owners.

2. 02

   Baseline

   Representative cases, current time and error baseline, known exceptions, expected outputs, and complete operating cost.

3. 03

   Controls

   Least privilege, isolated execution, action allowlist, source validation, checkpoints, approval gates, and stop states.

4. 04

   Evaluation

   Task success, critical errors, false completion, exception routing, human correction, latency, and cost per accepted outcome.

5. 05

   Acceptance

   Pre-agreed thresholds, zero-tolerance failures, rollback conditions, reviewer signoff, and evidence retention.

6. 06

   Expansion

   Add another action, system, or user group only after the prior boundary remains reliable over repeated runs.