CAD-grade output that engineering can sign off on. Permit-ready package the AHJ won't kick back. Cost model and crew handoff baked into the same source. One design, three outputs, zero translation.
Drag-and-drop layout. AI render generation. One-click export to deal room or proposal.
Sales designs in PowerPoint, engineering redoes it in CAD, the AHJ kicks it back, and the crew builds something else. Deployment Design collapses that chain.
The six capabilities that make this module work end-to-end. Pick any one as your starting point — they compound.
Components, conduits, equipment — every drop-in respects clearance, code, and capacity. Rule violations flagged at design time, not site time.
LiDAR, drone scans, satellite imagery, parcel data — all importable as a base. Design on top of the actual site, not a stylized drawing.
Every component carries its cost (from Cost Engine) and install hours (from job-costing data). Design changes update margin in real time.
Single-line, three-line, site plan, equipment list, structural calcs — exported as the AHJ-specific package on request.
Designs route to the licensed engineer for stamp. Comments, redlines, and the audit trail of who approved what — all in-app.
What ships to the crew is the same canonical design — same BOM, same drawings, same install instructions. No translation, no drift.
From the address, the design surfaces the site. From the design, three packages export at once: AHJ-specific permit, BOM-costed proposal, crew-facing job package. Same source. No drift.
Parcel, satellite, LiDAR, AHJ rules — loaded with real geometry and real codes.
< 30sComponents carry cost, install hours, code constraints. Violations flag immediately.
RealtimeRoutes to licensed PE for stamp. Comments, redlines, version history all in-app.
Same dayPermit pack to AHJ. Costed BOM to sales. Crew package to field. One source.
1-clickEach AHJ has its own rule set — setbacks, fire access lanes, equipment clearance, signage. Deployment Design knows them all. Drop a panel where the local code says you can't, and the editor blocks the placement at design time.
1,400+ jurisdictions modelled. New rules ingest as AHJs publish them. Your design always reflects today's code, not last year's.
# AHJ Rule Set · Charlotte-Mecklenburg, NC jurisdiction "charlotte-mecklenburg-nc": # NEC 2023 base + local amendments base_code = "NEC-2023" amendments = ["CM-AMD-2024-04"] # solar PV setbacks rule fire_access: setback_ft = 3 # 3' from ridge apply_to = ["residential"] rule rapid_shutdown: require "NEC-690.12-compliant" label_inverter = true rule esS_clearance: setback_ft = 3 # 3' from windows setback_door_ft = 5 # permit pack template permit_template = "CM-PV-RES-2024" reviewer_email = "permits@..."
Nearmap, EagleView, Google — refreshed on capture cadence.
Native export to AutoCAD-compatible formats. Engineering stays in their tools.
1,400 jurisdictions modelled. Permit packs in the AHJ's preferred format.
Job package syncs to ServiceTitan, FieldEdge, native crew app.
We'll design it, cost it against your stack, render the permit pack, and route it for engineering stamp — all in one session, on your data.