SOMPO Japan
Profit-making and sales decisions for commercial insurance
Palantir
Insurance
Typical Forward Deployed model
Standard case | Useful reference with remaining gaps
Evidence level A
Scaled
A
Evidence level
SOMPO Japan: Profiting and sales decisions in commercial insurance
Evidence level measures whether a source can be located and reviewed; it does not mean vendor-reported claims were independently audited.
Standard case | Useful reference with remaining gaps
9 / 12
Business context1 / 2
Transformation workflow1 / 2
Technical workflow2 / 2
Human roles & governance1 / 2
Measured outcomes2 / 2
Source traceability2 / 2
Remaining gaps: Business context, Transformation workflow, Human roles & governance
Business problem
Commercial insurance sales and insurance require the translation of decentralized business data into enforceable client/risk decisions.
Solution
Using Foundry/RDP as the base for business data, it provides access to workflows such as profit, customer, sales and disaster response, and extends to sales teams.
Technical architecture & production workflow
Step 01
Multi-source operating data and historical events
→
Step 02
Foundry harmonized data models and privileges
→
Step 03
Online map of business objects, relationships, status and executable Action
→
Step 04
AIP/rules/prediction model generation recommendations or automated steps
→
Step 05
First-line personnel confirm and execute in Workshop/Application
→
Step 06
The feedback, the results and the new facts form a closed loop.
Key technology & infrastructure components
FoundryReal Data PlatformOntologyCommercial insurance dataSales workflow
Human roles & accountability
The sales, insurance and management team makes the final commercial judgement based on the recommendation.
FDE delivery actions
- Together with the first line of insurance sales and insurance teams, complete the process and identify nodes that really require decision-making rather than presentation of data
- Collapse decentralized data sources, competencies and business terms into a single, operational Ontology
- Combine business rules, optimization models, LLM and traditional software according to a reliable boundary, instead of letting the LLM operate
- Insert recommendations directly into existing operating workstations and design approvals, rejections, upgrades and write back to Action
- Continue to modify Ontology, rules and automation with operational KPI acceptance and feedback
Reusable delivery patterns
- Let's be clear about the client, the relationship, the state and the action, and then talk about Agent.
- The recommendation must enter the executable stream, otherwise it's just another dashboard.
- High-value deployment is often a combination of data integration + rules/ optimization + AI + Human-in-the-lop
- Continuous rewriting of the results of implementation to build cumulative operational memory
Business outcomes & delivery results
The public client of the Palantir network quoted a profit improvement of about $60 million over the past three years and an increase of about $100 million is expected over the next three years; the related workflow extends to 10,000+ salesmen.
Evidence boundaries & verification notes
- Official press releases confirmed 10,000+ salesperson expansion and commercial insurance profit stream; profit figures were quoted by Palantir network clients.
- The source can be directly located in the case; the value remains disclosed by the source and does not represent an independent audit.