Whose job is it to make the board understand the technology?
In deep tech, many strategic decisions are also technical ones - and a board needs someone close enough to the technology to translate it.
I write about what happens when software meets the physical world.
A builder with thirty years in software, regulated systems, electrification and physical products. These are notes on the decisions, mistakes and patterns that appear when those worlds meet.
Latest
All posts
When 80 amps wasn't really 80 amps
A lithium battery bank, two burned-out alternators and three seasons around Scandinavia - and the difference between what a component can deliver and what it can sustain.
I've built things from some strange places. One of them was a pigsty.
A software company in central Copenhagen, a garage on Frederiksberg, an old pigsty and a sailboat - and why companies only look inevitable in hindsight.
On my boat, every watt is visible. On my laptop, almost none of them are.
A battery monitor on a sailboat, an AI agent in the cloud - and why the weight of computing never went away. It just got harder to see.
Selected work
From regulated software to electric propulsion at sea.
Azomian, Rezet and Searine each started from a different problem: pharmaceutical software that had to satisfy the FDA, an electric city car shown at COP15 in 2009 and the battery systems behind it, and electric propulsion for sailing yachts. The fields changed. The way of working - questioning the structure before adding another layer - carried over.
Currently exploring
Some problems I keep coming back to.
- Software in physical things
- How much more existing hardware can do when the software around it gets better.
- How companies get built now
- What changes when software, and AI, is part of the work from the first day.
55.6536° N12.0771° ERoskilde harbour
Contact
Problems worth solving, and what to build next.
I’m always open to a conversation about any of them.