FFastBid24

AEC AI Lab

Things we probably shouldn't be able to automate yet.

The bench where FastBid24 products come from. Every card is real work — including where it still fails. We publish the failures because a lab that never fails isn't running experiments; it's running marketing.

What should AI understand?
Drawings · EstimatorsLive product

Can AI read a door schedule that exists only as a drawing?

Door schedules are often rendered images inside PDF sheets — no text layer, merged cells, revision clouds. The extraction pipeline reads the rendered schedule visually and as parsed text, then reconciles the two before structuring rows.

Became a product →
Estimating · EstimatorsLive product

Can AI map 250 hardware items to 41 openings without inventing one?

Hardware sets live in the spec; openings live in the schedule. The mapping layer joins them opening by opening — and refuses to guess when the documents are silent, flagging instead.

Became a product →
Coordination · Estimators · PMsLive product

Can AI notice when the schedule and the spec disagree?

Every extracted entity is checked against every other source that mentions it: schedule vs. spec, spec vs. plan, set vs. opening. Disagreements become review items with the evidence attached.

Became a product →
Coordination · Estimators · PMsLive product

Can AI turn a document gap into a question a GC will actually answer?

Every flag carries its evidence: what the schedule says, what the spec says, what's missing. The pipeline drafts the RFI with references attached, ready to send.

Became a product →
Estimating · Specialty contractorsLab prototype

Does the same pipeline work on plumbing fixtures, lighting, casework, and flooring?

The extract → map → reconcile → verify pipeline is trade-agnostic by design. Seven trade products are in development on the same foundation, prioritized by waitlist demand.

Project Risk · GCs · PreconConcept

Can AI find the scope nobody owns before bid day?

The reconciliation layer already finds disagreements between documents. The next step is finding disagreements between scopes — requirements that appear in the project but land in no one's bid.

The loop

Experiments graduate.

Experiment
Prototype
Pilot
Product

Schedule extraction, hardware mapping, reconciliation, and RFI drafting all started as “can AI even do this?” — and shipped inside Doors & Hardware AI. The multi-trade pipeline is in the prototype stage now; waitlist demand decides what graduates next.

Have a problem that belongs on this bench?

The next experiment could start with the workflow your team hates most.