Three ways to work together
Each way includes the services listed under it, and each has recent work behind it.
An outside view
An independent assessment of where you stand: architecture reviews, strategic IT advice, or a third-party audit of a delivery.
Strategic IT advisory
An independent architectural perspective on where to invest, where to simplify, and where not to build at all. Useful when important choices need to be made without turning the decision process into a performance of its own.
Independent software auditing
Third-party review of software deliveries against agreed expectations. Relevant for quality, SDLC maturity, security, reliability, and regulatory concerns where an outside assessment should be concrete and useful rather than ceremonial.
Recently: An independent audit for Klimadatastyrelsen, 2025
Architecture, hands-on
Designing the system with you, greenfield or legacy, including cloud and AI where they serve a real purpose.
Software architecture & design
Architecture for both greenfield and legacy systems. Especially useful when the technical direction has become unclear, the system boundaries are weak, or important decisions need a calmer and more structured basis.
Cloud and AI solutions
Cloud-native and AI-based solutions where they serve a real purpose. This includes platform work, containerised workloads, computer vision, and architecture that still has to function under operational and compliance constraints.
Recently: Manufacturing architecture at ROCKWOOL Group, 2026
Leading the technical delivery
Technical lead through the difficult parts of delivery, with the team, the vendors, and the stakeholders.
Technical leadership and mentoring
Support for teams that need senior technical direction without unnecessary layers. Architecture reviews, sparring, mentoring, and practical help through the difficult parts of delivery.
Recently: AI computer vision in GxP production at Novo Nordisk, until 2025
When clients usually call
The system has become too hard to reason about
Responsibilities are blurred, integrations have grown fragile, and every change feels more expensive than it should.
An important technical decision needs firmer footing
Modernisation, cloud direction, architecture boundaries, or whether a proposed path is actually worth the cost.
The team needs senior technical direction
Clearer judgement, better structure, and help carrying the work through delivery in a sustainable way.
Principles
The same principles apply to every engagement, whether it is an outside view, hands-on architecture, or leading the delivery.
Architecture with a long view
Decisions should still make sense when the project pressure is gone. Maintainability, traceability, and operational reality are part of the job from the beginning.
Pragmatic and clear-headed
There are no best practices, only good practices, and the judgement to know which ones fit here. It starts with listening. Understanding the actual problem before proposing a solution is not a courtesy. It is the work.
Hands-on when needed
Architecture, delivery, reviews, mentoring, and implementation support. The work follows the problem instead of protecting a role description.
Calm under delivery pressure
Much of the work has been in programmes with real deadlines, competing stakeholders, and systems that could not simply fail and be retried later.
Knowledge that stays behind
An engagement should leave the organisation with better understanding, better practices, and a team that can continue without artificial dependency.
Less, but better
Complexity is easy to add and expensive to carry. Good architecture often comes from reducing what is unnecessary and making the rest clearer.