Omnichannel Orchestration Architect · Interim & consulting · available now

Your omnichannel ambition is set. The foundation beneath it isn’t. For pharma.For medical.For financial institutions.

I connect your silos – CRM, marketing clouds, data warehouse and lakehouse – into one unified customer profile and activate it across all channels: MLR-compliant and auditable.

No obligation · 30 minutes

Enterprise project experience

  • Bristol Myers SquibbPharma, global
  • Consors Finanz BNP ParibasFinance
  • Amoena Medizin-Orthopädie-TechnikHollister IncorporatedMedical technology
  • Bosch SicherheitssystemeIndustry

Sound familiar?

The typical breaking points before an orchestrated system exists.

Silos instead of a system

Every channel runs on its own – no connected journey.

No unified customer view

HCP/HCO data scattered, identity and consent unresolved.

Architecture undefined

Ambition is there – target picture and data flows are missing.

MLR slows the pace

Approvals slow, the process doesn’t scale.

Vision without a roadmap

Strategy without a prioritized execution plan.

Teams without a shared language

Business, IT and data – the translator is missing.

The approach

From silos to an orchestrated system

The problem is rarely the tool – it’s the foundation beneath it. I connect CRM, marketing clouds and your warehouse landscape into a data core that carries every journey: identity-safe, consent-driven, MLR anchored in the process.

My services
From silos to an orchestrated systemA company’s systems feed a shared foundation of identity graph, unified profile and segments; from there four channels are activated. A consent withdrawal travels through the foundation and stops activation across every channel. YOUR SYSTEMSFOUNDATIONACTIVATION RESPONSES & SEGMENTS BACK INTO THE WAREHOUSE Your systemsCRM · WAREHOUSEEVENTS · CONSENT Identity GraphCRMID · ECID Unified ProfileMAIN ID · CONSENT SegmentsSTREAMING · EDGE EmailWebApp pushField force CONSENT WITHDRAWN PROFILE REMOVED 4 CHANNELS STOPPED

How to read it: a consent withdrawal in the CMP travels over the bus into the unified profile, removes the profile from the affected segments – and stops activation on all four channels.

Case study · Financial services

Bank data into the public cloud – and through the audit

A consumer-finance institution replaces its email system with Adobe Journey Optimizer. The hardest part was not the rollout but releasing internal customer data: an attribute catalogue with purpose and retention, schema design, evidence for three review bodies.

Read the case study
20months to handover
3on-site workshop days
10+people trained
✓production ready
Fundamentals · Article

What Omnichannel Really Means – for Four Roles in the Company

Marketing, analytics, leadership and architecture each mean something different by omnichannel. The article shows what each role gets from it, where it fails and what they need from each other. Backed by vendor documentation and peer-reviewed studies.

Read the article →
MarketingAnalyticsCMOArchitecture
Omnichannel in practice

One profile. Every channel. The right moment.

What orchestration looks like in practice – from signal to delivered message.

Closing frame of the animation: Seven channels. One conversation. – The moment decides, not the campaign calendar.
Example scenario with fictitious values. Adobe and Adobe Journey Optimizer are trademarks of Adobe Inc. No partnership with or endorsement by Adobe is implied.

One identifier, one person

Email, app, web and CRM converge on one main identifier.

The right moment

The journey reacts to signals and delivers on the right channel – all the way to the website.

Dry Run & Forecast

A fictitious audience runs through the journey before go-live – bottlenecks become visible.

MLR anchored in the process

Consent, governance and MLR-compliant approvals are part of the architecture – not bolted on afterwards.

Zero-copy instead of data copies

Snowflake, Databricks and BigQuery are connected federated – without costly sync jobs.

Enabled instead of dependent

Enablement, co-building and hypercare – your team takes over confidently, not the agency.

Insights · From real rollouts

Want to know how omnichannel actually gets built in the enterprise?

What actually happens in rollouts: new Adobe, Salesforce and Veeva releases put in context, architecture decisions explained, integrations and workflows from real projects – increasingly including AI workflows and MCP. New deep dives regularly.

RolloutsReleasesIntegrationsAI workflowsArchitecture
Latest deep dive Could this happen to us? When sensitive customer data reaches the wrong department – and how Salesforce Data 360 governance prevents it Salesforce & Veeva · September 2026 Explore the insights
Christopher Dettinger – Omnichannel Orchestration Architect
The person behind it

Christopher Dettinger

Omnichannel Orchestration Architect

