June 8, 2026 · AEC + AI

Construction's AI money is flowing into submittal and RFI review

A $13.8M seed round and a wave of new tools point the same direction: AI is arriving first in submittal and RFI review. It's worth understanding what that does well — and the line the engineer of record still has to stand on.

The news

In March 2026, Zero RFI launched with a $13.8 million seed round led by General Catalyst, founded by technology veteran KP Reddy, and built around a three-company roll-up of construction firms. The name says where the founders see the opening: requests for information and the document review that drives them. They're not alone — across the industry, document management and submittal/RFI processing keep getting named the highest-impact early uses of AI.

You can watch the same shift in practitioner forums. On Reddit's r/ConstructionManagers, people are openly testing tools that take a spec PDF plus a submittal, auto-locate the relevant clauses, flag mismatches (fire rating, finish, applicable standard), and even draft an RFI when the spec and drawings conflict. That's not a pitch deck — that's the actual review task, described by the people who do it.

Why this workflow first

Submittal and RFI review is paperwork-heavy, pattern-matching work: open a 300-page spec, find the right section, check the proposed product against it, document the result. That maps cleanly onto what current models are good at. The honest split is this: quantitative checks — dimension consistency, spec-to-drawing material alignment — get high precision. Interpretive checks — design intent, constructability — still need a human. AI gives you broad coverage at moderate confidence; a person takes the items that matter to high confidence.

The line that doesn't move

This is the same workflow AECdesign.ai's live review tools support. Submittal Review compares vendor product information against the approved drawings and specs and prepares a structured compliance draft. RFI Response drafts an answer from approved project sources and keeps the contract-document trail visible where available. The difference is what happens to the output: every result is a draft. The engineer of record reviews, revises, accepts, or rejects each finding before anything is issued. AECdesign.ai never produces a sealed determination.

An honest caution about the money: a venture-backed roll-up funded to "transform" an industry carries pressure to push toward automation — fewer humans, faster cycles, broader claims. In work that carries a seal, that pressure cuts against the very thing that makes the output defensible. The quantitative/interpretive split above isn't a temporary limitation to engineer away. It maps to professional accountability. The licensed professional owning the interpretive call is the design — not a missing feature.

What to watch

The funding and attention are good news in one plain sense: they confirm this is a real workflow worth doing well, and that helps everyone building here. The thing to watch in any tool — ours included — is where it draws the human-in-the-loop line. A tool that cites its sources and hands you a reviewable draft fits a liability-bearing practice. One that quietly issues conclusions does not.

Sources

• Zero RFI launches, backed by General Catalyst — Crowdfund Insider (March 2026; $13.8M seed, KP Reddy, roll-up).
• Zero RFI raises $13.8M seed round — citybiz (March 16, 2026).
• "AI finds spec clauses & flags submittal mismatches — useful or overkill?" — r/ConstructionManagers (practitioner discussion).
• AI document review: drawings, specs, RFIs, and submittals — Helonic (quantitative vs. interpretive split; vendor source, Med confidence).

Draft, not determination. Every substantive AECdesign.ai result is a draft. A licensed engineer of record must review, revise, accept, or reject each finding before it is issued. AECdesign.ai never provides a sealed determination.