International Commercial Transformation Advisor

Turning complexity into commercial momentum.

I work where commercial ambition becomes organisationally difficult—across markets, functions, data and technology. I create the clarity, operating logic and implementation path that move transformation beyond concepts and pilots.

Explore the work My perspective

Clarity in complexity.
Direction before acceleration.

15+years connecting commercial strategy and implementation

40+markets connected through tools, governance and transformation

72retail outlets developed within three years in India

01 — Point of view

Transformation becomes real when people make better decisions inside a system designed to support them.

I start with the commercial question and follow it through decision rights, incentives, data, interfaces and local market reality. Only then do technology and AI take their proper role: enabling a better way to sell, decide and operate—and making it scalable.

02 — Global experience

Depth, not just reach.

Every highlighted market represents professional involvement, not travel. Colour shows the depth of responsibility; a copper outline marks physical market exposure.

Market

India2011–2014

Long-term market assignment

3 years 2 months on site

03 — Professional capability system

The system behind the work.

Not a proficiency chart. A navigable view of how commercial expertise, technology, delivery methods and human judgement reinforce one another.

Filter capabilities

Level00

Capability system

Nine fields. One connected professional system.

Choose a field, then move through its disciplines, capabilities, methods and tools one structural level at a time.

9categories

Start here

Choose an entry point. No skill scores or isolated keywords—each field opens into the disciplines, methods and tools behind it.

04 — Selected work

Transformation stories.

Not a project catalogue. A growing set of stories about the complexity, choices and implementation behind meaningful change.

Case index

Select a story to explore the decisions and implementation behind the work.

Market buildingFrom market footprint to a functioning retail networkIndia

Case thesisMarket expansion was a system problem: footprint, partner quality and retail readiness had to scale together.

The challenge

The task was not simply to add retail points. Expansion required suitable investors, viable locations and outlets that could represent the brand credibly in sales and after-sales from the start.

Why it was complex

Seventy-two outlets in three years meant an average expansion pace of roughly two openings per month. Investor decisions, point-of-sale execution and after-sales improvements therefore had to progress in parallel rather than sequentially.

My contribution

I worked across dealer-network planning, investor identification and selection, point-of-sale marketing and after-sales optimisation—linking the expansion target to the practical conditions for a functioning outlet.

Implementation

The market-embedded role made it possible to follow decisions beyond approval: from evaluating potential partners to supporting the commercial and operational readiness of the resulting network.

What changed

The footprint reached 72 outlets within three years. The visible result was the network size; the underlying work connected growth with investor quality, retail execution and after-sales capability.

Transferable insight

Outlet count alone is a weak measure of network development. The more useful question is whether partner quality and operating capability are scaling at the same speed as the physical footprint.

Executive decision supportFinding material efficiency potential after a market shockJapan

Case thesisEfficiency becomes decision-grade when identified potential is separated from realised savings and connected to the operating reality that must deliver it.

The challenge

The financial crisis created immediate pressure to identify material cost opportunities while the market organisation still had launches to deliver and day-to-day decisions to make.

Why it was complex

The task required translating a broad efficiency question into initiatives that senior management could review—while keeping identified potential distinct from realised savings.

My contribution

I developed the programme and its analytical structure while supporting the C-suite and gaining direct exposure to vehicle launches in the Japanese market.

Implementation

I consolidated the opportunities into a structured programme with estimated potential, creating a clearer basis for management review and prioritisation.

What changed

The analysis identified approximately €18 million in potential. The number is intentionally stated as identified potential—not as a claim that every euro was subsequently realised.

Transferable insight

Value language is part of analytical quality. A credible programme distinguishes identified potential, approved measures and realised savings instead of blending them into one headline number.

Decision systemsEvolving stock decisions from local process to digital productSouth Korea · Canada · United States

Case thesisA decision product earns scale when its logic survives the move from local process to materially different market conditions.

The challenge

Dealers had to decide which vehicle configurations to order before demand was fully visible. The goal was to improve those choices without ignoring local sales processes or the constraints of central tools.

Why it was complex

South Korea and Canada required local process mapping, configuration statistics and retailer volume planning. The United States added dealer-specific micro-markets and a much larger set of demand signals.

My contribution

I led concept, local process design, central-tool mapping and rollout in South Korea and Canada, including retailer quota tools intended to improve planning quality and speed. I then helped develop the United States successor.

Implementation

The United States product divided the market into dealer-specific micro-markets and combined macroeconomic indicators, local weather and competitor activity with an Amazon-style stock-ordering interface.

What changed

What began as local optimisation and volume-planning tools became a more advanced analytical ordering product, while retaining the practical link to dealer and market workflows.

Transferable insight

