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 BIM data and puts it to work within your organisation.
BIM, Building Information Modelling, is the digital twin of a building or 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 partner that processes, unlocks and connects BIM data 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 asset owners and construction software vendors. The common thread: they have a good BIM model and want to get more out of it than a nice image in the boardroom.
In practice, we see four recurring types of BIM challenge. One: the model is well built in Revit or Tekla, but only the modeller can use it — the planner, estimator or site engineer 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 manually exported to Excel or paper before the work can proceed. Four: the model was handed over to the client at completion and never touched again, even though it should add value during operation. For each of these patterns, software is the answer — not extra modelling hours.
Three main directions in which we deliver custom work. In practice, one project often combines them: a viewer with an ERP integration, or a plug-in that sends data to the shop floor.
Web and mobile viewers where your team, clients or residents can view the model without a Revit licence. Built on xeokit, Three.js or Autodesk Platform Services (APS / Forge), depending on performance requirements, model size and which metadata needs to be visible. Includes section tools, measurement functions and integration with your document management.
Plug-ins that extract data from the modelling software and pass it on to where you need it: a works planner exporting material lists, a calculator 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 without touching the modelling tool.
The heavier side: unlocking BIM data for your business processes. Linking model elements to order lines in your ERP, writing machining instructions to CNC machines or prefab lines, and at handover delivering the as-built model to an asset management or CMMS system. Much of this runs through smart API integrations that we co-design with you.
A working solution that fits your landscape, not just a prototype. We deliver the software, the documentation and a handover to the team that will take it forward.
For many clients, BIM software doesn't run in isolation: we often integrate with existing manufacturing software or the management system already in place. We include that in scope.
Building BIM software is largely about using open standards cleverly rather than seeking vendor lock-in. Our order of preference is clear: where possible through open formats, where necessary through vendor APIs, and only as a last resort parsing native file formats.
Open standards we support as standard: IFC (Industry Foundation Classes) for geometry and metadata, BCF (BIM Collaboration Format) for exchanging issues with modellers, and COBie (Construction Operations Building Information Exchange) for handover to facilities 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 Revit model rendering in the browser and server-side processing, the Tekla Open API for structural engineering, Bentley iModel.js for infrastructure, and the Bricsys API where it fits. For 3D viewers in the browser, we choose between xeokit (open source, performant for large IFCs), Three.js (complete freedom, more custom work) and the APS Viewer (the fastest route if you already run an Autodesk stack).
Existing SaaS we deliberately don't replace: Autodesk Construction Cloud / BIM 360, Trimble Connect, RIB iTWO, Bentley ProjectWise, Bricsys 24/7 and Solibri. For large multidisciplinary projects these packages are excellent and expensive to replicate. We build the add-ons, integrations or industry-specific workflows that such a suite doesn't provide out of the box.
Six situations where we add the most value. If you recognise one of these patterns, a conversation is worth having.
Pre-construction planning is generated automatically from the model: material schedules, work orders, machine instructions for the prefab line or CNC saw. No more manual retyping, and no version conflicts between drawing and shop floor.
Once handed over, the BIM model often ends up gathering dust. We connect it to your CMMS or asset management: faults on site linked to the 3D model, maintenance history per object, warranty information and COBie data from the handover phase.
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.
For installers working on large projects: pull pipe lengths, fixture counts or fitting quantities directly from the BIM model for costing, scheduling and installation sequencing. Often combined with our software for installation companies.
Manufacturers producing to BIM specifications, such as window frames, prefab elements and steel structures. Order-to-production, where each element is driven directly from the model, with traceability from engineering through to delivery.
Roads, cables, water, sewerage. Combining GIS data with BIM objects for network managers, with inspection apps linked to location and object, and an audit trail that meets the client's requirements.
With OneDayBuild, we turn your idea into something tangible in one day for €1,150, so you can see whether further development is worth the investment. Decide to go ahead with the full build? Then we credit the full cost.
Explore OneDayBuild →A point of confusion in many exploratory conversations: the term "BIM modelling software" is often used by searchers for two entirely different things. On one hand, the modelling itself, such as Revit, Tekla Structures, Archicad or Rhino, where geometry is drawn and filled with parameters. On the other hand, all the software that works with that model: viewers, integrations, pipelines and reporting.
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 matters in practice, so it's worth being clear on it upfront. A project often starts with the question "can you build us a BIM platform?", and only in the conversation does it become clear that the real need lies in viewer functionality, an ERP integration or a reporting layer on an existing model. Clarifying scope in the first session saves a lot of unnecessary discussion later and makes sure we're the right partner before we start on anything.
If your question is broader — for example, a complete manufacturing industry platform of which BIM is one component, or digitalisation of an installation company — then BIM software is often one of the building blocks in a larger project. We can deliver that larger whole too, but we then begin with a separate scope determination at organisational level.
We examine a representative model — what objects it contains, how the data is structured, which parameters are always filled in and which are not. This gives an honest assessment of what is realistic and where work on modelling conventions needs to start first.
A workshop with your project preparation team, BIM coordinator and IT. Together we determine which workflow we build first, how it fits your landscape, which standards we follow (IFC, BCF, COBie) and which integrations take priority.
A working piece of software 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.
Before rolling out widely, the solution first runs alongside one live project. This is where the real edge cases surface — deviating modelling conventions, missing parameters, production exceptions — which we resolve before the rest of your organisation starts working with it.
A wider rollout to projects and users, with training and a clear point of contact for incidents. After that, ongoing development paced to your working process: new Revit or Tekla versions, additional integrations, or new reports where they prove necessary.
What clients usually want to know first. If you're missing something, please feel free to ask us.
A non-binding half-hour introductory call. We listen to your workflow, which model platforms are involved and which integrations you're looking for, and give you direction you can use, even if it turns out we're not the right partner.
Appfront uses cookies and similar technologies to keep the website working properly, for analytics and for marketing. You choose what you allow. Read more in our privacy policy.
