Features
One model, the whole chain: validation → logbook → billing → site → export. Every section below exists in the software today — this is a list of what ships, not a wish map.
Validation: so the model can't lie
A model can look complete — and still lie to the takeoff. Doors with no dimensions filled in, elements with no storey, walls without base quantities: the eye can't see it, and the billing comes out wrong. So validation runs first, and its finding is not 'the model has errors' but a concrete list: which check, how many elements, and which setting in the authoring tool fixes it. Clicking a finding lights the affected elements up on the 3D model itself — you see exactly which doors and windows, storey by storey.
The full catalogue of checks is on the How it works page.
A construction logbook with visible arithmetic
The logbook is derived from the model, in the statutory Serbian format — and every line shows its own arithmetic. An opening deduction is not swallowed into a total; it stands as a minus row with its formula, e.g. −(1,80×1,90−3,00): the supervising engineer follows the figure with a finger, row by row, instead of trusting a total that “came out of the software”. The deduction rule (“openings over 3 m²”) is the same one the validation applies — the logbook and the checks cannot drift apart. A closed period never changes silently: every later change leaves a trail — who, what, when.
Bills of quantities and monthly certificates
Quantities are resolved into work types following your naming conventions: a type name from your model (e.g. “RC wall 20”) is mapped once, during onboarding, to a work type (e.g. “reinforced-concrete works”) — and that rule holds for the whole project; the software adapts to your model, not the reverse. From the closed logbook, the monthly certificate comes out ready for invoicing, in the Excel format your accounting and the investor already know.
Site records, attached to the model
Site records don't live in general folders — they live on elements. Progress is tracked per element and per trade: the model shows what is built, in progress, or late, with no retyping into spreadsheets. A site photo attaches to the specific wall or slab, so a year later it is found in a second — through the element, not by scrolling a phone gallery by date. A non-conformity is raised on the element, gathers comments and history, and stays open until closed — the issue doesn't die in a phone call or a chat message. The daily sheet — crew, works, weather — exports to PDF.
Export, and the provenance of every figure
The logbook, the quantities and the certificate export to Excel. Beneath every line sits its history: who entered, changed and closed it, and when. When the investor or supervision disputes a figure, the answer is not an argument but the audit trail — every figure has a provenance defended by a document, not by memory.
Everything above runs on your project during the pilot — free of charge, with onboarding.
Book a pilot conversation