AI CAD for architecture: different world, same promises

AI CAD for architecture uses a completely different set of tools than mechanical CAD AI, because buildings are not brackets. Architectural design requires BIM data, code compliance, environmental analysis, and coordination between dozens of disciplines, none of which text-to-CAD tools even attempt to address. I learned this the hard way last year when an architect friend asked me to look at "the AI tools everyone's talking about" and I spent an evening realizing that my entire frame of reference was wrong.

I'd been testing text-to-CAD tools for months at that point. Zoo.dev, AdamCAD, the usual suspects. My friend watched me generate a bracket from a text prompt and said, "That's cute. Can it do a floor plan with fire egress compliance and structural column placement?" I stared at him. He stared at me. We both realized the AI-in-CAD conversation has been happening in two completely different rooms, and neither room knows what the other is talking about.

This post is for the people in my room, the mechanical CAD users, who keep seeing "AI in architecture" headlines and wondering if it's the same technology. It's not. Here's what's actually happening.

Why architectural CAD is a different problem#

Mechanical CAD and architectural CAD share a surface similarity: both involve creating 3D geometry on a computer. That's roughly where the overlap ends.

In mechanical CAD, a bracket is a bracket. It has geometry, dimensions, material properties, and tolerances. The file contains the shape and maybe some metadata. The geometry is the deliverable.

In architectural CAD, a wall is not just geometry. It's a BIM object. It has a type (load-bearing, partition, curtain), a fire rating, an acoustic rating, a thermal resistance value, material layers (gypsum board, insulation, vapor barrier, structure, more gypsum board), connections to floors and ceilings, penetrations for mechanical systems, and relationships to every other element in the building model. The geometry is maybe 20% of what the wall object contains. The other 80% is data that makes the building compliant, constructable, and coordinated across disciplines.

This is why text-to-CAD as it exists in mechanical design doesn't translate to architecture. Generating a wall shape from a text prompt is trivial. Generating a wall that carries its full BIM data, connects correctly to adjacent elements, meets fire code requirements for its location in the building, and coordinates with the HVAC ducts passing through it? That's a completely different problem. No text prompt captures that level of intent.

The tools that matter in architecture aren't trying to generate geometry from words. They're trying to solve the problems architects actually have, which are about configuration, compliance, analysis, and visualization.

Concept visualization: where AI actually landed#

The most visible use of AI in architecture right now is concept visualization. Midjourney, DALL-E, Stable Diffusion, and similar image generators have been adopted by architecture firms for early-stage design exploration. An architect types a description of a building, a material palette, a mood, and gets a rendered image in seconds.

This is useful in the same way that a concept sketch is useful: it communicates an idea without committing to technical decisions. A partner at a mid-size firm I spoke with uses Midjourney to generate a dozen exterior concepts before a client meeting, pins the three that feel right, and uses them as conversation starters. The images aren't architecture. They're not BIM models. They're not even 3D models. They're pictures. But for aligning on aesthetic direction before any real design work starts, they save time that would otherwise be spent on hand sketches or SketchUp studies that the client might not even like.

The limit is obvious: these images contain no technical information. The AI doesn't know about structural grids, floor-to-floor heights, code-required setbacks, or the difference between a feasible facade system and a beautiful impossibility. I've seen AI-generated architectural images with cantilevers that would require structural engineering bordering on magic, window-to-wall ratios that would violate energy code in every climate zone, and building massing that ignores the lot boundary by a comfortable margin. They look wonderful. They communicate mood. They don't communicate architecture.

For mechanical CAD users wondering how this compares to text-to-CAD vs text-to-3D, it's the same distinction at a larger scale. Image generation creates pictures. Model generation creates geometry. Architecture mostly uses the picture side, because the model side requires too much embedded data to generate from prompts.

Building configurators: Hypar and Testfit#

The AI tools that come closest to "generative design for architecture" aren't really AI in the mechanical-CAD sense. They're parametric configurators with optimization layers.

Hypar is a cloud-based platform where architects and developers define building parameters (site boundaries, floor counts, unit mix, parking requirements, structural grid) and the system generates building configurations that meet those parameters. It's not generating architecture from a text prompt. It's solving a constraint satisfaction problem: given this site, these zoning rules, and this program, what configurations work?

Testfit does something similar for multifamily and mixed-use developments. You define the site, the unit types, the parking requirements, and it generates feasible building layouts showing unit stacking, corridor configurations, and parking garage layouts. The output is diagrammatic rather than BIM-ready, but it answers the fundamental feasibility question: can this program fit on this site?

These tools are useful because the early architectural design problem is largely about configuration and fit. Can I put 200 apartments on this lot and still meet parking requirements and setback rules? That question used to take an architect a week of sketch studies. Hypar or Testfit answer it in minutes, with multiple options.

The connection to AI in CAD software in the mechanical world is thin. These tools don't generate detailed geometry. They don't produce BIM models ready for construction documents. They produce feasibility studies and configuration options that architects then develop into real designs using Revit, ArchiCAD, or whatever their BIM platform is. The AI handles configuration. The architect handles architecture.