The transferable asset was not one identical screen. It was a stable decision logic that could absorb materially different local data, processes and user expectations.

Technology to valueConnecting commercial demand to constrained local productionRussia · Malaysia

Case thesisCommercial demand becomes useful only when it is translated into supply decisions that respect local production and tariff constraints.

The challenge

Local teams needed stock and production decisions that responded to actual market demand while respecting assembly capacity, component constraints and country-specific duties and tariffs.

Why it was complex

The sales floor and production floor operated on different signals and time horizons. A commercially attractive configuration could still be infeasible or uneconomic once CKD constraints and tariff effects were applied.

My contribution

I developed and rolled out the market-specific optimisation concept, translating demand sensing into a shared logic for commercial stock, production planning and local constraints.

Implementation

A lean AWS backbone and machine-learning-supported optimisation were developed through recurring on-site work—approximately one week per month in each market over the year.

What changed

The result was a common decision approach connecting observed demand with stock and production choices—explicitly adjusted for the realities of local CKD operations.

Transferable insight

Optimising stock without production feasibility simply moves the problem. The useful unit of analysis was the complete path from local demand signal to buildable, economically viable supply.

Operating-model transformationReframing B2B sales for an agency worldEurope

Case thesisAn operating model becomes credible when customer journeys, decision rights and system behaviour reinforce the same commercial reality.

The challenge

Agency sales changed who contracted with the customer, who owned each process step and how B2B requirements entered systems designed around a new retail model.

Why it was complex

Corporate, special and rental business do not follow one simple retail journey. The European concept had to create common direction while leaving room for local responsibilities and market-specific execution.

My contribution

I developed the B2B sales concept and customer journey, translated operational needs into requirements and represented the business side in agile system development.

Implementation

The work moved repeatedly between journey design, roles and responsibilities, backlog decisions and market feedback—so that policy, process and system behaviour stayed connected.

What changed

The shared European concept and customer journey provided a common basis for B2B implementation across the major agency markets, rather than leaving each market to redesign the model independently.

Transferable insight

An operating model is not finished when roles are drawn. It becomes real when the customer journey, decision rights and system permissions produce the same answer in daily work.

Global governanceCreating a common language for global sales channelsGlobal programme

Case thesisGlobal comparability starts with a shared commercial language, not with a more sophisticated dashboard.

The challenge

Markets used different answers to a basic management question: which customer group belongs in which channel for planning, reporting and commercial steering?

Why it was complex

The differences were not cosmetic labels. They were embedded in targets, reports and local practice across Europe, the Americas and Asia-Pacific—and harmonisation took place during the disruption of COVID-19.

My contribution

I defined and aligned the channel logic, then developed the global Tableau reporting solution and managed its backend so the common definitions became operational rather than documentary.

Implementation

Definition workshops and market alignment were followed by data logic, a self-managed backend and a management-facing reporting layer that made deviations visible.

What changed

Markets gained a more consistent basis for planning, reporting and comparing channel performance across a global scope of more than 40 markets.

Transferable insight

The difficult part was not Tableau. It was agreeing which commercial reality every number represented. The dashboard became useful only after the governance question was resolved.

Market building2011–2014India

From market footprint to a functioning retail network

Three years and two months inside the Indian market organisation, building the dealer footprint while working on the quality behind each opening.

Case thesisMarket expansion was a system problem: footprint, partner quality and retail readiness had to scale together.

72outlets developed within three years

The challenge

The task was not simply to add retail points. Expansion required suitable investors, viable locations and outlets that could represent the brand credibly in sales and after-sales from the start.

Why it was complex

My contribution

Implementation

The market-embedded role made it possible to follow decisions beyond approval: from evaluating potential partners to supporting the commercial and operational readiness of the resulting network.

What changed

The footprint reached 72 outlets within three years. The visible result was the network size; the underlying work connected growth with investor quality, retail execution and after-sales capability.

Transferable insight

Outlet count alone is a weak measure of network development. The more useful question is whether partner quality and operating capability are scaling at the same speed as the physical footprint.

Market developmentDealer networksInvestor selectionRetail operations

DisclosureMarket case · employer, investor and partner details omitted

05 — Thinking

Ideas for the real organisation.

Working propositions on the decisions, operating models and technologies that determine whether transformation becomes useful work.

Foundational principle

Direction before acceleration

Speed is a multiplier, not a substitute for direction. If the problem, decision rights or operating model are wrong, acceleration scales confusion. These six questions create the conditions for useful execution.

Clarity→Decisions→Design→Delivery

Interactive diagnostic01 / 06

Problem

What problem are we actually solving?

Separate the visible symptom, the management concern and the underlying system problem before choosing a solution.

Developing library

Active lines of inquiry rather than a finished publication archive.

AI & organisations

