u/EyeonHealth

Your company just landed a big contract. Everyone’s excited. But has anyone stopped to ask whether your operations can actually support the growth?

I’ve watched this same pattern play out in construction for years. A company opens a new division. Hires 20 people. Wins three more bids. Six months later the estimating team is buried. Schedules are slipping. The one ops person holding everything together is working 60 hour weeks and quietly burning out.

Leadership starts blaming the tools. But the tools were never set up to handle this volume in the first place. I watched this cycle repeat for 14 years in homebuilding.
Here’s what I’ve learned from both sides of it. If your business breaks when one person takes a week off, you don’t have a system. You have a person. If your team can’t describe how work moves through your company without saying “well, it depends” or “usually Sarah handles that”… that’s not a process. That’s tribal knowledge.

Before you scale, before you add the next big thing, take a hard look at what’s actually holding things together. Is it a system or is it a person running on caffeine and willpower? And if you’re growing, it’s probably worth asking yourself too.

I sat in a room with a commercial construction company for an hour. One person was managing projects in Smartsheet. Another in Excel. A third just kept it all in their head. Three different systems. Zero overlap. This is the part nobody talks about when they sell you software. You can build the cleanest tool in the world. If your team isn't on the same train, going the same direction, using the same process... it doesn't matter. The technology isn't the hard part anymore. Adoption is. Getting everyone aligned on one process. Communicating why it matters. Connecting the dots between "this is annoying to learn" and "this is what moves us into the next decade." I spent 14 years in homebuilding watching expensive software roll out and then sit unused because nobody liked the complexity of the new system and they weren't properly trained. So they went back to trusty Excel. Right back to the data silos the software was supposed to fix. The companies winning have fewer tools, not more. Everything just talks to each other.

A project coordinator in construction costs $55-65K a year. Most GCs and builders hire one the second projects start slipping through the cracks. Submittals not tracked, RFIs piling up, subs not getting back to you, owners asking for updates you don’t have ready. The instinct is always to hire. But sometimes the problem isn’t headcount. It’s that information is scattered across inboxes, spreadsheets, and text threads with no single place to see where everything stands. I hit that exact wall in my own business. Multiple clients, multiple projects per client, builder updates coming from every direction. I was losing track of things I never lose track of. So I built an AI project coordinator agent instead of posting a job. It pulls from my emails. It pulls from my Airtable project updates. It gives me on-demand status across every client and every builder. And it writes my weekly client update emails based on real data, not whatever I can remember on a Friday afternoon. Total cost: a few focused hours. After 14 years in construction ops at Pulte, I can tell you the pattern. Project’s getting messy? Hire a coordinator. Communication is slipping? Hire an admin. Reporting is behind? Hire an analyst. Some of those roles are real decision-making roles. But a lot of them are just moving information from one place to another. That second kind doesn’t need a person anymore.

Curious how other teams handle this because I’ve seen it become a hidden admin job fast.

Somewhere in your office, a human is manually checking a permit portal.

They log in. They look for a status change. They screenshot it, paste it in a spreadsheet, update the project tracker, and move on to the next one.

Then an hour later, they do it again.

This is not a joke.

Permit status. Inspection scheduling. Utility clearance. Plan check comments.

All of it sitting on city or county portals that someone on your team has to babysit.

14 years at Pulte and I watched this play out across every market. I was the person doing it.

In December, I'd get pulled from the office to the field, refreshing municipal sites to make sure conditions were clearing, updating the tracker, running between inspectors and trades to keep things moving for year-end close.

That was the job.

Here's what most operators don't realize: there's usually a way to make those portals talk directly to your system.

It's called an API.

Think of it like a key card that lets your project tracker walk into the database and grab what it needs without a human typing anything.

When it's set up right, your status updates happen on their own. Your team gets alerts when something changes. Your dashboard reflects reality without anyone checking anything.

If your operations coordinator's job is to be a permit portal refresher, you don't have an ops problem.

You have an automation gap.

Most real estate companies are not behind because they have not heard of AI anymore.

They are behind because the tool is being used like a chatbox instead of being built into how the business runs.

Some teams are using AI to write emails and summarize notes. Useful, but shallow.

Other teams are starting to connect AI to operations handoffs, project documentation, training, and knowledge capture.

Same technology. Completely different operational impact.

The companies that win will not be the ones with the most AI tools. They will be the ones that turn what their best operators know into systems the rest of the team can actually use.

Curious how other teams handle this because I’ve seen it become a hidden admin job fast.

Somewhere in your office, a human is manually checking a permit portal.

They log in. They look for a status change. They screenshot it, paste it in a spreadsheet, update the project tracker, and move on to the next one.

Then an hour later, they do it again.

This is not a joke.

Permit status. Inspection scheduling. Utility clearance. Plan check comments.

All of it sitting on city or county portals that someone on your team has to babysit.

14 years at Pulte and I watched this play out across every market. I was the person doing it.

In December, I'd get pulled from the office to the field, refreshing municipal sites to make sure conditions were clearing, updating the tracker, running between inspectors and trades to keep things moving for year-end close.

That was the job.

Here's what most operators don't realize: there's usually a way to make those portals talk directly to your system.

It's called an API.

Think of it like a key card that lets your project tracker walk into the database and grab what it needs without a human typing anything.

When it's set up right, your status updates happen on their own. Your team gets alerts when something changes. Your dashboard reflects reality without anyone checking anything.

If your operations coordinator's job is to be a permit portal refresher, you don't have an ops problem.

You have an automation gap.

