AI Agents for Construction: Subcontractor Onboarding, Compliance, Vendor Risk

A general contractor running a dozen active sites does not have a code problem, it has a paperwork problem wearing a hard hat. Every new subcontractor needs an insurance certificate verified, a W-9 on file, a signed lien waiver template, a safety orientation logged, and a rate confirmed against the master service agreement, and that intake has to happen correctly forty or fifty times a quarter without anyone dropping a step. The compliance folder for each site grows faster than the ops team can file it: certified payroll reports, updated certs of insurance that expire mid-project, change order documentation, incident reports. And underneath all of it sits the vendor risk nobody notices until it is too late, the electrical sub who has been late on the last three jobs, the framer whose insurance lapsed two weeks ago and nobody caught it, the supplier whose last four deliveries slipped and whose fifth is due the week the crew shows up. None of this is a coding problem. It is an operations problem, and it is exactly the kind of work that stalls a site not because the concrete didn't get poured, but because a paperwork gap froze the crew that was supposed to pour it.

Why a chatbot and an autocomplete tool both miss this work

Ask ChatGPT or Claude.ai to build a subcontractor onboarding checklist and you get a checklist. It reads fine. It has the right vocabulary, insurance cert, W-9, lien waiver, safety orientation. What it does not have is your company's actual master service agreement language, your actual insurance minimums, your actual list of which twelve sites are active right now and which subs are already on which of them. It has no memory of the framer whose cert lapsed last month, because it has no access to your vendor records at all. You get a generic template, you paste it into a doc, and three weeks later you are back to manually cross-referencing spreadsheets because the checklist never became a process, it stayed a document. A generalist chatbot answers the question you asked. It does not own the ongoing operational cadence of tracking forty active vendor relationships against a compliance calendar that never stops moving.

Cursor and GitHub Copilot solve an entirely different problem and were never built for this one. They are autocomplete layers for people writing code in an editor. A construction ops director is not writing code, they are managing vendor files, compliance calendars, and process documentation, none of which lives in a source file that an autocomplete tool can see. Even for the engineers who build a company's internal vendor portal or site dashboard, Cursor will happily suggest the next line of a form component, but it has no concept of what a lien waiver deadline is, no model of vendor risk, and no mechanism for producing a documented, auditable onboarding process that a compliance officer can point to during an audit. The tool that construction operations needs is not a better autocomplete and not a better chat window. It is an operations engineer that treats vendor management, compliance, and process design as the actual deliverable, not a side effect of a code change.

The mismatch is structural. A generalist tool answers isolated questions well and forgets everything the moment the conversation ends. An autocomplete tool lives inside code and has no visibility into the paperwork, contracts, and vendor history that actually run a construction operation. What a general contractor's ops team needs is something closer to a dedicated operations hire, one who designs the process once, keeps it current as vendors rotate on and off active sites, and flags risk before it becomes a stalled crew standing around a site with no material and no explanation.

Meet Keel, and where Forge and Chain fit

Keel is Tonone's operations engineer, the agent built for process design, vendor management, legal ops, compliance tracking, and OKR execution inside Claude Code. Where a generalist chatbot produces a document and an autocomplete tool produces a line of code, Keel produces a running process: a documented subcontractor onboarding workflow, a vendor file that stays current, a compliance calendar that flags what is about to expire, and an audit trail that survives a subcontractor dispute or an insurance carrier's review. Keel does not replace your ops director. It does the repetitive, detail-heavy process work that eats a full-time role's week, so the ops director spends time on the fifteen vendor relationships that actually need judgment instead of the ninety that just need a checklist followed correctly.

Tonone's Keel designs and documents the subcontractor onboarding process so every vendor intake, insurance cert, and compliance step happens the same way every time, on every active site.

Designing the onboarding process itself

The keel-process skill is where onboarding stops being a spreadsheet someone half-remembers and becomes a documented, repeatable workflow. Give Keel the shape of your operation, how many active sites, what your master service agreement requires, what your insurance minimums are, whether you run certified payroll or prevailing wage jobs, and it produces a step-by-step onboarding sequence with owners, required documents, and hard deadlines attached to each step. It is not a generic checklist pulled from a template library. It is built from your actual requirements, versioned so that when your insurance minimums change or a new site adds a certified payroll requirement, the process updates once and applies everywhere instead of living in forty separate memories.

Vendor management that scores risk before it becomes a delay

The keel-vendor skill turns your vendor file from a static contact list into a tracked relationship. Every subcontractor and supplier gets a record: contract terms, on-time delivery history, insurance cert expiration, past disputes, current active sites. Keel uses that record to flag risk before it turns into a stalled crew, a supplier who slipped delivery on the last two jobs, a sub whose cert expires in nine days with no renewal on file, a vendor concentration problem where three of your twelve active sites depend on the same overstretched electrical crew. This is the piece that most directly answers the supply chain problem that never shows up on anyone's radar until the site goes idle: not a forecast of freight delays, but a documented, current picture of which vendor relationships are carrying more risk than the schedule can absorb.

