Services / Service line 01
Plugin & Custom Software Development
Tools your team opens every morning — built to survive real models, real deployments and the next version release.
02problem
The problem
A plugin that works on a demo file and a plugin that works on Monday morning are different pieces of software. The demo runs on a clean model, on one machine, with the developer standing next to it. The production tool runs on a federated model with fifty thousand elements, on forty workstations with locked-down admin rights, during a sync with central, in a firm that upgrades Revit every spring.
Most plugin projects do not fail on the idea. They fail on transactions, worksharing, installers, and the version migration nobody scoped. The functionality was demonstrated in week three and the tool was quietly abandoned in month nine.
We build the second kind. Since 2021 we have shipped more than 200 tools, and we still maintain our own commercial products in production — which means we carry the consequences of our own architectural decisions for years, not weeks.
03capabilities
What we build
Autodesk ecosystem
- Revit add-ins on .NET Framework 4.8 and .NET 8, WPF ribbon interfaces
- Modelling automation, family generation, parameter management
- View, sheet and documentation automation
- Numbering and renumbering engines, static and event-driven
- Batch and headless processing of RVT files
- Navisworks and AutoCAD automation
Steel, mechanical and manufacturing
- Tekla Open API tools and model-data extraction
- Siemens NX Open automation, including MBD and GD&T workflows
- SolidWorks API — server-side drawing generation, PDM integration, product configurators
- CAM and NC data preparation pipelines
Cross-cutting
- Rule-based validation and clash-preprocessing engines
- ERP, PLM and CRM connectors for engineering data
- Licensing, activation and update channels
- Signed installers and silent enterprise deployment
04where_it_breaks
Where it breaks
Six failure modes we scope for before the first line of code.
Transactions and worksharing
Sub-transactions, failure-handling and regeneration behave differently in a worksharing environment than in a single-user file. A tool that never gets tested against a sync with central will corrupt something eventually.
Version migration
Revit 2022 through 2024 run on .NET Framework 4.8; 2025 and 2026 on .NET 8; 2027 moves to .NET 10. API members get renamed and deprecated across the line. Deciding upfront whether you maintain one codebase with conditional compilation or several forks determines your support cost for the next five years. We treat 2027 as a complexity flag in every estimate rather than a footnote.
Scale
Filtered element collectors that are fine on a house become unusable on a hospital. Memory pressure, UI thread blocking, and a frozen ribbon that makes users force-quit Revit are not edge cases — they are the normal condition of production models.
Deployment
Per-machine installation, missing admin rights, antivirus quarantine of unsigned assemblies, add-in manifest placement, and a rollback path when a release goes wrong. This is where enterprise rollouts die, and it is almost never in the original scope.
Lifetime ownership
Autodesk ships a new API every year. The question is not whether your plugin breaks, but who fixes it, how fast, and under what agreement.
Handover
Documentation, build pipelines and a codebase that a different team can pick up. Clear IP terms mean this is never a hostage situation: intellectual property terms are settled in writing before development begins.
05stack
Stack and coverage
- Languages and runtimes
- C# / .NET (Framework 4.8, .NET 8, .NET 10), WPF, WinForms, Python, Node.js
- APIs
- Revit API, Tekla Open API, Siemens NX Open, SolidWorks API, Navisworks API, AutoCAD .NET API, DWG processing via ACadSharp and netDxf, Rhino/Grasshopper and Dynamo for prototyping
- Delivery
- MSI/WiX installers, code signing, silent deployment, update channels, GitLab CI and Azure DevOps pipelines
Version coverage
- Revit 2022
- 2023
- 2024
- 2025
- 2026
- 2027
06proof
Proof
Our own products, live in production
Distributed through our own portal at update.consedge.app.
Public references
Teams at Swinerton and Dusty Robotics use tools we built. Drawing generation work delivered with Teamvoy, our development partner.
200+tools shipped since 2021
Case — pending
Format: the client had X. It broke at Y. We built Z. The measurable outcome was W. Two to three per page, anonymised where required.
07engagement
How we work
- 01
Feasibility Review
A 30-minute technical session and a written verdict: what the API allows, where the risks are, what production costs.
- 02
Paid discovery
Scope, architecture and a phase plan. You own the output whether or not you continue with us.
- 03
Fixed-scope delivery
Phased, with a working build at the end of each phase. Fixed prices, not ranges.
- 04
Support retainer
Version releases, API migrations, user support.
A countersigned mutual NDA precedes any access to your repositories or model data, without exception.
08faq
Frequently asked
Which Revit versions do you support?
2022 through 2027. Because the line spans three .NET runtimes, we decide the single-codebase-versus-fork question during the Feasibility Review rather than after the first migration hurts.
Can you take over a plugin another team built?
Yes. We start with a Production Readiness Audit of the existing codebase, which tells you what it would cost to stabilise versus rebuild, before you commit to either.
Who owns the intellectual property?
This is agreed in writing before development starts, and the terms are explicit in the contract rather than assumed.
We already have a working prototype. Do we still need this?
That is the most common starting point. A prototype proves the idea is possible; the work that follows is transactions, scale, deployment and support. A Production Readiness Audit prices that gap precisely.
Do you work as a subcontractor under our brand?
Yes. White-label development and QA capacity under a partner’s brand is a significant share of what we do.
From prototype to production
AI made prototypes cheap. We make them ship.
A Feasibility Review is a 30-minute technical session with the engineers who would build it, followed by a written verdict: what the API actually allows, where it will break at scale, and what production costs. No obligation to proceed.
- Straight answers
- Written verdict
- Senior engineers, not account managers