Automotive digitalisation often starts with visible touchpoints: websites, configurators, lead forms, booking tools, apps and retailer interfaces.

Those matter, but the customer usually experiences the failure somewhere else. A lead is not recognised by the retailer. An online configuration cannot be continued in-store. An order status is held in another system. A service request reaches a team that cannot see the sales history.

The interface can be modern while the operating model behind it remains fragmented.

When work moves from one team or system to another, three things need to remain intact: ownership, information and the next permitted action.

If the new owner is unclear, the event waits. If the information is incomplete, somebody recreates it. If the system does not permit the next action, staff work around it by email, spreadsheet or phone.

That is where digital journeys become manual operations.

Connecting two systems can move data. It does not decide who is responsible when the data is wrong, the customer changes the request, a local market needs an exception or a dealer rejects the central process.

Those are governance questions. They need an owner, a response time, an escalation path and a commercial rule.

Without that layer, the organisation has integrated technology and fragmented execution.

A practical design starts with events such as lead created, configuration saved, order changed, vehicle delayed, payment failed, handover completed or service issue raised.

For each event, the organisation can define who owns it, which system is authoritative, what the customer should see and what happens when the normal path fails.

That creates a much stronger basis for technology decisions than starting with a list of desired platforms.

A process that works in one market can fail when tax, finance, language, dealer contracts, payment methods or customer-service obligations change.

Scaling digitalisation therefore requires a controlled way to handle local variation without duplicating the whole journey in every market.

The architecture needs common events and data, with explicit local exceptions. Otherwise every rollout creates another version of the operating model.

Digital transformation is not complete when the customer can click through the journey. It is complete when the organisation can carry the resulting work through ownership, systems and exceptions without rebuilding the context by hand.

That is why the handoff deserves at least as much design attention as the interface.