Services
The client work: automation, scan-to-BIM, plug-in development, coordination and visualization. It is where we meet the problem in its real form, on real projects, with real deadlines.
It tells us what is worth building.
Models get better every year. The decisions behind them still live in email, in meetings and in people's heads. ZERO.BIM exists to close that gap - with automation where it helps, and with our own tools where nothing suitable exists.
ZERO.BIM does two things, and they feed each other. Neither would be as good on its own.
The client work: automation, scan-to-BIM, plug-in development, coordination and visualization. It is where we meet the problem in its real form, on real projects, with real deadlines.
It tells us what is worth building.
The tools we build ourselves - the Scan-to-BIM plug-in, 0.Agent, Family Viewer - and, above all, TOBiE. Built once, used everywhere, independent of any single project.
It makes the services faster than they could otherwise be.
We founded TOBiE. It is the second eye - looking further than any single client project ever could.
A typical delivery team runs somewhere between eight and twelve disconnected applications. Every boundary between them is a place where information is translated, and every translation is a place where something is lost. We spent years working around that gap one client at a time, and it became obvious the gap itself was the thing worth attacking.
TOBiE is that attempt. A browser-native environment for open BIM: nothing to install, no proprietary format holding your data hostage, IFC as the native language rather than an export option. Authoring, viewing, clash detection, validation, coordination, digital twin and XR - in one place, all speaking the same standards.
It is under active development with a dedicated engineering team, and it is where a great deal of our thinking ends up. The services pay for the present. TOBiE is the argument about the future.
No workstation requirement, no licence server, no version drift between team members.
IFC 4.3, ISO 19650, IDS and BCF are the working format, not something bolted on at export.
Authoring through to operations, so information never crosses a vendor boundary to stay useful.
Built by a dedicated team, with modules shipping progressively rather than in one release.
Nobody stands between the person who scoped your work and the person who does it. Questions get answered by someone who knows the answer.
Every model we deliver carries a note of what was assumed and where confidence was low. It is the same principle the whole company is built on.
The workflow audit exists so nobody has to commit to a project to find out whether we are useful.
Source code, scripts and documentation are handed over. Nothing we build for you depends on us still being around.
Tell us what you are trying to fix. We read everything and reply ourselves.
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.