Salesforce Architecture at Scale

1 min read
In This Article

The Challenge

When I joined SiriusXM, the Salesforce org had grown organically over several years. Multiple teams had built solutions in isolation, leading to duplicated logic, inconsistent data models, and integrations that were difficult to maintain. The platform needed a cohesive architecture that could scale with the business.

My Approach

Discovery & Assessment

I started by mapping every integration, automation, and custom object across the org. This audit revealed over 40 process builders and workflows that could be consolidated, and several integration points that were prone to failure without proper error handling.

Architecture Design

I designed a layered architecture that separated concerns clearly:

Implementation

The rollout was phased over three quarters to minimize disruption:

  1. Q1: Migrated legacy process builders to Flow, reducing automation count by 60%
  2. Q2: Implemented the integration framework with proper retry logic and dead letter queues
  3. Q3: Data model refactoring with backward-compatible field migrations

Results

Key Takeaways

The biggest lesson was that architecture isn’t just about the technical design - it’s about getting buy-in from every team that touches the platform. I spent significant time building documentation, running workshops, and creating self-service tools so teams could work within the new framework independently.


This case study covers work completed at SiriusXM in 2024. Specific implementation details have been generalized to protect proprietary information.