Resources/The TeamOS Brief/Start AI in one department, not all of them

Start AI in one department, not all of them

Monday, November 02, 2026

The TeamOS Brief | Issue 6

Three levels, one department at a time, and why the numbers come first.

Nobody in the conference room touched the mouse. On the screen, an AI agent opened the accounting software, pulled the WIP report and started checking the settings, and the room went quiet, because everyone could see what used to take a controller half a day.

That's where AI starts to pay off in a construction company, and most contractors haven't seen it yet. In AGC's 2026 outlook survey, 61% of contractors said their firms use AI or plan to increase their investment in it, up from 44% the year before. But when I look closer, somebody in estimating has a personal ChatGPT account, somebody in accounting uses a different one, and the office manager uses it for emails. Nobody knows where company data went, and nothing has changed about how the work gets done.

Last week we talked about the first honest WIP report. I promised to explain why your numbers have to be right before AI can help. Let's start with what AI actually looks like in a construction company.

The three levels

  1. Ask. You type a question; it answers. Write this email, summarize this contract, explain this clause. Useful, and where most companies stop.
  2. Assist. It does a real task with your files, and you check the result. Compare these two bid packages. Find the scope gaps in this subcontract. Pull this report out of our accounting software. I use zero brain power on the task itself. I save it for checking what comes back.
  3. Agents. It runs recurring work on a schedule, with a check built in. Process the AP inbox every morning. Run a quality check on every finished bid. Flag every job whose cost to complete didn't change this month.

Most contractors are at level one. The money is at levels two and three.

That demo in the conference room was level two. Nothing about it was exotic: it was the same accounting software the team uses every day, doing the same report, without anyone clicking through it.

One department at a time

The biggest mistake I see is dabbling everywhere. A little in estimating, a little in accounting, a little in HR. Nothing sticks, because nobody owns it.

Pick one department and go all in. For most contractors, I'd start with estimating. It carries the highest risk; a mistake there lives for the life of the job, and the inputs are documents AI reads well.

Here's the easiest first step. When a bid is finished, before it goes out, drop the documents into a company AI project and ask it to check for red flags: missing scope, exclusions that don't match the specs, quantities that look off. It won't catch everything. It will catch things a tired estimator misses at 9 p.m. the night before a bid is due.

Get one department to level two before you start another one.

Clean numbers first

This is the connection to last week. Give AI bad data, and it will process it faster and present it with more confidence.

Point an AI agent at a WIP report that doesn't tie to the balance sheet, and you'll get a beautiful, well-written analysis of the wrong numbers. Garbage in, garbage out, at machine speed.

That's why the numbers come before the AI. In the companies we work with, the order is always the same: honest numbers first, then one department, then a written policy, then the tools. Get the close on a date, get the WIP tying out, get cost to complete updated every month. Then let AI do the pulling, the checking, and the flagging.

The policy before the tools

Before anyone pastes another bid or contract into a chatbot, set five rules:

  • One company account, managed by the company. No personal accounts for company work.
  • The same data and privacy settings for everyone on it.
  • A written list of what never goes in: employee personal information, anything a customer contract says is confidential.
  • Who gets which level of access, and who approves it.
  • One person who owns AI for the company: tracks what's being used, what's working, and what changed.

Five rules on one page. They have to exist before the habits do.

What not to do

  • Don't buy an AI product for the whole company before you've proven one task in one department.
  • Don't let anything go to a customer, a GC, or a supplier without a person reading it first.
  • Don't measure success by how many people logged in. Measure the hours saved on one task and the errors caught.
  • Don't hand it to the most junior person and walk away. The leader of the department has to use it first.

That last one matters most. If the head of estimating doesn't use it, nobody in estimating will. The same goes for the owner. I use these tools every day, and when a leadership team sees that, the conversation changes from whether to how.

Start with one task

Here's how I take a task to level three:

  1. Pick one recurring task with a clear right answer. Processing a vendor invoice is a good one.
  2. Do it once with AI, step by step, and watch what it gets wrong.
  3. Correct it in writing, so the next run starts smarter. When you get a credit memo, this is what it looks like, and this is what you do.
  4. Run it daily with a person checking every result for the first few weeks.
  5. Only then let it run with spot checks, and keep one person accountable for the output.

AI doesn't replace judgment. It changes which skills your people need. The estimator who can check an AI's work is worth more than the one who can only do the takeoff.

Why this matters for owner independence

If you're the only one in the company who knows how AI fits the work, you've just built one more thing that runs through you. When each department head owns their own level-two task, the company gets faster without you in the middle of it. That's owner independence: better tools, owned by the people who use them.

Take this to your leadership meeting on Monday

  1. Who in our company uses AI today, on which account, with what company data?
  2. Which one department goes first, and who owns it?
  3. What's one recurring task we'll take to level two this quarter, and how will we check it?

Next week: overbilling feels like cash. Part of it is work you still owe. How much of your bank balance is actually yours?

Let's go win.
Carlos

P.S. The real question is where else your team still depends on you. Get your Owner Independence Score in 3 minutes. If you'd rather talk it through, book your Owner Independence Review with me. In 30 minutes you'll know what you have to do to reach owner independence.

customer1 png

How Much Does Your Business Still Depend on You?

Take the first step toward true accountability

Get your Owner Independence Score in 3 minutes. It shows where your company still runs through you across Identity, Structure and Systems. Your results are private, delivered instantly, and show the first moves to raise your score.

Get The TeamOS Brief every week.

A short weekly note for construction owners on cash, margins, people and the leadership team. Practical enough to take into your Monday leadership meeting. No fluff, and you can unsubscribe anytime.

SEND ME THE NEXT ISSUE:

TeamOS logo

Legal

TeamOS™ 2026 | All Rights Reserved
Privacy Policy
Terms And Conditions
Cookie Policy