Text-to-CAD for rapid prototyping

Friday afternoon, 4 PM, and a client sends over a revised board layout with mounting holes that moved 8mm from where they were last week. I had a prototype enclosure sitting on my desk that was now wrong in exactly the ways that matter: the standoffs didn't line up and the USB cutout was in the wrong spot. In the old days I would have opened Fusion 360, adjusted the sketch, rebuilt the feature tree (which would probably complain about at least one lost reference), re-exported, and sent the file to the printer. Forty-five minutes, minimum, mostly spent arguing with the timeline about why a moved hole affects a fillet three features later.

Instead I typed a new prompt into Zoo.dev with the updated dimensions, waited about thirty seconds, opened the STEP file, spot-checked the critical measurements, exported STL, and hit print. The part was on the build plate before 4:20. Was it perfect? No. The wall on one side was 0.3mm thinner than I'd have liked, and the corner radii weren't exactly what I'd have modeled by hand. But it was close enough to hold up to the board and check fit, which was the entire point. Prototyping is not about perfection. It's about learning fast enough to make the next version less wrong.

That's the argument for text-to-CAD in prototyping, and it's the strongest argument the technology has right now. When the goal is speed, the tolerance is plus or minus "can I tell if this works," and the part is going in the trash after it teaches you something, text-to-CAD is genuinely useful.

Why prototyping tolerates what manufacturing doesn't#

Every complaint about text-to-CAD output, the inconsistent wall thickness, the approximate dimensions, the missing tolerances, the absent DFM considerations, becomes less important when the part is disposable.

A prototype exists to answer a question. Does the board fit? Can the user reach the button? Is the enclosure too bulky? Does the cable route work? These questions need physical geometry, but they don't need precise geometry. If the enclosure is 1mm wider than intended, you can still tell whether it feels too big in your hand. If the mounting holes are 0.5mm off, you can still check if the board orientation makes sense. If the wall thickness varies a little, the structural concept is still visible.

Manufacturing demands precision because the parts go into products that go into customers' hands. Prototyping demands speed because the faster you learn, the fewer mistakes survive into production. Text-to-CAD is bad at precision and good at speed. The match with prototyping is obvious once you stop expecting it to be a manufacturing tool.

The thirty-second first draft#

The time savings are real and measurable. I've tracked my workflow on about two dozen prototyping iterations over the past few months, comparing text-to-CAD generation to manual modeling in Fusion 360 for simple bracket-and-enclosure type parts.

Manual modeling for a simple bracket: 10-20 minutes. Create a sketch, dimension it, extrude, add holes, fillet edges, export.

Text-to-CAD for the same bracket: 30 seconds for generation, 2-3 minutes for import and spot-checking critical dimensions, maybe 5 minutes if I need to adjust something in Fusion before exporting. Call it 5-8 minutes total.

For a single part, that's not life-changing. But prototyping is iterative. You don't make one part. You make five versions of the same part as the design evolves, the board layout changes, the client moves a connector, or you realize the cable needs to route a different way. Five iterations at 15 minutes each is 75 minutes of modeling. Five iterations at 7 minutes each is 35 minutes. Over a project with a dozen prototype parts going through three or four rounds, the cumulative savings add up to hours. Not days, but hours. And in a tight prototyping timeline, hours matter.

What to prototype with text-to-CAD#

Not everything in a prototype needs AI-generated geometry. Some parts are too complex, too critical, or too dependent on specific dimensions to trust to a text prompt. Here's what I've found works and what doesn't.

Works well: enclosure shells where you're checking fit and form. Mounting brackets for PCBs, sensors, and small motors. Cable routing guides. Battery holders. Display bezels (rough fit check only). Standoff and spacer geometry. Simple jigs for holding components during testing. Structural test pieces for evaluating basic load paths.

Works poorly: gear mechanisms. Flexible latches that need specific deflection behavior. Anything with mating surfaces that need to seal. Parts with threads (the AI generates decorative threads, not functional ones). Anything that needs to snap together with another AI-generated part, because the two parts won't agree on dimensions. Multi-component assemblies where fit between parts matters more than the individual shapes.

The pattern is straightforward: if the prototype question is "does this shape work in this space," text-to-CAD helps. If the prototype question is "do these two parts work together at this tolerance," text-to-CAD introduces more problems than it solves.

The iterate-fast loop#

The best prototyping workflow I've found with text-to-CAD is a tight loop:

Prompt. Generate. Download STEP. Open in Fusion 360. Check three or four critical dimensions. Fix anything that's off by more than a millimeter on a feature that matters. Export STL. Slice. Print.

Evaluate the print. Hold it. Try to fit the components. Take notes on what's wrong. Write a new prompt that addresses the problems. Repeat.

The key insight is that you're not refining the same model through a feature tree. You're regenerating from scratch each time with an updated description. This sounds wasteful if you're used to parametric modeling, where you'd adjust one dimension and rebuild. But for prototyping, regeneration is actually fine because the part is simple, the generation is fast, and you're going to throw it away after the next revision anyway.

