A Salesforce enterprise cost estimate should cover the subscription, the work needed to put it into use and the cost of maintaining it. A per-user price answers only part of the buying question. The useful comparison is what each proposal includes and what your team would still need to fund.
Keep this budget separate from the expected benefits. A licence purchase does not establish that the team will save time or win more business. Those outcomes need their own assumptions and a way to check them.
Check the current product and price
On 29 September 2026, the US Salesforce Sales pricing page lists Core at US$195, Advanced at US$395 and Max at US$550 per user per month, billed annually. The page also lists Free, Starter and Pro suites. Treat these as published list prices, not a quote for your organisation.
If an existing agreement uses names such as Enterprise or Unlimited, ask Salesforce to explain the options for that agreement. Do not assume that an older edition name maps directly to a current package or that every advertised feature is included in a renewal.
Use the Salesforce pricing guide for the broader plan comparison. This article focuses on the costs and decisions around a larger implementation.
Build the estimate around the work
Subscription and usage
List the people who need access, what they need to do and when they will start. Check the proposed licence rights for each group. A cheaper licence helps only if it permits the work required.
Ask the supplier to identify separately priced products, support, capacity and usage-based charges. Record the currency, billing period and assumptions alongside each amount so that competing proposals can be compared on the same basis.
Implementation and data
Describe the workflows to configure, records to migrate and systems to connect. Request an estimate for that scope rather than applying an unsupported percentage to the subscription price.
Include work your own team must do: agreeing field definitions, cleaning records, reviewing permissions and testing the result. A supplier’s estimate may exclude these tasks even when the project depends on them.
Training and ongoing ownership
Budget for users to learn the revised process and for someone to maintain it. Identify who will handle access changes, reports, data issues and requests for new automation after launch.
Separate the initial setup from recurring work. This makes it easier to see whether an apparently cheaper first year creates obligations that the later budget has missed.
Compare proposals with the same assumptions
Consider a fictional team comparing two implementation offers. One includes data cleanup and user training; the other covers configuration only. Comparing their totals without adjusting the scope would give a misleading result.
Ask each supplier to price the same required outcome and identify exclusions. Record where an amount is fixed, estimated or dependent on an unresolved decision. Keep a provision for uncertainty visible rather than presenting an incomplete total as firm.
Review the agreement before relying on it
Have the people responsible for procurement and contract review check the proposed term, payment obligations, renewal process and rules for adding or reducing access. Confirm support commitments and any usage limits in the actual documents.
Do not assume that every enterprise purchase has the same agreement structure, discount or service commitment. Resolve important questions in the proposal and contract before using them in the business case.
Keep checking the cost after launch
Assign an owner to compare actual usage and support work with the estimate. Investigate unused access and repeated manual work, while checking the agreement before assuming a subscription can be reduced.
Review renewal decisions early enough to gather evidence and consider alternatives. The timing should reflect your notice obligations and internal buying process. Keep the sales process under review too: a configuration that supports obsolete work may need attention before another tool is added.
