AI & automation for construction and engineering teams — buying back the hours lost to RFIs, ITPs, and re-keyed data.

Every big thing starts as a blank canvas.

AI & automation for construction and engineering teams — buying back the hours lost to RFIs, ITPs, and re-keyed data.

Fifteen years of delivery — roads, rail, and the software that runs them.

AI buys that time back. I'll show you where.

GROUND TRUTH

Field note — Kilimanjaro shows itself at dawn. Tanzania, 2014.

Projects run on documents, deadlines, and duplication — the same data re-keyed across submittals, RFIs, timesheets, ITPs, and closeout. AI is genuinely good at that drudgery. The trick is applying it carefully to your workflows, not bolting on a chatbot and hoping.

The work is real. So is the paperwork.

Time back

hours returned to your team by automating routine documentation

Your tools

works with the systems you already run — not a migration

On the ground

built by someone who has worked the sector, not just the software

Own build — Nexus Sentinel · Automated quantity take-off (QTO)

Client work is confidential by default — no logos, no vanity numbers. The work shows up in your workflows, not my homepage.

  • Civil & road infrastructure
  • Rail infrastructure
  • Project controls & delivery
  • Quantity take-off & estimating
  • Field-performance software
SERVICES

Field note — the summit line at first light. Kilimanjaro, 5,895 m.

Start anywhere. Most engagements begin small, prove value, then expand.

Three ways I can help.

01

Strategy

A clear, honest read on where AI and automation will (and won't) pay off in your operation — prioritised by effort and return, with no vendor axe to grind.

Client work is confidential by default — no logos, no vanity numbers. The work shows up in your workflows, not my homepage.

02

Implementation

Building the automations that earn their keep: document extraction, report generation, compliance checks, and the integrations that connect the tools you already use.

Client work is confidential by default — no logos, no vanity numbers. The work shows up in your workflows, not my homepage.

03

Support

Keeping it running and improving it as the work changes — training your team, measuring what's saved, and adjusting as you grow.

Client work is confidential by default — no logos, no vanity numbers. The work shows up in your workflows, not my homepage.

PROCESS

Field note — the arch at the end of the track. Kokoda, PNG, 2014.

How we work together.

01

Listen

I learn how your projects actually run and where the time goes — on site language, not slideware.

02

Map

We pick the few workflows where automation returns the most, and agree what 'better' looks like.

03

Build

I build it against your real tools and data, in small increments you can see working.

04

Support

We measure the time saved, train your people, and keep improving it.

Automated quantity take-off (QTO)

Nexus Sentinel is my own product build: AI applied to quantity take-off, extracting measured quantities from project drawings so estimating is faster and more consistent, with less manual re-work — every measurement traceable back to the drawing it came from.

  • Compliance reporting

    Automated document extraction and report generation for RFI and ITP tracking — reducing the weekly admin load on project managers.

  • Project controls integration

    Unifying progress, cost, and risk data from existing tools into a single real-time view — eliminating duplicate data entry across systems.

  • Handover automation

    Templated handover documentation generated from existing project data — improving closeout consistency and reducing manual effort.

ABOUT

Field note — Bomana to the coast. Papua New Guinea, 2014.

The time goes somewhere better.

Hi, I'm Bernhard.

I'm Bernhard — a civil engineer who's worked across construction and engineering: road design, on-site delivery with a major civil contractor, and project controls on large infrastructure. Always as part of a larger team and in focused technical roles, not running the projects myself.

From there I moved into the product layer of the same work — as an implementation engineer and then product manager for a construction field-performance platform used by tier-one contractors on site. That journey through design, delivery, controls, and software is why the automations I build fit how the work actually happens.

I also serve as an officer in the Australian Army Reserve.

Credentials
  • Bachelor of Engineering (Civil) — Griffith, 2011
  • Master of Engineering — Project & Engineering Management (RMIT)
  • Graduate Diploma, Mining & Mineral Engineering — UNSW
  • MBA — International Business / Finance (Deakin)
  • Graduate Certificate of Artificial Intelligence (Deakin)
  • Officer, Australian Army Reserve
CONTACT

Field note — the original blank canvas. Western Sahara, 2013.

Let's talk about your project

A short, no-obligation conversation. Tell me where the time goes on your projects and I'll tell you honestly whether AI can help.

Your details are used only to reply — never shared, never added to a list. I reply within one business day. Prefer email?

A first conversation is 30 minutes about your current workflow. No deck, no obligation.