The trucks are booked for six the next morning, and at half past four the site foreman is standing on the formwork with a drawing in each hand that don’t agree. The structural set has the suspended slab poured flat through the wet areas. The architect’s revision, issued a fortnight ago, shows a 60mm set-down for the bathroom falls. He raised an RFI about it on Monday. It’s Thursday afternoon. Nobody has answered.

So he does the only thing a foreman can do at half past four with a pour booked and a crew turning up at six. He backs his own reading of it, decides to pour flat and pick up the falls later with a topping screed, and gets the boxing signed off for the morning. The trucks come. The slab goes down. It’s a clean pour, and he’s proud of it.

Three weeks later the answer to his RFI lands in his inbox. The set-down was real. A screed won’t give enough fall under the finished floor level, the waterproofing detail won’t certify, and the only way through is a saw, a jackhammer and two days that were never in the program. Demolition and redo, on a slab that was structurally perfect.

The gap he built around

That’s the whole story, and every builder reading this has lived a version of it. The failure wasn’t the pour, which was good work. It was the four days an honest question sat in a system while a crew, quite reasonably, kept moving around it. The workaround became the rework. The gap became the wall that had to come down.

And it is a gap, not a person’s fault. The foreman did his job. The engineer, buried under a dozen other jobs, hadn’t got to it. Nobody stands in the space between the question and the answer, because that space isn’t staffed by anyone. It’s the seam where site meets office, and things fall down seams.

The cost of a question left open

The single open RFI is a small thing. In the aggregate it stops being small. On the Navigant Construction Forum’s study of 1,362 projects and more than a million RFIs, the median one takes about 9.7 days to close, costs near US$1,080 to review and answer, and nearly 22% never get a response at all. Not answered late. Never answered. The crew builds around them and hopes.

The bill for that arrives downstream as rework. FMI and PlanGrid, in their Construction Disconnected study, traced about 48% of all rework to poor project data and miscommunication — bad handoffs, not bad tradesmen — and put rework at roughly 5 to 10% of total project cost. On a $5 million job that is a quarter to half a million dollars of margin, spent twice on work you already did once. That’s directional arithmetic off the 5–10% range, not a quote for your job, but you know it’s about right.

The leak is in the handoffs

Here is the thing worth sitting with. The money doesn’t leak on the slab. It leaks in the space between site and office, wherever information has to change hands and doesn’t quite make it. The RFI that sits for a week and a half. The variation under-claimed because the instruction to move the wall was a text on someone’s phone that never reached a claim. The tender read at midnight because that was the only quiet hour left.

None of that is one person being slow. It’s the structure of the work. Deloitte Access Economics, in a 2025 study commissioned by Autodesk across the Asia-Pacific, found the median construction business runs eleven separate data environments — eleven places the truth of a job might live — and estimated that moving to a single one could hand back around 10.5 hours a week of skilled people re-keying and reconciling, just to carry context between systems that won’t talk to each other.

And you’re doing it short-handed. Master Builders Australia reported in 2024 that 85% of builders struggle to find qualified workers, with the sector needing something like 130,000 more of them. The hours lost in the seams are the ones you can least afford, spent by people you can least afford to have doing clerical detective work.

Why the fix the vendors sell is the wrong one

If you’ve sat through an AI demo this year, it was probably an estimating or takeoff tool: plans in, quantities out, measured off the drawing by a model. The tools are genuinely clever. But that clever middle of your software stack is largely closed. Buildxact, Cubit, Togal, Bluebeam Revu and RIB CostX mostly have no public provider API. They read from your ledger or your project-management platform, but an outside system can’t reliably read or write them back. So the AI everyone is demoing lives in the one part of your stack an agent can’t actually reach.

The reachable ground is at the two ends. At one end, the project-management platforms your RFIs and variations already flow through — Procore, Autodesk Construction Cloud, Aconex — expose real provider APIs, OAuth-secured, with create-and-update webhooks over RFIs, submittals and financials. The trades job-management tools (simPRO, ServiceM8, AroFlo, Fergus) sit there too. At the other end, the ledgers and the document substrate the claim settles into (Xero, MYOB, QuickBooks, Sage Intacct, and the Microsoft 365 your team already lives in) are mature systems an assistant can read and write.

