Most construction AI answers questions. These take the next step. They read your jobs, draft the change order, chase the RFI, and stop for a person on anything that costs money.
The problem was never the AI. It was that nothing ever gave it permission to finish.
Scoped by role and enforced where the data lives, not by instructions in a prompt. Nothing typed into a chat box widens it.
The reason most contractors have not put AI near a live job is that nobody could answer what happens when it is wrong. Three answers, built into the platform rather than written into a prompt.
An agent inherits the permissions of the person it works for. A foreman's agent cannot reach the financial actions, because the foreman cannot. The scope is enforced where the data lives, so no instruction typed into a chat box can widen it.
Every action in the registry is marked either automatic or always-human, and the ones that move money or go to a customer are always-human. Looking up a job or assigning a contractor runs on its own. Sending a packet for approval, submitting a pay application or releasing a payment waits in a queue for a person. That split ships with the platform today and is the same for every customer: changing it for your organization is part of an agent build, not a switch in your settings.
Each tool the agent calls is recorded with what it did, which job it touched and why it chose that step. When a GC asks who approved a change in March, the answer is a query, not a memory.
An agent that goes live on day one is a demo. An agent that spent three weeks proving it agrees with your best PM is a system.
We start from a decision somebody makes the same way every week: which jobs slipped, which RFIs are past due, which close-outs are missing a photo. One decision is testable. 'Automate project management' is not.
The agent works on your jobs, your customers and your documents, in the platform, with your field names. No separate knowledge base to maintain and no export that goes stale the day after it runs.
We agree what it may do on its own, what needs a signature, and who it answers for. That gets written as permissions, not as instructions in a prompt, so it holds when the model changes.
It runs alongside your team first, choosing what it would have done while a person still does the work. You compare the two for a few weeks. The agent goes live on the day its answers stop surprising you, and not before.
Worth being straight about, because the gap between an AI roadmap and an AI product is where most of this industry’s money goes.
The assistant is included on Professional and Enterprise. See what each plan includes.
We are building these with a small number of contractors on real jobs. If one of them is the decision eating your week, that is the conversation to have.
Jobs, schedule, documents, approvals and billing in one system your crews actually open.
Agents built on your process, scoped to a role, and stopped for a human wherever you say so.
The team that builds the platform, putting AI into your operation and proving it moved a number.
Thirty minutes. We will tell you whether an agent is the right answer, and say so plainly when it is not.
