I have spent my career in the middle of things.
Every role I have had put me somewhere things were changing faster than the systems underneath: growth, mergers, acquisitions, a separation. The job was always the same. Find out what is actually going on, and build what makes it hold.
It started in the server room
I started in 2012 carrying the on-call pager for a hosting company. Fixing a failed storage system at three in the morning teaches you to value what works in production over what looks good in a diagram. From there I moved into automation, DevOps and development leadership.
Then into architecture
As enterprise architect I brought four countries onto one shared system, and led the technical carve-out of Sentia Denmark after Accenture acquired it, without a minute of downtime for customers. The lesson that stuck: architecture that nobody can build is not architecture.
Building my own
In 2026 I founded UnoArch to build full time. Some platforms started with a problem at home: CreateBooksAI exists because my wife needed a picture book where the character stayed the same from page to page, and no tool could do it.
Others were built together with people who know an industry from the inside, like Certo, developed with Danish property developers. Eight platforms are in production today, and I design, build and run all of them myself.
Both sides of the table
Fifteen years of seeing how systems fail inside large organisations, and the hands-on ability to build and run a complete platform myself. That combination is rare, and it is what you get when we work together.
- 01I understand the business problem before I write a line of code.
- 02I can tell you what a system will really take, because I build them.
- 03I stay until it runs, and I tell you plainly when something will not work.
Have something hard to build, or a system to untangle?
Tell me what you are working on. The first conversation is about the problem, not a proposal.