One correction worth making out loud, because it gets claimed the other way. Buildertrend, despite the “we have an API” line, has no official provider API. Its read-and-write only exists through an unofficial, reverse-engineered adapter, which means it’s really closed, and we won’t tell you we integrate with it when we can’t do so cleanly. The same honesty applies to the vendors’ own AI, from Procore’s agents to Autodesk’s Construction IQ to Sage’s Copilot. It’s all in-product only, bundled assistants you can’t call from outside. The reasoning layer has to come from somewhere an agent can reach.

Which reframes the whole question. Whether AI pays back for your business is decided less by how clever the model is than by which parts of your flow run through a system an agent can reach. The RFI is the good news here, because it already runs through Procore, or ACC, or Aconex. It’s standing on reachable ground.

What actually changes

Now put the reachable tools on that half-past-four moment.

When the drawings disagree, an assistant reads both, pulls the relevant spec clause and the earlier RFIs on the same detail, and drafts the RFI — the question sharpened, the clash quoted, the drawing references attached. It routes that to the right consultant instead of the general inbox. Then it does the unglamorous part that actually saves the slab: it chases. It tracks the clock against the pour date, nudges when the answer is overdue, and escalates before the trucks are booked, not three weeks after. When the engineer replies, it files the response against the drawing revision it cited.

What it never does is answer the question. The engineer signs off the answer — always. The set-down is a structural and certification call, and no model gets to make it or to quietly be right about it. The AI makes sure the question is asked well, routed correctly, and chased hard, so the answer arrives before the concrete does. That is the entire trick, and the human stays exactly where they belong.

The same mechanism works down the seam. A Variation Claim Builder captures the instruction the moment it lands, so the wall you were told to move becomes a drafted claim, not an under-claimed text. A Tender Compliance Matrix Builder reads the tender so the midnight hour isn’t spent hunting clauses. An RFI Triage Desk keeps every open question visible against its deadline instead of scattered across three inboxes.

Does it work? The honest evidence is other people’s. Coastal Construction, a US general contractor, cut estimators’ manual takeoff from about half the week to roughly a tenth, with an independent University of Kansas study finding up to 76% time savings. Buffalo Construction connected AI over their existing Procore and Sage and halved the effort on proposals across around eighty projects a year. Lallier, a multi-entity builder, took 90% off intercompany month-end reconciliation. Treat all of it as directional: mostly vendor-reported, none of it ours, and none of it Australian yet.

The honest ledger

Two things I won’t dress up. First, RMAI is new to construction, and we have no named Australian client result to show you. The numbers above are third-party benchmarks, mostly vendor-reported, and we label them directional on purpose. What transfers between one builder and the next is the mechanism, not the percentage.

Second, the payback is conditional. You’ll see an ROI sum floating around — something like 200 documents a year, twenty minutes each, at $85 an hour, near $68,000 saved. That’s illustrative, off arbitrary defaults, and it’s gross. Hours returned under a fixed wage bill are a soft saving until they turn into something real: a bid you won because you had time to chase it, an FTE you didn’t have to hire, claim leakage you stopped losing. And it only banks if you redesign the workflow around the tool, not bolt the tool beside the old one. A build usually ships in three to six weeks in the $10k–$60k band, one useful tool from around $10,000, and it starts with a free 30-minute discovery call, where we walk one real path on your jobs and name the highest-value fix; any build is quoted fixed-scope after that, on your numbers. Net of the build, the sums point to payback in roughly two to eleven months. Directional, not a quote.

And the guardrails are real. Sign-off is an enforced step the system requires, not a courtesy: a named person can reject any draft, and every decision is logged against the exact drawing revision it cited. Point AI at a folder of duplicate, unmarked drawing revisions and it will amplify the mess, which is why the readiness look comes first.

Where to start

You don’t need a transformation programme to test whether this is real. You need one honest look at where your RFIs and variations actually go after they’re raised, and how long the ones that matter sit before someone with an answer sees them.

Two ways in, both low-risk:

• Read the map first. We’ve written a plain-English brief on the Australian construction software landscape — which of your systems an agent can actually reach, by what mechanism, and what “closed” really costs you. → https://realmindsai.com.au/guides/construction/
• Book a free 30-minute discovery call. We’ll take one real path — an RFI to its answer, or a variation to its claim — name the API tier underneath it, and show you the highest-value place to close the gap, before anyone promises a build. → https://outlook.office.com/book/[email protected]/?ismsaljsauthenabled

There’s an RFI open right now, somewhere on one of your jobs, with a pour date quietly bearing down on it. The only question worth asking is whether anything in your systems is going to make sure it gets answered before the concrete does.