Day: April 9, 2026

The Road to becoming a Global Brand.

How FUSO Uses Three Powerful Applications to Unify CX Across 170+ Markets and What Japanese Enterprises Must Do to Keep Up. Being a global successful brand takes more than traditional service in today’s world. It means that you are taking your CX (Customer Experience) to the next level. Why? Because CX is the sum of every single interaction, emotion, and perception a customer has with your brand. It doesn’t just mean changing your website design or doing surface level interaction. It is the complete feeling your brand leaves behind. And that’s where FUSO has successfully broken the code and have globalised their brand in more than 170 countries. Their commercial vehicles have diverse customers that range from a fleet manager in Indonesia, a dealer network in Japan, to a logistics operator in Europe. People from different corners of world interact with the same brand, same digital infrastructure without a compromise in service quality. So how did FUSO make this situation possible? Because Consistency is not the branding exercise. It is an application architecture challenge. Branding gets you the audience, but it’s your application and your consistent service that makes them loyal. A successful architecture plays out across three distinct types of enterprise applications. Each one has a different function, a different set of users, and a different role for AI. Over the past three articles, we explored how to evaluate applications for AI readiness, how to keep humans in control as AI moves from assistance to action, and where agentic AI earns the right to act. April brings the question that follows: When the applications are ready, and the people are ready: how do you scale it globally without losing what made it work? This article answers that question through the lens of three application types Cubastion has built and operates for FUSO and what every global enterprise can take from that pattern. “The Enterprise AI Map: Three Application Types, Three Distinct Roles.” Global enterprises are run on a complex application landscape. When we look at our client base, be it automotive, manufacturing or enterprise services, we consistently see three categories of application, each with a distinct global scaling challenge and a distinct role for AI. Application Type Global Challenge AI Role Cubastion Example 1 — Customer Experience Platforms Fragmented touchpoints — customers interact with multiple disconnected apps across markets Unified personalisation, predictive service scheduling, intelligent engagement across channels CCP: Central Customer Portal — FUSO / MFTBC (Salesforce, Truckonnect, FUSO Shop, invoice, fleet & service) 2 — Dealer, Sales & Content Operations Inconsistent dealer processes; manual, error-prone document and content workflows across global markets Intelligent document processing, AI-driven content automation, consistent operational quality at scale Salesforce CRM + DMS + AI-enabled Content Management System — 7 live AI use cases 3 — Data Intelligence Platforms Disconnected data, no single source of truth, insights too slow for operational decisions GenAI on data — natural language querying, predictive analytics, automated data quality, real-time decisioning ICDB Data Lakehouse + GenAI solution — enterprise data intelligence at global scale Understanding which type of application, you are dealing with is the first step to applying AI correctly. A GenAI capable of making your documents process smarter in a CMS (type 2) is not the same as the AI that makes your customers feel seen (Type 1). And neither is the same as the predictive AI intelligence layer on a data lakehouse (type 3) that tells you what is going to happen in your business before it happens. Apply the wrong one to the wrong problem, and the result is not transformation. It is expensive confusion. Type 1: Customer Experience Platforms: Building the Portal That Makes Complexity Invisible For most global enterprises, their customer facing layer is the most visible part. These types of applications allow the customers and fleet operators to interact directly. But they face a major challenge of “fragmentation” at the global scale. This results to customers usually interacting with multiple disconnected applications across the lifecycle, each with its own login, its own data model, and its own experience quality. All of these activities increase agitation and reduces collaboration. In FUSO, the problems were same. fragmentation was identified as the starting point to upgrade their CX because Customers needed to navigate separate touchpoints for vehicle information, service booking, telematics data, invoicing, and fleet management. Each interaction was functional. The overall journey was not. The CCP Solution Cubastion responded the problem of fragmentation by building the Central Customer Portal (CCP) for MFTBC: a unified Salesforce Experience Cloud platform that consolidates the complete customer journey into a single, coherent digital experience. Our solution delivered CCP Phase 2 using an Agile framework with six development sprints. CI/CD pipelines enabled rapid, reliable deployments across environments. This contained: FUSO Shop which handles service booking and parts purchasing, integrated directly into the portal so customers never need to leave to complete a transaction. Truckonnect, powered by Daimler Truck Connect, delivers live telematics data giving fleet operators real-time visibility of every vehicle in their fleet from within the same environment they use for everything else. Invoice Management that gives customers complete access to their financial documents, removing the need to contact support or navigate separate finance systems for something as fundamental as retrieving an invoice. Fleet and Service Management which consolidates vehicle registration, maintenance scheduling through a calendar-based interface, and lease and finance cost management, giving fleet operators a single operational view of their entire relationship with FUSO. Unified Customer Identity meaning that Vehicle history and finance information are synchronised with internal SFA systems, connecting eight enterprise systems through secure APIs meaning that every part of the portal draws from a single, consistent view of the customer, regardless of which underlying system is actually serving the interaction. This is not a portal that links to other applications. It is a platform that makes those applications invisible to the customer, replacing navigation friction with a coherent, branded experience regardless of which underlying system is serving the interaction. The result? 30%