Where Salesforce may fit
Salesforce can serve as a CRM and workflow foundation while also extending into customer data, marketing, service, commerce, analytics and integration. That breadth creates architecture choices around system-of-record boundaries, customer identity, cross-cloud data flows, process ownership, integration and the division between Salesforce-native and external capabilities.
Decisions the architecture must make explicit
- 01
Which Salesforce clouds and capabilities are required, and which responsibilities should remain outside Salesforce?
- 02
Which systems own customer, account, identity, consent, interaction and analytical data?
- 03
How should customer context move between Salesforce and data, digital, service and channel platforms?
- 04
Which processes require shared governance across marketing, sales, service, data and technology teams?
- 05
What sequencing and readiness evidence is needed before consolidation, migration or expansion?
Where independent advice can help
- Frame one consequential Salesforce scope, fit or vendor decision before commercial or delivery commitments harden.
- Define portfolio boundaries and target architecture across CRM, customer data, engagement, service, commerce, analytics and integration.
- Assess capability overlap, governance, decision rights, operating ownership and implementation readiness.
- Challenge programme, vendor and integrator decisions against the agreed architecture without taking over implementation delivery.
Boundaries and non-fit
- Salesforce administration, configuration, managed services or production support
- Detailed solution build, data migration execution or programme management
- Licence resale, formal tender administration or vendor negotiation
- An engagement whose recommendation must favour Salesforce