Experience

Five architecture engagements across enterprise CRM, healthcare, pharmaceuticals, and frontline operations — each involving platform consolidation, integration redesign, or operating model alignment at scale.

2023–2024

Enterprise CRM and Platform Architecture

CRM Consolidation · 10 000+ users

Challenge

CRM capabilities had grown across multiple patterns, making integration behavior harder to predict and change increasingly expensive. Shared data was inconsistent, and integration points multiplied with each new delivery.

Approach

Established shared platform standards, clearer application boundaries, and a phased roadmap that aligned business processes, shared customer data, and core technology platforms without expanding the estate unnecessarily.

Tech Stack

Salesforce MuleSoft Event-Driven Integration Data Mesh

Impact

  • Improved release predictability across shared platform
  • Reduced integration surface area by consolidating point-to-point connections
  • Supports high user and transaction volume with stable throughput

Architecture Shift

Before: Point-to-Point Growth

After: Platform-Centred Boundaries

Simplified C4 container view. Exact topology varies by engagement.

2022–2023

Provider Network Modernization

Healthcare Platform · Salesforce Health Cloud

Challenge

A healthcare provider platform relied on aging systems where workflows and integrations were tightly coupled and difficult to evolve without cascading side effects.

Approach

Introduced cloud architecture on Salesforce Health Cloud, separated provider workflows from partner-facing integrations, and clarified how operational data moves between business capabilities and supporting platforms.

Tech Stack

Salesforce Health Cloud AWS Event Streaming API Gateway

Impact

  • Workflow modernization decoupled from external partner connections
  • Improved operational visibility without sacrificing delivery stability
  • Cleaner data flows enabled phased migration with controlled risk

Architecture Shift

Before: Tightly Coupled Workflows

After: Separated Concerns

Simplified C4 container view. Exact topology varies by engagement.

2021–2022

Global Contract Management Transformation

CLM Platform · Multi-system Orchestration

Challenge

Contract lifecycle capabilities were distributed across systems and teams, creating orchestration friction in a business-critical process. Inconsistent data models made cross-system reporting unreliable.

Approach

Used Salesforce, cloud services, and a service layer to coordinate contract business processes, clarify application ownership, and establish a coherent data model across the supporting technology stack.

Tech Stack

Salesforce Apttus/Conga Azure Service Bus Power BI

Impact

  • Delivery coordination improved across distributed teams
  • Platform became easier to adapt as requirements evolved
  • Cross-system reporting became consistent and reliable

Architecture Shift

Before: Fragmented CLM Ownership

After: Service-Layer Orchestration

Simplified C4 container view. Exact topology varies by engagement.

2020–2021

Frontline Workforce Transformation Platform

Mobile-First · 25 000+ frontline users

Challenge

Frontline teams were operating with fragmented tools, making field collaboration and operational consistency difficult at scale. Delivery had to balance frontline usability against the complexity of distributed operations.

Approach

Designed a mobile-first Salesforce platform matching frontline business processes, kept field applications simple, and phased supporting data flows around real operating constraints.

Tech Stack

Salesforce Field Service Mobile SDK Offline-First MuleSoft

Impact

  • Supported 25 000+ frontline users at scale
  • Improved day-to-day collaboration across distributed operations
  • Phased delivery reduced transformation risk without sacrificing scope

Architecture Shift

Before: Fragmented Field Tools

After: Unified Mobile Platform

Simplified C4 container view. Exact topology varies by engagement.

2019–2020

Global Pharmaceutical Commercial Platform

Multi-Region · Salesforce Unification

Challenge

Regional commercial platforms had diverged over time, making global reporting, integration, and governance increasingly difficult. Local variations compounded the data inconsistency problem.

Approach

Unified regional systems into a Salesforce-centred operating model with shared commercial data, clearer application and integration boundaries, and controlled regional variation across the platform landscape.

Tech Stack

Salesforce Veeva Snowflake Informatica Tableau

Impact

  • Commercial users moved to a more consistent operating platform
  • Architecture set a stronger foundation for analytics and AI capabilities
  • Regional variation controlled through configuration, not code divergence

Architecture Shift

Before: Diverged Regional Platforms

After: Global Shared Platform

Simplified C4 container view. Exact topology varies by engagement.