Hesper AI
BlogVendor Landscape
Vendor LandscapeMay 13, 2026·12 min read·Nitish Badu, COO

Top 10 claims management systems for P&C carriers in 2026

A 2026 buyer's guide to the 10 claims management systems US P&C carriers actually run, sorted by carrier tier, deployment model, and integration profile.

NB
Nitish Badu · COO, Hesper AI
May 13, 2026·12 min read
270+
Guidewire ClaimCenter customers
Across 30+ countries
30M+
Claims processed via Duck Creek OnDemand
With 60K/day CAT capacity
$729M
Thoma Bravo's Majesco acquisition
Closed August 2020
16 of 20
Top P&C carriers on Snapsheet
~$6B in appraisals processed

The US P&C claims management system (CMS) category looks different in 2026 than it did in 2020. Cloud-native vendors that were greenfield experiments six years ago now process tens of millions of claims a year, private equity has rolled up most of the mid-market, and every incumbent has had to rewrite its deployment story to compete with vendor-managed cloud. The buyer's question has shifted from "what does the workflow look like" to "what deployment model, ownership profile, and integration ecosystem matches our carrier tier." This guide covers the 10 systems that actually show up on shortlists at US P&C carriers today, with sourcing tied to each vendor's public claims.

The post is written for CIOs and Claims VPs sizing a CMS decision against a 3-5 year horizon. It is a landscape view, not a head-to-head. For buyers already narrowed to four vendors, the companion four-vendor head-to-head comparison goes deeper on Guidewire, Duck Creek, Majesco, and Snapsheet side by side. This post sits inside the claims-fraud leakage pillar because CMS choice shapes the loss-cost surface across the claims and fraud stack.

Hesper AI is not in the top-10 list. Hesper is the investigation layer that integrates into whichever CMS the carrier runs - flagged claims flow into Hesper, an audit-ready report flows back as a case attachment. That distinction is covered in the closing section. The other nine sections are neutral on Hesper and read as a pure CMS buyer's guide.

The 2026 P&C CMS landscape

Five forces reshaped the CMS buyer's question between 2020 and 2026. The first is cloud-native scale. Vendors that started as greenfield SaaS plays have crossed enterprise throughput thresholds: Duck Creek OnDemand processes 30M+ claims with 60K/day CAT capacity, Sapiens IDIT Go ships as a pre-configured cloud-native P&C solution, and EIS ClaimCore positions as a coretech challenger on cloud-native architecture. The second force is private equity consolidation. Thoma Bravo acquired Majesco for $729M in August 2020. GI Partners acquired Insurity in August 2019 and TA Associates reinvested in November 2021. Vista Equity took Duck Creek private in 2023 after its 2020 IPO and 2016 Apax spinoff. PE ownership shapes roadmap velocity and pricing posture more than analyst quadrants do.

The third force is the rise of CMS marketplaces. Guidewire Marketplace and Duck Creek Content Exchange now serve as the primary distribution channel for third-party detection, fraud, document, and analytics vendors. The fourth is specialty and MGA fragmentation - OneShield, Insurity, and ICE InsureTech have grown by selling into segments the Top-25 incumbents under-serve. The fifth is the SIU and fraud-tech ecosystem the CMS itself does not ship. As Celent's 2024 regional P&C Claims Systems reports named Guidewire ClaimCenter a Luminary in all four regions with seven XCelent awards, none of the CMS recognitions extend to autonomous SIU investigation. That gap sits downstream of every system on this list.

ClaimCenter is the only solution to be named a Luminary in all four regional 2024 P&C Claims Systems reports and the only Luminary in the Latin America report.

Guidewire press release, April 9 2024

How we ranked the 10

Six criteria shape the ranking. We avoided weighting them into a composite score because the right CMS is carrier-tier-dependent and a single score collapses real tradeoffs.

  1. Market presence among the Top 50 US P&C carriers, weighted by named deployments rather than installed-base claims.
  2. Deployment model, with cloud-native treated as the 2026 default and hybrid or on-prem flagged as a constraint rather than a feature.
  3. Modular flexibility, measured by how cleanly the claims module decouples from policy, billing, and rating in a partial-replacement scenario.
  4. Fraud-tech and third-party ecosystem depth, measured by named partners in the vendor's marketplace or content exchange.
  5. Total cost of ownership posture, qualitative only - none of the 10 publishes list pricing - using public ownership profile and deployment shape as proxies.
  6. Integration footprint with detection vendors, SIU tooling, and document AI partners that carriers run alongside the CMS.

