Redlines are a pain to update.
Every revision round means hand-tracing changes across plans, elevations, sections, and details — and missing one is what holds a project up.
AI-assisted shop drawing automation for millwork teams. Millwork IO is being built to take architectural drawings and redlines in — and produce BricsCAD-ready shop drawing packages out. Less drafting time. Less revision friction. Fewer manual errors.
See the workflowEvery revision round means hand-tracing changes across plans, elevations, sections, and details — and missing one is what holds a project up.
Dimensions, tags, and casework counts get out of sync the moment a drawing is touched. Catching it in shop is the expensive option.
Two drafters, two sets of standards, two-sheet packages that don’t look like they came from the same shop. Reviewers feel it.
AI Drawing Intake reviews the drawings. Millwork IO’s deterministic tools draw the package. BricsCAD stays the executor. You stay in control of the DWG output.
Drop in the architect’s plans, elevations, sections, and the latest redline markup. PDFs, DWGs, scans — the messy stuff a real project ships with.
AI Drawing Intake reads cabinetry plans, elevations, sections, and redlines, and surfaces what it found for you to confirm before anything is drawn.
Deterministic tools generate the full shop drawing package in DWG — plans, elevations, sections, details, sheet meta, and revisions — and regenerate the package on every revision round.
You can step in and adjust the DWG output with the same Millwork IO tools at any point. AI doesn’t freely edit DWG entities — you and Millwork IO do.
AI doesn’t directly edit DWG entities. Millwork IO inside BricsCAD remains the deterministic executor for drawing generation, validation, and regeneration — reviewed by you.
Spending too much of the week pushing geometry around instead of solving the hard details.
Running multiple casework-heavy projects in parallel and feeling the per-sheet cost.
Wanting shop-ready output to come out of design intent without a second translation pass.
Working with millwork shops and tired of revisions sitting in a drafting queue for a week.
Where the cost isn’t the first issue — it’s the 4th, 5th, and 6th rev that crushes the schedule.
Millwork IO isn’t public yet. The early access list is how we’ll line up the first shops, drafters, and designers we work with — and how we’ll send the first build invites when they go out.
No. Millwork IO is in active development and is not publicly released. The early access list is how we’ll line up the first shops and drafters when builds start going out.
Yes. AI Drawing Intake is part of the intended release product. We’re not planning to release Millwork IO publicly without it.
No. AI doesn’t freely edit DWG entities. Millwork IO inside BricsCAD remains the deterministic executor for drawing generation and regeneration, and you can step in and adjust the DWG output with Millwork IO’s tools at any point.
No. Millwork IO runs inside BricsCAD. BricsCAD remains the CAD environment your team works in — Millwork IO sits on top of it and handles the shop drawing automation.
Millwork drafters, commercial casework teams, designers, architects, and shops dealing with frequent revisions — anyone whose week gets consumed by producing or updating millwork shop drawings.
Not in the first release. The initial focus is the shop drawing package in DWG. Manufacturing-export workflows are on the longer roadmap, not the launch scope.