How it works, in one line
In construction, the bottleneck is rarely the building — it’s keeping subs, documents, and deadlines under control across several sites at once, without letting a delay surprise the schedule. The agent doesn’t approve a payment or sign a contract, and never makes an engineering, safety, or structural call: it makes sure every front gets chased, every RFI becomes a task with an owner, every risk surfaces before it stops the site — and it hands you anything that needs judgment, money, or professional liability.Concrete flows
1. Chase subcontractors and suppliers — status and dates
Trigger: an agreed front hasn’t checked in by its promised date, or a supplier’s delivery date is approaching without confirmation. The agent pulls the sub, the front, the site, and the agreed date from the CRM, checks the Company Brain for that supplier’s history — who tends to run late, the real lead time, the right contact — and assembles a clean chase: “confirming the 3rd-floor pour at the Aurora site, scheduled for the 28th — still on track?”. The send goes out by email or WhatsApp with Marcus handling it, and the option to require your approval before each send while you don’t yet trust the tone. The reply comes back as an activity on the card and the front’s stage updates — confirmed, late, rescheduled. The result: you don’t find out the structure stopped when you arrive on site. You find out when the agent chases, days ahead, and it only calls you in if the sub goes silent or gives you a bad date.What to ask and when to chase lives in the Brain, not a fixed script. A
front that blocks the critical path — foundation, structure — is chased
earlier and more firmly than a finish with float. The agent pulls that
cadence from the history and the schedule you’ve already ingested.
2. Keep drawings and documents organized in the right folders
Trigger: a document arrives — a revised drawing, a spec, a permit, a site diary, a material invoice — by email, WhatsApp, or chat. The agent reads the file, works out what it is, and files it in the right folder — by site, by discipline (architecture, structure, plumbing, electrical), by revision — preserving the original and noting the version. In the same move, it ingests the content into the Company Brain, so the next question (“what’s the latest electrical drawing for the Aurora site?”) has an answer right away, with the correct document — not the one from three revisions ago. The win isn’t “a bot that renames files.” It’s that nobody builds off an old drawing because the right version is always in the right folder — and the answer to a site question comes from the real document, not a guess in a WhatsApp group.3. Turn an inbound RFI or request into a tracked task with an owner
Trigger: a request for information arrives — a client RFI, a question from the site foreman, a scope-change request — by email, WhatsApp, or form. The agent reads the message, extracts what matters — which site, which discipline, what’s being asked, the deadline, and who asked — and creates a task on the RFI board with the fields filled in and the original attachment along, routing it to the right owner for that discipline or front. If the RFI matches something already in the Company Brain — a drawing, a spec, a similar prior answer — the agent notes the reference on the card so whoever responds isn’t starting from zero.The RFI that becomes rework almost always sat untouched in an inbox.
Turning each request into a tracked task — with an owner and a deadline,
the moment it arrives — is what stops a question from becoming a wrong
wall, and lets the client see the matter is moving.
4. The routine that flags milestones and deliveries at risk
Trigger: a routine the agent schedules for itself sweeps, every morning, the schedule milestones and open material deliveries across every site. The routine compares milestones and promised dates and separates what’s late or about to be late. For each, the agent raises a proactive notification in your bell, prepares the chase to the sub or supplier (flow 1), and, if the delay threatens a client milestone, flags it on the site board. At end of day, Athena — the org’s chief of staff — pulls together what changed status, what was confirmed, what slipped, and what’s due tomorrow into a short digest, in your bell and on the channel you use. With the Composio integration, that summary can land in the site team’s Slack or become a calendar event — without anyone compiling a spreadsheet by hand.The delay that becomes a liquidated-damages claim was almost always
visible in advance. A routine never has a hectic Monday: it looks at the
milestones every day, at the same time, and turns “nobody saw it” into an
alert in your bell before the problem reaches the site.
What stays human
Where to start
Teach your sites, contacts, and drawings to the Brain
Upload to the Company Brain your active sites, your
subcontractor and supplier contacts with lead times, and the drawings and
project sets you consult every week. That’s where the agent pulls the
right chase, the right version, and the on-the-spot answer from.
Let the agent chase the first batch of fronts
Connect a channel and let the agent follow
the open fronts and material deliveries and chase status. Start with human
approval before each external message and loosen as it proves itself.
Schedule the milestone sweep and the daily digest
Create a routine that sweeps milestones and
deliveries every morning, and another that delivers the sites digest. One
agent, one cadence, one channel — and autonomy grows slowly.
Next steps
Back office
The full office pattern that holds the build together — records,
documents, chasing, and the summary that ties the ends.
Operations
Following a front, deadline, and delivery end to end — of which a build
is a many-fronts-at-once case.
Documents
Drafting and editing specs, reports, and RFI responses — with the right
version always at hand.
Composio
Taking the record and the summary to where the team already works —
Slack, Notion, calendar, and hundreds of apps.