Salesforce
What it is
A CRM built for sales organizations with structure: territories, permission layers, approval chains and a sales motion complicated enough to need custom objects.
What it’s good at
Permission and territory models that hold at scale, so hundreds of reps see exactly the accounts they should. Deep customization, bending the object model to unusual sales motions where lighter CRMs force you to flatten the process. And endurance: companies grow past a few hundred people without leaving it.
What it costs to own
An administrator is a standing role: profiles, permission sets, integrations and the stream of change requests from sales leadership, becoming a full-time hire past a few hundred users. Every customization is deferred maintenance that the next administrator must decode before changing anything. Left unowned, the instance ossifies, reps route around it, and the pipeline report drifts from reality.
When it’s a poor fit
You are under a hundred people and hoping the system will supply the process; it records the process you already run, and without one it tends to become an expensive, mostly empty database. Marketing needs to live in the same system, which means buying and integrating a second platform on top. Or the champion is a new sales leader rebuilding a former employer’s setup without the former employer’s ops team.
What it sits beside
At the top end it replaces HubSpot or Pipedrive. It is usually bought alongside a marketing automation platform, and the contact sync between the two is where reporting breaks: two systems, each holding its own version of the customer. The integration is therefore part of what the purchase costs.
My experience
In the companies under a hundred people where I have seen Salesforce bought, it was usually the process that was missing, and the system could not supply it.