What this list is not

This is a US P&C-focused landscape. L&AH-only CMS, pure reinsurance platforms, and TPA-only case-management tools are out of scope unless the vendor also has a meaningful P&C posture. Origami Risk is in the list because it serves self-insured corporates and risk pools that show up in P&C buying conversations; pure L&AH platforms are not.

The 10 systems

Profiles are sized to 130-180 words. Each names founding year, ownership, deployment shape, one verified carrier or customer, and the segment where the vendor wins. Vendors are ordered roughly by Top-25 visibility, not by overall preference.

1. Guidewire ClaimCenter

Guidewire was founded in 2001 and is publicly listed on the NYSE. ClaimCenter is the dominant CMS in the Top-25 US P&C tier and has 270+ customers across 30+ countries per the Guidewire ClaimCenter product page. The 2024 Celent recognition - Luminary in all four regional P&C Claims Systems reports and seven XCelent awards - is the strongest analyst signal in the category. Deployment is hybrid plus Guidewire Cloud, with the cloud variant now the default new-logo posture. Named deployments include Tokio Marine, Zurich, AXA, Allianz, Nationwide, Mercury, Tryg, Farm Bureau Michigan, and Grinnell Mutual. The Guidewire Marketplace is the deepest third-party partner ecosystem in the category, which is one reason Top-25 carriers cluster here: the integration cost of bolting an investigation or detection layer on top is lower when the partner already ships a packaged connector. The tradeoff is implementation timeline and total cost of ownership; full ClaimCenter deployments at Top-25 carriers run 24-48 months.

2. Duck Creek Claims

Duck Creek was founded in 2000, acquired by Accenture in 2011, spun off to Apax Partners in 2016, IPO'd in 2020, and taken private by Vista Equity in 2023. Duck Creek Claims reports 30M+ claims processed through Duck Creek OnDemand and 60K/day CAT-event throughput - the headline number in the cloud-native CMS conversation. Deployment is cloud-native via OnDemand. Named deployments include Mutual Benefit Group, BHSI, and AXIS. Duck Creek Content Exchange is the closest analog to Guidewire Marketplace and includes the major detection and document vendors. Duck Creek wins in mid-market and Top-25 carrier evaluations where cloud-native posture and configuration-over-code are the decisive criteria. The Vista take-private has shifted the public roadmap conversation to invite-only briefings, which is a consideration for CIOs who relied on quarterly earnings color to track roadmap velocity.

3. Majesco ClaimVantage

Majesco was founded in 1992 as a Mastek US subsidiary, demerged in 2014, and taken private by Thoma Bravo for $729M in August 2020. ClaimVantage is Salesforce Lightning-native, which is the architectural differentiator - the UX, security model, and reporting inherit from the Salesforce platform. ClaimVantage has 35+ L&AH customers; the P&C footprint is smaller. Deployment is cloud on Salesforce. Mid-market multi-state P&C carriers evaluate Majesco mainly as a cost alternative to Guidewire and Duck Creek, particularly when the carrier already has Salesforce as a CRM standard. The partner ecosystem runs through the Salesforce AppExchange in addition to Majesco's own partner program. Where Majesco struggles in P&C evaluations is depth of property and auto adjudication features relative to the Top-25 incumbents; carriers buying primarily on P&C breadth tend to land elsewhere.

4. Snapsheet

Snapsheet was founded in 2011 in Chicago and started as a mobile-first appraisal vendor before extending to end-to-end claims management. The Snapsheet product page reports 170+ customers, 16 of the top 20 US P&C carriers running some Snapsheet capability, and approximately $6B in appraisals processed. Kin Insurance is the named end-to-end deployment. Deployment is cloud-native. State Farm Ventures has invested. Snapsheet wins with digital-first carriers and with Top-25 carriers that adopt the appraisal or virtual-handling capability without replacing the system-of-record CMS. Open APIs make integration with detection vendors and downstream investigation layers straightforward. Where Snapsheet is weaker is depth of policy and billing integration at scale - it is rarely the answer for a Top-25 carrier looking to replace ClaimCenter outright on all lines.