The translator between business, data and technology: hands-on on the “how” behind omnichannel – target architecture, data foundation and orchestration, in global multi-country environments at different maturity levels.

10+
years of martech, CRM & omnichannel
2
enterprise stacks: Adobe & Salesforce/Veeva
3
regulated industries: pharma, medical, finance
360°
view of the customer – one profile, every channel

What I build for you

Hands-on architecture instead of slide decks – eight building blocks, individually or as a program.

Assessment & gap analysis

Transparency across systems, data and gaps – documented, not claimed.

Target architecture

Target picture, data model and integration paths – as a resilient blueprint.

Unified Customer Data

One profile from CRM, web and warehouse – identity-safe and consent-driven.

Cross-Channel Orchestration

Journeys across email, web, app and field force – signals instead of campaign calendars.

Compliant Content Lifecycle

MLR approvals in Veeva Vault PromoMats, modularization and reuse – anchored in the process.

Roadmap & Operating Model

Prioritized execution plus roles, rituals and responsibilities.

Team Enablement & Co-Building

Training, building together and hypercare – your team takes over with confidence.

Measurement & ROI

Attribution, journey reporting and KPIs – the value contribution becomes visible.

Stacks & technologies I build with

Adobe Experience PlatformAdobe Journey OptimizerReal-Time CDPAEMSalesforceVeevaSnowflakeDatabricksApache Kafka Adobe Experience PlatformAdobe Journey OptimizerReal-Time CDPAEMSalesforceVeevaSnowflakeDatabricksApache Kafka

How we work together

01

Assessment

Full transparency: systems, data, capabilities – and what’s missing.

02

Architecture

A clear target picture: target architecture and data model – defined in phase 1.

03

Pilot & Roadmap

First use cases live – plus a roadmap for scaling and capability building.

04

Enablement & handover

Training, documentation and hypercare – your team takes over confidently, the knowledge stays in-house.

Empowerment over dependency

Your team makes data-driven decisions – and runs the system itself

Role-based training in your own environment, co-building the first real journeys, documentation and playbooks in-house, hypercare after handover. For directors that means investment security: teams become independent, the stack delivers measurably.

See enablement in detail
Example · dry run in Adobe Journey Optimizer

Decide before the journey starts

A fictitious test group runs through the entire journey – before a single real message goes out. Reach and bottlenecks per step become visible while corrections still cost nothing.

Dry run in Adobe Journey OptimizerA fictitious test group of 10,000 profiles passes through consent gate, email, wait time and an open-rate branch; the forecast shows reach per step and flags the consent gate as the bottleneck, with 580 profiles lost. DRY RUN · FICTITIOUS TEST GROUP · 10,000 PROFILES NO SENDING · ZERO RISK GO Start 10.000 Consent gate 9.420 ✉ Email 9.420 3 d Wait ? opened? 62% 38% Web personalization 5,840 profiles App push · reminder 3,580 profiles NO CONSENT · 580 BOTTLENECK · consent gate: −580 profiles (−5.8%) FIX · double-opt-in refresh before journey start

← Swipe to explore →

Schematic simulation with fictitious values. Adobe, Adobe Journey Optimizer and Real-Time CDP are trademarks of Adobe Inc. No partnership with or endorsement by Adobe.

Frequently asked questions

What does 360° omnichannel actually mean?
One system instead of silos: CRM (Salesforce/Veeva), web (AEM), content (DAM), the data layer (Data Cloud / CDP) and your internal data world (warehouse, lakehouse) work connected – one unified customer profile, activated across all channels, from field force to digital.
Interim role or project – how do you work?
Both. As an interim omnichannel orchestration architect I take on the role for a defined period; alternatively I support a scoped initiative as a consultant – from assessment to implementation.
We use Adobe and Salesforce in parallel – does that work?
That’s exactly what I’m here for. The value is created in the integration: I build the bridge between both worlds – vendor-neutral and aligned to your maturity level.
How fast do we see results?
Phase 1 already delivers the target architecture, the data model and full transparency about gaps. Pilot use cases follow, showing integrated journeys for real.
Why the focus on regulated industries?
Pharma, medical and finance need consent, governance and MLR-compliant processes from day one. With me, these requirements are part of the architecture – not bolted on afterwards.
How do you make sure my team can run the system afterwards?
Enablement is a fixed part of every project: role-based training, co-building the first journeys, documentation and playbooks in-house – plus a hypercare phase after handover. Details on the enablement page.

Let’s run your assessment.

In a first conversation we’ll clarify where your omnichannel foundation stands and where the biggest levers are.

Request an assessment