Case stories, not slides.
Essays for the people who ship.

— SituationA growth thesis that the platform couldn’t keep up with.

The business was growing on the back of internationalisation. Each new country, though, took multiple quarters — localisation, payments, taxes, returns, carrier integrations, every one of them an engineering project. The roadmap was clogged with country-specific exceptions and the org was burning out launching markets instead of compounding on them.

The diagnosis surfaced a structural problem: every assumption about a single home market was hard-coded somewhere. Internationalisation wasn’t failing because of capacity. It was failing because the platform had nationality baked into it.

— ApproachExternalise the assumptions, ship a blueprint.

We started by cataloguing every national assumption in the platform — tax, payments, language, currency, carriers, returns, regulation, even copy. Each of those became a configuration surface, with feature flags and per-country defaults. A new launch became a checklist run, not a sprint.

• Configuration surface: tax, payment, locale, currency, returns
• Per-country feature-flag matrix tied to release management
• Launch operating model with explicit go/no-go gates
• Embedded carrier and partner integrations as data, not code

— ExecutionOne launch, one cadence, one team.

We ran the first three markets ourselves under the new model, with the local commercial teams as in-room partners. By the third launch, the engineering involvement was minimal — the work had moved into product configuration and operations. The fourth and fifth markets were run by the in-house team without us.

— OutcomeFrom quarters to weeks — without heroics.

Country roll-outs collapsed from a quarter-scale programme to a few weeks of focused operational work. The platform stopped fighting itself. Engineering capacity, formerly spent on per-country exceptions, was redeployed to compounding features that benefited every market simultaneously.

More importantly, the operating model survived without us. Markets four through twelve were launched by the in-house team on the same blueprint, with quarterly check-ins rather than embedded oversight.

— SituationAn AI initiative trapped in workshop mode.

The organisation had run multiple AI pilots. None of them had survived contact with the operating model. Discovery happened in one place, feasibility in another, analytics somewhere downstream. AI lived in slides and demos, never in the release branch.

The leadership knew the answer wasn’t another tool. It was a different operating model — one where AI sat inside the workflow, not next to it.

— ApproachSix growth pillars, one execution system.

We redesigned the roadmap planning to integrate User Research, Technical Feasibility, Product Discovery, Data Analytics and Delivery into a single end-to-end execution system — explicitly aligned to the company’s strategic pillars.

• Six growth pillars with clear owners and measurable outcomes
• AI tooling embedded into Figma, analytics, and release pipelines
• Customer Effort Score and automated feedback wired to roadmap
• Competitor monitoring as a continuous research function
• Career frameworks and 3×/year micro-reviews to sustain the model

— ExecutionBehaviour, not posters.

The hard part wasn’t the architecture. It was making sure the values showed up in how teams actually planned, built, and shipped — under deadline. We embedded inside the leadership team, ran coaching programmes and workshops, and protected the cadence until it became default.

— OutcomeCulture as behaviour, growth as a side effect.

The product culture that emerged contributed directly to double-digit YoY business growth and consistent KPI overachievement across all teams. AI tooling stopped being a quarterly demo and became how design pipelines, analytics, and feedback loops worked.

Retention and team progression both improved measurably, with the career framework and micro-review cadence absorbing what used to be hallway promotion politics.

— SituationAn innovation lab without a commercial engine.

The lab had been generating credible IoT concepts but struggling to convert them into recurring enterprise revenue. Roadmaps slipped, ExCo sponsorship cooled, partner conversations stalled. Innovation was happening; productisation wasn’t.

— ApproachA KPI-driven operating model.

We formulated business cases directly with ExCo members, established a KPI-driven operating model across multiple self-managed cross-functional teams, and aligned partnerships with the broader group’s infrastructure strategy.

• Business cases co-authored with ExCo sponsors
• Self-managed cross-functional teams with measurable outcomes
• Discovery, analytics, and BI as continuous functions
• Partnership model aligned to global infrastructure

— ExecutionIdeation to release, every quarter.

Two enterprise IoT products went from ideation to release management within the engagement, with release governance designed to work inside a global carrier’s constraints rather than around them.

— OutcomeRecurring revenue, in-house ownership.

The lab generated new revenue lines for both the German entity and the global enterprise IoT business. More importantly, it shifted from a project-funded experiment into a continuous productisation engine — with cadences, scorecards and accountability that survived leadership changes.

— SituationA platform pulled in three directions.

OEM partners wanted a stable, frozen surface. End-consumers wanted continuous improvement. Safety and homologation wanted both. Four global delivery teams were ostensibly building one platform but operating off four different sets of requirements and four different release calendars.

— ApproachStandardise the motion, not the feature set.

We revamped the product development workflow to standardise requirements gathering, technical reviews, release management and go-to-market execution across the four global teams — without imposing a single feature set on every OEM partner.

• Unified requirements and technical review process
• Coordinated release management with regional flexibility
• OEM partner cadence with explicit alignment rituals
• Continuous research into driver safety and product usability

— ExecutionThe OEM partnership as a product.

Partner relationships moved from ad-hoc engagement to a formal cadence: shared roadmaps, joint go/no-go reviews, instrumented release artefacts. Driver safety and usability research drove a meaningful slice of the roadmap, raising satisfaction and reducing post-release defects.

— OutcomeFaster releases, fewer defects, higher loyalty.

Release cycle times shortened materially, post-release defects dropped, and customer satisfaction with the in-car and companion-app experience rose — with measurable improvements in driver-safety perception. The platform reached global scale on a single coherent stack.

— SituationOperations as a cost centre.

Last-mile operations were running on a mixture of spreadsheets, point tools and tribal knowledge. Customer experience varied widely by route; new market expansion required hand-built process replication; investors were sceptical about scaling.

— ApproachA product per workflow.

We defined a new digital product and operations strategy that turned each major workflow into a first-class product — with its own roadmap, owner, metrics and release cadence.

• In-house e-commerce platform with subscription support
• Route planner with ML-assisted optimisation
• Driver application with operational dashboards
• Internal planning and operations tools

— ExecutionFrom plan to product.

Each workflow was rebuilt as a product with explicit metrics: time-on-route, complaint rate, capacity utilisation. ML was introduced where it earned its place — planning, dispatch — not where it merely sounded innovative.

— OutcomeNew funding, lower opex, national reach.

The digital backbone supported a successful new investment round, a continuous reduction in operational cost, and a national expansion that the previous setup would not have supported. B2B and B2C product lines began to compound on a single platform.

— SituationA platform that couldn’t carry the strategy.

The business had outgrown its Magento-era webshop. Customer acquisition, supply chain digitalisation and analytics were all bottlenecked by platform constraints. Internationalisation was on the strategy — but the stack couldn’t carry it.

— ApproachReplatform with internationalisation built-in.

We led the transition to a self-developed in-house commerce stack — designed from day one to support international launches, segmentation, and end-to-end automation of payments and logistics state machines.

• In-house commerce platform with international hooks
• Complete digital marketing setup — GA, GTM, SEM, SEO, CRM
• Customer segmentation and lifecycle tracking
• Automated payment and logistics state machines
• Real-time dashboards for fulfilment operations

— ExecutionMigrate without stopping the business.

The migration ran in parallel-run mode, with the new platform absorbing markets and product lines one cohort at a time. The marketing stack went live early and started informing the catalogue and merchandising strategy before the migration was complete.

— OutcomeCategory leadership, multi-market.

The strategic plan enabled the business to establish category leadership in the nutrition space in Europe — with a blueprint to launch into adjacent markets (Austria, Switzerland, Sweden) on the new stack.