WORKFLOW / SYSTEM OF RECORD
Salesforce
Use Salesforce as the CRM authority when outbound needs field governance, auditability, and RevOps control.
ROLE
System of record
Workflow
LAYER
crm
primary stack layer
USED IN
1
public stacks
PRICING
Seat-based
Cost scales mainly with users or workspace seats.
LOCK-IN
High
modeled risk
OWNER
RevOps
CRM admin or RevOps owner
ROLE INSIDE THE STACK
Salesforce is evaluated by the job it owns inside a stack: system of record in the crm layer. The buyer question is whether that layer already has an owner, not whether the tool is broadly popular.
Where it shines
- 01Salesforce is already modeled in 1 public stack.
- 02Cost scales mainly with users or workspace seats.
Where it struggles
- 01Light founder-led motions where admin overhead slows learning.
- 02Stacks without a CRM owner or data governance rules.
Avoid if
- 01No CRM admin or RevOps owner exists.
- 02The team needs the lowest possible outbound budget.
WHEN REDUNDANT
Skip Salesforce for the stack if HubSpot already provides enough CRM governance for the current team size.
Redundant with
FOUND IN