Construction agent
Built for the $10M–$100M contractor — too big to run on the site engineer's memory, too small for a year-long enterprise rollout. Start with one or two read-only use cases and expand once the results have earned it.
Construction · agent spec
Manual pain
SAP knows what you spent. Primavera knows you're late. The BOQ knows what you planned. No system connects them.
Action 01
Early risk detection
Action 02
Cash-flow intelligence
Action 03
Management copilot
Read-only
against your systems of record
SAP · P6 · BOQ
connected in one intelligence layer
100%
of flags carry quoted evidence
Human
sign-off on every action
From documents in to decisions out.
Each agent starts with a small set of operating actions, clear escalation, and visible ownership.
The pipeline
Ingest
Daily site reports, SAP cost exports, Primavera schedule updates and the BOQ land in one place each morning.
Cross-reference
Spend is lined up against progress against plan, item by item, instead of waiting for month-end.
Flag
Divergences surface with the exact source line quoted: the delayed pour, the uninstructed variation, the short delivery.
Brief
The PM and commercial lead get a ranked morning brief: what moved, what it touches, what to do first.
Decide
A human accepts, overrides or escalates each flag. The agent logs the decision and watches the follow-through.
Agent actions
Early risk detection
Site reports, cost ledgers and the schedule are cross-checked daily, so a divergence surfaces the morning it happens — not at month-end.
Cash-flow intelligence
Every flag is traced through to its cash and margin consequence, so risk shows up in the numbers that matter, not just the schedule.
Management copilot
A ranked morning brief gives the PM and commercial lead what moved, what it touches and what to do first, in one screen.
What it reads, does and shows
Reads
- Daily site reports (email, WhatsApp exports, PDF)
- SAP FI/CO and PS cost ledgers
- Primavera P6 schedules and float
- BOQ line items and variation registers
- Supplier POs and delivery notes
Does
- Reconciles claimed progress against certified quantities
- Traces a site event through schedule, cash and margin
- Builds variation candidates from uninstructed work
- Drafts the morning exceptions brief
Shows
- A ranked flag list with the triggering line quoted
- The cash and margin consequence per flag
- A one-screen project pulse for management review
Connects to
A cancelled pour, traced to money
Workflow trace
Thursday's site report notes the concrete pump broke down and the Block C pour was cancelled. This is how the agent walks that single line through the project.
Read
Pour cancelled — pump breakdown; replacement available Sunday.
Schedule
The Block C slab sits on the critical path; a three-day slip consumes the remaining float.
Cash
Twelve carpenters idle until the pour; formwork crew cost accrues with no earned value.
Procurement
The Sunday pump slot clashes with the rebar balance delivery — same crane window.
Action
Flagged high. Suggested: confirm the pump slot, resequence Block D formwork, notify the client engineer today.
What changes once the agent runs it
Finding the problem
Month-end reconciliation, weeks after the event
Next-morning flag with the source line quoted
Variations
Uninstructed work discovered at final account
Variation candidates raised while the crew is still on site
Management view
Chasing three systems and a WhatsApp thread
One ranked brief, evidence attached
Connect the systems once, and these come free.
Not shipped today — the natural next step once the spine is in place. Same reasoning, applied to more decisions.
01
BOQ vs. reality
Planned 10,000 tiles, trending to 12,000 — caught while there's still time to file the variation.
02
Change-impact analysis
A drawing revision or supplier delay traced through quantities, procurement, schedule, billing and cash.
03
Procurement intelligence
Required-on-site dates vs. the real supply path — a PO is not a delivery.
04
Resource visibility
Idle equipment and crew conflicts across sites, with feasibility checked before anything moves.
05
Cross-project learning
Every job teaches the system your real productivity rates, supplier reliability and client payment patterns.
Production means the team can trust it.
The system is designed with human review, evaluation, auditability, permissions, and monitoring before expansion.
Human-in-the-loop stays visible.
The agent handles the repetitive path. People still own approvals, exceptions, and high-risk decisions.
Read-only — never writes to your systems
Runs in your private cloud
Deterministic math, not model guesses
Sources, freshness and confidence on every answer
Proof signal
Concluding an implementation with Vel Amrith, a construction and facility-management company in Riyadh, and in discussions with a second, larger Gulf group.
Start the construction workflow audit.
Bring one workflow your team still handles manually.