Custom software for contractors and engineering firms: quantity take-off straight from IFC, automated model checks, Revit plug-ins and web apps your site team can open on a tablet. Built by a BIM engineer who writes the code.
Software for the work your team keeps doing by hand.
Every firm has the same hidden spreadsheet: quantities, checks and reports rebuilt manually after each model revision. That is exactly what I automate.
From tender to handover: less retyping, fewer surprises on site, quantities you can defend.
Estimating
Quantity take-off straight from the model
Measured quantities per element, level and cost code, exported to Excel, Presto or your ERP. Re-run it on every model revision instead of re-measuring.
Your cost codes and units
Revision-to-revision diff
Works with any IFC
Site
A model your site team actually opens
A web viewer that runs on a tablet: colour by phase, status or subcontractor, scan a QR on site and see the element’s data. No licences, no installs.
Phone & tablet ready
QR codes on elements
Offline-friendly
Planning
Progress and 4D colouring
Import your schedule (MS Project, Primavera or a CSV), colour the model by planned vs. actual and share a link with the client in the weekly meeting.
Planned vs. actual
Weekly snapshots
Shareable link
Procurement
Work packages per trade
Split the model into packages with rules, then generate quantities, IFC extracts and drawings per subcontractor automatically.
A browser IFC application built on IFCLite and WebGPU. It is a small sample of what I build for clients, and it is already useful on its own. Your file never leaves your computer.
Connect your BIM models to your business data. ERP integration, document management, custom SQL databases and REST APIs.
Revit ↔ ERP integration
Custom REST APIs for BIM data
SharePoint / Procore / Autodesk Docs connectors
Data consistency pipelines
SQL ServerREST APIs.NETWeb
Why JidokaBIM
Automation with a human touch.
自働化Jidoka is a cornerstone of the Toyota Production System: a machine that stops the moment it detects a defect instead of producing bad parts at scale.
That is how I build software for construction. It understands your workflow, checks the data as it goes, and tells your team when something does not add up, before it reaches the site.
IF
Ignasi Fabrat
Industrial Engineer · AEC software developer · Barcelona
Industrial Engineer (MSc, UPC Barcelona). I know what a cost code, a pour sequence and a fire compartment are, so you don’t have to translate.
Automation that stops on errors
Every tool validates its input and flags inconsistencies instead of silently pushing bad data through your project.
You talk to the person writing the code
No account managers, no handoffs. Weekly demos on your own models and full transparency at every step.
Projects delivered
24+
Projects delivered
Years building AEC software
5+
Years building AEC software
Countries: Spain, UK, Canada
3
Countries: Spain, UK, Canada
Reply time
24 h
Reply time
How I work
From first call to working tool, without surprises.
01
30–60 min · free
Discovery call
We walk through the workflow that hurts, on your own models and spreadsheets. I document everything and tell you honestly if software is the right fix.
02
2–5 days
Specification
A written spec with scope, architecture, timeline and a fixed price. You know exactly what you get before anything is built.
03
2–12 weeks
Build & weekly demos
Iterative builds with a demo every week on real project data. A focused tool usually reaches a first working version in 2–4 weeks.
04
30-day support
Handoff & support
Deployment, documentation and team onboarding. Handoff includes the source code and an architecture guide, so you are never locked in.
FAQ
Questions I get every week
Missing yours? Ask it on the call: it is free and there is no obligation.
Both. Contractors usually come to me for quantity take-off from the model, site viewers, progress tracking and subcontractor packages. Engineering firms for automated model QA, drawing production and keeping calculations and models in sync. The common thread: data that already exists in the model and is being retyped by hand.
A small, well-defined tool that removes one painful manual step: for example, a quantity export in your cost-code format or an automated pre-submittal check. It is scoped in the specification phase with a fixed price, and a first working version usually arrives in 2–4 weeks, so you see value before committing to anything bigger.
No. Anything that exports IFC (IFC2X3, IFC4 or IFC4.3, including bridges, roads and rail) works with the web tools, as the free viewer on this site shows. For deeper automation inside the authoring tool I also work with the Revit, AutoCAD and Civil 3D APIs.
Wherever you decide. Browser tools like the IFC viewer run entirely on your computer, so files are never uploaded. Server-side tools can be deployed on your own infrastructure, your Azure or AWS tenant, or connected to Autodesk Construction Cloud.
JIDOKA (自働化) is a core principle of the Toyota Production System: autonomous automation that stops when something goes wrong. Applied to BIM: software that understands your workflow and alerts you to errors, rather than blindly processing incorrect data. Every tool I build includes intelligent validation, not just automation.
No. Web-based BIM tools I build run entirely in the browser using open standards (IFC, web-ifc). Your team can view models, track issues, and access data without any Autodesk license. For tools that automate Revit itself (add-ins, Design Automation), a Revit or APS license is required.
A focused add-in (single workflow, clear scope) typically takes 2–4 weeks from spec to delivery. Complex enterprise plugins with UI, database integration, and multi-user access can take 6–12 weeks. I always start with a scoping session to define the exact spec before committing to a timeline.
Fully remote. I have worked with teams in Spain, the UK (London), and Canada (Toronto). Time zones up to UTC+6 are manageable. All collaboration is async-first: detailed specs, video updates, and structured handoffs. If you are in Barcelona, in-person sessions are also possible.
Use native Revit API when you need to write back to the Revit model, manipulate parametric families, or run complex automated workflows inside Revit. Use IFC-based tools when your team needs browser access without Revit, for cross-authoring coordination (Revit + Tekla + ArchiCAD), or for read-only viewing, QA, and reporting pipelines.
Contact
Tell me what your team still does by hand.
Send a short brief or book a discovery call. I reply within 24 hours with a first opinion on how I would solve it, and what it would roughly take.