How the dependency formed
A longitudinal note. Dependency rarely arrives in a single decision.
Adoption usually begins with pipeline management. Over time custom objects, validation rules, and process automation accumulate until Salesforce is the place where commercial process is authored, not merely tracked.
By year four or five, the organization's commercial vocabulary — stages, statuses, role hierarchies — is Salesforce's vocabulary.
The platform read through the five frameworks
Each section applies one of the System Drift frameworks to Salesforce.
Dependency Concentration
Concentration is concentrated in revenue workflow and increasingly extends into service, marketing, and analytics through adjacent products. The dependency is narrow in surface and deep in operational weight.
Few alternatives carry equivalent customization surface, which makes the concentration self-reinforcing once a critical mass of custom objects exists.
Observed indicators- —Commercial process is authored inside Salesforce, not described elsewhere.
- —Reports and dashboards are the canonical view of the business.
- —A small number of administrators understand the full configuration.
Reversibility
Reversibility is constrained by the volume of declarative configuration: flows, validation rules, page layouts, permission sets, and managed package dependencies. The data is exportable; the logic is not, in any portable form.
Replacement systems can hold the records. Holding the rules is the harder problem.
Governance Surface
Governance lives in profile and permission set hierarchies, record-level sharing rules, and field-level security. Approval matrices and forecast hierarchies encode commercial authority directly in the platform.
Auditors and compliance functions increasingly read policy out of Salesforce rather than into it.
Operational Capture
Capture is high. The platform absorbs not only CRM workflow but quote-to-cash, customer success, partner workflow, and field service. Each absorption further binds the organization's operating model to Salesforce's data model.
Workflow that originated in spreadsheets is reliably the next thing to be absorbed.
Exit Complexity
Exit complexity is dominated by re-implementation of declarative logic, retraining of revenue operations staff, and renegotiation of integrations that assume Salesforce as system of record.
Institutional memory of why fields exist, why flows fire in a particular order, and why a given role hierarchy is shaped as it is, is rarely documented outside the system itself.
What separation would involve
A description, not a recommendation.
Separation would require reconstructing the commercial process model in a replacement system, migrating active and historical records, and rewriting the integration graph that points at Salesforce as the system of record. The dominant cost is the recovery of business logic that exists only as Salesforce configuration.
Editorial note
This profile is a dependency study, not a product review. It is not a buyer's guide, a feature comparison, or a recommendation. It does not argue that Salesforce is good or bad. It documents how the platform shapes organizational behavior, where concentration accumulates, and what separation would involve.
The framework readings are revised on the transparent methodology cadence. The indices are analytical signal, not procurement advice.