Agentic AI needs an operating model, not another pilot

Working note · grounded in current Agentic AI work

The difficult question is not whether an agent can perform a task. It is whether the organisation can give that task a clear owner, a measurable economic logic, a safe decision boundary and a path from isolated use case to repeatable work.

01 · The pilot trap

Capability is not yet a business model.

A convincing demonstration can show that a model is able to act. It does not show who owns the outcome, what changes in the process or whether the economics survive contact with the real organisation. The first discipline is therefore to evaluate business potential before selecting a tool.

02 · The ecosystem

Agents need a designed environment.

An agent is one part of a wider system of models, data, interfaces, orchestration, human approvals and controls. AI ecosystem design makes those relationships explicit instead of treating each use case as an isolated experiment.

03 · Employee economics

Productivity is a transition question.

Value is not created by removing a task from a job description. It depends on what people do with the capacity that is released, how management measures contribution and whether employees are prepared to work with the new system. That is why AI employee economics and enablement belong in the design from the start.

04 · The implementation test

Move from use case to repeatable work.

The practical test is simple: can the organisation explain the decision boundary, assign accountable ownership, measure quality and adoption, and repeat the workflow without depending on one enthusiastic pilot team? If not, the work is still a demo.

Current practice

My current work connects business-potential pipeline evaluation, AI ecosystem design and employee and management enablement. The common thread is turning technical possibility into an operating model that can carry responsibility.

Commercial systems

Why reporting is really a governance design problem

Working note · drawn from global reporting governance

A dashboard cannot repair a fragmented commercial language. In global reporting work, the decisive design questions were which customer groups belong to which channel, who owns the definition and how markets use the information to make decisions—not which chart appears on screen.

01 · The language

Comparability starts before the chart.

When markets classify customers or channels differently, a global report can look precise while comparing different realities. The first design task is a shared commercial language: what is being planned, reported and steered through each channel.

02 · The ownership

Every definition needs a home.

A taxonomy without ownership decays quickly. Someone must be accountable for definitions, exceptions, data quality and the point at which a change becomes a new standard rather than another local workaround.

03 · The interface

Central consistency needs local intelligence.

Global programmes work when central direction and market reality are designed together. Local teams need room to explain context; central teams need enough consistency to make decisions across markets without creating parallel systems.

04 · The decision

Reporting is valuable only when behaviour changes.

The output is not a dashboard. It is a better decision: a clearer allocation, a faster intervention, a more credible forecast or a shared understanding of where commercial performance is actually moving.

Current practice

My experience spans global stock-optimisation reporting, cross-market sales-channel definitions and reporting solutions that evolved from Qlik Sense to Tableau. The transferable lesson is that the data model and the operating model must mature together.

AI, economy & society

The thorny path to an age of abundance

Working thesis · long-form argument in development

The transition toward a Star Trek-like abundance will not be smooth. In Western welfare states, employment losses may arrive before productivity gains can support new safety nets, creating dissatisfaction and political risk. The response needs a shared target system, transitional fiscal mechanisms, legal certainty and responsibility across governments, companies and society—not a search for one actor to blame.

Working draft · 01 · AI & organisations

Agentic AI needs an operating model, not another pilot

The competitive question is no longer whether an agent can perform a task. It is whether an organisation can build a reliable system around the work: value, ownership, decision rights, controls and adoption.

01 · The pilot trap

Capability is not yet a business model.

02 · The ecosystem

Agents need a designed environment.

03 · Employee economics

Productivity is a transition question.

04 · The implementation test

Move from use case to repeatable work.

Current practice

Working draft · 02

Why reporting is really a governance design problem

Shared dashboards only become useful when the organisation has shared definitions, ownership and a decision rhythm behind them.

01 · The language

Comparability starts before the chart.

02 · The ownership

Every definition needs a home.

03 · The interface

Central consistency needs local intelligence.

04 · The decision

Reporting is valuable only when behaviour changes.

Current practice

06 — About

Professional narrative

A perspective built across markets, systems and transformation.

Built through embedded market roles, global decision systems, European operating-model transformation and current work on Agentic AI.

Professional viewpoint

See the system before changing the part.

Commercial outcomes rarely belong to a single function. I look at the decisions, operating model, technology and organisational conditions that need to move together before a transformation can hold.

Commercial judgementSystems thinkingOrganisational reality

Working principles

How perspective becomes practice.

Create clarity before adding speed

Connect business logic and technical possibility

Design for adoption, not presentation

Leave ownership in the organisation

07 — Connect

Good conversations often start with a complex question.

For serious exchange on commercial transformation, operating-model design, decision intelligence or how Agentic AI changes the economics and organisation of work.

Start a conversation ↗

Click or tap the signet to turn the card.