AO
AEC Orchestrator
How it works Who it's for Request a pilot
Now recruiting design partners

One canvas orchestrating your entire design stack.

Wire Revit, AutoCAD, Bluebeam, and Navisworks into a single visual pipeline. Claude reads, filters, and acts on real project data across every one of them — no custom integration code, no manual handoffs.

Request a pilot See how it works ↓
AEC Orchestrator pipeline canvas with AutoCAD, AI, and Bluebeam nodes wired together, node settings panel open on the right
Works with the tools you already run
REVIT AUTOCAD BLUEBEAM NAVISWORKS OUTLOOK
The problem

Coordination happens by hand — every week, every project.

BIM and VDC teams manually shuttle data between a Navisworks clash report, a Bluebeam markup, a Revit model, and an Outlook status email or Excel tracker. Each handoff is manual, repeated on every active project, and easy to get wrong.

01
Manual handoffs

Every export, every markup, every email typed and copied by hand between tools that don't talk to each other.

02
Repeated weekly

The same coordination loop runs again on every active project, with no memory of how it went the last time.

03
Error-prone

A missed field or a stale export slips through, and nobody notices until it shows up on site.

How it works

Build a pipeline. Each node is one app.

NAVISWORKS
Pull clash results for Level 3
→
CLAUDE
Filter to structural clashes only
→
BLUEBEAM
Push markups to sheet A-301
→
OUTLOOK
Email the summary to the coordination team

Each node runs one scoped call — just that app's tools, plus your instruction for what to extract or push. Anything that writes into a live model waits for your confirmation, by default.

Who it's for

Built for teams already running Revit, Navisworks, and Bluebeam together.

BIM / VDC teams

General contractors and MEP or structural firms running clash detection and coordination across Revit, Navisworks, and Bluebeam. Your weekly workflow is exactly the pipeline this automates.

Independent BIM consultants

Running the same coordination workflow across many client projects — a saved pipeline pays off again on every new one.

Why now

The hard part of AEC integration was always the connectors — the .NET add-ins, the OAuth, the platform APIs. That part is already solved. What's left is orchestration.

Pilot program

Run one real workflow. Free.

We're onboarding a small number of design partners to run a real internal pipeline on real project data — free access and hands-on setup, in exchange for feedback and a case study if it works.

Free access + onboarding
Your real workflow, your data
Direct line to the team building it
Request a pilot
AEC Orchestrator The visual automation layer for your design stack.
hello@aecorchestrator.com