5. Sapiens IDITSuite

Sapiens has its origins in 1982 and trades on NASDAQ. IDITSuite is a cloud-native modular P&C core built on a service-oriented architecture with a NoOps/DevOps framework, with claims as one module alongside policy, billing, and rating. Sapiens IDIT Go is the pre-configured cloud-native variant, aimed at greenfield carriers and MGAs that want a faster deploy. Sapiens is EMEA-strong and expanding in the US, often through mid-market and specialty deployments. Carriers that need a unified core across multiple international entities evaluate Sapiens against Guidewire on integration cost across geographies. The partner ecosystem is open-API-first but thinner in published US-carrier deployments than Guidewire or Duck Creek. Implementation timelines are competitive with Duck Creek for mid-market and slightly faster for the IDIT Go variant on greenfield builds.

6. OneShield

OneShield was founded in 1999 and is headquartered in Marlborough, Massachusetts. The OneShield Software platform is sold as an all-in-one cloud SaaS core covering policy, billing, claims, and rating, which makes it attractive to mid-market and regional P&C carriers that want a single vendor rather than a best-of-breed stack. Named customers include Erie Insurance, WestCongress, Travelers Canada, and Hiscox. OneShield is one of the strongest options for MGAs and program managers because the unified core reduces integration burden across policy and claims. Where OneShield wins is mid-market multi-state carriers and MGAs that have outgrown a legacy single-state stack but are not ready for a Top-25 build. Where OneShield is weaker is the very top of the market, where Guidewire and Duck Creek have more depth of named-carrier proof and a more developed third-party fraud-tech ecosystem.

7. Insurity ClaimsXPress

Insurity was founded in 1985 and is headquartered in Hartford, Connecticut. GI Partners acquired Insurity in August 2019; TA Associates reinvested in November 2021. ClaimsXPress is the claims module in the Insurity portfolio and runs on AWS, with hybrid options for carriers with regulated-data constraints. Insurity is one of the deeper specialty-lines and commercial CMS plays - the Hartford-rooted DNA shows up in the depth of program and specialty workflows. AWS partner pages list ClaimsXPress as a cloud deployment for specialty carriers. Mid-market specialty and commercial carriers evaluate Insurity as a credible alternative to Guidewire for narrower line-of-business builds. Where Insurity is weaker is the analyst-recognition cycle - it has not chased Celent Luminary positioning the way Guidewire and Duck Creek have, which can matter to procurement teams that lean on external rankings.

8. EIS ClaimCore

EIS Group was founded in 2008 and is headquartered in San Francisco. EIS ClaimCore ships as a cloud-native end-to-end claims management module on the EIS coretech platform, covering FNOL through subrogation and closure. EIS positions itself as the cloud-native challenger to Guidewire and Duck Creek for mid-market and Top-25 carriers that want an API-first platform with fewer of the customization-as-code constraints that show up on older stacks. Configuration sits at the platform layer, which appeals to carriers that have been burned by deep code customization on legacy CMS. EIS is less visible than Guidewire or Duck Creek in published US-carrier named deployments, but is increasingly shortlisted in greenfield and full-replatform evaluations. Implementation timelines are competitive with Duck Creek for mid-market builds. The third-party fraud-tech ecosystem is thinner than the two leaders but improving.

9. ICE InsureTech

ICE InsureTech is UK-headquartered in Camberley with 23+ years of delivery experience per the ICE InsureTech site. Named customers include the AA, MCE, UIA, ERS, and Provident Insurance - a UK-and-EMEA-centric roster. Deployment is cloud-native with hybrid options. US carriers most often see ICE InsureTech through their Lloyd's of London or London-market exposure rather than as a primary CMS selection for US-domiciled lines. Where ICE wins is specialty lines, personal motor in the UK, and Lloyd's syndicate-aligned builds. For US carriers with a UK or Lloyd's subsidiary, ICE is a credible single-vendor answer that avoids running two CMS stacks across geographies. For US-only mid-market and Top-25 carriers, ICE is rarely the shortlist answer; Guidewire, Duck Creek, and EIS dominate that conversation.

10. Origami Risk

