We build the add-ins your BIM team keeps wishing Revit had: tools that set up sheets in minutes, check models against your standards before they leave the office, and move clash and model data where it needs to go. Every tool is tested on your own models, and you own the source code.
What our BIM tools have changed for clients
Measured on live projects, not in demos. The case studies further down explain how each result was reached.
70%
less design time for a European scaffolding firm, after we automated its CAD to Revit pipeline
50%+
faster model sync and structural reporting, through a Revit plugin connected to BIM 360 and ACC
46%
less rework on a Qatar infrastructure project, with Revit and Navisworks clash issues kept in sync
MEP
models validated against building code rules automatically, before drawings are issued
A BIM plugin development company writes software that runs inside the tools your team already uses: Revit add-ins built on the Revit API, Navisworks plugins for coordination, AutoCAD and Civil 3D tools, and web applications on Autodesk Platform Services (APS). The aim is simple. Work your people repeat on every project should run the same way every time, in a fraction of the time.
We work with BIM managers, design technology leads, and engineering directors at architecture firms, MEP and structural consultancies, contractors, and AEC software vendors. We recommend starting with the one workflow that hurts most, proving the time saved, and then working through the rest of your AEC automation backlog one tool at a time.
A BIM plugin is a compiled add-in that loads inside a BIM application such as Autodesk Revit or Navisworks and adds commands, checks, or data connections the standard software does not provide. A Revit plugin is usually written in C# against the Revit API and appears on the Revit ribbon like a built-in tool. Unlike a Dynamo graph, it is versioned, tested, and deployed the same way on every workstation.
If any of these sound familiar, a plugin will likely pay for itself. Each one is a workflow our tools are built to take off your team's plate.
TodayA modeler spends hours creating sheets, placing views, and renaming everything to the office standard on each new project.
With a pluginSheets, views, and titles are generated from your template in one command and named correctly the first time.
TodayClash results are exported, grouped, captured, and pasted into reports by hand before every coordination meeting.
With a pluginClash tests run, group, and export to your report format automatically, and issues sync back into Revit where modelers fix them.
TodayNaming errors, missing parameters, and off-standard families are found late, often by the client or the contractor.
With a pluginModels are checked against your rules before they are issued, with a report that shows exactly what to fix and where.
TodayEngineers check MEP layouts against building code requirements manually, one clause at a time.
With a pluginRule-based validation flags code issues inside the model, so fixes happen before drawings go out.
TodayLegacy DWG drawings are redrawn in Revit by hand, layer by layer and block by block.
With a pluginLayers and blocks map to Revit families and categories automatically, with a log of anything that needs a human decision.
TodayQuantities and parameters are exported to Excel and retyped into cost, ERP, or reporting systems.
With a pluginModel data flows straight into Excel, SQL, Power BI, or your ERP, with nothing retyped.
Each tool below starts from one workflow that costs your team hours today. Where a topic has its own page, the link takes you to the detail.
Ribbon tools in C# on the Revit API for sheets, views, parameters, family placement, and model checks, built for architectural, structural, and MEP templates.
Explore Revit plugin development
Plugins on the Navisworks .NET API that run and group clash tests, export issues to your report format, and sync them back into Revit.
AutoCAD .NET and AutoLISP tools for drawing standards, batch plotting, and cleanup, plus Civil 3D tools for alignment, surface, and corridor data.
Explore AutoCAD plugin developmentProven Dynamo graphs rebuilt as compiled add-ins with a proper interface, error handling, and one-click deployment.
Explore Dynamo automationPlugins that map DWG layers and blocks to Revit families and categories, and log anything that needs a human decision.
Explore CAD to Revit pluginsBrowser model viewers, translation pipelines, and connections to Autodesk Construction Cloud and BIM 360 for documents, issues, and model data.
Extractors that send quantities, parameters, and element data to Excel, SQL databases, Power BI, or your ERP.
Explore BIM automationRule-based and machine learning checks that flag naming errors, missing parameters, and off-standard modeling, with a person approving every change.
Explore AI Revit automationAlso available
We can develop RhinoCommon plugins and Grasshopper components, including tools that pass geometry and parameters to Revit.
We can build Tekla Open API extensions for model queries, numbering checks, and drawing and report automation.
Custom software is not always the answer. This is how we advise BIM managers before they spend anything.
| Option | Best when | Watch out for |
|---|---|---|
| Off-the-shelf add-in | The task is common across the industry and a maintained tool from the Autodesk App Store, a commercial tool pack, or an open-source project such as pyRevit already does it well. | You adapt your workflow to the tool, and license costs grow with every seat. |
| Dynamo script | One person or a small team needs a quick automation and can maintain the graph themselves. | Graphs often break between Revit versions and depend on the person who wrote them. |
| Custom plugin | The workflow depends on your own standards, runs across many users or offices, or must connect to other systems. | A larger up-front investment, which pays back through repeated use on every project. |
If an existing tool already does what you need, we will say so in our proposal. If your Dynamo graphs are worth keeping, our Dynamo automation team can clean them up instead.
Each application exposes a different API, and the deliverable changes with it.
| Application | API and language | Typical plugin work | What you receive |
|---|---|---|---|
| Autodesk Revit (2021 and later) | Revit API, C# and .NET | Ribbon commands, model checks, parameter and sheet automation, family placement | Add-in DLL with .addin manifest, installer, full source code |
| Autodesk Navisworks | Navisworks .NET API | Clash test automation, issue grouping and export, search sets | Plugin DLL, clash reports in Excel or XML, source code |
| AutoCAD and Civil 3D | AutoCAD .NET API, AutoLISP, Civil 3D .NET API | Drawing standards, batch plotting, block and layer cleanup, alignment and corridor data | .NET plugin bundle or LISP routines, source code |
| Dynamo | Python, Zero Touch nodes in C# | Graph cleanup, custom nodes, conversion to add-ins | Documented graphs or a compiled add-in |
| Autodesk Platform Services (APS) | Viewer SDK, Model Derivative, Data Management, ACC and BIM 360 APIs | Browser model viewers, dashboards, document and issue sync | Web application, cloud deployment, source code |
| Rhino and Grasshopper | RhinoCommon, Grasshopper SDK | Geometry tools, custom components, Rhino to Revit data exchange | Plugin (.rhp) or components (.gha), source code |
| Tekla Structures | Tekla Open API (.NET) | Model queries, numbering checks, drawing and report automation | Extension or standalone application, source code |
When the goal is moving data between Revit and another platform rather than adding commands, our Revit interoperability team handles the file and system exchange.
Revit add-ins are compiled against a specific version of the Revit API. With Revit 2025, Autodesk moved that API from .NET Framework 4.8 to .NET 8, so add-ins built for earlier versions have to be rebuilt before they load in Revit 2025 and later.
Most firms run more than one Revit version at a time, because projects stay on the version they started in. We structure each plugin so one codebase produces a tested build for every version your offices use, from Revit 2021 on .NET Framework to Revit 2025 and later on .NET 8.
Autodesk ships a new Revit release every year. Under a support agreement, we rebuild your add-ins, replace deprecated API calls, and retest them on your templates before your offices upgrade.
Client names stay confidential. The work, the tools, and the results are real.
We sit with the people who do the work today and time the task we are replacing. The output is a short brief with inputs, outputs, and the standards the tool must respect.
We agree the ribbon layout, dialogs, and reports on a prototype before production code, while changes are still cheap.
We develop against your own sample projects, because real templates expose the edge cases generic files hide, and test on every Revit version you run.
You receive an installer, deployment notes for your IT team, user documentation, and the full source code.
Each new Revit release is rebuilt and retested, and new features are added, under a support agreement.
Our plugins run inside your own Revit installations and process models locally. Model data only leaves your network when a tool is designed to send it somewhere you choose, such as Autodesk Construction Cloud or your ERP.
Two plugins with the same name can differ by weeks of work once your templates, standards, and integrations are on the table. So we price defined plugin projects at a fixed cost after scoping, and the written proposal reaches you within 48 hours of your inquiry.
Fixed price after scoping
Best forOne defined tool or a small suite with clear inputs, outputs, and acceptance tests
Request proposal$18 to $55 per hour
Best forA standing backlog of tools, or a design technology team that needs extra hands
$15,000 to $40,000 per month
Best forMulti-tool programs, APS platforms, and rollouts across several offices
Quoted after scoping
Best forKeeping plugins working as Autodesk ships a new Revit version each year
Our developers work alongside BIM specialists who know Revit templates, families, and worksharing, so the tool fits how your team actually models.
The client owns the full source code and IP, so you can take development in-house at any time.
Plugins process models on your own machines. Nothing goes to our servers.
When a project needs a web viewer, a mobile field app, or an ERP connection, the same team builds it.
Building software since 2013, with 250+ apps and software products delivered and offices in Chicago, Oakville, New Delhi, and Dubai.
Common questions from BIM managers and engineering leads. Have a specific workflow in mind? Talk to our team about it.
Describe the task and the tools involved, and we will send a scoped written proposal within 48 hours.
Request Proposal