What this covers
- The friction is linguistic
- Stages are the bigger problem
- Configuration is not customisation
- What good configuration looks like
The friction is linguistic
A recruiter does not think in Deals. A law firm does not think in Accounts. A clinic does not think in Leads. When the software insists on vocabulary that does not match the work, every interaction carries a small translation cost.
One translation is trivial. Fifty a day, across a team, for a year, is why the CRM ends up half-updated and the real pipeline lives in someone spreadsheet.
Stages are the bigger problem
Vocabulary is annoying. Missing stages are damaging. If your process contains a decision point the CRM cannot represent — a conflict check, an insurance approval, a sampling round, an advance payment — then deals sit in an approximate stage and the forecast inherits that approximation.
Teams notice this quickly, and they respond rationally by trusting the CRM less.
Configuration is not customisation
Most CRMs allow custom fields and custom stages, which sounds like the same thing. It is not. Custom configuration is work someone has to do, maintain and document, and it typically happens once during implementation and then decays.
Shipping preconfigured industry packs is a different proposition: the vocabulary and stages are correct on day one, and nobody has to become the internal CRM administrator.
What good configuration looks like
Records named the way the team speaks. Stages that match the real decision points. Reports that answer questions the business actually asks. None of that is exotic, and all of it materially changes whether the CRM gets used.