GO First Consulting
Grant Fuellenbach·September 20, 2026

How to use AI in a construction business

Start with the work, not the model. Find one recurring workflow where people lose time, information, or margin — plus a reliable source and a clear human decision. Ask: what work happens weekly, depends on information we already have, and still falls back on the owner?

1. Find a workflow, not a feature

Look for work that is frequent, costly when it breaks, structured enough to describe, and reviewable. If you cannot describe the trigger, the inputs, and who reviews the output, it is not ready.

Examples

▸Meeting follow-ups that never get sent
▸Estimate scope checklist that lives in the owner's head
▸Unbilled change-order signals buried in daily logs
▸Weekly client updates cobbled together from three places
▸Company knowledge answers that require texting the owner
▸Stale tasks and logs no one flags until the client calls

2. Name the source of truth

Every AI workflow reads from somewhere. Identify the PM record, scope, schedule, policies, and history it needs. Fix the process before connecting tools.

PM record

Is it current? Does the team trust it?

Scope and schedule

Is the approved version in one place?

Company policies

Written, approved, and findable?

Project history

Can AI read past jobs for context?

Access

Can the workflow reach the data it needs?

Final storage

Where does the reviewed output live?

3. Decide what stays human

AI prepares. A person decides. The system records. Define that boundary before building anything.

Estimate comparison
AI:Pull historical costs, flag variances
Person:Review and approve the number
System:Store approved estimate version
Change-order risk list
AI:Scan logs for unbilled scope signals
Person:Decide whether to issue the CO
System:Record CO status and client response
Weekly client update
AI:Draft update from project record
Person:Review and send
System:Log sent update with timestamp
Stale task alert
AI:Flag tasks past due or missing logs
Person:Investigate and reassign
System:Update task status
Company knowledge answer
AI:Search approved policies, cite source
Person:Verify answer fits context
System:Store Q&A for future reference

4. Build the smallest version

Use 5–10 real examples including bad inputs. Define the trigger, inputs, output format, required citations, reviewer, prohibited actions, and where the result is stored.

5. Train the role in real work

Not a demo. Not a recording. The estimator runs their next estimate with the new workflow. The PM updates their next project.

6. Measure outcome and adoption separately

Outcome: is the workflow producing a better result? Adoption: is the team actually using it? Both matter. Fix adoption before adding the next workflow.

7. Add the next workflow after the first is stable

Stable means the team runs it without daily support, the owner is not routing around it, and the data is current.

Where companies start

Estimating

Pull historical costs, compare scope, flag variances

Project management

Summarize status, draft updates, flag stale items

Change orders

Scan logs for unbilled scope, prepare CO review

Company knowledge

Answer team questions from approved policies with citations

Leadership visibility

Weekly digest of project health, cash flow, and exceptions

A practical 7-point AI policy

1.Only use approved AI accounts provisioned by the company
2.Confidential project data only enters approved tools
3.Verify any AI output involving cost, date, scope, safety, or commitments before acting
4.A person owns every external message and decision — AI drafts, you send
5.Store the reviewed record, not just the AI output
6.Document standard workflows so the next person can run them
7.Report errors and improve the source data and process, not just the prompt

The test

It is working when your team gets an approved answer, completes the next step, and leaves the right record — without routing every question through the owner.

From Beyond the Bid: What a Construction Company's AI Policy Should Actually Cover · How to use AI for change orders before the work starts

Tell us one repeating workflow in the free Diagnostic.

Roadmap in 2 business days · No obligation

Not ready to talk? Take the free 7-minute SkillMatch assessment