The client was building a premium EV commercial model without an inherited retail network, market organisation or established operating routines.

That removed some of the constraints an incumbent would carry. It also removed the reference points. Retail footprint, customer ownership, pricing, inventory, parts, last-mile delivery and aftersales could not be left to legacy processes because there were none.

Over a 12-month programme, the work therefore treated the commercial value chain as one operating system rather than a collection of launch workstreams.

The retail concept included different facility types, from urban showrooms to mobile formats, so the physical footprint could change with market maturity and density.

A Client Ambassador role was defined to carry customer ownership across inquiry, sale and aftersales rather than handing the relationship between functions at each stage.

The useful part of the design was not the number of formats. It was the ability to decide which customer activities needed a permanent site, which could move, and which could remain digital before committing fixed cost.

The pricing model combined a top-down market view with a bottom-up cost view.

Top-down work used market indices and competitor research. Bottom-up work used production cost, landed cost and margin assumptions. Pricing layers across OEM, importer and point of sale were then defined explicitly.

That made the gap between what the market could support and what the value chain required visible early enough to change the operating model rather than discover it after launch.

The last-mile model was designed to vary by market. Depending on scale and infrastructure, fulfilment could run directly to the point of sale or through a fulfilment-centre structure.

A watchtower concept was used to create visibility over inventory flow and operating status, with roles and responsibilities mapped through RACI logic.

Parts planning used vehicle specifications, forecast demand, lead time, reorder points and ABC classification to decide stocking depth across points of sale and regional depots.

High-voltage battery storage and transport were treated separately because hazardous-goods requirements, warehouse certification and country handling rules changed the operating design.

The project initially looked like a retail and market-entry build. Aftersales could not remain a later support workstream because service capacity, parts, training and customer ownership changed the economics of the launch.

Performance dashboards were designed around customer satisfaction, throughput and retention, while service bundles and onboarding routines were developed for the retail teams.

The shift mattered because the vehicle sale was only the first operating event. The organisation needed to know who owned the customer, which systems carried the relationship and how post-purchase work would be funded before launch.

Focused eight-week market sprints in the UK and UAE were used to test volume assumptions, pricing logic and local operating plans against demand and regulatory conditions.

Those sprints did not prove the complete commercial model. They reduced uncertainty around specific assumptions and exposed where a common global design needed local variation.

That distinction matters in startup work. A pilot or sprint should change the next decision, not become evidence that every part of the future-state model has already been validated.

The original programme considered a wide set of possible future capabilities: mobile retail and service, third-party retail partnerships, digital contracting, AI-supported customer tools, circularity and battery recovery, and more flexible staffing models.

Those ideas are useful as design options. They should not be presented as delivered operating outcomes unless they were actually implemented and measured.

The stronger architecture is one that leaves room for those options without making the current business case depend on all of them becoming real.

• A modular retail and facility concept across different market conditions.
• A defined Client Ambassador role spanning customer acquisition through aftersales.
• Top-down and bottom-up pricing logic with explicit OEM, importer and point-of-sale layers.
• Market-dependent last-mile and fulfilment design supported by inventory visibility and RACI governance.
• Parts stocking and reorder logic using lead time, demand and ABC classification.
• High-voltage battery warehousing and logistics requirements.
• Aftersales processes, dashboards, service concepts and training structures.
• Market sprints used to test selected commercial and operating assumptions.

Starting without legacy does not mean the organisation starts with freedom. It starts with unanswered operating questions.

The advantage is that those questions can be answered before large amounts of capital, contracts and local workarounds harden around the first version of the model.

The discipline is to separate what must work at launch, what can be modular by market, and what remains an option until evidence justifies the next commitment.