Work / From 2009
Rezet
Applied technical development, electrification and industrial systems
Founder rezet.dk

Rezet has been my longest chapter and the common thread. It's my own company, and has been since 2009.
It's where I built Eldyt.dk, the electric city car presented at COP15 in 2009. That became an early lesson in how batteries, electronics, software, physical products and business models have to work together. A technically interesting product is not necessarily a viable business, and the assumptions around the product can matter as much as the technology itself.
Since then, Rezet has been the workshop for everything in between, much of it sitting where software meets something physical. Battery systems and software for a diver communication system, effectively a telephone that has to work underwater. Integrations connecting customers' software to shops, hardware and other systems. Regulated software, industrial projects and technical concepts that crossed several disciplines at once.
The range is the point. A battery system, a hardware integration and an e-commerce flow may look like different trades, but they tend to fail in surprisingly similar places: at the boundaries.


Question the structure first
Over time, that became a recurring way of approaching problems. Before adding another feature, another integration or another layer of technology, I try to understand where the actual constraint sits. Sometimes the problem is in the software. Sometimes it is in the hardware, the process, the business model or an assumption nobody has questioned for years.
The solution does not always begin with technology. Sometimes it begins by changing the structure around the problem.
My role
Rezet has mostly been hands-on development from idea to working result. That has meant moving between concept development, system architecture, software, electronics, battery technology and integration, with external specialists and partners where a project called for them.
The common thread has been taking something ambiguous and turning it into something that can actually be tested, built or used.
What I learned
Working across different industries has reinforced something I keep coming back to: the most interesting problems rarely belong to a single discipline. They tend to exist between technologies, processes, business constraints and people.
And sometimes the most valuable improvement is not adding something new, but questioning what was already there.
Rezet is still where I explore new ideas today.

