Revit add-ins
Ribbon tools, dockable panels and background automation for Revit 2023–2027. Shared parameters, view filters and templates, DirectShape geometry, and transaction-safe model edits that undo cleanly.
The tools on this site exist because we needed them first. When the thing you need doesn’t exist either, we build it the same way, for you — a Revit or Navisworks add-in, or a standalone Windows app when the work doesn’t belong inside a host application at all.
Everything here is something we already run in production — not a capability deck.
Ribbon tools, dockable panels and background automation for Revit 2023–2027. Shared parameters, view filters and templates, DirectShape geometry, and transaction-safe model edits that undo cleanly.
Manage-only plugins — clash workflows, selection sets, quantity takeoff and model automation driven from the Navisworks API.
Lighter-weight Revit tooling when a compiled add-in is more than the job needs, and faster for your own team to iterate on.
WPF or Python desktop tools for the work that never opens a host application — receiving, logistics, the tasks still done by hand.
Accounts and trials, per-seat or floating-pool licensing, metered or prepaid billing, code-signed installers and version gating — the same platform our own tools run on.
Plenty of companies already have developers. What they usually don’t have is someone who has already shipped, signed and licensed an Autodesk add-in. We work alongside in-house teams on the parts that are easy to get wrong.
Where the Revit or Navisworks API will fight you, and how to structure around it before the code gets written.
One codebase across Revit 2023–2027 without four forks — the build isolation, API shims and runtime targeting that make it hold.
Authenticode signing, timestamping, installer packaging, and the antivirus and Mark-of-the-Web problems that silently stop .NET add-ins loading after download.
Trials, seats, floating pools, offline tolerance and revocation — what can be enforced on the client, and what has to live on a server.
Work is scoped and priced one engagement at a time.
Tell us the workflow and the software you run. We’ll tell you whether we can help — and say so plainly when we can’t.
What it does, which versions it targets, and what “done” means — agreed before anything gets built.
Built and tested against the Revit or Navisworks releases you actually have installed, not only the newest one.
A signed installer your IT department will accept and a written manual. Once the project is complete, we hand over the source code — so you are never locked to us to keep it running.
Send the workflow, the software you run, and roughly when you need it. First call is 15 minutes, no sales script.
Start a conversation