The Insurance landscape
Insurance splits into two buyer types that sell to each other. Carriers write and service policies, adjudicate claims, and manage distribution partners. Agencies and brokerages sell and service policies from many carriers, earn commissions, and live or die by producer productivity and retention of the book. A carrier deal is usually larger and slower, with a policy administration system at the center. An agency or brokerage deal moves faster but runs into an agency management system that holds policies, billing, and accounting.
- 01
On the carrier side, the sponsor is often a head of distribution, a chief underwriting officer, a claims leader, or a COO driving a service initiative.
IT architecture and the core system team decide what can be integrated and when. In agencies and brokerages, the principal or CEO decides, operations runs the project, and producers decide whether it gets used. Brokerages that grow by acquisition add one more stakeholder: the integration team trying to fold acquired books and commission rules into one model.
- 02
Salesforce now covers much of this lifecycle.
Its Digital Insurance products for carriers span product definition and rating, quoting, policy administration (issuance, endorsements, billing, renewals, commissions), claims management from intake through reserves and payment, and group benefits quoting, enrollment, and renewal. For distribution, Salesforce launched Financial Services Cloud for Insurance Brokerages in October 2024 with commissions management, producer split definitions, agency billing, and servicing for employee benefits and property and casualty lines.
- 03
Regulation is state based.
States license producers and examine carriers' market conduct, so licensing, appointments, and complaint handling show up in every requirements list. AI governance is the newer topic. In December 2023 the NAIC adopted a model bulletin on insurers' use of artificial intelligence that sets expectations for how insurers govern AI, and individual states decide whether to adopt it. Expect compliance and actuarial leaders to ask how any AI in underwriting or claims is documented, tested, and overseen. Answer with controls they own, not promises.
Who buys, and how to open with them (6)
Agency Principal or Brokerage CEO
Cares about: Organic growth, producer productivity, retention of the book, and folding acquisitions in without losing clients or margin.
“When you acquire an agency, how long before you can see its clients, renewals, and commissions in the same view as yours?”
- Where do producers track prospects and cross-sell opportunities today, separate from the agency management system?
- How many of your clients have only one line of coverage with you?
- What happens to a producer's book and client relationships when that producer leaves?
- How long does month-end commission processing take, and who does it?
Head of Distribution or Producer Management (carrier)
Cares about: Partner productivity, onboarding and appointing new agents and brokers, visibility into which partners write profitable business, and partner experience.
“If I asked which 20 percent of your agents brought most of your new premium last quarter, how long would it take your team to answer?”
- How do you onboard and appoint a new agency, and how long does it take?
- Where do distribution managers log partner visits and plans?
- How do partners get quote and submission status today?
- Which licensing and appointment checks are manual?
Chief Underwriting Officer or Underwriting Operations Leader
Cares about: Submission intake and triage, quote turnaround, underwriter capacity spent on the right risks, and documented decision making.
“How many submissions does an underwriter open before finding the one that fits your appetite?”
- How do submissions arrive, and how are they triaged before an underwriter sees them?
- What share of submissions could go straight through with clear rules?
- How do you document referrals and underwriting decisions today?
- If you used AI in triage, who would need to approve it and what would they need to see?
VP Claims
Cares about: Cycle time, adjuster caseload, claimant communication, reserve accuracy, and complaint volume.
“How much of an adjuster's day goes to answering status calls instead of moving claims forward?”
- Where does first notice of loss come in, and how is it routed?
- How do claimants and agents get status today?
- Which claim types have the longest cycle time, and why?
Head of Policyholder Service or Contact Center
Cares about: Handle time, first contact resolution, self-service adoption, and a consistent experience across phone, email, and portal.
“What are the top three reasons policyholders call you, and how many of those could they handle themselves?”
- How many screens does a rep open to answer a billing or coverage question?
- Which service requests, like endorsements or certificates, still need manual work?
- How do you route calls between service, claims, and the agent of record?
CIO or Head of Core Systems
Cares about: Protecting the policy administration or agency management system, integration cost, data quality, and not adding another platform without a clear owner.
“Which work happens around your core system today in email and spreadsheets because the core was never built for it?”
- What does your core expose through APIs, and what does each new integration cost?
- Is a core replacement on the roadmap, and how would CRM work fit with it?
- Who owns customer data quality across policy, billing, and claims?
- What does your vendor security review require?
The problems worth solving (6)
No single view of the client across lines
Personal, commercial, and benefits lines often run in separate systems with separate client records. Producers and service reps cannot see what else a client has or should have. Cross-sell and account rounding depend on memory, and renewal conversations start from scratch every year.
Where Salesforce fits: Financial Services Cloud gives a client view across households, businesses, policies, and producers. Data 360 can bring in policy, claims, and billing data so the view stays current.
Commission splits and producer compensation
Brokerages split commissions among producers, account managers, and referral partners, and the rules change when someone leaves or an agency is acquired. Most firms run this in spreadsheets outside the agency management system. Errors damage producer trust and take hours to unwind.
Where Salesforce fits: Financial Services Cloud for Insurance Brokerages includes commissions management with a rule library for splits that finance teams can reassign when a producer leaves or an acquisition closes.
Submission intake and underwriter capacity
Submissions arrive by email with attachments in every format. Underwriters spend time sorting and rekeying instead of evaluating risk. Brokers wait for a quote and send the business to the carrier that answers first. Leaders cannot see where submissions wait or why.
Where Salesforce fits: Salesforce Digital Insurance quoting supports straight-through processing of digital applications, automated referrals, and an underwriter workstation. Agentforce can produce policy and quote summaries for faster review.
Claims communication and cycle time
Claimants and agents call for status because nobody tells them what is happening. Adjusters lose hours to those calls. Information from first notice of loss gets rekeyed into the claims system, and handoffs between intake, adjusters, and vendors leave gaps that stretch cycle time.
Where Salesforce fits: Salesforce Claims Management covers intake, adjudication, reserves, and payment. Service Cloud and Experience Cloud give claimants and agents status without a phone call.
Distribution partner management
Carriers work with many agencies and brokers but see little about partner activity beyond premium reports. Onboarding and appointing partners is slow and manual. Distribution managers plan visits from spreadsheets, and partners get inconsistent service depending on who they call.
Where Salesforce fits: Salesforce distribution management tools track partners, producers, and plans and automate onboarding workflows. Experience Cloud gives partners a portal for quotes, status, and resources.
Acquisitions that never fully integrate
Brokerages that grow by acquisition inherit different systems, client records, and commission rules with every deal. Years later, books still sit in separate tools. Leaders cannot report on the combined firm, and producers from acquired agencies keep working the old way.
Where Salesforce fits: Financial Services Cloud for Insurance Brokerages gives a common client, policy, and commission model that acquired books can migrate into, with Data 360 and MuleSoft for systems that stay in place during transition.
The numbers leaders run on (6)
Retention or renewal rate
Retaining the book is the foundation of agency and carrier economics. Renewal opportunities and service history in Salesforce flag at-risk accounts before the renewal date.
Policies or lines per client
Account rounding drives growth and retention in agencies and brokerages. Policy data on the client record shows the gap by producer and segment.
Quote turnaround and hit ratio
Underwriting and distribution leaders watch how fast quotes go out and how many bind. Submission and quote records with timestamps show both by line and partner.
Claims cycle time
Long cycles cost money and drive complaints. Claim records and task history show where each claim waited, by claim type and adjuster.
Commission accuracy and processing time
Errors erode producer trust and take finance hours to fix. Commission and split records in Financial Services Cloud for Insurance Brokerages give an auditable trail.
Producer or partner productivity
New premium per producer or per appointed agency shows where to invest. Opportunity and policy data by producer or partner feeds the view.
Product fit (7)
Cross-sell sequence (5)
- Sales Cloud Financial Services Cloud for Insurance Brokerages"Our commission splits are in a spreadsheet," or the brokerage just closed another acquisition.
- Service Cloud Experience CloudStatus calls from agents, brokers, or claimants make up a large share of contact volume.
- Financial Services Cloud Agentforce"Reps spend most of a call looking up policy details," or underwriters complain about reading submissions.
- Financial Services Cloud Data 360Leaders want cross-sell lists that use policy, claims, and billing data the CRM does not hold today.
- Service Cloud Claims Management"We built claims tracking in cases and it's outgrowing them," or the carrier is planning a claims system change.
Objections, and what to say (5)
"Our agency management system already does this."
It holds policies, billing, and accounting, and it should keep doing that. Ask where producers track prospects, cross-sell, and renewal strategy, and where commission splits get worked out. Usually it is spreadsheets and inboxes. Position Salesforce as the place producers and account managers sell and service, connected to the agency system. Show one workflow, like a renewal with a cross-sell, from start to finish.
"We're replacing our core. Talk to us after that."
Core projects take years, and the business still has to sell and service in the meantime. Ask which customer-facing problems the core project will not solve, like partner engagement or service routing. Salesforce work can run in parallel and connect to the new core through MuleSoft when it arrives. For carriers evaluating policy and claims platforms, Salesforce's own Digital Insurance products may belong in that evaluation.
"Producers won't use a CRM."
Producers use what helps them sell. Give them renewal lists with cross-sell gaps, client history in one place, and accurate commission visibility. Ask what a top producer would want to see before a renewal meeting and build that first. Keep data entry light and let account managers and automation do the rest. Measure adoption by team and fix friction fast.
"Regulators are watching AI in insurance. We're staying out."
That caution is reasonable. States can adopt the NAIC model bulletin on AI governance, and coverage and claim decisions get the most scrutiny. Start with AI that helps staff without deciding outcomes, like summarizing a policy for a service rep. Ask compliance what documentation and oversight they would require, then show how agent actions are configured, reviewed, and logged. Don't promise the product satisfies any state requirement.
"We're too small for Salesforce."
Ask what breaks today: commissions, renewals, client privacy between producers, or reporting. A focused Sales Cloud or Financial Services Cloud rollout can start with a small team and a fixed scope. Point to a smaller agency that moved from shared spreadsheets to Salesforce with record privacy by producer. Size the first phase to the pain, and show how it grows with the next acquisition.
Implementation watch-outs to raise before signature (5)
Agree on the data model for clients, policies, and producers
Decide how households, businesses, policies, and producer relationships are represented before building. Brokerages need clear rules for producer of record and account manager roles. Changing the model later breaks sharing, reports, and commissions. Get operations and finance to sign off.
Commission rules need finance in the room
Split rules, overrides, and reassignment on departure or acquisition are finance decisions, not admin settings. Document every rule and edge case before configuration. Reconcile a full month in parallel with the old process before switching over, and keep an audit trail of changes.
Record privacy between producers
Many agencies require that producers see only their own clients, while service teams see more. Design sharing rules with leadership, test them with real users, and plan for changes when producers leave. Getting privacy wrong destroys trust in the system quickly.
Keep the core boundary clear
The policy administration or agency management system usually remains the record for policies, billing, and accounting. Decide which data syncs to Salesforce, how often, and in which direction. Budget integration testing with real volumes, and confirm what the core vendor exposes and charges for API access.
Document AI before deploying it
If agents or AI features will touch underwriting, claims, or customer communications, write down their purpose, data, human review steps, and testing. Compliance teams in states that adopted the NAIC bulletin will ask. Start with internal-facing uses and expand once the governance process works.
Qualify honestly
Strong fit
- A named business owner with a cost they can measure, such as commission processing time, quote turnaround, or claims status calls
- A trigger: acquisition, core replacement, renewal season pressure, or a failed homegrown tool
- Core or agency management system integration path confirmed with the vendor
- Finance and compliance engaged in discovery
Risky fit
- The buyer wants Salesforce to replace the agency management system's accounting in phase one
- No one owns commission rules, or the rules are undocumented
- Core vendor API access is unknown or priced per call and nobody has checked
- AI use cases that decide coverage or claims with no governance owner
Case studies to send (1)
Questions (4)
Financial Services Cloud or the Digital Insurance products?
Agencies and brokerages usually start with Financial Services Cloud and Financial Services Cloud for Insurance Brokerages. Carriers evaluating policy administration, claims, or group benefits platforms should look at Salesforce's Digital Insurance products. Many carriers use Financial Services Cloud for distribution and service while the core stays in place.
Does HIPAA apply to insurance deals?
It can. Health plans are covered entities under HIPAA, and group benefits or life lines may handle medical information. Ask the privacy team which lines and data are involved, and if PHI is in scope, confirm which Salesforce services the customer's BAA covers before you design.
How do I talk about the NAIC AI bulletin?
Describe it accurately: a model bulletin adopted by the NAIC in December 2023 that sets expectations for how insurers govern AI, which each state decides whether to adopt. Ask how the customer's compliance team is responding. Don't claim any product satisfies it.
When should I bring in Abstrakt?
Bring us in for commission modeling, core or agency system integration, acquisition consolidation, or AI governance questions. We reply to AEs within four business hours and offer a free health check for customers you refer who already run Salesforce.
Sources (6)
- Salesforce: Insurance (Digital Insurance, Policy Administration, Claims Management)
- Salesforce: Financial Services industry solutions
- Salesforce news: Financial Services Cloud for Insurance Brokerages (Oct 15, 2024)
- Trailhead: Get to know insurance solutions in Salesforce
- NAIC: Artificial intelligence (model bulletin adopted December 2023)
- 45 CFR 160.103 definitions (covered entity, health plan), via Cornell LII