Origami Risk was founded in 2009 and is a different shape from the other nine vendors. Its integrated RMIS, claims, and GRC platform serves 950+ organizations - mostly self-insured corporates, public entities, risk pools, and TPAs rather than primary P&C carriers. Origami earns a place in any honest top-10 because the CMS category extends past pure carriers: self-insured workers comp programs, public-entity risk pools, and TPAs evaluate CMS choices on the same axes that primary carriers do, and Origami is the strongest single-platform answer for that segment. Deployment is cloud-native SaaS. Origami partners with claims analytics vendors and is increasingly visible in the AI-augmented claims conversation. Where Origami is not the answer is Top-25 primary carrier P&C builds - that segment runs on Guidewire, Duck Creek, or Sapiens, not Origami.

Honorable mention: Hi Marley

Hi Marley is not a full CMS, but the platform has crossed a visibility threshold that makes excluding it dishonest. Founded in 2017, Hi Marley has raised $41.7M since inception and runs as an intelligent conversational platform purpose-built for P&C. The Hi Marley platform overview reports 40+ carriers live, including American Family, MetLife, Auto-Owners, Erie, and MAPFRE. Hi Marley sits adjacent to the CMS, handling carrier-policyholder messaging and adjuster communication. Carriers evaluating Hi Marley evaluate it as a layer on top of their CMS, not as a replacement for it. The platform is mentioned here because more than one carrier on a CMS evaluation in 2026 already has Hi Marley deployed, and any CMS shortlist needs to confirm clean integration with it.

Comparison matrix

The matrix below collapses the 10 profiles into a single view. Columns are founded year, deployment model, carrier-tier fit, strongest module, and fraud-tech ecosystem depth. Hi Marley is excluded because it is an adjacency, not a CMS.

VendorFoundedDeploymentCarrier tier fitStrongest module
Guidewire ClaimCenter2001Hybrid + CloudTop-25 nationalEnd-to-end claims workflow
Duck Creek Claims2000Cloud-native (OnDemand)Mid + Top-25OnDemand throughput; Content Exchange
Majesco ClaimVantage1992 (2014 demerge)Cloud (Salesforce)Mid-market; L&AH stronger than P&CSalesforce-native UX
Snapsheet2011Cloud-nativeSmall + digital-firstMobile-first FNOL & appraisal
Sapiens IDITSuite1982 (Sapiens)Cloud-native + IDIT GoMid + Top-25 (EMEA-heavy)Modular international P&C core
OneShield1999Cloud / SaaSSmall + mid; MGAsAll-in-one core
Insurity ClaimsXPress1985Cloud (AWS) + hybridMid; specialty + commercialSpecialty-lines claims
EIS ClaimCore2008Cloud-native (SaaS)Mid + Top-25 challengerConfigurable workflow on coretech
ICE InsureTech2002 (UK)Cloud-native + hybridSpecialty / Lloyd's / EMEAPersonal + specialty motor
Origami Risk2009Cloud-native (SaaS)Self-insured / public / TPAs / risk poolsIntegrated RMIS + Claims + GRC

Carrier-tier fit by vendor (qualitative score, 0-100)

Guidewire ClaimCenterTop-25
Duck Creek ClaimsTop-25 / Mid
Sapiens IDITSuiteTop-25 / Mid
EIS ClaimCoreMid / Top-25
Insurity ClaimsXPressMid / Specialty
Majesco ClaimVantageMid-market
OneShieldMid / Small
SnapsheetSmall / Digital-first
Origami RiskSelf-insured / TPAs
ICE InsureTechUK / Lloyd's

Matching CMS choice to carrier tier

