Browse categories
English
$
USD
Connect to your AI
I will build a custom web app that generates cad drawings and dwg files
Evan H
About this gig
$35 to start. Browser-based CAD tools for industries between desktop seats and spreadsheets. Engineer (BSE, Case Western Reserve, EIT) who co-founded a solar design automation company. Built: utility solar layout app, signed browser-to-AutoCAD bridge, Autodesk integrations, geometry engines. Your team uses it in a browser with no installs, no CAD licenses per seat. Real CAD output (DWG, PDF, IFC, not screenshots). Your rules encoded. Process: scoping prototype, then milestones with deployed URLs. I'll say if you need a desktop plugin or different specialist.
Get to know Evan H
Evan H
CAD Automation and Platform Developer
- FromUnited States
- Member sinceAug 2022
- Avg. response time11 hours
Languages
English
I build production CAD automation: AutoCAD plugins in C# .NET and AutoLISP, natural-language CAD tooling, web control planes, cloud CAD execution and ML-backed solar design automation. Custom commands, palettes, drawing generators, batch processors, equipment databases, string-sizing tools and layout engines. My own build-and-test automation ships reliable tools in days, with source code, installers and support for AutoCAD 2018-2026.
My Portfolio
Other Software Development Services I Offer
FAQ
Do I need AutoCAD licenses for my users?
No. The tool runs in the browser. If you need round-trips to desktop AutoCAD, I've built signed bridges that do exactly that, and we scope it explicitly.
Can it output real DWG files?
Yes, via Autodesk Platform Services or open libraries depending on your licensing needs; the scoping prototype settles which.
Who owns the code?
You do, once the order completes. Delivered as a repo you control plus a deployed instance.
Why is there no flat quote for my whole project on this page?
Custom CAD tools vary enormously. The Basic package exists so scope gets locked in before the full build quote, with no surprises later.
Can the tool be extended or customized after delivery?
Yes, that is the normal path: most tools grow features after the first release. You own the source and the deployment, so you can extend it yourself, or book a follow-up order for new rules, formats, or workflows. Changes are scoped and priced before any work starts.
