System Drift
Dependency Research
Research →
IndexProfilesSalesforceMethodologyCRM-SFDCRevenue Workflow

Salesforce

Salesforce is documented as a configurable platform for customer and revenue workflow. The extent to which commercial process is expressed as platform configuration differs by organization, so this profile describes surfaces rather than measuring dependency.

Documented surface
Records · Configuration · Automation
Category
Revenue Workflow
Status
Evidence review pending
§ 02

Status of this profile

This profile is currently a shell. An earlier version of this page carried numerical concentration and reversibility indices, a dependency tier and a review date. None of those were produced by a documented, reproducible methodology, so they have been removed rather than restated in softer language.

What remains is descriptive: the platform name, its broad category and the product surfaces the vendor publicly documents. Substantive platform-specific findings will be published here only when each is supported by a traceable primary source.

Evidence review pending — no findings published.

§ 03

What a dependency profile examines

System Drift documents the surfaces on which dependency can form. It does not measure any organization's dependency on a vendor.

  • Identity and control surface
    Where authentication, authorization and administrative authority are exercised.
  • Workflow surface
    The everyday operational activity carried out inside the platform.
  • Data surface
    What organizational data is held, and in what form it can be extracted.
  • Integration surface
    The connections between the platform and the rest of the software estate.
  • Governance surface
    Where policy is authored and where compliance posture is read from.
  • Portability mechanisms
    Documented export, migration and interoperability paths the vendor publishes.
§ 04

Questions only an organization can answer

Diagnostic, not advisory. No scores are attached.

  • Which of these surfaces does this organization actually use, and which does it not?
  • Where is configuration stored as exportable artefacts, and where does it exist only in the platform interface?
  • Which documented export or migration mechanisms does the vendor publish for the surfaces in use?
  • What would have to be reconstructed elsewhere before normal operation could resume?
§ 05

Editorial note

This profile is not a product review, a buyer's guide, a feature comparison or a recommendation. It makes no claim that Salesforce is good or bad.

System Drift publishes no numerical dependency score, dependency tier or impact rating for any platform. Dependency is organization-specific, and no reproducible measurement of it exists here. View methodology →

All profilesFrameworksResearch