Plugin Development
Tools that run inside Revit, Tekla, Allplan or Archicad, using their APIs, so nobody has to export a model or learn a second application to get the benefit.
Services
Automate the Work Nobody Should Be Doing by Hand
Plugins that turn repetitive BIM tasks into one click workflows, running inside the authoring tools your team already works in: Revit, Tekla, Allplan and Archicad.
Get Started
What we build
A large share of design office time goes on work that follows rules somebody could write down. That is the work worth automating.
Placing components to a standard detail, generating drawing sets, renaming and renumbering, checking a model against an office standard: none of it needs judgement, all of it needs doing, and it lands on qualified engineers. We build the tools that take it off their desks, inside the software they already use rather than beside it.
Standards Compliance
Your office standards, naming conventions and detailing rules encoded into the tool, so the output is correct by construction rather than corrected in review.
Continuous Updates
Authoring tools change every year. We maintain what we build against new releases so a plugin does not quietly become the reason you cannot upgrade.
* On automated workflows, teams have reported drawing production several times faster. What a given office gains depends on how much of its work is rule based.
How we work on it
-
Find What Is Actually Repetitive
We sit with the people doing the work and watch how a project really moves through the office. Which steps repeat on every job? Where does the same correction get made twice? Not everything that feels tedious can be automated, and some things that can are not worth it. The output is a ranked list, with the effort and the payback next to each item.
-
Build Inside the Authoring Tool
We develop against the API of the software you use, so the tool appears where your team already is: a ribbon button, not a separate application. It reads your models, respects your templates, and writes back in a form the rest of your process understands.
-
Roll Out and Maintain
A plugin gets tested on live projects with the people who will use it, then rolled out across the office with the documentation to go with it. After that we keep it current as the authoring tools release new versions and as your standards move.
The point is not clever software. It is drawings out the door.
Automation in design offices fails when it produces output somebody still has to check line by line. We build so the result is trusted: rules taken from your own standards, tested on your own projects, with the cases the tool will not handle made explicit rather than guessed at.
- Runs inside the authoring tool, so nothing has to be exported or relearned
- Your office standards encoded, so output is right the first time
- Maintained against new releases, so automation never blocks an upgrade
Know which task is eating your team's week?
Tell us what your office repeats on every project. We will come back with an honest read on whether it is worth automating and what it would take.
