IBM Financial Services United States

LEXXARI by CCG Software Solutions

Document Processing

Claims Connection Group needed to help carriers, agents, policyholders, and repair partners interpret dense insurance policy language quickly and consistently because manual review delayed claims decisions, drove no-pay disputes, and increased inbound calls after storms.

40% reduction in no-pay claims
60% fewer post-storm calls
70% increase in policy review speed
co-developed in just 14 weeks

Reported impact

Business outcome

LEXXARI accelerated policy review, reduced no-pay claims and post-storm call volume, and gave field professionals faster, more confident guidance during claims handling.

  • Customer Experience
  • Productivity Improvement
  • Risk Reduction

Solution

CCG and IBM built LEXXARI as a policy-interpretation platform that uses IBM watsonx and watsonx Orchestrate to read, summarize, and guide users through complex insurance documents. In just 14 weeks, the teams modeled the workflow around real interactions among carriers, agents, and policyholders so the assistant could do more than answer isolated questions. Watsonx was trained on real-world insurance policies to generate fast interpretations, while watsonx Orchestrate coordinates the AI agents that guide users through step-by-step actions during claims handling. The resulting platform turns hours of dense policy review into immediate, decision-ready insight that insurance professionals can use in the field and customers can understand more clearly. Because the experience is grounded in policy content and operational workflows, it reduces confusion, improves claims consistency, and creates a reusable document-intelligence pattern CCG plans to extend into other document-heavy industries.

Data flow

Insurance policy documents are ingested into watsonx for summarization and interpretation, watsonx Orchestrate routes the resulting insight through workflow steps that mirror claims handling, and users receive immediate guidance or answers instead of manually re-reading policy text.

Solution architecture

2 components · 2 layers
  1. Compute
    • IBM watsonx Provides the AI model layer that reads and interprets real insurance policies for users.
  2. Orchestration
    • IBM watsonx Orchestrate Coordinates AI agents and workflows so users receive step-by-step guidance during claims analysis.

Architecture clues

  • CCG plans to expand the same platform into auto, legal, government, and education.
  • IBM watsonx was trained on real-world insurance policies.
  • The workflow was designed to mirror how carriers, agents, and policyholders interact with policy data.

Evidence from the source

“AI agents from IBM watsonx Orchestrate were integrated into the platform to provide users with actionable, step-by-step guidance.”
“Clearer coverage understanding has led to a 40% reduction in no-pay claims and 60% fewer post-storm calls.”
“IBM watsonx was trained on real-world insurance policies”
“LEXXARI speeds up policy reviews by 70%”
“LEXXARI was co-developed in just 14 weeks.”
Transparency Evidence & methodology 100/100 reference value · 89% confidence · 1 source

Review how this reference was scored and trace each normalized claim back to its documented source.

01

Scoring methodology

How scores are calculated

Customer Reference Value measures usefulness as a customer reference. Evidence Confidence measures the quality and traceability of available evidence, not independent verification.

Customer reference value100/100
  • Problem clarity20/20
    Measures whether the customer's operational problem is specific enough to compare.
  • Implementation depth25/25
    Rewards named components, data flow, integrations, and architecture detail.
  • Outcome specificity20/20
    Measures whether the reported benefit is concrete rather than a generic claim.
  • Quantified impact25/25
    4 metrics describe measurable impact.
  • Deployment scale10/10
    Rewards evidence of a live or scaled deployment and meaningful integration scope.
Evidence confidence89%
  • Source authority20/25
    The main evidence is an official vendor-published customer story.
  • Claim traceability21/25
    10 of 12 key fields link to a named source.
  • Direct evidence20/20
    5 direct source quotes retained.
  • Date provenance10/10
    The publication date comes from the source page or publisher.
  • Source transparency8/10
    1 source reference document publisher, URL, authority, retrieval, and supported fields.
  • Implementation specificity10/10
    Rewards source-backed components, data flow, quantified impact, and a specific outcome.
02

Traceability

Sources & provenance

Field coverage shows which facts each source supports. Dates are shown only when documented by the source.

  1. IBM

    LEXXARI by CCG Software Solutions customer story

    First-party
    https://www.ibm.com/case-studies/lexxari-by-ccg
    Source type
    Vendor-published customer story
    Published
    Jul 28, 2026
    Supports
    • Customer
    • Business problem
    • Solution
    • Products
    • Solution components
    • Data flow
    • Integrations
    • technical area
    • use case category
    • Business outcome
    • outcome category
    • Metrics
    • Architecture
    • evidence quotes
    • Publication date

Date evidence

Not separately sourced Industry, Region, Company size. Treat these normalized attributes as lower-confidence until a dedicated source is added.