Proving AI Value in Architecture and Construction With Nemetschek

How much of construction’s cost, delay, and waste begins with information that fails to survive the journey from design to delivery? That question runs through my conversation with Julian Geiger, Chief AI Officer at Nemetschek Group, as we look at the practical role of AI across architecture, engineering, construction, and operations.

Julian describes what he calls the industry’s 90, 40, 20 problem. According to the figures he shares, 90 percent of projects are over budget or over time, the built world accounts for roughly 40 percent of global carbon emissions, and around 20 percent of material is wasted. His argument is that many poor outcomes start as information and decision problems. Each project phase may work reasonably well on its own, but handovers can strip away context. A building information model becomes a PDF, a PDF becomes an email, and a decision may never be recorded against the object it changed.

We discuss how AI, building information modeling, and digital twins can identify missing information, scope gaps, clashes, and design choices before they become expensive construction site problems. Julian shares Nemetschek’s work bringing Firmus AI into Bluebeam to review two dimensional drawings, then explains the broader goal of feeding lessons from construction back into design and engineering tools. The commercial promise is easy to understand. Finding a mistake while a wall exists only in software costs far less than finding it after workers and materials are waiting on site.

The conversation also moves beyond the assumption that every task needs the largest available model. Julian sets out a four tier approach. Deterministic calculations such as structural math should remain deterministic. Stable, high volume checks may be handled by conventional rules. Smaller domain models can classify objects, retrieve data, and interpret geometry close to the source. Frontier models earn their place when the work involves ambiguity, reasoning across documents, or several dependent steps. His test is refreshingly practical: use the least expensive method that is reliably right and fast enough for the person waiting on the answer.

That discipline matters when finance teams ask for proof. Time saved on drawing reviews or tender preparation can be measured quickly, while reductions in rework or missed issues require a longer data series. Julian also notes a familiar problem for enterprise AI programs. If a firm never established a baseline, it becomes difficult to show what improved. Usage can indicate that people find a tool useful, but adoption alone does not settle the return on investment question.

Data sovereignty adds another layer. Construction files can include valuable designs, commercial information, and details tied to national infrastructure. We discuss where the data is stored, who processes it, which jurisdiction applies, and whether customer material is used for model training. Julian argues for separating genuine intellectual property from routine usage data, then matching controls to the sensitivity of each project rather than treating every data set as identical.

Finally, we consider people. In an industry facing a skills shortage, removing junior roles creates a future shortage of experienced professionals. Julian sees AI as a way to shorten the apprenticeship period and reduce repetitive documentation, while preserving a clear line of accountability: AI proposes and a qualified human decides. Could that model help construction professionals spend more of their time on judgment, design, and better buildings, and where should the industry draw the line? Listen to the episode and share your thoughts with me.