Who is responsible for all of this

Businesses as systems

I read businesses as systems: inputs, processes, incentives, constraints, outputs. That lens has applied equally to a four-language catalog, a paid-growth model, a pricing engine and a team. The common denominator is ownership across business, technology and commercial execution - not any single job title.

That means a conversation about margin structure and the Python that computes it are the same job. Both are on this site, deliberately.

How the work compounded

1. Commerce execution Running the shop floor

   Storefront operations day to day - where the friction that later became system designs was first felt.

2. Infrastructure ownership Consolidate, then rebuild

   Four storefronts into one Magento backend; then the international platform rebuild across four languages and five markets.

3. Data / analytics systems Make the economics explicit

   Rebuilt tracking and measurement, then proprietary margin, pricing and forecasting tools owned locally.

4. Team & process design Hire and structure the team

   Recruited, hired, onboarded and managed the team; defined roles, delegated, documented ~47 SOPs.

5. AI-enabled operating models Delegate to machines, carefully

   Specialist agents with orchestration and governance - AI Operations as a way of running work, not a tool.

Each stage made the next one possible. The migration taught me content operations; the tracking rebuild taught me measurement; the team taught me delegation. The AI work is all three lessons at once.

Functions, not just systems

Rebuilt the digital function from a solo operation to four specialists plus an apprentice - capability-gap analysis, recruiting, interviewing, hiring, onboarding, direct management, role definition, mentoring of junior and mid-level e-commerce and business-development staff.

Budget responsibility across media, technology and external partners.

Introduced documentation as a discipline - approximately 47 SOPs - and cross-trained responsibilities, reducing key-person dependency across the function. Reduced, not eliminated. The org chart still has single points of failure.

External partner governance: sourced, selected and onboarded the specialist paid-growth partner and defined the reporting and decision structure; coordinated an external development agency through Jira and UAT during the Magento consolidation.

The same discipline applied to people and to models - reduce key-person dependency, whether the key person is a specialist or a model.

What should exist, at what price

The commercial product side runs alongside the digital function: strategic supplier sourcing, development of new collections and products, upsell architecture across the range, and go-to-market planning that gets a new product earning sooner. In a catalogue business this is product management - deciding what should exist, at what price, against which demand, and how it reaches the market. It is also why the margin and pricing work exists: I needed to know what a product earned before I could decide what the range should become.