Agentic: What It Means, and What It Means for Construction

Picture your IT team’s face when you tell them you want to give ChatGPT full access to your company’s entire OneDrive. Their eyes are screaming what their mouth is too professional to say. That image is the whole problem with “agentic AI” in construction right now. Every vendor is using the word. Nobody is using it the same way. And the ones shouting loudest usually mean “we pointed a chatbot at your files and hoped for the best.”

We know this is exhausting. Every quarter brings a new pitch deck, a new “agentic” claim, and a new vendor who cannot explain what their tool actually does when you push them on it. You sit through the demo, nod politely, and walk out knowing less than when you came in. That is not your fault. That is the market.

This post is the cheat sheet: a working definition of what an agent actually is, the tradeoff every general contractor needs to understand before signing a contract, and three options for what to do about it. One of those options is the only defensible one. The other two put you in a bad spot. For the wider view on where AI is actually earning its keep in preconstruction, start with our no-BS guide for GCs in 2026.

---

What Agentic AI Actually Means

An AI agent is an AI system with access to tools, running in a loop, trying approaches until it reaches the right result.

That is the whole definition. Strip the marketing off and that is what is under the hood. Anthropic, the company behind Claude, describes agents as “systems where LLMs dynamically direct their own processes and tool usage, maintaining control over how they accomplish tasks” (source). Same idea, more words.

Think of it like a new hire. You give them a laptop, access to a few systems, a task, and a deadline. They try something. It does not work. They try something else. Eventually they come back with an answer. The tools they have access to, and the limits you put on those tools, decide whether that hire is useful or a liability. Agents work the same way.

Some tools just read things: pull a document from a knowledge base, look up a number, check a history. Other tools take action: send an email, update a schedule, move money. The gap between reading and doing is where every serious design decision lives.

Here is the part vendors do not want you to focus on. The model itself is mostly a commodity. The real product is the set of tools the agent can use and how those tools are scoped. That is the differentiator.

Two agents can run on the exact same underlying model and produce wildly different results because one has access to clean, structured project data and the other is rummaging through a shared drive named “Final_FINAL_v3” (every GC has one; some have seventeen). McKinsey estimates AI could boost construction productivity by up to 20 percent (source), but that number assumes the AI can actually find and trust the data it needs. Garbage in, confident garbage out.

When you evaluate a vendor, stop asking which model they use. Start asking: what tools does the agent have, what data can it read, what actions can it take, and who signed off on those decisions.

---

Agentic AI vs. Generative AI

Agentic AI differs from generative AI in that generative AI produces content when asked, while agentic AI decides what to do and does it. Generative AI is a ghostwriter: you ask, it writes. Agentic AI is a project coordinator: you describe the outcome, it figures out the steps.

In preconstruction terms, generative AI drafts a cover letter for a bid. Agentic AI reads the request for proposal (RFP), checks your historical win rate with that owner, pulls three comparable projects from the past two years, flags scope gaps, and drafts the cover letter with all of that context baked in. Same final artifact. Completely different amount of work delegated.

---

The Utility and Security Tradeoff

Every agent design sits on the same dial a bank uses when deciding how much a teller can do without a manager’s signature. Small withdrawal, teller handles it. Large wire transfer, two people and a phone call. The dial is not a bug. It is the entire job.

On one end is utility: give the agent everything, let it roam, let it act. On the other end is security: lock it down, limit access, require approvals for everything.

Push the dial all the way to utility and you get guaranteed bad outcomes. In October 2025, a researcher demonstrated how Claude agents could be tricked into exfiltrating private data from users who had handed over too much access (reported by The Register). Anthropic’s own research is blunt: “every webpage an agent visits is a potential vector for attack” (source). The specific recipe has a name: the lethal trifecta of access to private data, exposure to untrusted content, and the ability to act.

Push the dial all the way to security and you get shelfware. A tool so locked down it cannot do anything useful. Your team stops opening it by week three. You keep paying for it until renewal (somewhere, a line item nobody wants to defend).

In construction, the primary agent security risk is data exposure: agents need access to project files, pricing, and subcontractor data to be useful, so scope and audit controls matter more than model choice. The bar is 80 percent of the utility, 100 percent of the security. Anything less is shelfware.

Strip it down and a GC has three moves:

• Partner with a vendor who has already solved scope and security at scale. You get 80 percent of the utility at 100 percent of the security. This is the defensible option.
• Do nothing. Zero utility, zero risk, and your competitors eat your lunch over the next 24 months.
• Give too much access to a tool that still does not work. You get the breach and the shelfware. The worst of both.

Two of these options end badly. One of them is how you stay in business. The choice is not really a choice.

---

What Good Looks Like: Scope, Plan, Approve, Apply

This is where Kit comes in. Kit is Buildr’s preconstruction agent, and it is built exactly around the tradeoff above.

Scope first. Kit is scoped to Buildr data only. Not the open internet. Not your email. Not OneDrive. The things that make IT nervous are off the table by design, not by policy.

Then the workflow. Kit uses a Plan, Approve, Apply sequence: the agent drafts a plan for how it will handle the task, a human reviews and approves the plan, and only then does the agent take action. Human review is not a footnote buried in a security whitepaper. It is how the product works.

Inside that scope, Kit reads RFPs, surfaces relationship history with an owner, builds preliminary cost models, and drafts proposals. The agent does the fetching and the drafting. The estimator does the judging and the approving. Tools plus guardrails plus a human with final say.

That is what 80 and 100 looks like in practice. Read more about how it fits into the Buildr Platform.

If you are running preconstruction at a mid-size commercial GC, the next 18 months of vendor conversations will be noisy. Everyone will claim “agentic.” Most of them will be selling you a chatbot with a new label. A few will be selling you a breach waiting to happen. Walk in with the definition. Ask what the tools are. Ask what is scoped out. Ask where the human signs off. If the answers are vague, the product is vague. If the answers are specific, you have something worth testing. Want to see what that looks like for your team? Schedule a demo.