Compliance as a maintained program, not a fire drill

The keel-comply skill keeps the compliance program itself current: which certificates are required, which are on file, which are expiring, and what the audit trail looks like when a bonding company or an owner's rep asks for proof. For a general contractor this means insurance certs, W-9s, lien waivers, and safety documentation tracked the same way a SOC2 program tracks controls, as a living, versioned record instead of a folder someone reconstructs under deadline pressure. Paired with keel-audit, which reviews the internal controls around vendor payments and compliance sign-off, Keel gives an ops team something they can hand an auditor without a week of prep.

Keel keeps compliance paperwork as a maintained, auditable program rather than a folder someone reconstructs from memory when an auditor calls.

Reconnaissance before the process gets designed

Before Keel writes a single onboarding step, keel-recon reads what already exists, current vendor spreadsheets, past onboarding docs, whatever compliance tracking is already in place, however informal. This matters for construction ops specifically because most of the existing process lives in someone's head and a shared drive, not in a system. keel-recon inventories that reality first so the process Keel designs actually replaces what people are doing today instead of adding a second, competing system nobody adopts.

Two related agents round out the picture for a general contractor running internal tooling alongside its fieldwork. Forge, Tonone's infrastructure engineer, handles the cloud side of whatever internal systems the ops team runs, the site dashboards, the vendor portal, the equipment tracking tool, keeping the hosting cost and network configuration sane across a dozen sites' worth of cameras, sensors, and status boards. Chain, Tonone's supply chain security engineer, is worth being precise about: its job is scanning the software supply chain of whatever code your team builds or runs, generating a software bill of materials and flagging vulnerable open source dependencies, not forecasting when a steel delivery will slip. If your ops team has built even a lightweight internal vendor portal to track the onboarding Keel designed, Chain is the agent that scans its dependency tree so a vulnerable package in that portal doesn't become the next incident report.

A worked example: Ridgeline Builders

Ridgeline Builders is a general contractor running twelve active commercial sites with one operations director, Dana, covering vendor management and compliance for all of them. Forty-three subcontractors are active across those sites this quarter. Dana hands Keel the brief: design a subcontractor onboarding process that works the same way whether the sub is a two-person electrical outfit or a sixty-person framing crew, and surface which of the forty-three carry risk that could stall a site.

Keel runs keel-recon first and finds the current process: a shared spreadsheet, insurance certs emailed and saved inconsistently, no standard lien waiver tracking, three different onboarding emails depending on who at Ridgeline handled the intake. Then keel-process produces the documented workflow, and keel-vendor scores the existing forty-three vendor records against it.

Keel, Subcontractor Onboarding + Vendor Risk, Ridgeline Builders
Recon: 12 active sites, 43 active subs, insurance/W-9/lien waiver tracking
currently spreadsheet-based, no expiration alerts, 3 divergent intake emails.

━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
Onboarding workflow (keel-process)
  Step 1: W-9 + COI (min $2M general liability) collected before PO issued.
  Step 2: Master service agreement signed, rate schedule attached.
  Step 3: Safety orientation logged, site-specific hazard briefing on file.
  Step 4: Lien waiver template confirmed per state, tied to payment schedule.
  Step 5: Vendor record opened in tracked file, renewal dates calendared.
  Owner per step assigned. SLA: 5 business days, PO blocked until complete.

Vendor risk pass (keel-vendor) on 43 active subs
  6 subs: COI expiring within 14 days, no renewal on file. Flagged red.
  4 subs: 2+ late deliveries or schedule slips in trailing 6 months.
  1 vendor: supplies 3 of 12 active sites, single point of failure.
  32 subs: current, no flags.

Compliance program (keel-comply)
  Certified payroll tracked for 2 prevailing-wage sites, weekly cadence.
  Audit trail exportable per site for bonding company review.
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
Recommendation: renew 6 flagged COIs this week before next PO cycle.
Review the single-point-of-failure vendor before adding a 13th site.

Dana now has, in one pass, a documented onboarding process every future sub goes through the same way, and a live picture of which six vendors need an insurance renewal chased down this week before it becomes a stopped crew. That single-point-of-failure flag, one supplier tied to three of twelve sites, is exactly the kind of risk that used to surface only after a site sat idle for a day and someone asked why. If Ridgeline's team later builds a lightweight internal portal so field supervisors can see this vendor status without calling the office, Chain scans that portal's dependencies before it goes live, and Forge keeps the hosting and site-camera network configuration for the dozen locations running without anyone in ops needing to think about cloud infrastructure at all.

The risk that stalls a construction site rarely shows up as a dramatic failure, it shows up as an insurance cert nobody renewed and a vendor concentration nobody mapped. Keel is built to surface exactly that, before the crew is standing idle.

Install and try

Tonone is free and MIT-licensed. Install it once and Keel, Forge, Chain, and the rest of the 100-agent roster are available in your Claude Code session. You pay only for the Claude Code token usage during the work itself.