Service · Web development

Custom BIM software development.

Custom software around your BIM model: viewers, plug-ins for Revit and Tekla, IFC parsers, integrations with ERP, production or asset management. We don't design the building — we build the software that unlocks the BIM data and puts it to work in your organisation.

IFC & BCFRevit / Tekla plug-insBIM to productionERP integrations

BIM is data, not drafting.

BIM — Building Information Modelling — is the digital twin of a building or piece of infrastructure: geometry, materials, relationships and metadata in a single model. Architects and structural engineers create that model in Revit, Tekla, Archicad or Rhino. The question then is: what do you do with that data?

We are not BIM modellers. We are a software company that processes BIM data, makes it accessible and connects it to the rest of your IT landscape. Think of a viewer for your clients, a plug-in that generates work orders from Revit, or an integration that loads a Tekla model into your ERP system. The data is already in the model; we turn it into usable workflows.

Our clients are contractors, prefab manufacturers, installation companies, property managers, infrastructure managers and software vendors in the construction sector. The common thread: they have a good BIM model and want to get more out of it than a nice picture in the meeting room.

In practice, we see four types of BIM challenges come up again and again. One: the model is well built in Revit or Tekla, but it only exists for the modeller themselves; the work planner, estimator or fitter cannot access it. Two: the model exists in multiple versions across disciplines and there is no reliable single source of truth. Three: the data is there, but has to be moved manually into Excel or onto paper before work can continue. Four: the model was handed over to the client on completion and never touched again, even though it should be adding value during asset management. For each of these patterns, the answer is software, not extra modelling hours.

What we build around BIM.

Three main areas in which we deliver custom software. In practice, a single project often combines them: a viewer with an ERP integration, or a plug-in that sends data to the production floor.

BIM viewers & portals

Custom 3D viewers and client portals

Web and mobile viewers where your team, clients or residents can view the model without a Revit licence. Built on xeokit, Three.js or the Autodesk Platform Services (APS / Forge), depending on performance requirements, model size and which metadata needs to be visible. Including section tools, measuring functions and an integration with your document management.

IFC viewerxeokit / Three.jsForge / APSBCF issues
Plug-ins & data extraction

Revit, Tekla and Archicad plug-ins

Plug-ins that pull data out of the modelling software and send it where you need it: a work planner exporting material schedules, an estimator retrieving quantities, or an integration that synchronises the Tekla model with your ERP every night. Written in C# for Revit/Tekla, in Python for Rhino/Grasshopper, or as an external IFC pipeline that never touches the modelling tool.

Revit C# add-insTekla Open APIRhino / GrasshopperIFC pipelines
Integrations

BIM to ERP, production and asset management

The heavier side: making BIM data available to your business processes. Linking model elements to order lines in your ERP, writing machining instructions to CNC machines or prefab lines, and delivering the as-built model to an asset management system or CMMS on completion. Much of this runs through smart API integrations that we help design.

BIM → ERPBIM → productionCOBie handoverCMMS integration

What you get.

A working solution that fits your landscape, not just a prototype. We deliver the software, the documentation and the handover to the team that will take it forward.

For many clients, BIM software does not stand alone: we often integrate with existing manufacturing software or the management system that is already running. We include that in the scope.

  • The application itselfViewer, plug-in, integration or dashboard: production-ready, with a staging environment and deployments via CI/CD.
  • Full codebase + documentationSource code in your own Git repository, architecture overview, API documentation and an incident runbook.
  • IFC and BCF supportWhere the model is central: import, export and mapping of IFC schemas (IFC2x3, IFC4) plus BCF issue exchange with the modellers.
  • User trainingSessions for your key users and a short manual for the people carrying out the work in the office or on site.
  • Maintenance and further developmentOptional: monitoring, security patches, support for new Revit or Tekla versions, and ongoing functional expansion.

Standards and technology.

