I write the tools, not just the model
Every MEP project runs on the same handful of actions done thousands of times. None of it is difficult and none of it is where the value is — but it eats the day. So I build the tools that do it instead, and the team’s hours go to coordination.
Four languages, one reason
Revit add-ins in C#
Commands on the ribbon, built on the Revit API with WPF interfaces, for the jobs a drafting team repeats every week — view and graphics control, MEP routing and elevation work, coordination checks, dimensioning and tagging.
One codebase builds for every Revit release a project is on, so the team is never split across versions.
pyRevit and Python
The faster path for a tool that is needed this week: a script that reads the model, finds what is wrong and writes the answer back, without waiting on a build and an installer.
Dynamo
Where the job is a one-off piece of data work on a live model and a graph is the honest tool for it — bulk parameter work, take-offs, checks a modeller can read and adjust themselves.
AutoLISP
Where the work is still in AutoCAD. This is where the automation started, and it is still the right answer for a drawing office that lives in DWG.
Where it is going: an AI platform that turns a sentence into a checked, reversible, logged change in a real model. Open source, and still in development.
Heron AIA tool a team can rely on, not a clever trick
A personal script helps one person. The difference between that and something a company can actually run on is not the code — it is everything around it.
An installer, not an email
The whole drafting team runs the same version of the same tools, installed the same way. Nobody is copying a file into a folder and hoping.
One codebase, every release
Revit changes its API between versions — units, parameters, element ids, dimensions. One codebase handles all of it, so a project on an older release is not left behind.
Versioned and written down
Every change has a version number and a note saying what it does. When something behaves differently from last month, there is a record of why.
Built around the team’s own standard
A tool that enforces somebody else’s naming is a tool nobody uses. These are built around the templates, the parameters and the conventions the team already has.
Reversible, and quiet about it
Anything that changes a model does it in one undo step, says plainly what it is about to do, and leaves the model in a state a person can check.
Tell me the job you are tired of doing
I take automation work remotely — scoped up front, version-controlled, and handed over with documentation. If a tool is not worth building for your workflow, I will tell you that instead.
Looking for an MEP BIM Coordinator?
Doha, Qatar · transferable QID with NOC · able to join within days.