Technical-commercial operator
I design systems that turn complex digital operations into measurable growth.
Business problem → system design → execution model → measurable leverage. I decide what should be built, build the critical parts myself, and lead the people around the rest.
Currently Head of Digital & Product at a premium commerce brand - four-person team, six market configurations, four languages.
- AI systems
- Commerce infrastructure
- Commercial intelligence
- Digital transformation
Evidence before adjectives
Four numbers from the recent work. Context included, because numbers without context are marketing.
~5 months on the new platform (Mar-Aug 2026) vs. 12 months of legacy-shop revenue in 2025.
Metadata across four languages, automated after calibration. Human baseline ~7 min per entity.
After the paid-growth operating model was rebuilt with a specialist partner.
Local forecasting application vs. actual generated net revenue.
Selected work
Four transformations · 2022 - 2026-
AI Operations
Repetitive knowledge work rebuilt around specialist AI agents - with governance that keeps judgment human.
Measured / estimated leverage220+ hours of manual production avoided; ~9.5 analytical hours saved weekly
Model evaluation10 models, 6 runs, fixed rubric
-
International Commerce Transformation
The commerce platform rebuilt for four languages and five markets - while the legacy shop kept selling.
Measured outcome+52.8% net revenue · zero revenue downtime
-
Commercial Intelligence
Proprietary decision infrastructure around margin, pricing and cash - owned locally, not rented from SaaS.
Measured outcome2.1% full-year forecast variance · 1,153 SKUs
-
Performance & Growth
The paid-growth operating model rebuilt - specialist partner, trustworthy measurement - then augmented with AI.
Measured outcome+371% YoY ROAS improvement · −29% CPC
One portfolio, shared systems
Work ↔ SystemsThe projects are not isolated. Systems built for one transformation hardened into infrastructure for the next - the same performance intelligence serves AI Operations and Performance & Growth; the same metadata and semantic systems serve AI Operations and the commerce platform.
| Transformation | Performance Intelligence | Metadata Automation | Semantic Architecture | Margin & Pricing | Revenue & Cash-Flow | Magento Consolidation | EU Expansion |
|---|---|---|---|---|---|---|---|
| 01AI Operations | |||||||
| 02Commerce Transformation | |||||||
| 03Commercial Intelligence | |||||||
| 04Performance & Growth |
Operating principle
AI should remove repetitive cognition before it removes human judgment.
That principle shows up as permission boundaries, calibration runs and deliberate human checkpoints across the AI work - and as documentation, delegation and cross-training across the leadership work. The same discipline, applied to machines and to teams: reduce key-person dependency, whether the key person is a specialist or a model.
The same discipline built the function it runs on: one person to four specialists plus an apprentice, ~47 documented SOPs, cross-trained responsibilities. How the work compounded →
Notes - how I think
All notes →-
On systems
Most digital problems are systems problems
What presents as a website problem is almost always a technology-process-people problem wearing a website costume.
-
On architecture
Complexity should be earned
More architecture is not better architecture. This site is plain HTML and CSS on purpose.
-
On leverage
AI should create organizational leverage, not headcount theatre
220+ hours, ~9.5 hours a week, ≥4 days per hub - what recovered time actually becomes.
Contact
Open to roles in AI operations, technical product and commerce infrastructure.
Remote across the EU, or Vienna and Hamburg. Also happy to talk about agent governance, model evaluation or commerce architecture with no agenda attached.