I am an engineer, and I have spent my career on the part of technology that has to
physically work - rigs, processes, instruments, data that has to survive being
checked.
For ten years I worked inside a company that builds its own technology: first
supercritical water gasification, then CO2 capture, then metal recycling. I came in as
a mechanical design engineer in a three-person team in a warehouse and left as the
technology lead for a recycling programme with a team of about fifteen and a budget
near two million euros. In between I went through the full cycle several times -
idea, prototype, pilot, demonstration plant - and found that I enjoy it. I
started Bolwerk because the gap between a brilliant idea and scaling it up is where
most of them stop. Closing it takes a broad view: technology, people, legislation,
finance.
In every one of those places I noticed the same gap. Genuinely good technical people,
a real result on the bench - and then months disappearing into the unglamorous
part. The rig nobody instrumented properly. The report that took three weeks because
the data was in four formats. The standards review everyone agreed was important and
nobody had time for.
That gap is the whole reason Bolwerk exists. Not to advise you about
it from a distance, but to come in and close it - with a soldering iron, a
P&ID, a Python script or an AI pipeline, whichever the problem actually calls for.
The name is deliberate. Bolwerk is Dutch for bastion: the reinforced corner of
a fortification, the part built to hold when the rest is under pressure. It also
happens to be my surname.