Total Cost of Ownership:
The Salesforce Numbers Nobody Shares

The Licence Price Is the Smallest Part

Salesforce will tell you the licence price per user per month. Your AE will give you a number — perhaps discounted — and that number will go into the business case as the primary cost. It is almost always the smallest significant cost category in a real Salesforce deployment.

I have sat in too many investment approval meetings where a CFO approved a Salesforce business case based on a licence cost that was presented as the total cost. The implementation cost was described as "one-time" and therefore less important. The ongoing support cost wasn't discussed. The add-on licences were "phase 2." Three years later, the actual annual spend on Salesforce — including licences, support, development, and the consulting partner that never really left — was three to four times what the business case projected.

This tutorial gives you the complete picture. Not to discourage investment in Salesforce — in the right scenarios, the ROI is real. But to ensure that the decision to invest is made with accurate numbers, not optimistic ones.

Cost Category 1: Software Licences

Salesforce licences are priced per user per month, billed annually. The list price is rarely what you pay — discounts of 20-40% are achievable for multi-year commitments and volume, particularly at contract renewal. But the licence structure is more complex than a single price per user.

Full licences vs limited licences. Salesforce has multiple licence types at different price points. A full Sales Cloud Enterprise licence gives access to the full CRM. A Platform licence gives access to custom apps but not the core Sales or Service clouds. A Salesforce Starter licence is limited in its capability. The licence mix matters — and getting it wrong means either paying for capabilities you don't use, or discovering mid-programme that your planned users need a more expensive licence type.

Add-on licences. The base CRM licence does not include Salesforce Shield (field-level encryption, event monitoring), Einstein Analytics (CRM Analytics), Marketing Cloud, Data Cloud, or Agentforce. These are separately priced. A programme that requires any of these — and many regulated industry programmes require Shield — needs to budget for them separately. The add-on costs can approach or exceed the base licence cost.

Storage. Salesforce includes a base storage allocation (10GB data storage per org, 10GB file storage). Large implementations with significant historical data, file attachments, or Chatter use will exceed this. Additional storage is purchased in blocks — and the price per GB is not cheap. Data archiving strategy directly affects your ongoing storage costs.

Cost Category 2: Implementation

For any meaningful Salesforce programme — more than a simple out-of-the-box configuration — the implementation cost will be the largest single cost in Year 1. The ratio of 3-5x implementation to annual licence is not unusual; for complex, multi-cloud, integrated implementations it can reach 8-10x.

Implementation cost has four sub-components:

Partner fees. The cost of the System Integrator — the Salesforce consulting partner doing the implementation. Day rates for senior Salesforce consultants, architects, and developers vary significantly by market and partner tier. For enterprise programmes, a team of 8-15 consultants over 6-12 months is a significant spend.

Data migration costs. Often underestimated. Data assessment, cleansing, transformation, load, and validation is a project in its own right. Programmes with large historical datasets (millions of records), complex data quality issues, or data from multiple source systems should treat data migration as a separate cost line — not a sub-task of the main implementation.

Integration development. Every integration between Salesforce and another system requires design, development, testing, and documentation. Complex enterprise environments with 5-10+ systems to integrate can spend as much on integration as on core Salesforce configuration.

Change management and training. The cost of preparing end users for the new system. This includes communication campaigns, training material development, training delivery, and the internal effort of change management activities. Programmes that treat this as "a few training sessions" invariably have adoption problems post-go-live.

Cost Category 3: Ongoing Support and Development

The implementation ends. The support costs begin. And they do not end — they continue for as long as the Salesforce org is live, which in an enterprise environment is measured in decades.

Salesforce admin capability. Every Salesforce org requires ongoing administration: user management, configuration changes, report and dashboard maintenance, release management for Salesforce's tri-annual platform releases, and first-line user support. The cost depends on complexity — a simple Sales Cloud org for 50 users needs less admin than a complex multi-cloud org for 2,000 users. Budgeting at least 1 FTE for admin capability for any significant Salesforce deployment is a reasonable baseline.

Development and enhancement costs. Business requirements don't stop when the implementation goes live. New processes, new integrations, new automation, new reporting needs — all require ongoing development investment. Programmes that go live with no ongoing development budget typically accumulate technical debt rapidly as workarounds replace proper solutions.

Partner support retainer (if applicable). Many organisations maintain a post-go-live support arrangement with their implementation partner. This is appropriate for the immediate hypercare period and for complex programmes where internal capability doesn't yet cover the full technical scope. The cost should be explicitly planned for and reduced as internal capability grows.

Salesforce Premier Support. Salesforce's standard support has known response time limitations. Premier Support (and Signature Support at the highest tier) provides faster response times, dedicated resources, and proactive advisory services. For organisations where Salesforce is business-critical, the premium is often justified — but it adds meaningfully to the licence cost.

Cost Category 4: Infrastructure and Integration

Salesforce is a SaaS platform — you don't run your own servers. But integrating Salesforce into an enterprise environment has infrastructure costs that are often overlooked.

Integration middleware. If the integration architecture uses MuleSoft, Boomi, Workato, or another iPaaS platform, those platforms have their own licence costs. MuleSoft in particular — owned by Salesforce — has a pricing model that can add significantly to the overall Salesforce cost envelope. Understanding the integration platform cost before committing to an integration architecture is essential.

Monitoring and observability. Production Salesforce environments need monitoring — for integration failures, automation errors, performance degradation, and security events. Third-party monitoring tools (some integrated with Salesforce Shield Event Monitoring) have their own costs.

Salesforce sandbox environments. Development, testing, UAT, and staging environments require Salesforce sandboxes. Sandbox costs are typically included in the org licence, but Full Copy sandboxes — which include complete data replication — can have additional cost implications for very large data volumes.

Cost Category 5: Internal Talent

The internal cost of Salesforce — the time of your own people — is the most frequently omitted cost category in business cases. It is also one of the largest.

Salesforce Admins and Developers. If you're building internal capability (which you should be), the salaries of your Salesforce Administrator, Developer, and eventually Architect represent a significant ongoing cost. The Salesforce talent market is competitive — experienced professionals command premium salaries, particularly in major markets.

Business Analyst and Product Owner time. Managing the Salesforce backlog, writing requirements, coordinating releases, and engaging with the partner team requires sustained internal effort. These are not additional headcount in most programmes — they're existing employees with existing salaries whose time is partially reallocated. That reallocation has a cost, even if it doesn't appear as a new line in the budget.

IT infrastructure and security team time. Salesforce integration, SSO setup, security review, and ongoing governance all require IT involvement. This is rarely zero — particularly in the first year.

Building the 5-Year TCO Model

A credible TCO model for a Salesforce investment should project costs over at least 5 years, for two reasons. First, the return on investment in an enterprise Salesforce programme typically becomes clearer in Year 2-3 — Year 1 is dominated by implementation costs. Second, the cost profile changes materially year-on-year as licence counts grow, internal capability matures, and ongoing development replaces partner implementation.

The five-year model should include:

• Year-by-year licence costs, with an assumption for user count growth and price increases at renewal
• Implementation costs in Year 1 (and Year 2 if phased), with a clear scope boundary
• Ongoing support costs from Year 1 onward, declining as internal capability grows
• Development investment (enhancement backlog) from Year 1 onward
• Add-on licence costs if any are required (Shield, Analytics, Data Cloud)
• Internal headcount costs for the Salesforce Centre of Excellence