I Built a Team of AI Agents. Here's What They Taught Me About Construction.

Yesterday I showed my friend Marcus something I’ve been building.

Not a building — though that’s still my day job.

I showed him my Mission Control.

He stared at the screen for a minute and said,
“Wait… this is all running on your computers?”

Yeah. It is.

But here’s the important part:

This didn’t start as some massive AI lab.

It started because I was tired.

The Friction We All Feel

If you’re in construction, you know the grind.

RFIs. Submittals. Email chains. Owner questions. Coordination meetings.
You spend your day reacting — and somehow you’re also supposed to think strategically.

Most mornings feel like you’re behind before you even start.

I wasn’t burned out on construction.
I was burned out on friction.

So I did what builders do.

I started building a system.

The First Automation Changed Everything

Here’s what I learned early:

If a simple AI tool can do 80% of a task, let it do 100% of the first pass.

That’s the rule.

I started small.

An email sorter.
It reads overnight messages and flags what actually needs my attention.

It’s not perfect.

But when I sit down with my coffee, I’m not staring at chaos.
I’m starting at clarity.

That one shift saved maybe 15–20 minutes a day.

That doesn’t sound like much.

Until you multiply it by 250 working days.

Now we’re talking about weeks of life back.

Meet the “Team”

Over time, I added more tools.

• One summarizes long documents before I read them.
• One drafts first passes of reports or posts.
• One scans research and pulls out key insights.
• One helps build automations so I don’t have to write code myself.

None of them are geniuses.

All of them are fast.

And together, they function like a support team — handling first passes, reducing noise, organizing information.

Not replacing me.
Supporting me.

Just like a well-run jobsite.

What Marcus Really Saw

When I walked Marcus through the system, here’s what he actually saw:

• A dashboard showing what’s in progress and what’s done — just like a project board.
• A searchable memory of everything I’ve written, researched, or documented — no more digging through folders.
• A daily morning brief generated automatically: calendar, tasks, important emails.
• A video workflow that edits while I move on to other work.
• A content engine that drafts ideas so I can focus on refining them.

After a few minutes he said:

“This isn’t about AI. This is about systems.”

Exactly.

Builders Already Know How To Do This

This is what I want the construction industry to hear:

You already have the skillset to build this.

We take complex projects.
We break them into parts.
We assign the right people to the right roles.
We sequence.
We inspect.
We adjust.

That’s systems thinking.

AI is just another subcontractor.

You don’t hand them the whole project.

You give them scoped work.

You inspect the output.

You refine the process.

Sprint by sprint, it improves.

The Skeptic’s Question

“Felipe, this sounds cool, but I’m not technical.”

Good.

You don’t need to be.

You didn’t start your career knowing scheduling software.
You didn’t start knowing BIM.
You didn’t start knowing pull planning.

You learned because the tools made you better.

This is the same.

Start with one friction point.

Not ten.

One.

If you want a place to begin, here’s my recommendation:

Start with meeting summaries.

Every week, construction teams sit in coordination meetings, OAC meetings, pull planning sessions — and someone has to turn 90 minutes of conversation into clean action items.

It’s slow.
It’s inconsistent.
And it’s a huge source of frustration.

Let AI do the first pass.

• Record the meeting.
• Transcribe it.
• Have AI extract decisions made.
• Identify action items.
• Assign responsible parties.
• Capture due dates.

Then you review and refine.

Instead of starting from a blank page, you’re starting at 80%.

That alone can save hours a week.

Why This Actually Matters

Efficiency isn’t about squeezing more output.

It’s about reclaiming time.

Construction takes a lot from us — long hours, mental load, constant responsibility.

If a simple meeting-summary workflow gives you back two hours a week…

That’s real.

That’s margin.

That’s energy.

This isn’t a tech flex.

It’s about building systems that support the people doing the work.

What’s Next

Inside the EBFC Scrum Community, we’re starting with practical applications like this:

• Meeting summaries
• Daily briefs
• RFI first-pass reviews
• Schedule narrative drafts

Nothing fancy.

Just friction reduction.

Built the way we build projects:
Incrementally.
With inspection.
With adaptation.

If this sparked even a small “what if…” in you —

Start with your next meeting.

And if you want guidance building from there —
That’s what we’re doing inside the community.

Let’s build it.