Runs on the stack you already have. No migration, no new place for the team to live.
AroFlo 
BuildXact
Microsoft 365
Google Workspace
Xero
Most construction AI reads documents you remember to upload, or lives inside a system you already have to keep up to date. Rory is an AI administrator: it watches what comes at you, works out what needs you, spots the money leaking, and does the admin. Every send waits for your okay.
Runs on the stack you already have. No migration, no new place for the team to live.
AroFlo BuildXact
Microsoft 365
Google Workspace
Xero
A contracts administrator watches the commercial side of a job: variations, RFIs, claims, correspondence, evidence, close-out. Most small and mid-size builders never get to hire one, so the owner does it at 9pm, badly, and money walks out the door in the gaps.
An AI administrator is that job as software. It does the watching and the paperwork continuously, across every job at once, and it leaves the decisions with you. It is not a chatbot you have to remember to ask, and it is not a system of record you have to feed. It sits on top of the tools you already run and does the work around them.
Six things, running continuously, on every job you have open. See each one in the product, or read the moments it earns its keep.
Email threads, drawing revisions, specs, site photos, texts. Not a folder you remember to upload. The inbox is where the commercial life of a job really happens, so that is where it watches.
Most of what lands is for information. A little of it is waiting on you and quietly holding up the job. It sorts one from the other and leads with where you are the blocker.
A change agreed in a thread that never made it into the job system. A new callout on rev C that nobody priced. A claim that went out short. It ties each one to a job and a dollar figure.
It learns how fast each contact actually replies, the council, the engineer, the subbie, then chases against their own baseline instead of a fixed window.
Drafts the reply, writes up the variation, reconciles the record, assembles the close-out list. The work that eats your evenings, done before you sit down.
Every outbound message and every write to your job system waits for one tap from you. There is no autonomous mode to switch on. That is the design, not a setting.
Money at risk on top, because that is the part that does not come back. Every item carries the job it belongs to and the reason it surfaced.
And the jobs view, where healthy jobs stay quiet and the ones bleeding margin get taller.
| Project | Phase | Status | At risk | Open loops | Why | Updated |
|---|---|---|---|---|---|---|
| Kitchen Retrofit Ellis St | On site | At risk | $4,200 | 2 open | Steel variation not in AroFlo | 25m |
| Office Fit-out Kennedy Builders | Quote | Watch | $3,800 | 1 open | Sparky quiet, 2 days over usual | 4h |
| Henderson Slab Pacific Civil | Invoiced | On track | — | None | Nothing waiting | 2d |
| Parkside Reno Doyle Group | Won | On track | — | None | Nothing waiting | 3d |
An assistant waits for you to ask. You will forget to ask, on the day it matters most. Rory watches without being asked, and it knows a variation from a newsletter because it is built around construction rather than general office work.
AroFlo, Buildxact or Procore hold the record. Rory never becomes it. It reads what they hold, finds the gaps between them and reality, and writes back with your approval. If you leave, your record is untouched.
There is no setting that lets it act on its own. Every email, every variation, every write is a draft until you tap approve, and every action lands in an audit log with the source it came from attached.
Connect email, a document store, and your job system. It starts surfacing work on the first sync. Days, not months, and nobody has to learn a new place to live.
The parts that eat the most time, yes. Reading what lands in your inbox, working out what needs a person, spotting a change that was agreed but never logged, drafting the reply, chasing the trade who went quiet, and reconciling the record. What it should not do is decide on your behalf. Rory drafts and waits. Every outbound message and every write to your job system sits behind one tap from you.
A contracts administrator watches the commercial side of a job: variations, RFIs, claims, correspondence, evidence, closeout. Most small and mid-size builders never get to hire one, so the owner does it at night. An AI contracts administrator is that job as software. It does the watching and the paperwork continuously, and leaves the decisions with you.
Only if it cannot. Rory has no send button of its own. It writes the draft, shows you the reasoning and the source it came from, and waits for approval. Nothing is sent, updated or logged until you tap approve, and every action is written to an audit log with its provenance attached.
Yes. Rory reads and writes to the stack you already run: AroFlo, Buildxact, Microsoft 365, Google Workspace, Xero. It is not a replacement for your job system and never becomes your system of record. There is nothing to migrate.
No. Rory learns your stages, your people and your job names, then works inside them. Connect email, a document store and your job system, and it starts surfacing work on the first sync. Days, not months.
An assistant waits for you to ask. Rory watches without being asked, and it knows the difference between a variation and a newsletter because it is built around construction, not around general office work. It ties a change to a job and a dollar figure, keeps the evidence, chases the silence, and reconciles the record. You are not pasting emails into a blank chat and re-explaining your business every time.
Book a demo and we'll point it at a real job of yours, then show you what it found that nobody logged. No deck, no commitment.
No commitment. No sales deck. Just a conversation about your admin.