I've found myself writing prompts that get more specific with each iteration. First round: "rectangular enclosure 100x60x35mm with lid." Second round: "rectangular enclosure 100x60x35mm, 2mm walls, lid with 4 alignment pins, USB-C opening on the short side centered 12mm from the bottom." Third round: same but with "add ventilation slots on both long sides, 8 slots each, 2mm wide." Each prompt builds on what I learned from the previous print, and the regeneration takes seconds.

This workflow won't work for everyone. If you're a parametric-modeling purist who wants a single source of truth with full design intent captured in the feature tree, throwing away geometry and regenerating feels wrong. I get it. But prototyping is a different game. The feature tree doesn't matter when the part has a lifespan of one afternoon.

The Fusion 360 checkpoint#

I never go straight from text-to-CAD to the printer without opening the STEP file in Fusion 360 first. This takes 2-3 minutes and has saved me from enough failed prints that it's non-negotiable.

What I check: overall dimensions against the prompt. Wall thickness on at least two faces (the AI sometimes gets these inconsistent). Hole diameters on critical mounting features. Whether the geometry is actually a solid (occasionally you get a model with internal faces that slice weirdly). Whether any feature is below the minimum printable size for my printer and material.

What I fix: holes that are too small (AI consistently generates holes 0.2-0.5mm undersized, and FDM shrinks them further). Walls that are below 1.2mm. Obvious errors like missing features or features in the wrong location.

What I ignore: non-critical dimensions being off by half a millimeter. Fillets that aren't exactly the radius I'd have chosen. Cosmetic details on a functional prototype. The fact that the feature tree is essentially one imported body with no history.

This checkpoint is the difference between text-to-CAD being a time-saver and text-to-CAD being a filament-waster. Five minutes of checking versus two hours of reprinting after a failure. The math works out every time.

Materials for prototyping AI-generated parts#

PLA. Almost always PLA for the first round.

PLA is forgiving, cheap, fast to print, dimensionally stable enough for fit checks, and it doesn't care about the minor geometry imperfections that text-to-CAD tools produce. A wall that varies between 1.5mm and 2mm still prints. A slightly faceted curve still looks like a curve. An oversized fillet still functions as a fillet. PLA absorbs the imprecision of AI-generated geometry better than any other common FDM material.

For later prototype rounds where I need to test mechanical properties, I switch to PETG or ABS. These materials are less forgiving of geometry quirks (ABS warps more, PETG strings more) but they're closer to production material behavior. By the time I'm printing in engineering materials, I've usually already corrected the critical geometry in Fusion, so the AI's original output has been refined.

I've also printed AI-generated parts in TPU for a flexible gasket prototype. This worked surprisingly well because the gasket was a simple ring shape, exactly the kind of geometry text-to-CAD handles without trouble.

Where this sits compared to parametric prototyping#

I'm not going to pretend text-to-CAD is always faster than traditional modeling for prototyping. It depends on the part, the complexity, and how fast you are in your CAD tool of choice.

If you're an experienced Fusion 360 user and the part is a simple bracket you've modeled a hundred times before, you can probably sketch, extrude, and export in under ten minutes. Text-to-CAD saves you maybe five minutes. Not nothing, but not transformative.

If you're exploring a shape you haven't modeled before, or if you need multiple variations quickly, or if you're less experienced in CAD and every bracket takes thirty minutes, the time savings grow. A hardware engineer who's more comfortable writing English than creating sketch constraints can get a printable part from a text description in minutes instead of wrestling with a feature tree for an hour.

The biggest advantage isn't speed on any single part. It's the lower barrier to trying things. When generating a shape takes thirty seconds, you try more shapes. When you try more shapes, you learn faster. When you learn faster, the final product is better. The value isn't in the individual model. It's in the velocity of the iteration loop.

The prototyping use case is real#

Prototyping is where I recommend people start with text-to-CAD, and it's where I think the current tools deliver genuine value. The accuracy is good enough. The speed is clearly better. The failure cost is a few dollars of filament and an hour of print time, not a blown manufacturing run.

The parts are disposable by design. You print them to learn something, not to ship something. Every limitation of text-to-CAD output, the missing tolerances, the approximate dimensions, the absent DFM awareness, matters less when the part's purpose is education rather than production.

Start here if you're curious about text-to-CAD. Generate a bracket. Print it. Hold it against the thing it's supposed to fit. You'll immediately understand both what the technology can do and where it stops. That understanding is more useful than any demo, and it only costs you thirty seconds of prompting and a bit of plastic.

The parts that survive prototyping get modeled properly in real CAD for production. The parts that don't survive go in the scrap bin, having done their job. Either way, the prototyping was faster than it would have been without the AI. That's a narrow win, but a real one, and in 2026 it's the clearest justification for text-to-CAD that I can honestly make.