Ecommerce & CMS consultant · Copenhagen
I work in Danish and English
I’m a Copenhagen-based consultant architect and .NET developer. I help mid-size and large businesses choose, integrate and untangle their ecommerce and CMS platforms, with backend integrations to CRM and other third-party systems, order management and custom development in C#.
Five areas, one thread: ecommerce and CMS platforms that have to work with the rest of the business.
Architecture, integrations and custom apps for Shopify and Shopify Plus, so the store keeps up with the business behind it.
Architecture, upgrades, migrations and integrations for Optimizely CMS and Commerce.
Architecture, data integration and custom C# development on Dynamicweb for ecommerce, CMS and PIM.
CRM, order management and third-party integrations that keep working when one of the systems does not.
APIs, services and platform extensions in .NET and C#, built to be tested, deployed and handed over.
You describe one system and share a diagram if you have one. I tell you the three things I would look at first. No pitch; if I am not the right person, I will say so.
If a deeper look makes sense, I send a short proposal: what I will do, what I need from you, the timeline and the price. You decide; there is no obligation.
I do the review, the advisory work or the development as agreed, and report in writing.
Clever · EV charging
Backend and infrastructure engineering in Clever’s Intelligent Charging team, which focuses on backend systems and the smart-charging ecosystem.
Aller Media · Nordic media and publishing
Backend work on moving multiple brand sites from an Umbraco CMS to Optimizely CMS.
Commerce is rarely one system. It is a platform, a CMS, a CRM, an order flow and a dozen third-party services that all have to agree. I design how those parts fit together and stay easy to change — clear boundaries, explicit data ownership, and no more operational complexity than the problem needs.
My day-to-day engineering work is backend and cloud, mostly .NET and Azure. I advise on platform choices, integrations, order management and content architecture without being tied to any one platform.
· 3 min read
A proxy service layer is cheap insurance against third-party APIs: the pattern, why it works, and how to adopt it without a maintenance window.
· 3 min read
An ORM makes data access easy, which is exactly why it makes performance mistakes easy. How to spot the N+1 problem, prove it, and fix it three different ways.
· 3 min read
If a message can be delivered twice, your handler has to do the right thing twice. How to design message handlers that are safe to retry.
Scorecard
Twelve questions, three minutes. See where your integration layer is exposed.
Checklist
25 checks to make every Azure Service Bus handler safe to run twice.
Decision guide
A scored framework for deciding whether to split, what to extract first, and how to do it without a big-bang rewrite.
Tell me about the system or decision you are working on. I usually reply within about one business day.