Building BIM software is largely about making smart use of open standards instead of seeking out vendor lock-in. Our order of preference is clear: open formats wherever possible, vendor APIs where necessary, and parsing native file formats only as a last resort.

Open standards we support by default: IFC (Industry Foundation Classes) for geometry and metadata, BCF (BIM Collaboration Format) for exchanging issues with the modellers, and COBie (Construction Operations Building Information Exchange) for handover to facility management. For those who want to work with open BIM data without an Autodesk stack, we also use Speckle as a data layer.

Vendor platforms we integrate with: Autodesk Platform Services (APS, formerly Forge) for rendering Revit models in the browser and server-side processing, the Tekla Open API for steel engineering, Bentley iModel.js for infrastructure, and the Bricsys API where relevant. For 3D viewers in the browser, we choose between xeokit (open source, performant for large IFC files), Three.js (complete freedom, more custom work) and the APS viewer (the fastest route if you already have an Autodesk stack).

Existing SaaS we explicitly do not replace: Autodesk Construction Cloud / BIM 360, Trimble Connect, RIB iTWO, Bentley ProjectWise, Bricsys 24/7 and Solibri. For large multidisciplinary projects, those packages work well and are expensive to replicate. We build the add-ons, integrations or sector-specific workflows that such a suite doesn't offer out of the box.

Who we build BIM software for.

Six situations where we add the most value. If you recognise one of these patterns, a conversation is a good fit.

Contractors

BIM to production

The model automatically generates your work preparation: material lists, work orders, machine instructions for the prefab line or CNC saw. No more retyping by hand, and no version conflicts between drawing and shop floor.

Property and facility management

BIM for management and maintenance

After handover, the BIM model is often put away in a drawer. We connect it to your CMMS or asset management system: faults pinpointed in the 3D model, maintenance history per object, warranty information and COBie data from the handover phase.

Structural engineers & architects

Tekla and Revit integration with ERP

Model elements become order lines in your ERP — Exact, AFAS, Microsoft Dynamics or your own system. Quantities, materials and positions stay in sync, including version control when the model changes between tender and execution.

Installation companies

BIM data for quotes and planning

For installers working on large projects: pull pipe lengths, numbers of fixtures or fittings directly from the BIM model for costing, planning and installation sequence. Often linked to our software for installation companies.

Manufacturers

Window frames, prefab, steel

Manufacturers producing to BIM specifications — window frames, prefab elements, steel structures. Order-to-production where every element is driven directly from the model, with traceability from engineering to delivery.

Infrastructure and utilities

GIS + BIM for public space

Roads, cables, water, sewerage. A combination of GIS data and BIM objects for network operators, with inspection apps linked to location and object — and an audit trail that meets the client's requirements.

Not sure about a large project yet?

Test your idea first: a working prototype in 1 day

With OneDayBuild, we make your idea tangible in a single day for €1,150, so you know whether further development is worth the investment. Decide to go ahead with the full build? Then we deduct the cost in full.

View OneDayBuild →

BIM modelling versus BIM software.

A confusing point in many initial conversations: people searching for "BIM modelling software" often use the term for two completely different things. On the one hand, the modelling itself — Revit, Tekla Structures, Archicad, Rhino — where geometry is drawn and populated with parameters. On the other hand, all the software that works with that model: viewers, integrations, pipelines, reports.

We work in the second field. For the first category, we refer you to BIM modellers and construction consultants we regularly collaborate with on projects. For the second category — everything that comes after the modelling — we are the party that builds custom software for you.

That distinction is worth getting clear up front. A project often starts with the question "can you build our BIM platform?", and only in conversation does it turn out that the real need is viewer functionality, an ERP integration or a reporting layer on top of an existing model. Getting that scope clear in the first session saves a lot of needless discussion later and ensures we are the right partner before we start on anything.

If your need is broader, for example a full manufacturing industry platform of which BIM is one part, or the digitalisation of an installation company, then BIM software is often just one of the building blocks in a larger project. We can deliver that bigger picture too, but we would start with a separate scoping phase at organisation level.

