Why Teams Choose CRAFT
You spend three hours labeling corridor stations every week. Auditing 2,000 doors for fire ratings takes a full day. Checking layer names against your firm’s standard is the kind of task nobody wants to do twice. CRAFT turns those tasks into trusted, reusable automations that run inside Revit or Civil 3D — with a full safety preview before anything changes.
The work that eats your week
Real tasks everyday CAD users run all the time — by hand, one model at a time, every single time.
Civil 3D
“I spend 3 hours labeling corridor stations every week”
Corridor station labels, surface queries, pipe-network reports — the kind of repetitive Civil 3D work that should take one click, not half an afternoon.
Revit
“Checking 2,000 doors for fire ratings takes a full day”
Parameter audits, naming-convention checks, coordination reports — tasks that shouldn’t require hand-inspecting every element. CRAFT validates in seconds with a full preview before execution.
Both hosts
“Standards drift whenever anyone’s in a hurry”
Layer naming, family usage, parameter conventions. CRAFT turns “we’re supposed to do it this way” into a one-click check that anyone on the team can run.
And the team-level problem on top of it
Even when automation exists, nobody trusts it.
Automation Sprawl
50 overlapping Dynamo scripts, a dozen AutoLISP routines, a shared drive full of “use this one, not that one” — and nobody trusts any of them. There’s no way to know which version is current, who made it, or whether it’s safe to run on your project.
No Review Process
Anyone can create and share scripts with no review. No approval step, no duplicate detection, no deprecation process. The shared drive grows but never gets cleaned up.
Black-Box Execution
Most automation tools don’t show you what they’ll do before they do it. You run a script, hope it works, and deal with the consequences. There’s no preview, no safety check, no declared data handling.
Knowledge Loss
When the person who wrote the script leaves, the automation leaves with them. No documentation, no versioning, no way to understand what the tool actually does without reading the code.
How CRAFT Is Different
Five things, in the order they matter to your team.
1. Reuse-First
Before CRAFT ever asks you to build something new, it checks your team’s library for an automation that already does the job. The fastest path is the one your team already paid for once.
2. 100% Local Execution
Every automation runs on your machine inside your CAD host. Cloud services are passive — library, licensing, and trust anchors only. No cloud execution path exists.
3. Preview Before Every Run
Every action passes a mandatory safety preview showing exactly what will change, what data is read, and what (if anything) leaves your machine. If safety can’t be proven, it blocks. There is no override.
4. Signed & Locked Releases
Every published automation is cryptographically signed and locked. Released versions can’t be overwritten or modified. You always know exactly what you’re running. Full security details.
5. Reviewed Before Sharing
A draft only you can run never automatically becomes a team tool. Sharing to the team library goes through review and near-duplicate detection — so 50 overlapping scripts can’t accumulate again.
Bonus: Guided, not autonomous
When you do build something new, a guided form walks you through it step by step. AI runs in the background to rank matches from your library, but you always fill out the form yourself and nothing becomes a draft until you confirm it. See the two paths through CRAFT.
CRAFT vs. the Status Quo
| Scattered Scripts | CRAFT | |
|---|---|---|
| Authoring | Write code from scratch | Pick from your team’s library, or use a guided form |
| Review | None — run and hope | Mandatory draft review + safety preview |
| Safety | Trust the author | Fail-safe preview showing exactly what leaves your machine |
| Sharing | Copy to shared drive | Governed promotion with duplicate detection |
| Versioning | Filename suffixes | Versioned, signed, and locked — releases never change |
| Deprecation | Email: "don't use that one" | Formal deprecation with migration paths |
| Data handling | Unknown | All data leaving your machine is declared and reviewed before execution |
Neither Script Sprawl Nor Reckless AI Generation
There’s a middle position between unmanaged scripts and unbounded AI. CRAFT lives there.
Option A
Unmanaged Scripts
No safety preview. No signatures. No library hygiene. No way to surface reuse. Knowledge walks out the door when authors leave.
CRAFT
Bounded Automation
AI proposes. The deterministic compiler and the fail-safe safety preview decide. You approve. AI is used where it earns its keep — and a deterministic safety system everywhere it doesn’t.
Option C
Reckless AI Generation
Black-box code in your project. No review. No reproducibility. Hallucinations land directly in your model. Library fills with junk.
What the Safety Preview Protects You From
The same safety preview that catches missing dependencies and unsafe operations also catches the things buyers actually fear from AI-assisted automation.
AI misinterpreting your request
Rule-based parsing runs first. AI fills in classification gaps only as an advisory ranking signal. You always fill out the guided form yourself, and nothing becomes a draft until you confirm it.
Wrong target or scope
The safety preview shows the expected inputs, outputs, and required host context in plain English — before anything runs.
Unsafe side effects
The safety preview cross-checks declared side effects against what the host APIs actually do. A claim of “read-only” that touches a write API gets flagged.
Unreviewable AI drafts
AI proposes; the deterministic compiler validates; humans review. Nothing reaches execution without a human acknowledging the safety preview.
Silent data leaving your machine
The data-disclosure panel is mandatory and present even when every field is “none.” Telemetry and host-context sharing default off.
Generated junk & near-duplicate sprawl
Similarity checks catch near-duplicates at publish. Abstraction discovery proposes consolidation when patterns repeat — under human approval.
For Every Role on Your Team
Engineers & Designers
Stop doing repetitive tasks by hand. Pick a starting point from your team’s library, or use a guided form to describe what you need — CRAFT turns it into a reusable automation that runs the same way every time. No coding required for common tasks.
CAD Managers
Control what automations your team can access. Approve promotions, deprecate outdated tools, and prevent duplicate scripts from proliferating. Learn more about governance tools.
IT & Security
Local execution only. No cloud data processing. All automations signed and locked. Everything leaving your machine is disclosed before execution. Telemetry off by default. Read the full security report.
VDC Directors
CRAFT prevents the automation sprawl that creates tech debt. Governed promotion, audit trails, and library health monitoring mean you can scale automation without losing control.
See How It Works
Walk through the full automation lifecycle — from describing a task to running it in your CAD host.