Environmental analysis: Autodesk Forma#

Autodesk Forma (formerly Spacemaker) is probably the most interesting AI tool in architecture right now, because it addresses a problem that architects have always struggled with: understanding how a building design affects and is affected by its environment before committing to a geometry.

Forma analyzes wind patterns around proposed buildings, solar exposure on facades and surrounding streets, daylight availability inside units, noise propagation from nearby roads, and microclimate effects. You place building masses on a site and the analysis runs in real time, showing you which facades get adequate daylight, which outdoor spaces will be uncomfortably windy, and which units won't meet local daylight requirements.

This is genuine AI applied to a genuine architectural problem. The analysis uses machine learning models trained on CFD (computational fluid dynamics) and environmental simulation data to produce approximate results in seconds rather than the hours or days that full simulations would require. The trade-off is precision: Forma gives you directional answers (this facade will be windy, this courtyard will be shaded) rather than precise numbers (the wind speed at this point will be 4.7 m/s). For early design decisions, directional is enough.

I find Forma interesting because it's one of the few AI tools in any CAD domain that solves a problem humans genuinely can't solve intuitively. I can sketch a bracket from experience and get close to what the optimizer would produce. An architect cannot intuit the wind patterns around a 30-story building next to two existing towers and a river. The physics is too complex for human intuition, which makes it a good problem for AI.

What mechanical text-to-CAD can't do here#

People occasionally ask whether tools like Zoo.dev or AdamCAD could be applied to architectural design. They can't, and the reasons go beyond technical capability.

AI-generated CAD for real work in mechanical design means producing geometry that can be manufactured. The equivalent in architecture would be producing a building model that can be permitted, bid, and constructed. The gap between those two is enormous.

An architectural model for construction documents contains thousands of objects, each with properties, relationships, and code compliance data. A door is not just a rectangle in a wall. It's an assembly with a fire rating, an accessibility clearance, hardware specifications, a frame type, and a location that satisfies egress path requirements. None of this exists in a geometry-only model.

Text-to-CAD's output, geometry without engineering data, is already a limitation in mechanical design. In architecture, where the data-to-geometry ratio is even higher, geometry alone is nearly useless. You can't permit a building from shapes. You can't coordinate MEP systems through shapes. You can't do a code review on shapes. The BIM requirement kills the text-to-geometry approach before it starts.

Where AI helps architects today#

The honest list is short but real.

Concept visualization through image generators. Fast, cheap, good for client communication and early design exploration. Not architecture, but useful before architecture begins.

Site and building configuration through tools like Hypar and Testfit. Answers feasibility questions quickly. Saves weeks of sketch studies in early project phases. Doesn't produce BIM-ready output.

Environmental analysis through Forma and similar tools. Provides directional environmental feedback in real time during massing studies. Genuinely useful for decisions that humans can't make intuitively.

Code compliance checking through emerging tools that scan BIM models against building code requirements. This is early-stage but promising. The code compliance process is rule-based and data-heavy, which makes it a reasonable AI application.

Documentation assistance through AI that helps generate specifications, schedules, and code narratives from BIM data. This is more about language models than CAD models, but it addresses a real time sink in architectural practice.

Where the promises outrun reality#

Vendors love to demo AI generating floor plans from text descriptions. "A 2-bedroom apartment with an open kitchen and a corner living room." The result is a floor plan that looks plausible until you measure the corridor width (too narrow for accessibility), check the structural column locations (not on a grid), notice the plumbing walls don't stack between floors, and realize the window placement violates the energy code.

The demo-to-production gap in architectural AI is, if anything, wider than in mechanical CAD. A mechanical bracket that's dimensionally close is still useful as a starting point. A floor plan that violates accessibility code is useful as a conversation piece and nothing else.

I've seen architects excited about AI-generated floor plans and architects dismissive of them, and the divide usually comes down to whether they've tried to take one past the concept phase. The concept is fine. The execution requires an architect to redo most of the work, which is the same conclusion I reach about text-to-CAD for real work in the mechanical world, just with higher stakes and more regulations.

The honest comparison#

Mechanical CAD AI and architectural CAD AI are solving different problems with different tools for different users. The marketing makes them sound like cousins. In practice, they barely share a vocabulary.

Mechanical text-to-CAD generates parts. Architectural AI generates images, configurations, and analyses. Neither industry has AI that produces production-ready output without significant human work.

The interesting parallel is the maturity curve. Both fields are at the "useful for early-stage exploration, not ready for production deliverables" phase. Both have vendors overpromising. Both have users who are excited and users who are skeptical, and both groups are right about different things.

If you work in mechanical CAD and someone asks you about AI in architecture, the honest answer is: different tools, same growing pains. And if an architect asks you whether text-to-CAD could help with their work, the honest answer is no, but not because the technology is bad. It's because the problem is different, the data requirements are different, and a building is not a bracket, no matter how much the LinkedIn posts want them to be the same story.