How a BIM software project works.

1

Model analysis and use case

We review a representative model: what kinds of objects it contains, how structured the data is, and which parameters are always filled in and which are not. From that comes an honest assessment of what is realistic and where the modelling conventions need work first.

2

Scope and architecture

A workshop with your work preparation team, BIM coordinator and IT. Together we decide which flow to build first, how it fits into your landscape, which standards we follow (IFC, BCF, COBie) and which integrations take priority.

3

Building in sprints

A working piece every sprint: a first viewer, a first plug-in that exports data, a first integration that creates test orders. You test with a real project, not dummy data. You can adjust course every sprint.

4

Pilot on a real project

Before we roll out widely, the solution first runs on a single live project. That is where the real edge cases surface, such as deviating model conventions, missing parameters and production exceptions, and we resolve them before the rest of your organisation starts using it.

5

Rollout and further development

A broad rollout across projects and users, with training and a clear point of contact for incidents. After that, we continue development at the pace of your working process: new Revit or Tekla versions, additional integrations, or new reports if they turn out to be needed.

Frequently asked questions.

What clients usually want to know first. If we have missed one, just ask us.

Do you also do the modelling yourselves?
No. Creating the BIM model (geometry, parameters, families) is the work of an architect, structural engineer or BIM modeller. We are the software partner that uses the model: viewer, integration, plug-in or automation. If you do not yet work with a modeller, we can refer you to parties we have worked with on several projects.
Do you support IFC, or do you only work natively?
Both. IFC (IFC2x3 and IFC4) is our standard for open BIM, and we build parsers, viewers and pipelines on it. For projects where performance or specific parameters require it, we also read native Revit files via APS/Forge or Tekla via the Open API. We use BCF for issue exchange with the modellers.
Which packages can you integrate: Revit, Tekla, Archicad?
We have experience with Revit (C# add-ins and the APS API), Tekla Structures (Open API and IFC export), Archicad (IFC and API), Rhino/Grasshopper (Python and .NET) and Bentley tools via IFC. For steel engineering in particular, Tekla-to-ERP is a recurring project; for architecture and building services we see more Revit work.
Can you link BIM data to our ERP?
Yes. We have built integrations between BIM models and packages such as Exact, AFAS, Microsoft Dynamics and industry-specific construction ERPs. The practical challenge rarely lies in the technology but in the mapping: which model object belongs to which order line, how we handle version differences, and who owns which data.
Do you replace Autodesk Construction Cloud or Trimble Connect?
Usually not. For large multi-disciplinary projects, packages such as Autodesk Construction Cloud, Trimble Connect, RIB iTWO or Bentley ProjectWise work well, and they are expensive to replicate. We often build add-ons: a custom viewer for clients, a specific integration the package doesn't offer out of the box, or a lightweight CDE for projects that don't justify a full enterprise suite.
Can we use BIM for the management phase, not just during construction?
That is a large part of our work. We link the as-built model to a CMMS or asset management system, so maintenance engineers can see faults in 3D, maintenance history is available per object, and the COBie data from handover actually gets used. This often goes hand in hand with our facility management software.
What determines the cost of a BIM software project?
Three factors weigh the most: the quality and consistency of the model data (dirty data prolongs every project), the number of integrations with other systems (one ERP or five), and the degree of automation (export only vs. full order-to-production). In an initial conversation, we'll work out an honest estimate together.
How long until we can go live?
A first viewer or plug-in can be up and running within a few sprints. A full BIM-to-ERP integration or order-to-production pipeline is a multi-sprint project with a pilot phase. We start small and scale up at a pace your organisation can handle.

Talk to us about your BIM challenge.

A no-obligation introductory call of half an hour. We'll listen to your workflow, which modelling packages are involved and which integrations you're looking for, and give you useful direction, even if it turns out we're not the right partner.

Edit content