Insurance agencies · choosing the cloud
Financial Services Cloud is built to hold the policy.
If Epic holds it, Service Cloud is usually enough.
A small agency that keeps its policies in Applied Epic or another agency system usually needs Service Cloud Core with a light Policy object, at $195 per user a month. Financial Services Cloud starts at $325 and includes its insurance brokerage features from $500, and it earns that price when Salesforce itself is meant to hold policies, producers and commissions. Below are the prices side by side, what the insurance data model contains, and the choice made for a trucking insurance agency in the US.
Reviewed 1 November 2026.
The short answer
Does a small insurance agency need Financial Services Cloud?
Not while the agency system stays the system of record. The service desk needs to see the policy number, carrier, line, dates, premium and billing type, and a custom Policy object carries that. Financial Services Cloud pays off when policies, renewals and commissions are meant to live in Salesforce instead of the agency system.
| Licence and data model | Service Cloud Core | Financial Services Cloud, Service Core | Financial Services Cloud, Service Advanced |
|---|---|---|---|
| List price per user per month, billed annually | $195 | $325 | $500 |
| Extra a year for ten users, at list | The baseline | $15,600 | $36,600 |
| Email to Case, queues, the service console | Yes | Yes, built on Service Cloud Core | Yes |
| The policy record | Your own object with a handful of fields | InsurancePolicy, a standard object with more than 90 documented fields | The same |
| Who is on the policy | Account and contact | InsurancePolicyParticipant: owners and beneficiaries | The same |
| Who sold it | A user or a field | The Producer object | The same |
| Insurance Brokerages: policy actions and commissions | No | Not included | Included |
| Billing type values | Yours, for example three | Agency Billing, Direct Billing | The same |
Prices in US dollars from the Service Cloud and Financial Services Cloud pricing pages, read on 31 October 2026; both pages list the same figures in euros. The extra a year is the list price difference times ten users times twelve months. Objects and fields from the Financial Services Cloud Developer Guide, Winter ’27, updated 23 October 2026. The three billing types are the reference agency’s.
What the data model holds
What does the insurance data model in Financial Services Cloud give you?
Standard objects for the policy and everything around it: InsurancePolicy with more than 90 documented fields, coverages, insured assets, participants such as owners and beneficiaries, producers, claims and policy transactions. Salesforce’s own insurance features work on these objects directly. A custom Policy object gives the desk what it reads, and none of the machinery around it.
- 01
InsurancePolicy
Named insured, producer, writing carrier, line of business and line of coverage, effective and expiration dates, premium, billing type and status. It also has SourceSystem and SourceSystemIdentifier, documented as the ID of the record in the system it came from: the natural place for an Epic key.
- 02
Coverages and insured assets
InsurancePolicyCoverage holds each coverage with its limits and deductible; InsurancePolicyAsset is, in Salesforce’s words, the customer property insured through the policy. A truck or a building becomes its own record under the policy.
- 03
Participants and producers
InsurancePolicyParticipant joins a policy to accounts, so owners and beneficiaries are records, not text. Producer represents an agent or an agency selling insurance, which is what producer splits and commissions are calculated on.
- 04
Brokerage actions, from the Advanced edition
The Insurance Developer Guide, Winter ’27, updated 23 October 2026, lists actions to issue, endorse, cancel, reinstate and renew a brokerage policy, compute producer splits and create producer commissions. Salesforce’s agency page adds direct bill commission processing from carrier statements.
The brokerage actions are in the Insurance Developer Guide; commission processing is on Salesforce’s insurance agency page, both read on 31 October 2026.
Being fair to both
When is Financial Services Cloud worth the price?
When Salesforce is meant to become the place where policies are written, renewed and paid on: renewals and commissions run there, Applied’s connector fills the standard policy objects, or producers sell from Salesforce with the whole book on the record. If none of that is planned for this contract term, the difference buys features nobody opens.
- 01
Salesforce is taking over part of the agency system
Renewals, endorsements or commissions are meant to run in Salesforce rather than in Epic. That is what the brokerage actions are for, and rebuilding them on a custom object is a project of its own.
- 02
Applied’s connector will fill the policies
Applied says its connector has specific integrations with Financial Services Cloud for policy terms, lines and agency structure. If you plan to sync, the standard objects are where the data is meant to land.
- 03
Producers sell from Salesforce
When producers work their book in Salesforce, they need each client’s policies, coverages and participants on the record, and those relationships are already modelled.
Service Cloud with a light Policy object is enough when
- 01
Epic stays the system of record
The desk reads the policy and changes it in Epic. A copy with a handful of fields answers which carrier, which line and when it expires.
- 02
The pain is the inbox
Lost emails, two replies, nobody knowing who owns a request. None of that needs an insurance data model; it needs Email to Case, queues and ownership rules.
- 03
The contract term will end before any of the above
Licences renew. Buy the edition for what the agency will run in this term, and move up when the plan changes.
One agency’s choice
What the agency in our case chose, and why.
A trucking insurance agency in the US, on Applied Epic, went with Service Cloud Core. Two decisions written into the project drove it. Epic stayed the system of record with no integration, and tasks told the agent what to enter there. And Pro Suite stops at five flows per org, too few for policies, renewals and policy changes, as measured on the edition limits page.
With Epic holding the policy, the Salesforce Policy object needed only what the desk reads: number, client, carrier, underwriter, line of coverage, effective and expiration dates, premium, billing type and status. The billing type is where Financial Services Cloud would not have saved work. The agency’s policy changes run different steps for agency bill fleet, agency bill non fleet and direct bill: three values. The standard BillingType field lists two, Agency Billing and Direct Billing, so the split that drives the process would have been custom either way.
How the desk was built is in the insurance agency case study. What the licence bill depends on beyond the list price is in the Service Cloud pricing article.
Before you sign either
Three checks that change the answer.
- 01
Which edition the demo was on
Insurance Brokerages is included from Advanced, and Digital Insurance from Max; on Core and Advanced, Digital Insurance is an add-on the pricing page lists at $180,000, with no period stated. Ask which edition every screen you were shown needs.
- 02
Who needs the insurance objects
The extra licence applies to every seat. If only producers will touch policies and commissions, find out before ordering whether the rest of the desk can stay on Service Cloud.
- 03
Whether the custom object can move later
If you start on Service Cloud, name the Policy fields after their InsurancePolicy counterparts and keep the Epic code in a field like SourceSystemIdentifier. The day the agency outgrows it, the move is a data load, not a redesign.
Asked often enough to answer here
Questions
- Q
Is Financial Services Cloud an agency management system?
Salesforce does not present it as one. Its insurance agency page says Salesforce integrates with other agency management software through an open API. The brokerage features overlap with an agency system on policy lifecycle and commissions; replacing yours is a separate project.
- Q
Can we start on Service Cloud and move to Financial Services Cloud later?
Yes. The org, the cases and the service automation stay. What moves is the policy: records from the custom object into InsurancePolicy, and anything that pointed at the old object. Keep the custom object small and its fields close to the standard ones, and that move stays short.
- Q
Does Applied Epic work with both?
Applied says its connector, Applied Epic for Salesforce, works with Service Cloud and Financial Services Cloud, with specific integrations for policy terms, lines and agency structure on Financial Services Cloud. Applied does not publish the connector price.
The first stage of the service desk on the insurance agency page: €5,200 to €7,150 for 80 to 110 hours, every service mailbox turned into queues of cases. The connector facts are from Applied’s product page, read on 31 October 2026.
Serhii Skrypnyk · Senior Salesforce Administrator · 7 Salesforce certifications · on the platform since 2018. Reviewed 1 November 2026.
Read next
The question that usually comes after this one.
- 01
Applied Epic and Salesforce: Who Holds What
An agency on Applied Epic adding Salesforce: what stays in Epic, what moves to the service desk, and how clients and policies cross over without an integration.
- 02
Insurance Renewal Reminders in Salesforce
How 90, 60 and 30 day renewal tasks work on a Policy record in Salesforce, and the three things that break them: dates, imported policies and duplicates.
- 03
What Service Cloud Actually Costs a Year
Salesforce lists Service Cloud from €25 to €550 per user a month. Six things the list does not show decide what a year costs, and four of them can be changed.