Construction and contractors on GO Pilot GO

RFI nudges, submittal tracking, daily-log drafts, change-order follow-ups, subcontractor coordination, and weekly owner reports for GCs and trade contractors.

The problem

On a construction job, money leaks through paperwork: RFIs that sit unanswered, submittals nobody reviewed, change orders that never get signed, and daily logs that get written from memory at 9pm. An agent fleet treats the paperwork as a queue and watches it every day, so the super can stay on the deck and the PM can stay on the schedule.

Agents in the fleet

RFI watcher. Reads the RFI log every morning. Anything past its required-by date or sitting open for more than five business days gets a nudge drafted to the responsible party, copied to the PM, with the original question and what is blocked downstream.

Utterance"Every morning at 7am, scan the RFI log. For anything open more than five business days, draft a nudge to the assigned party copying the PM."

Submittal tracker. Watches the submittal schedule against the lead-time matrix. Flags any submittal whose required-on-site date is within its lead time and not yet approved. Drafts a reminder to the sub and a heads-up to the super.

Daily-log drafter. At 4pm, drafts the day's log from the field-app entries, weather data, manpower counts, and any flagged delays. Super reviews and signs in the morning instead of writing from scratch at 9pm.

Change-order chaser. Tracks every change order from issued to signed. Anything unsigned past 7 days gets a polite nudge to the owner's PM with the dollar amount and schedule impact called out.

Sub coordination agent. Two days before a trade is scheduled on site, confirms manpower, materials on the way, and any prerequisite work complete. Drafts a confirm-or-reschedule message to the sub's coordinator.

Weekly owner report. Friday 4pm, drafts a one-page owner report: percent complete, two-week look-ahead, open RFIs and change orders, schedule variance, safety incidents. PM edits the narrative paragraph and sends.

Workflow

  1. Project data lives in Procore, Buildertrend, CMiC, or a Google Sheet exported nightly.
  2. RFI and submittal agents run at 7am, drafts to the PM inbox.
  3. Daily-log drafter runs at 4pm, super reviews next morning.
  4. Change-order chaser runs daily at noon.
  5. Sub coordination fires two days before each trade window, on schedule webhook.
  6. Owner report drafts Friday 4pm.

Setup checklist

  • Connect Gmail, Google Sheets, and your construction-management tool (Procore, Buildertrend) via guided OAuth or scheduled CSV export.
  • Attach a markdown memory file with the project name, owner, GC, key subs, and the lead-time matrix per material.
  • Per-project memory: a 300-word project brief so multi-project PMs get the right context per job.
  • Approval gating on every outbound to owner or sub. Field-internal nudges can auto-send.

Costs and capacity

CostA single mid-size job (5M to 30M) typically runs ~3M tokens/mo. Starter ($197/mo or $158/mo annual) covers a small GC. A multi-job PM running 4 plus active projects moves to Pro ($497/mo or $397/mo annual) for the seat count and per-project memory budget.

Guardrails

  • Agents never commit to schedule changes or pricing. Drafts and nudges only, human signs.
  • Daily-log drafts cite the source field entry for every claim. No fabricated counts.
  • Safety incidents auto-route to the super and PM immediately, never delayed into a digest.
  • All owner communication requires human approval before send.

Pairs well with

Stack with the project management fleet for cross-job status, the finance ops fleet for pay-app and AR follow-up, and the service trades fleet if you also run warranty service work.