A construction company told me they're spending $8,500 a month on their project management software. Not because it's good. Because it does everything. The problem is they don't need everything. They need to see their jobs, know where their money is, and stop chasing updates from the field. That's it. But the software they're paying six figures a year for has 400 features, and they use maybe 12 of them. The rest just makes it harder to find the 12 that matter. This is the thing nobody talks about in construction tech. The issue isn't that companies won't spend money on software. They're spending plenty. The issue is they bought a Swiss Army knife when they needed a hammer. And now their team hates the tool, half of them have gone back to texting updates and tracking things in their own spreadsheets anyway, and the $102K/year software is basically an expensive filing cabinet. I see this constantly. The companies that actually get their operations running clean aren't the ones with the biggest software budget. They're the ones who stripped it down to exactly what they need and nothing more. Simple systems get used. Complicated ones get worked around.

A contractor posted a photo on Facebook recently.

“Guess how many tons of gravel this is.”

I was curious, so I fed the photos straight into AI and let it do the math.

7 tons.

I won. He tagged me by name in the winner announcement and gave me $200 in credit.

Here’s the part that should get your attention though.

That was two dumpster loads, photographed from the back of a truck, with zero measurements provided.

AI looked at the photos, assessed the volume, factored in the material, and nailed it.

If it can do that from a casual Facebook post, imagine what it can do when you actually give it project data.

Construction estimating is changing.

The teams that figure that out now are going to have a serious advantage over the ones who figure it out later.

Construction companies are spending six figures on software they hate. AI vendors can’t explain what they do in plain English. That gap is showing up over and over again in real conversations with $10M-$100M construction and real estate companies.

The problem is not that operators are anti-technology. It is that most tools either do way too much, do not match how the field actually works, or are explained in language that makes the buyer tune out.

The useful conversations are much more specific: what is breaking in estimating, where the handoff between field and office fails, what people are still tracking in spreadsheets, what software the team is paying for but not actually using.

That is where custom software and AI systems get interesting. Not as hype. Not as a magic fix. As a way to build around how the company already runs.

I've been talking to homebuilders across the country about AI adoption and there are two completely different camps right now.

Camp 1: The company rolls out Copilot, runs formal training, makes it part of onboarding. Everyone gets the same baseline.

Camp 2: The company gives everyone access and says "have at it." No training. No push. If you pick it up, great. If you don't, nobody's checking.

Both camps think their approach is working.

The builders running formal training say adoption is higher and more consistent. The ones letting people figure it out say the people who actually want it are the ones who get the most out of it.

I spent 14 years at Pulte in construction ops. What I'm seeing now from the outside is that the gap between these two camps is getting wider every quarter.

The teams that started early are compounding. The ones still waiting are falling behind in ways they can't see yet.

Which camp is your company in right now? And is it actually working?

“He’s really busy so he forgets a lot. You just have to keep asking him. He’s a good boss though.” I overheard that at a coffee shop recently. A guy training someone on their first day. That’s the onboarding. That’s the system. “Just keep asking.” And the thing is, nobody thinks it’s a problem. That’s just how it works. The boss is busy, things fall through the cracks, so you learn to chase. I spent 14 years in construction. I’ve seen this everywhere. The schedule update that doesn’t go out unless someone calls twice. The approval that sits because the person who owns it has 40 other things on their plate. The request that just… disappears until you follow up again. Nobody’s lazy. The system just doesn’t exist. So the workaround becomes the culture. And the new hire on day one learns that “following up” is actually their most important skill. That’s not operations. That’s survival. The fix isn’t a better boss or a more persistent employee. It’s a system that doesn’t rely on someone’s memory to function. Automated reminders. Task tracking that moves without being chased. Approvals that escalate on their own when they sit too long. I build these systems now. But I only know what to build because I lived inside the chaos for over a decade. If “just keep asking” is part of your training, that’s not a people problem. That’s a systems problem.

When construction and real estate operators evaluate a software partner, the first build should be treated like a test.

Not a pitch deck test. A real operating test.

Do they understand how your business actually runs?
Do they deliver what they said they would?
Are they still around when something breaks at 6am?
Do they ask better questions after seeing the first workflow up close?

The first build proves whether the partner can ship.

The second build is where trust shows up.

By then, they understand the business, the edge cases, the weird handoffs, and the parts of the workflow that never make it into the SOP.

That is usually where the real work starts.

The construction industry has an estimating shortage. That's the story everyone's telling. 300,000 workers short. Can't hire fast enough. Bids slipping through the cracks. Experienced estimators retiring faster than they can be replaced. I spent 14 years inside one of the largest builders in the country. I don't think we have an estimator shortage. I think we have a tooling problem dressed up as a hiring problem. Walk into most estimating departments and watch what the estimators actually do with their day. Measuring takeoffs by hand. Re-entering the same quantities into three different documents. Rebuilding a bid from scratch every time an addendum drops. Hunting through email threads for a subcontractor quote someone sent two weeks ago. None of that requires an estimator. It requires a pulse. The real estimating work, the judgment, the risk evaluation, the scope interpretation, the vendor relationships, that's maybe 30% of the day on a good week. The rest is mechanical work that no one has bothered to automate because "this is how we've always done it." So we hire. And we can't find people. And we blame the labor market. Meanwhile the senior estimator who actually knows how to price a complex job is buried in data entry alongside the new hire who should be learning from them. Hiring doesn't fix that. Nothing fixes that except looking at your workflow honestly and admitting that most of what your estimators do shouldn't be their job in the first place. The shortage is real. The cause is not what you think.