Salesforce is a commercial CRM platform delivered as a service, with a configurable data model, sales process automation and its own extension environment. The decision around it is rarely about the tool. It is about what an organisation is willing to pay so that knowledge of its customers stops being the private property of individual people.
Quick Overview
What this article covers:
- The cost carried before anyone proposes a CRM system
- The conditions that must hold together for a platform of this class
- The situations in which a CRM platform answers no real problem
- The alternatives and what each of them costs
- The commitment signed by moving to a service model
Who this article is for:
- Sales directors accountable for forecast reliability and relationship continuity
- Architects deciding where the customer record lives and how it is integrated
- Managers budgeting subscriptions, implementation work and skills
The Cost of Customer Knowledge Living in Private Inboxes
No invoice carries the name of the missing system. The bill arrives as losses nobody books separately: a departing account manager takes the conversation history along, the forecast is assembled from opinions rather than data, the same customer receives conflicting quotes, and marketing pays for contacts somebody has already worked. Then the auditor asks the plain question — where does the customer record sit, and who can reach it. That cost accrues daily, whether or not anyone decides anything about tooling.
The problem comes in variants, and confusing them is the most expensive mistake on offer. The first variant is a long sales cycle in which many roles touch the same opportunity: the account manager, pre-sales, legal, delivery. What breaks is continuity of the record — not the absence of a tool, but the absence of a single place where the state of the case is true. The second variant is a process that exists on paper and is never enforced: stages do not match reality, discounts are granted outside any approval threshold, the management report is stitched together by hand at quarter end. What is missing is enforcement, not documentation.
Both variants show sharpest where selling is multi-stage and regulated: banking and insurance, manufacturers selling through distributor networks, subscription services settled by renewals. There, a missing shared record ends in a lost renewal or in a regulator’s question nobody can answer.
Conditions That Make a Platform of This Class the Right Answer
A CRM platform of this class is the right answer when three conditions hold together, not when any one of them holds alone:
- The customer record is shared across roles and across systems. The same entity appears in a quote, a contract, an invoice and a support ticket, and divergence between those views costs real money. The platform supplies a shared data model and access control expressed as roles, not as file permissions.
- Process rules are meant to be enforced by machine. Discount thresholds, mandatory fields at each stage, an approval path and a change trail are requirements, not decoration. If the rules are allowed to remain advice, no tool will rescue them.
- The organisation accepts the service model. The environment, the release cadence and the location of the data belong to the vendor; predictability is bought together with dependence on the vendor’s decisions and its published service status.
Only once those conditions coincide does the next matter arise: extending the platform beyond configuration — custom logic inside the vendor’s development environment, integrations with billing systems, and execution limits that have to be understood before the first line of code. The scope of that work — design patterns, transaction handling, asynchronous processing, integration with external systems — is covered by the Salesforce Programming — Advanced Approach course.
Situations Where a CRM Platform Is the Wrong Answer
The most common mistake is reaching for a platform of this class in the name of “getting sales organised” before anyone has written down how selling is supposed to work. An implementation does not create a process. It freezes the one it finds, defects included, at a price nobody budgeted for.
Beyond that, there are situations in which the platform answers no real problem. Transactional selling with a short cycle, handled by a small team, needs a shared contact list and the discipline to write things down, not a model of roles and permissions. An organisation whose opportunities have no stages, because the customer buys in a single step, has nothing to automate — the stage machinery survives as an empty form field. Finally there is the data regime: if a regulator or an internal policy requires the customer record to stay inside infrastructure the organisation controls, the ruling is made one level above the choice of CRM. Sunk licence cost is not an argument for staying in any of them. Which model may hold the data at all is set out in the article on public, private and hybrid cloud strategy.
Alternatives and What Each One Costs
A lighter CRM delivered as a service costs less in subscription and less to implement, and the price of that saving is a ceiling on extensibility: once the process outgrows configuration, the customer record migrates along with its history, integrations and permissions. A sales module inside an existing ERP adds no vendor contract and keeps data close to settlement, but inherits the ERP release cadence and usually loses on automating the seller’s daily work. An in-house application gives full control of the data model and its location, and its price is the least visible in advance: not writing it, but keeping a team that will extend, patch and integrate it for years.
The remaining path is often the cheapest and the least considered: fixing the process without changing the tool — a named owner of the record, agreed stages, mandatory data, a weekly review. It is sometimes the only one that works, because the others assume a process already exists. Approaches to controlling the recurring spend that grows with user counts and add-ons are compared in the article on cloud FinOps and cost control.
The Long-Term Bill of Buying Sales Software as a Service
What gets signed first is an invoice that grows with the success of the rollout: platform pricing is counted per user and per chosen edition, so each additional seat and add-on raises a standing line in the budget. What gets signed next is a release cadence the organisation does not set: vendor-side changes have to be tested against local extensions, and the window for reacting is drawn from outside.
The most expensive item, however, is not the subscription. It is competence. A platform nobody inside the organisation can configure becomes a dependency on an implementation partner for the smallest field change. The role that lowers that bill is an administrator who knows the data model, permissions, process automation and reporting — the scope of the Salesforce Administrator — CRM Foundation course. Without it, an organisation pays twice over: for the service, and separately for each change made to it.
Frequently Asked Questions
Will a CRM platform organise a sales process we have never written down?
No. An implementation mirrors the process it finds and freezes it into fields, stages and rules. If the process is notional, the tool turns it into a notional form, paid for in subscription and implementation effort. The order runs the other way: agreed stages and a named owner of the record first, tool second.
Is configuration enough, or does this require programming?
It depends on how far the process departs from the model built into the platform. Configuration covers the data model, automation and reports; custom code enters where logic exceeds declarative rules, or where a system without a ready connector has to be integrated. That ruling belongs to the analysis stage — deferring it is a well-known source of budget overrun.
How do we know the organisation has outgrown a simpler system?
By watching the process rules move outside the tool: into control spreadsheets, into approval messages, into a hand-glued management report. While those things still fit inside the tool, changing platform is a cost without a return. Once they fall out of it, maintaining the workaround costs more than migrating.