Integrated Journey
A systemic redesign of the onboarding of a B2B MDM platform, dissolving the silos between pre-sales, activation and retention.
Context
The symptom and the system
The platform is a corporate MDM, contracted by companies to manage fleets of mobile devices. The diversity of clients was extreme: large enterprises, tech companies, public agencies, school networks, banks, logistics operators, manufacturers and many other segments. Each with its own compliance rules, scale of operation and support expectations.
The most visible symptom was low lead conversion. Investigation revealed a structural cause: the service ran in a linear sequence, while the client's expectation demanded simultaneous layers. Every hand-off carried loss of context, rework and the weakening of the bond built earlier.
Frictions mapped in the AS-IS
- i. Onboarding as a paid gate: the client arrived with no prior knowledge
- ii. Support absent from pre-sales, creating technical debt at onboarding
- iii. Hand-off to retention as a broken bond, not a transfer
- iv. A generic POC that created no anchoring in the product
- v. A knowledge base too thin to sustain autonomy
Design hypothesis
If the teams operate in planned overlap rather than in sequence, the client journey loses its visible seams and each phase becomes accumulation, not replacement.
Method
From listening to the blueprint
Phase 01 · Immersion
Interviews with the leaders of all four teams and listening to sales, onboarding and support calls to map language, expectations and operational contradictions.
Phase 02 · Diagnosis
Building the AS-IS blueprint, exposing frontstage, backstage and moments of friction. The biggest losses were in the hand-offs, not in the phases themselves.
Phase 03 · Co-creation
Workshops with the four teams to design an overlapping TO-BE model. Everyone's presence forced the negotiation of boundaries and responsibilities.
Phase 04 · Implementation
Piloting with real clients, documented hand-off protocols and transition rituals established between onboarding and retention.
Design principles defined in the workshop
“No team enters or leaves alone.”
Every transition between teams requires a minimum overlap and a documented handover ritual.
“The client learns, doesn't watch.”
From the first contact, the client operates the product with their own data, rather than watching demos.
“Autonomy is infrastructure.”
The knowledge base was treated as a design pillar, not as support backup.
Core insight
Diluting the density of onboarding
In the old model, onboarding concentrated all the complexity: learning the product, migrating data, configuring policies, training the team and absorbing the rules of the niche. It was dense, traumatic and operated as the only possible entry point. The intervention was to redistribute that load across the whole journey, turning once-passive moments into moments of learning.
Previous model
“Everything happens at onboarding.”
All cognitive and operational load concentrated in a single post-contract phase.
Redesigned model
“The learning is the journey.”
Load distributed across four proportional phases, with learning and data accumulating from the start.
When the client starts entering their own data into the platform during the POC and learns to operate the system from the first contact, two things change in parallel. First, they understand the product's advantages applied to their own business, not in the abstract. Second, they accumulate a growing layer of configuration that would make switching to another vendor seem too much work. Switching cost stops being a sales argument and becomes lived experience.
Solution
A layered journey blueprint
Sales as a collective ritual
Onboarding joins the discovery meeting to run the demo with the client's real data. Support attends as a technical observer. The client leaves the first interaction operating a platform already configured for their context, not watching a presentation.
POC as switching cost
With the platform pre-configured with real data, the POC stops being a test and becomes operation. The client accumulates configuration and familiarity over the weeks, and switching to another vendor comes to seem too much work. Anchoring through experience, not argument.
Onboarding as consulting
When the client reaches post-signature onboarding already operationally fluent, the team stops teaching how to use it and starts translating the product into the business. Onboarding becomes a space for generating insight, calibrated to each client's niche.
Hand-off as continuity
Retention enters halfway through onboarding, not at the end. The planned overlap replaces the rupture with a gradual handover, preserving the bond built and letting expansion conversations emerge from the relationship itself.
Pillar 05 · The track I led personally
Knowledge base as infrastructure
For the team overlap to work without overloading any of them, the client's autonomy had to grow. I led the expansion of the knowledge base on two fronts: written content (articles, FAQs and technical documentation organized by client niche) and video content (tutorials and webinars). The base stopped being a support repository and became a permanent layer of the journey, available in any phase.
Measured impact
Time-to-Value 30% faster
reduction in the time it takes the client to extract real value from the platform.
What Time-to-Value is. TTV is the interval between contract signature and the moment the client begins extracting concrete value from the product. In B2B SaaS, it's one of the most critical operational health metrics: long TTV means a frustrated client, early churn and difficulty expanding; short TTV means an engaged client, high retention and room for upsell.
In the old model, the clock only started after payment. In the redesigned model, it starts at pre-sales, when the client is already operating the product with their own data.
Early learning
The client reaches the post-sale stage already fluent in the product, eliminating weeks of basic training.
Distributed configuration
The client's data enters the platform during the POC, removing the migration concentrated at onboarding.
Frictionless support
Support's presence from pre-sales onward eliminates technical rework after signature.
Sustained autonomy
The knowledge base lets the client move forward alone between guided moments, keeping the pace.
Systemic impact
What changed in the system
For the client
Earlier learning curve
Reaches onboarding operationally fluent, shortening the activation phase.
Bond distributed across teams
Trust stops depending on a single point of contact and spreads across the journey.
Autonomy between touchpoints
The knowledge base lets the client move between phases without depending solely on people.
For the operation
POC as a conversion driver
A qualified switching cost reduced commercial friction at closing.
Fluid cross-team communication
Shared presence eliminated alignment meetings and context emails.
Upsell as a consequence
Expansion emerged organically from the client's maturity, not from isolated commercial effort.
Takeaway
When service design recognizes that journeys operate in layers rather than steps, the question stops being “how to improve each phase” and becomes “how to orchestrate the right presences at each moment”.
The project showed that client continuity is built in the space between teams, not inside them. It's the Service Designer's job to tend to that space.