Is AI coming for your job? An honest answer from someone building it

Every time I post about AI in construction, somebody tells me I’m helping build the thing that puts them out of work.

I want to take that seriously rather than wave it off, because in plenty of industries the fear is well founded. If your job is producing routine documents, or answering the same customer questions all day, or moving numbers between spreadsheets, the honest answer is that a lot of that work is going to get automated and the people doing it should be planning for that.

So here’s my actual view on construction, from the position of someone who’s both run the work and is now building the tools.

What the job actually is

Strip away the paperwork and a contractor’s job is three things.

You build. You hang the door, you frame the wall, you pour the slab, you run the wire. Physical work in a physical space that’s different every single day.

You judge. You look at a wall and know what’s behind it. You look at a client and know whether they’ll pay on time. You look at a schedule and know which trade is going to slip. You read a room.

You tell the truth. A homeowner has a budget and a Pinterest board and they don’t match. Someone has to say so. Someone has to explain what the money actually buys, and what the shortcut will cost them in five years.

None of that is going anywhere. I say that with some confidence, because I’ve spent a year trying to build software that helps with construction, and the closer you get to any of those three things, the more obvious it is that a computer can’t do them. Nothing I build can hang a door. Nothing I build can read a room. Nothing I build can look a homeowner in the eye and tell them the truth about their kitchen.

Those things are the job. They were always the job.

What’s actually at risk

What is genuinely at risk is the counting.

The two hours at the kitchen table adding up studs. The takeoff that ate your Sunday. The twenty small line items you have to remember every single time because they aren’t on the drawings. The pricing lookup. The re-typing of a material list into a quote.

Nobody has ever been proud of that part. Nobody bills for it. It’s the tax you pay for being allowed to do the real work, and it’s paid at 10pm when you’re already tired and most likely to make a mistake.

That’s the work I’m trying to automate. Not because I want to replace anyone. Because I’ve done that work and I know exactly how little it has to do with being good at construction.

The person who should actually worry

I’ll be direct about this, because I think a vague answer is worse than an uncomfortable one.

There is a group of people whose entire value is doing arithmetic slowly. The estimator whose skill is turning a plan set into a material list, and nothing more. The back-office role that exists only to move information from one form into another. If that’s the whole job, the job is going to change, and the person in it should be thinking about what else they bring.

But that’s a small group, and it isn’t most of you. Most contractors I know are doing the arithmetic because there’s nobody else to do it, not because it’s their skill. Take it away and what’s left is the part they’re actually good at and actually get paid for.

What I’d tell my own crew

If I were still running programs and someone on my team asked whether they should be worried, here’s what I’d say.

Learn the tools, because the contractor who quotes the same day is going to beat the one who quotes in three, and that gap is only going to widen.

Don’t trust the tools, because a number that arrives with confidence is more dangerous than one that arrives with a shrug. Check the reasoning. Override what’s wrong. Any tool that asks you to stop checking is selling you something worse than doing it by hand.

And double down on the judgment. The better the machines get at counting, the more valuable the person who can look at the count and say ‘that’s wrong, and here’s why’ becomes. That person has never been more important.

The version I might be missing

I’d rather say all this plainly than pretend the question isn’t fair. And I’m genuinely open to being wrong about it. If you’re in this industry and you read the situation differently, I’d like to hear the version I’m not seeing. Email me at info@dvcapps.ai. The arguments that have most improved what we build have come from people who thought I was wrong.