Carrier tier predicts the right CMS more reliably than any feature checklist. The pattern across the 10 systems sorts cleanly along three tiers, and the deviations from this pattern are almost always driven by a specific structural fact about the carrier (Lloyd's exposure, self-insured book, Salesforce platform standard) rather than a CMS feature comparison.

Small regional (10k-50k claims/year)

Small regional carriers, MGAs, and digital-first builds with annual claim volumes in the 10k-50k range cluster on Snapsheet, OneShield, and Origami Risk when self-insured or risk-pool-adjacent. The decision logic is total cost of ownership and time to live; a Top-25-grade CMS implementation timeline of 24-48 months does not match the operating tempo of a small regional carrier. Hi Marley shows up frequently as a communication layer in this tier as well.

Mid-market multi-state (50k-500k claims/year)

Mid-market multi-state P&C carriers evaluate Majesco, Insurity, EIS ClaimCore, OneShield, and the smaller side of Sapiens and Duck Creek. The decision usually turns on three variables: existing platform standards (Salesforce favors Majesco, AWS-native specialty favors Insurity), implementation timeline tolerance (EIS and Sapiens IDIT Go push toward the faster end), and the depth of the third-party fraud-tech and document-AI ecosystem the carrier intends to deploy alongside the CMS. Detection and investigation tooling integration is a sharper variable here than at the Top-25 tier because mid-market integration budgets are thinner.

Top-25 national (500k-5M+ claims/year)

Top-25 US P&C carriers cluster on Guidewire ClaimCenter and Duck Creek Claims, with Sapiens IDITSuite as the international-footprint alternative. The decision is almost always reduced to Guidewire vs Duck Creek at this tier, and the deciding variable is rarely the workflow - it is the deployment model preference (hybrid vs cloud-native), the marketplace ecosystem depth, and the ownership profile. For carriers running Lloyd's syndicates alongside US lines, Sapiens or ICE InsureTech may enter the conversation as a unified-vendor play across geographies.

Where the investigation layer fits

Every CMS on this list has the same remit: case workflow, document capture, adjudication tracking, and audit-trail-ready outputs. None of them ships autonomous SIU investigation. The layered category model splits the stack into prevention, detection, investigation, and adjudication; the 10 systems above all sit in case workflow and adjudication tracking. Detection is a separate layer that vendors like FRISS, Shift Technology, and Verisk occupy. Investigation - taking a flagged claim and resolving it end-to-end with an audit-ready report - is the layer no CMS occupies. The current incumbent at the investigation layer is manual SIU teams at every US P&C carrier, running a 14+ day investigation cycle at roughly $2,500 per case with ~25% coverage of flagged claims. That covers about ~10% of P&C claims that involve fraud, which sit inside the Coalition Against Insurance Fraud's $308 billion annual US insurance fraud loss estimate.

Hesper AI is the investigation layer that integrates into whichever CMS the carrier already runs. Flagged claims flow from the CMS or detection vendor into Hesper, 15+ investigation phases run in parallel on each flagged claim, and an audit-ready report flows back into the CMS as a case attachment. The CMS stays the system of record; Hesper is the system of investigation. The Hesper internal benchmark is 2-4 hours per case at ~$150 per case with 100% coverage of flagged claims. The investigator's role shifts from execution to decision-making. CMS choice is independent of the investigation-layer choice; the prevention vs detection vs investigation breakdown and the 2026 SIU technology stack post trace how that layered separation plays out in procurement. Carriers worried about integration cost on a CMS-plus-AI build should also read the hidden integration costs of legacy claims AI.

Key takeaways

  • The 2026 US P&C CMS shortlist splits cleanly between Top-25 incumbents (Guidewire, Duck Creek, Sapiens) and a mid-market and digital-first tier (Majesco, Snapsheet, OneShield, Insurity, EIS, ICE, Origami), with deployment model and carrier-tier fit predicting the right answer more reliably than feature checklists.
  • Guidewire ClaimCenter remains the only vendor named Celent Luminary in all four regional 2024 P&C Claims Systems reports and stays the default for Top-25 carriers with global footprints.
  • Private equity ownership has reshaped the mid-market - Thoma Bravo (Majesco, $729M, 2020), GI Partners and TA Associates (Insurity, 2019/2021), Vista Equity (Duck Creek, 2023) - and that ownership profile shapes roadmap velocity more than analyst quadrants do.
  • None of the 10 ships autonomous SIU investigation; every CMS on the list leaves the 14+ day manual investigation cycle downstream of the case workflow, which is why carriers run a separate investigation layer on top of the CMS.
  • Carrier tier is the strongest predictor of the right CMS: small regional belongs on Snapsheet, OneShield, or Origami; mid-market on Majesco, Insurity, EIS, or OneShield; Top-25 on Guidewire, Duck Creek, or Sapiens.

Frequently asked questions

For most Top 50 US P&C carriers in 2026, cloud-native or cloud-deployed-hybrid is the default. Duck Creek Claims processes 30M+ claims through OnDemand and offers 60K/day CAT capacity; Guidewire Cloud is now where most new ClaimCenter buyers land; Sapiens IDIT Go is the pre-configured cloud entry. Pure on-prem only still makes sense for carriers with regulatory or data-residency constraints that block public-cloud, or for mainframe-era stacks where the integration timeline of a CMS replacement is multi-year. The real CIO question is not cloud vs on-prem; it is whether to lift-and-shift the existing CMS into a vendor-managed cloud or re-platform onto a cloud-native CMS. The first is a 12-18 month project; the second is 24-48 months. Both leave the SIU investigation layer untouched downstream.

Yes. Every CMS in the top 10 exposes flagged-claim records through APIs or marketplace integrations - Guidewire Marketplace, Duck Creek Content Exchange, Majesco's Salesforce AppExchange surface, Sapiens' open API framework, EIS's API-first platform. An investigation layer like Hesper AI subscribes to the flagged-claim event, runs 15+ investigation phases in parallel, and returns an audit-ready report as a case attachment back into the CMS. The CMS remains the system of record; Hesper is the system of investigation. This is why CMS choice does not constrain the SIU technology decision - the investigation layer is decoupled from the case-workflow layer by design, and the integration pattern is the same regardless of which of the 10 CMS the carrier runs.

For a Top-25 US P&C carrier, full CMS replacement runs 24-48 months from contract through go-live across all lines. Mid-market multi-state carriers see 12-24 month timelines. Digital-first or greenfield carriers running a pre-configured cloud stack (Sapiens IDIT Go, Snapsheet end-to-end, OneShield as the all-in-one core) can go live in 6-12 months. The variables are line count, integration scope (policy, billing, FNOL, document repository, payments), data migration depth, and the legacy system being replaced. Mainframe-era replacements skew to the upper end of every range. None of these timelines include the SIU and fraud-tech integration work, which is a parallel workstream that typically runs 3-9 months on top of the core CMS deployment.

The CMS sets the system of record for case status, document attachment, and adjudication tracking. It does not investigate. Every CMS in the top 10 hands flagged claims off to either a detection vendor (FRISS, Shift, Verisk) or to manual SIU. The investigator opens the CMS case, reads the flag, and starts a 14+ day manual workflow at ~$2,500 per case. CMS choice affects SIU mainly in three places: the API surface for flag routing, the ease of attaching investigation outputs as audit-trail-ready documents, and the ecosystem partnerships with detection vendors. It does not affect investigation throughput, which is governed by SIU headcount, manual coverage, and the per-case investigation cycle - all variables that sit outside the CMS.

Yes, and the answer differs from the carrier-CMS list. Origami Risk is the strongest single-platform choice for self-insured corporates, public entities, risk pools, and TPAs - it ships an integrated RMIS, claims, and GRC stack used by 950+ organizations. OneShield serves MGAs and program managers strongly (WestCongress is a public example). Insurity is common in specialty programs. For pure TPAs, a hybrid of Origami plus a specialty claims module is common. For MGAs running on top of a carrier's paper, the CMS choice is often dictated by the fronting carrier rather than by the MGA itself, which collapses the decision to fronting-carrier alignment rather than feature comparison.

Guidewire Marketplace is the largest by partner count and is where detection vendors (Verisk, FRISS, Shift) and the investigation layer (Hesper) most commonly publish ClaimCenter integrations. Duck Creek's Content Exchange is the closest analog and includes the major detection vendors. Sapiens' open API framework and EIS's API-first platform are credible alternatives but with thinner third-party catalogs. The depth of the marketplace is one of the reasons Top-25 carriers cluster on Guidewire and Duck Creek - the integration cost of bolting an investigation or detection layer on top is lower when the partner already ships a packaged connector rather than requiring a custom build.

No. Hesper AI is not a claims management system. Hesper is the investigation layer that integrates into whichever CMS the carrier already runs. Flagged claims flow from the CMS (or a detection vendor sitting on top of it) into Hesper; Hesper runs 15+ investigation phases in parallel on each flagged claim and returns an audit-ready report back into the CMS as a case attachment. The CMS stays the system of record. Manual SIU investigation runs 14+ days per case at ~25% coverage and ~$2,500 per case; Hesper's internal benchmark is 2-4 hours per case at 100% coverage and ~$150 per case. CMS choice is independent of the investigation-layer choice; the layered category model treats them as separate procurement decisions.

← More articles on the Hesper AI blog

See Hesper AI on your documents

Request a demo and we'll run an analysis on your real document samples.