Custom Autodesk Add-in Development
Add-ins that live inside AutoCAD, Inventor, Revit, Civil 3D, Fusion and Vault: your own ribbon tabs, commands, dialogs and palettes that guide engineers through your process and automate the repetitive work.
Your workflow, built into the Autodesk interface
An add-in extends an Autodesk application from the inside. It loads with the product, adds its own ribbon panels and buttons, opens dialogs and dockable palettes, reacts to events such as document open, save or selection, and works directly with the model through the product API. For engineers, an add-in feels like part of the software rather than a separate tool.
ENGIMANDI designs add-ins around how your team actually works: guided product configuration, design checks while modelling, one-click drawing and BOM creation, lookups from ERP and standards databases, and custom panels that show the data engineers need. We focus on clear user experience, performance with large models, robust error handling and easy updates.
Related reading: custom CAD add-ins for engineering productivity and macro vs add-in vs plugin.
What you get
- Ribbon tabs & commands
- Dialogs & dockable palettes
- Event-driven automation
- Model API integration
- ERP & database lookups
- User settings & roles
- Logging & error handling
- Installer & updates
Add-ins for every Autodesk product
In-product tools built on official APIs.
AutoCAD & Toolsets
.NET add-ins with ribbons, palettes and custom objects for AutoCAD and its toolsets.
Inventor
Add-ins with ribbon tabs, browser panes and events for parts, assemblies and drawings.
Revit
External applications with ribbons, dockable panes and updaters for BIM workflows.
Civil 3D
Add-ins for alignments, corridors, surfaces and networks.
Fusion
Python and C++ add-ins with commands, palettes and CAM automation.
Vault
Explorer extensions with new commands, tabs and validation.
Add-in stack
Languages and frameworks we use.
Typical projects
- Product configurator panel inside Inventor
- Revit dockable pane showing room data from a database
- AutoCAD palette for standard details and blocks
- Design rule checks when a file is saved
- ERP stock and cost shown next to the model
- Fusion add-in for CAM template selection
How we build add-ins
Observe
How engineers work today.
Design
Commands, UI and data flows.
Build
Iterative releases with feedback.
Test
Real models, versions and users.
Deploy
Installer, training and support.
Add-in questions
What is the difference between an add-in and a plugin?
The terms overlap. We use "add-in" for tools focused on the in-product experience for your team, and "plugin" for packaged, distributable products that may span several Autodesk applications.
Will the add-in slow down the software?
We design add-ins to load quickly and do heavy work only when needed, and test on large models.
Can one add-in support several product versions?
Yes. We build and test for each version you use and keep code shared where possible.
Can users configure the add-in?
Yes. Settings, standards and rules can be stored in files or databases that administrators manage.
Do we get the source code?
Yes, with full ownership.