In short
- Health insurers overpay for Salesforce when they license seats nobody uses, editions above what a role needs, and add-ons for everyone that only one team uses.
- Salesforce bills per user per month on annual terms, and it raised list prices by an average of 9% in August 2023 and 6% in August 2025, so unused seats cost more at every renewal.
- You can audit your own bill with your order forms and a user list with last login dates, then right-size seats, move roles to cheaper editions, or move a poorly fitting workflow off the platform.
Mid-size health insurers overpay for Salesforce when the bill grows with headcount while the value does not. The usual causes are seats nobody uses, editions above what a role needs, add-ons licensed for everyone but used by one team, security tooling bought without a clear owner, and renewals that rise with list price. Per-seat pricing drifts this way whenever nobody audits it, and you can find each leak in your own org with data you already have.
An industry-wide overpayment figure would tell you little about your own bill. Only your contract and usage data show what you overpay, and the steps below measure it from them.
How does Salesforce pricing work for a health insurer?
Salesforce prices its clouds per user per month and bills them annually. Health Cloud, the healthcare edition, lists at $350 (Sales & Service Core), $525 (Advanced), $700 (Service Max or Sales Max) and $725 (Sales & Service Max). Standard Sales Cloud lists at $195 (Core), $395 (Advanced) and $550 (Max). Salesforce says these list prices are for information only and subject to change.
Two things follow from that structure. First, every user you add costs the full edition price, whether that person uses one screen or fifty. Second, you commit for a year at a time, so the seat count you sign at renewal is the seat count you pay for until the next one.
For PHI, Salesforce signs a Business Associate Addendum, and its restrictions page lists which services are covered. Health Cloud, Sales Cloud, Service Cloud and Experience Cloud are on the list. The customer must encrypt PHI transmitted using those services, and it is responsible for the compliance of any third-party services it connects.
Where does the overpayment come from?
Seats nobody uses
People leave, change roles or never really started. If their licenses are not removed, you keep paying for them. Insurers that sell Medicare plans have a specific version of this problem. The Medicare Open Enrollment Period runs October 15 to December 7, and the Medicare Advantage Open Enrollment Period runs January 1 to March 31. If you add agents for those windows and your contract counts seats for the year, you may pay for peak headcount all year. Check whether your contract lets you lower the count at renewal, or only raise it.
Editions above what a role needs
Health Cloud Sales & Service Core lists at $350 per user per month. Sales Cloud Core lists at $195. That is a $155 gap, or $1,860 per user per year at list price. If some of your users only log calls, update a lead status and run a report, ask whether they need the healthcare data model at all. Check with Salesforce which objects and features each license type can reach before you mix editions, because that decides what each group can see.
Add-ons licensed for everyone
Some features are sold on top of the edition. Health Cloud's pricing page lists Knowledge, Chat and Facebook Messenger at an additional $75 per user per month in certain editions, and marks several other features, including Digital Insurance, as available for purchase. Storage is also tied to edition: Core includes 20MB per user and the other editions include 1GB per user. A feature bought for a service team and then licensed to every user is a common place for money to sit idle.
Security tooling with no public price
Salesforce Shield bundles Platform Encryption, Event Monitoring, Field Audit Trail and Data Detect. Its page says pricing varies by customer and has no public figure. Because the BAA requires you to encrypt PHI in transit through the covered services, encryption and audit tools are often part of a healthcare deal. Find the Shield line in your order form, confirm who uses Event Monitoring and Field Audit Trail, and check that the settings match what your compliance team believes is turned on.
Renewal increases
Salesforce raised list prices by an average of 9% in August 2023 across Sales Cloud, Service Cloud, Marketing Cloud, Industries and Tableau. It announced another average increase of 6% effective August 1, 2025, for Enterprise and Unlimited editions of Sales Cloud and Service Cloud, Field Service and select Industries clouds. Your contract decides how list changes reach you. Every idle seat costs more after each increase that applies to you.
Customization you pay for twice
When the platform does not fit a workflow, teams pay a partner or an internal admin to bend it, and then pay again to keep the change working through releases. That cost is real even though it is not on the Salesforce invoice. Count it next to the license line.
How do you audit your own Salesforce bill?
You need three things: your current order forms, a list of assigned licenses by type, and an export of all users with role, profile and last login date. Then work through these steps.
- List every product and add-on on the order forms, with quantity, unit price and renewal date.
- Count assigned licenses by type and compare them to the quantities you pay for. Unassigned paid licenses are the first saving.
- Mark users with no login in the last 90 days. Confirm with managers whether each one still needs access.
- Group active users by role and write down what each role does in the CRM, in one sentence.
- Compare each role to its edition. Flag roles that use only basic records, tasks and reports on a premium edition.
- For each add-on, name the team that uses it. If nobody can, flag it.
- Read the renewal clause: notice period, how seat counts can change, and how list price changes apply.
Then put a number on each flag:
idle_seat_cost = idle_seats x price_per_user_month x 12
edition_gap_cost = users_on_premium_edition_who_need_less x (premium_price - lower_price) x 12
addon_waste = addon_seats_without_a_user x addon_price x 12For example, 20 idle Health Cloud Core seats at list price cost 20 x $350 x 12 = $84,000 a year. Your real figure depends on your discount, but the structure of the calculation is the same.
What can you change at renewal?
- Remove idle seats and unassigned licenses before the renewal date.
- Move roles that need less to a lower edition, after checking what data those users must still see.
- Drop or narrow add-ons that only one team uses.
- Ask for the renewal increase terms in writing, and for seat flexibility if your staffing is seasonal.
- Price the workflows that do not fit, and decide whether to fix them inside Salesforce or move them out.
Sometimes the cheaper fix stays inside Salesforce. For a US medical support center, we built a custom Salesforce app in 2 months with 1 specialist, because by default Salesforce forms list every field and cannot hide fields by request type. The app shows only the fields that matter for each request type and routes each request to the responsible staff.
When is leaving Salesforce the right call?
Leaving makes sense when most of your users need a narrow, insurance-specific workflow, the license line keeps growing with every hire, and the platform features you pay for go unused. It makes less sense when you use many Salesforce products together, have staff who know the platform well, and the workflow fits the data model.
A California health insurer took the first path. Its account managers needed a CRM for leads, opportunities and customers, and buying accounts and functionality from off-the-shelf platforms was cumbersome and impractical financially. We built a custom HIPAA-compliant CRM on the company's private server between January and June 2023, with 5 specialists. The company made a one-time payment instead of paying monthly third-party CRM fees, and now pays only for hosting and maintenance.
Moving off Salesforce has its own costs: migrating records and history, rebuilding reports and integrations, training staff and maintaining the new system. Put those in the same five-year model as the renewal you are trying to avoid. The companion TCO comparison shows how.
What compliance checks apply when you change anything?
- Check every product and connector against Salesforce's BAA restrictions page. A new tool outside the covered services can take PHI outside the BAA.
- Keep encryption and audit settings in place when you move users between editions.
- If you sell Medicare Advantage through third-party marketing organizations, keep the link between CRM records and call recordings. Under 42 CFR 422.2274, those marketing and sales calls must be recorded and retained.
- Export and keep audit history before you remove a product that held it.
Want help reading your bill?
Talk to an engineer at Onix Health. We offer a 5-day free technical audit that ends with a written report, so you have the numbers in hand whether you stay, trim or move.
Sources
- Salesforce: Health Cloud pricing
- Salesforce: Sales Cloud pricing
- Salesforce: Shield
- Salesforce: Business Associate Addendum restrictions
- Salesforce: pricing update, June 2025
- Salesforce: new list pricing effective August 2023
- Medicare.gov: joining a plan (enrollment periods)
- 42 CFR 422.2274: agent, broker and third-party requirements