BIM workflow automation
We find the repetitive work inside your process and remove it - batch parameter edits, sheet generation, model audits, exports that used to eat an afternoon.
ZERO.BIM builds the automation, plug-ins and scan-to-BIM tooling that keep reasoning inside the model - from the first sketch through to the day someone has to maintain the building.
Surveys are captured digitally. Models are federated. Handovers happen electronically. Yet the information still arrives in pieces, and the reasoning behind it usually does not arrive at all.
Everything we do sits in that gap.
We find the repetitive work inside your process and remove it - batch parameter edits, sheet generation, model audits, exports that used to eat an afternoon.
Registered point clouds turned into information-rich models. Surveyed once, modelled properly, delivered with the data attached rather than bolted on afterwards.
From a single button to a full ribbon. We build the add-in, package the installer, write the docs and train the people who use it daily.
Discipline models, federation, clash resolution and issue exchange run to ISO 19650, with QA at every milestone instead of a scramble at the end.
Renders, walkthroughs and VR/AR/MR experiences generated from the same model you build with, so they never drift out of date.
A short, fixed-price workflow audit. We tell you what implementation level you are genuinely operating at, and what it would take to move up one.
The platform we founded. A browser-native environment for open BIM, built on the same argument this whole site makes: the model should carry its meaning. It is where a great deal of our engineering goes.
Every square is one element. A filled square carries what somebody downstream will actually ask for - what it is, what it is made of, how it performs, and who to call when it fails.
Illustrative - the shape of the problem, not a measured figure.
Alongside client work we build our own software - plug-ins that turn point clouds into elements, an assistant that answers questions inside Revit, a family manager that saves a day a week. We build them because the gap we hit on one project is the same gap everybody hits, and a tool closes it once for the whole industry rather than once for us.
Three open standards come up in almost every conversation about openBIM, and they are regularly treated as interchangeable. They are not. Each one answers a different question, and a project that uses all three is doing something quite different from a project that only exchanges files.

A drawing shows you where things are. A model knows what they are, what they are made of, and who is responsible for them when they stop working. Everything we build lives in the distance between those two sentences.
Illustrative. The city is invented and the identifiers shown are examples of the kind of information an element carries.
Tell us what your team is doing by hand and how you deliver today. We will tell you what implementation level you are genuinely operating at, where the hours are going, and what it would take to move up one.
The exports stopped bouncing back. What used to take most of a week now runs overnight, and we can see why every value is what it is.
We use a cookie that is strictly necessary to remember this choice. Preference and analytics cookies are optional and stay off until you turn them on. You can change your mind at any time from the foot of any page. See our cookie policy and privacy policy.