I build complex platforms, and see them through to production.
Some for my own products, some together with the people who need them. Behind every one of them are fifteen years inside enterprise IT, where systems are not allowed to fail. Today I build through my company, UnoArch, and help other companies build, fix and decide.
Platforms I have built
Each one started with a real problem, mine or someone else's. Every one of them is in production today, on infrastructure I run myself.
Three ways to work together
The same person who builds the products above can build, partner or advise on yours.
Build
You have a business problem that needs software. I take it from idea to a platform running in production.
- Shaping the product and the first version
- Architecture that holds as you grow
- Build, launch and hand-over or run
Technical partner
For founders and ventures that need a senior technical person at the table, not a vendor on the side.
- Own the technical side of the venture
- Make the build-or-buy calls
- Stay until it runs for real users
Advice
A clear second opinion before an expensive decision, from someone who has built and run the thing himself.
- Architecture and platform reviews
- Carve-outs, mergers and separations
- Systems nobody dares to touch any more
Fifteen years inside enterprise systems
Before I built my own platforms, I spent fifteen years on the inside: from carrying the on-call pager in a server room to leading enterprise architecture across four countries. Almost every role put me in the middle of a merger, an acquisition or a separation.
- 01Led the technical separation of Sentia Denmark after its acquisition by Accenture, with no downtime for customers.
- 02Brought four countries onto one shared way of working and one set of systems.
- 03Merged a group of acquired companies into one operation, and retired the old systems behind them.
- 04Cut a manual business process by 90% by automating the core of it.
Built to run, not to demo
Everything I build is measured the same way: does it work in production, for real people, on a normal Tuesday.
Production is the finish line
A plan that only works on paper is not done. I stay until the system runs for real users, and I build it so it keeps running.
Senior judgment, small team speed
I build with AI-assisted development, which lets one experienced person move like a team. The decisions, the architecture and the responsibility stay with me.
The hard parts come first
Payments, privacy, security and numbers that must be exact are designed in from day one, not bolted on before launch.
Plain language
No jargon and no inflated reports. You get a straight answer about what is true, what it costs and what to do next.
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.