---
title: "Hesper AI vs. Snapsheet: a faster claim does not buy a better investigation"
description: "Snapsheet compresses cycle time on the claim that is going to be paid. Hesper works the flagged claim. Cycle time and investigation capacity are independent variables."
date: "2026-08-21"
lastModified: "2026-11-16"
author: "Nitish Badu"
tags: ["Vendor Comparison"]
canonical: "https://gethesperai.com/blog/hesper-vs-snapsheet/"
---

# Hesper AI vs. Snapsheet: a faster claim does not buy a better investigation

> **TL;DR** Snapsheet is a cloud-native claims management and virtual appraisal platform that compresses cycle time on the claim that is going to be paid. Hesper AI is an investigation layer that develops the claim that has been flagged. Cycle time and investigation capacity are independent variables, so a faster front end does not widen the investigation band underneath it. It narrows the slack in the regulatory clock on flagged claims.
>
> - Snapsheet publishes a 3-5 day cycle-time reduction on APD appraisals
> - California indexes SIU staffing adequacy to detection volume, 10 CCR 2698.32(a)
> - Investigation buys the extra time; the extra time does not buy the investigation

- **29.6 days** - Average property claim repair completion, down 2.8 days year over year (J.D. Power 2026 U.S. Property Claims Satisfaction Study, 5,093 homeowner responses)
- **1.4%** - SIU staff growth at participating insurers, 2021 to 2022 (CAIF Insurer SIU Benchmarking Study, via the Insurance Information Institute)
- **3-5 days** - Cycle-time reduction Snapsheet publishes on auto physical damage appraisals (snapsheetclaims.com, vendor-published, checked August 21, 2026)
- **~25% → 100%** - Flagged-claim coverage, manual SIU against an autonomous investigation layer (Hesper internal benchmark, not a published industry statistic)

Most people arrive at this comparison from one of two searches: Snapsheet alternatives, because a contract is up, or what Snapsheet does not do, because a flagged claim went out the door with nothing behind it. The ranked lists answer the first and are silent on the second, which is where the loss dollars sit.

Snapsheet is good at the layer it occupies, and nothing in this post argues a carrier should run less of it. But cycle time and investigation capacity are independent variables. For the layer map across the whole fraud stack, see the [AI fraud platforms buyer's guide](/blog/ai-fraud-platforms-compared-2026-pillar/).

## The Snapsheet alternatives list, sorted by what each one actually replaces

**What are the best Snapsheet alternatives?**

There is no single answer, because the ranked lists put four different products in one column. For the claims core: Guidewire ClaimCenter, Duck Creek, Majesco, Insurity, Sapiens, Five Sigma, Origami Risk, FileHandler Enterprise. For virtual appraisal and damage assessment: CCC Intelligent Solutions, Mitchell, Solera Audatex, Tractable, Claim Genius. For digital intake: RightIndem. For detection: Shift Technology, FRISS, CLARA Analytics, Charlee.ai. Nothing on any of those lists works a flagged claim end to end and writes the finding.

The ranked alternatives pages put a claims core, an estimating platform and a fraud detection engine in one flat list, as though a carrier chooses one of the three. Snapsheet occupies four lanes at once, so sort the names by the lane each one would replace.

| Lane | What it replaces in a Snapsheet footprint | Names that appear on the ranking lists |
| --- | --- | --- |
| Claims core and administration | The claims platform, workflow engine, financials, queues and dashboards | Guidewire ClaimCenter, Duck Creek, Majesco, Insurity, Sapiens, Five Sigma, Origami Risk, FileHandler Enterprise, Cloud Claims, SimpleSolve, Spear Technologies, PCIS ClaimsVISION, DOCOsoft, VRC Insurance Systems |
| Appraisal and damage assessment | Virtual vehicle appraisals, estimating, total loss valuation | CCC Intelligent Solutions, Mitchell, Solera Audatex, Tractable, Claim Genius, HOVER |
| Digital intake and self-service | Guided first notice of loss and policyholder photo capture | RightIndem |
| Field inspection | The physical look at the loss, where photos are not enough | WeGoLook, HOVER |
| Detection and analytics | Nothing inside Snapsheet's own product surface. This is the partner lane | Shift Technology, FRISS, CLARA Analytics, Charlee.ai, ISO ClaimSearch |
| Investigation | Nothing, in any footprint. The work between an accepted referral and a documented finding | Not on any of the ranking lists |

Read the bottom row as the point of the table. A carrier can replace Snapsheet lane by lane, and nothing on those lists produces the artifact that 10 CCR 2698.36(a)(5) asks for. The detection lane comes closest and still stops short: a score, a flag, a case record, then a person. The claims cores have the same gap, as covered in [the top claims management systems for P&C carriers in 2026](/blog/top-claims-management-systems-pc-carriers-2026/).

## What the analysts scored, and the dimension they left out

**Is Snapsheet a Celent Luminary, and what does that measure?**

Yes. Celent's P&C Claims Systems: 2026 North America Edition, published June 30, 2026, evaluated 66 claims systems and placed six in Luminary, its top tier. Snapsheet is one. The scoring runs on three dimensions: Advanced Technology, Breadth of Functionality, and Customer Base and Support. None of the three is investigation, and none is fraud. The most rigorous evaluation this category has does not score the work the loss dollars sit behind.

[Celent's P&C Claims Systems: 2026 North America Edition](https://www.celent.com/en/insights/p-and-c-claims-systems-2026-north-america-edition) is the one evaluation in this category done by analysts against a published framework, and it places Snapsheet in the top tier.

**Figure 1 (Celent 2026 · Claims systems) - Six of 66 systems made Luminary. None was scored on investigation.** Celent's three scored dimensions certify a modern, broad, well-supported claims core and say nothing about the flagged lane.

1. **Evaluated: 66** - P&C claims systems in Celent's 2026 North America Edition
2. **Luminary tier: 6** - Snapsheet is one, alongside Guidewire ClaimCenter, Majesco and Five Sigma
3. **Dimensions scored: 3** - Advanced Technology, Breadth of Functionality, customer base and support
4. **Investigation: Not scored** - Neither investigation nor fraud is one of the scored dimensions

**Read it as:** A good claims core picked from the Luminary tier is not yet a decision about the investigation lane.

Sources: Celent, P&C Claims Systems: 2026 North America Edition, June 30, 2026; Snapsheet announcement, July 7, 2026; Five Sigma release, June 30, 2026 (the six-of-66 count). Tier membership as each vendor announced it.

Celent sells the report and each vendor announces only its own result. Assembled from those announcements, the tier looks like this.

| Vendor | What the vendor's own announcement says | Dated |
| --- | --- | --- |
| Snapsheet | Named a Luminary in P&C Claims Systems: 2026 North America Edition, described as Celent's highest distinction across the 66 systems evaluated | July 7, 2026 |
| Guidewire ClaimCenter | Luminary in all four regional Celent claims reports, with eight XCelent awards including all three North America categories, the most of any vendor | August 19, 2026 |
| Majesco Intelligent Claims for P&C | Luminary, plus the XCelent Award for Breadth of Functionality in North America | August 19, 2026 |
| Five Sigma | Luminary, and the release that states the category holds only six claims systems | June 30, 2026 |
| Duck Creek | Highest possible rating in Celent's technical capabilities matrix with XCelent awards for Advanced Technology and Breadth of Functionality, under a release titled Claims Systems Vendors: North America P&C Insurance, 2026 | September 9, 2026 |
| Origami Risk | Named a Luminary in what its release calls Celent's 2026 Claims Administration Systems Report, a differently titled document, so read this row as adjacent rather than confirmed for the same edition | July 1, 2026 |

Read the Duck Creek and Origami Risk rows as hedged, because their releases use different report titles. Either way, a Luminary badge certifies a modern, broad, well-supported claims core. It certifies nothing about whether a flagged claim leaving that system carries a developed investigation behind it.

## Snapsheet's fraud posture, stated accurately

**Does Snapsheet do fraud detection?**

Snapsheet's fraud capability is partner-delivered, not native. OFAC and ISO compliance screening ships inside Payments; an ["AI, Analytics & Fraud" partner category](https://www.snapsheetclaims.com/partnerships) supplies ClaimSearch, Charlee.ai and CLARA Analytics; a May 2020 integration routes Shift Technology Force alerts into the platform. Signal reaches the platform. Developing the flagged file into a documented finding is a separate layer.

One correction first, because it belongs to us. Our May 2026 [four-vendor claims management systems comparison](/blog/claims-management-systems-comparison/) said Snapsheet's public pages do not mention fraud or SIU capability anywhere. That statement was too broad and this post supersedes it.

Snapsheet's [partnerships page](https://www.snapsheetclaims.com/partnerships) states the architecture clearly. Detection arrives through partners, and the platform is the surface that receives it. Sanctions screening inside Payments answers whether a party may lawfully be paid. It does not answer whether the loss happened the way it was described.

In May 2020, [Shift Technology and Snapsheet announced a partnership](https://www.shift-technology.com/resources/news/shift-technology-and-snapsheet-partner-to-add-fraud-detection-to-snapsheet-claims-management-platform). Brad Weisberg, CEO and Founder of Snapsheet, said "incorporating fraud detection from Shift is only a click away." He is describing his architecture correctly. A click that brings in a flag is upstream of every hour of work the flag creates.

Somebody still has to pull the prior loss history, examine the documents for alteration, cross-reference the recorded statement against the physical evidence, reconstruct the timeline, and write down what they found and why. That sequence is the investigation, and no notification produces it.

> **What was checked, and when**
>
> This post checked Snapsheet's homepage, claims platform, appraisals, payments, Snapsheet AI and partnerships pages on August 21, 2026, and re-checked all six on October 8, 2026. There is still no published capability for fraud investigation, SIU case management, or an investigation findings record. That is a statement about what Snapsheet publishes, not about what the platform could be configured to do.

The directories get this wrong. [SelectHub's Snapsheet profile](https://www.selecthub.com/p/claims-management-software/snapsheet/) says "Built-in fraud detection capabilities help identify suspicious claims early." Built-in is the wrong word. Partner-delivered detection means a second contract, a second data agreement, a second integration and a second vendor to name in a market conduct response.

Hesper is built for the investigation layer, with detection inside it. A carrier already running Shift Force, Charlee.ai, CLARA Analytics or ISO ClaimSearch through Snapsheet keeps all of it, because Hesper is complementary to FRISS, Shift Technology and Verisk, not a replacement. The same two-layer logic on the estimating side is in [Hesper AI vs. CCC Intelligent Solutions](/blog/hesper-vs-ccc-intelligent-solutions/).

## The clock does not stop for a fraud investigation. It changes what you owe.

**Does the claim payment clock stop while a carrier investigates suspected fraud?**

No. It converts. [NAIC Model Regulation #902](https://content.naic.org/sites/default/files/model-law-902.pdf) sections 7.A and 7.B replace the fixed 21-day accept-or-deny count with a reasonable time for full investigation, and only where a reasonable basis is supported by specific information available for regulator review. California [10 CCR 2695.7(k)](https://www.law.cornell.edu/regulations/california/10-CCR-2695.7) extends 40 days to 80, or suspends it by Commissioner order.

The NAIC [Unfair Property/Casualty Claims Settlement Practices Model Regulation #902](https://content.naic.org/sites/default/files/model-law-902.pdf) sets the pattern most states follow: 15 days to acknowledge a claim, 21 days to accept or deny after proofs of loss, 30 days to pay after affirming liability.

Relief from the day count appears twice, in sections 7.A and 7.B, and both times it applies only "Where there is a reasonable basis supported by specific information available for review by the insurance regulatory authority." California's 2695.7(k) repeats the condition. Suspicion alone does not open the valve. Developed information does.

| What the carrier owes | Provision | Day count |
| --- | --- | --- |
| Acknowledge receipt of the claim | NAIC Model Regulation #902, section 6.A | 15 days |
| Respond to an insurance department inquiry about a claim | NAIC Model Regulation #902, section 6.B | 21 days |
| Advise the first party claimant of acceptance or denial after properly executed proofs of loss | NAIC Model Regulation #902, section 7.A | 21 days |
| Written reasons more time is needed, then a further letter while the investigation remains incomplete | NAIC Model Regulation #902, section 7.B | 21 days, then 45 days and every 45 days after |
| Tender payment after affirming liability, where the amount is determined and not in dispute | NAIC Model Regulation #902, section 7.F | 30 days |
| Accept or deny the claim, in whole or in part (California) | 10 CCR 2695.7(b) | 40 calendar days |
| Written notice that additional time is required (California) | 10 CCR 2695.7(c)(1) | Inside the same 40 days |
| Tender payment or otherwise perform the claim obligation after acceptance (California) | 10 CCR 2695.7(h) | 30 calendar days |
| Relief where fraud is reasonably suspected (NAIC) | NAIC Model Regulation #902, sections 7.A and 7.B, second paragraphs | Fixed count replaced by a reasonable time for full investigation, on specific information available for review |
| Extension where fraud is reasonably suspected (California) | 10 CCR 2695.7(k) | 40 becomes 80, or is suspended by the Commissioner, on specific information plus Insurance Code 1872.4 |
| Conduct and diligently pursue a thorough, fair and objective investigation | 10 CCR 2695.7(d) | No day count. A continuous duty. |

Now map the manual baseline onto those numbers. A manual SIU investigation runs 14+ days per case, and one investigator is carrying 200+ open cases, both Hesper internal benchmarks. Against a 21-day clock, that file is routinely still open when the answer is due. Most flagged files never get the full workup, so the carve-out is unavailable in practice.

| The clocks a flagged claim has to fit inside, in days | Value | Share |
| --- | --- | --- |
| California 2695.7(k): extension once fraud is reasonably suspected | 80 days | 100% |
| California 2695.7(b): accept or deny the claim | 40 days | 50% |
| California 2695.7(h): tender payment after acceptance | 30 days | 38% |
| NAIC #902 section 7.A: accept or deny after proofs of loss | 21 days | 26% |
| Manual SIU investigation, per flagged claim (Hesper benchmark) | 14+ days | 18% |
| Autonomous investigation, per flagged claim (Hesper benchmark) | minutes | 3% |

> Investigation buys the extra time. The extra time does not buy the investigation.
>
> - Hesper AI product research

## A faster front end raises the pressure on the flagged lane

The front end of the claim is measurably faster, and investigation capacity is not moving at the same rate. J.D. Power [measured average property repair completion at 29.6 days](https://www.claimsjournal.com/news/national/2026/03/18/336327.htm) in its 2026 study, down 2.8 days year over year. Average time to final payment came in at 40.7 days, down 3.4 days.

Now the other curve. The [Insurance Information Institute](https://www.iii.org/fact-statistic/facts-and-statistics-insurance-fraud), citing the Coalition Against Insurance Fraud's Insurer SIU Benchmarking Study, reports that participating insurers saw SIU staff grow 1.4% from 2021 to 2022, below the 2.5% growth rates of the two previous studies. The same III page reports that "80 percent of respondents currently use predictive modeling to detect fraud, up from 55 percent in 2018."

**Figure 2 (Two curves) - The front end got days faster. SIU staff grew 1.4%.** Cycle time responds to software. Investigation capacity has historically responded only to headcount.

**Front end · J.D. Power 2026**

- **-2.8 days** - average property repair completion, now 29.6 days
- **-3.4 days** - average time to final payment, now 40.7 days

**Detection · SIU benchmark**

- **80 percent** - of respondents use predictive modeling to detect fraud
- **55 percent** - used it in 2018

**Flat: Investigation capacity, over the same years.**

- +1.4% SIU staff growth, 2021 to 2022, below 2.5% in the two previous studies
- 15 percent of automated referrals accepted by SIUs in 2019, down from 22 percent

**Takeaway:** Doubling detection against the same denominator does not double investigations. It doubles the queue.

Sources: J.D. Power 2026 U.S. Property Claims Satisfaction Study, via Claims Journal, March 18, 2026 (5,093 homeowner responses); Insurance Information Institute, citing the Coalition Against Insurance Fraud's Insurer SIU Benchmarking Study (participants only); Insurance Journal, 2019 SIU benchmark data published in 2020.

Detection is climbing while accepted investigations are not. On 2019 data, [Insurance Journal reported](https://www.insurancejournal.com/news/national/2020/08/25/580280.htm) that "the percentage of referrals from automated systems accepted by special investigation units has declined to 15 percent from 22 percent."

The same J.D. Power study shows how the claim now arrives: through digital channels, the model Snapsheet pioneered in auto.

| Digital channel use in the property claim (J.D. Power 2026 U.S. Property Claims Satisfaction Study, 5,093 responses) | Value | Share |
| --- | --- | --- |
| Submitted photos for estimates or payments | 49% | 49% |
| Received claim updates digitally | 45% | 45% |
| Filed first notice of loss digitally | 38% | 38% |

The reason is structural. Front-end cycle time responds to software. Investigation capacity has historically responded only to headcount, so doubling detection volume does not double investigations. It doubles the queue. Manual SIU capacity reaches roughly 25% of what a carrier flags, a Hesper internal benchmark covered in [why 75% of flagged insurance claims are never fully investigated](/blog/why-flagged-insurance-claims-never-investigated/).

Autonomous investigation changes the denominator. Hesper runs 15+ investigation phases in parallel on every flagged claim, so coverage moves from ~25% of flagged claims to 100% (Hesper internal benchmark). The investigator's role shifts from execution to decision-making.

## California indexes SIU staffing adequacy to what you detect

California measures the adequacy of an insurer's SIU staffing partly against the insurer's own detection volume. [10 CCR 2698.32](https://www.law.cornell.edu/regulations/california/10-CCR-2698.32) lists the "volume of suspected fraudulent California claims currently being detected" among the factors that may be considered in staffing the SIU.

**Figure 3 (10 CCR 2698 · California) - Turn on more detection and the SIU staffing bar moves with it.** Read left to right: an automated red flag is a credible referral, and the volume of those referrals feeds the staffing test.

**What a detection partner sets in motion**

1. A detection partner sends automated, system-generated referrals
2. Each one carrying a red flag is a credible referral under 2698.36(c)
3. Each produces an investigation or a documented reason there was not one
4. Staffing adequacy is weighed against the volume being detected, 2698.32(a)

**200+** - open cases per manual investigator, who completes roughly 10 investigations a month. Hesper internal benchmark.

**Flagged: The bar moved as a side effect.** Adding detection without investigation capacity is not non-compliance. It raises the standard the carrier will be measured against.

Sources: California Code of Regulations, 10 CCR 2698.36(c) and 2698.32(a), as quoted in this article. Caseload and throughput: Hesper internal benchmark for the manual baseline.

The companion provision, [10 CCR 2698.36(c)](https://www.law.cornell.edu/regulations/california/10-CCR-2698.36), requires the SIU to investigate each credible referral, "including automated or system-generated referrals." So a flag from a partner detection engine produces either an investigation or a documented reason there was not one. Both scale with detection volume rather than with headcount.

A carrier that adds detection without investigation capacity has not become non-compliant. It has moved the bar it will be measured against. The regime is walked through in [the 10 CCR 2698 SIU compliance guide](/blog/california-10-ccr-2698-siu-compliance/), and corroborating photo evidence in [the AI-generated evidence investigation playbook](/blog/ai-generated-evidence-fraud-investigation-playbook/).

## The two audit trails a carrier has to produce

**What documentation does a carrier have to produce for a suspected fraud claim?**

Two separate records. NAIC #902 section 4.B requires detailed claim-file documentation permitting reconstruction of the insurer's activities - an activity log a claims system produces. California [10 CCR 2698.36(a)(5)](https://www.law.cornell.edu/regulations/california/10-CCR-2698.36) additionally requires a written investigation summary, separate from every other document in the file, carrying the investigator's findings and the basis for them.

The first record is an activity log, and Snapsheet ships exactly the right artifact for it, named "Transparent Claim History" on its claims platform page. The second is a different animal: a written summary that carries the investigators' findings and the basis for them.

An activity log answers what did we do and when. A findings record answers what did we conclude and why, and it cannot be assembled by exporting the activity log. Only the second satisfies the prompt-payment carve-out, because only the second contains specific information available for review.

| Record the carrier has to produce | What the provision asks for | Layer that produces it |
| --- | --- | --- |
| Claim activity log | NAIC #902 section 4.B: documentation sufficient "to permit reconstruction of the insurer's activities relative to each claim." | Claims management system. Snapsheet ships this as Transparent Claim History. |
| Investigation findings summary | 10 CCR 2698.36(a)(5): a summary "separate from any other document prepared in connection with the investigation" containing "findings regarding the suspected insurance fraud and the basis for their findings." | Investigation layer. No workflow platform publishes this artifact. |
| Documented reason an investigation was not opened | 10 CCR 2698.36(c): where the SIU refrains from opening an investigation it "shall document in the claim file or SIU investigation file the reasons supporting its conclusion." | Investigation layer, or an SIU analyst doing it by hand, once per declined referral. |
| Basis for relief from the accept-or-deny clock | NAIC #902 sections 7.A and 7.B and 10 CCR 2695.7(k): "a reasonable basis supported by specific information available for review" by the regulator. | Investigation layer. The activity log shows the file was worked; it does not establish the basis. |

Hesper is built against that second record. Every phase of an investigation is logged with its sources, its reasoning and its timestamps, and the output is written findings rather than a score.

Hesper holds SOC 2 Type I and prices a flat per-case rate with no contingent or recovery-share component. That pricing matters for compliance: 10 CCR 2698.33(c)(2) requires insurer contracts to "Not include provisions that could provide disincentives to the referral and/or investigation of suspected insurance fraud." More in [how to generate an audit-ready fraud investigation report](/blog/audit-ready-fraud-report-speed-ai/).

## Both in one stack, and what to ask each vendor

**Should a carrier run Snapsheet and an AI investigation layer together?**

Yes, and most do. Snapsheet stays the intake, workflow, appraisal and payments engine; partner detection keeps supplying flags; the investigation layer consumes the flagged claim and returns a findings record onto it. Nothing is ripped out. The question is which duty is under-resourced: settlement speed, or the roughly three in four flagged claims closing undeveloped.

Picture the stack a digital-first carrier or MGA runs in 2026. Snapsheet is the claims platform, a partner supplies the fraud signal, and Payments screens at disbursement. Then a claim gets flagged, and the next step is a person carrying 200+ open cases. That is the seam.

*Figure: Four bands of the claims stack have a vendor. The fifth is the one where the loss dollars sit. Drawn in the order a claim moves through them: intake, appraisal, payments and detection are each covered, and in a Snapsheet-shaped stack they are covered well. Then the claim gets flagged and the next step is a person carrying 200+ open cases at 14+ days per case, which is why roughly three in four flagged claims close undeveloped on the Hesper internal benchmark. The meters underneath are the clock that band has to fit inside.*

The flagged claim and its attachments flow out for investigation; the finished findings record flows back onto the claim. Hesper never replaces the claims system of record and is not a claims adjudication tool: the human SIU lead and adjuster make the call. The detection-layer version of this boundary is in [Hesper AI vs. Verisk](/blog/hesper-vs-verisk/), and the agentic-handling version is in [Shift Claims vs. Hesper](/blog/shift-claims-agentic-ai-vs-hesper/).

| Dimension | Snapsheet | Hesper AI |
| --- | --- | --- |
| Layer | Claims management, virtual appraisal, payments | Investigation |
| The file it optimizes | The claim that is going to be paid | The claim that has been flagged |
| Primary metric | Cycle time, appraisal accuracy, cost to handle | Coverage of flagged claims, defensibility of the finding |
| Trigger | First notice of loss | A flag, from any detection source or from Hesper's own detection |
| Input | Loss notice, photos, documents, policy data | The flagged claim file plus external evidence |
| Core output | A settled, paid, documented claim | An investigation summary with findings and the basis for them |
| Published fraud capability | Partner-delivered: ClaimSearch, OFAC screening, Charlee.ai, CLARA Analytics, plus the May 2020 Shift Force integration and the April 2024 Talem AI Delta-V partnership | Built-in detection plus 15+ investigation phases run in parallel |
| Audit artifact | Transparent Claim History, a time-stamped record of every action taken | Decision trail with sources, reasoning and timestamps; written findings and their basis |
| Regulatory hook it serves | NAIC #902 sections 4.B, 6.A, 7.A and 7.F; CA 2695.7(b) and (h) | CA 2695.7(d) and (k); 10 CCR 2698.32(a), 2698.36(a)(5) and 2698.36(c) |
| Cycle-time claim | 3-5 day average reduction on APD appraisals (vendor-published) | Minutes rather than weeks per flagged case, against a 14+ day manual baseline (Hesper benchmark) |
| Lines of business | Auto-first heritage, now auto, property and commercial | Cross-line: auto, workers comp, property, general liability |
| What it replaces | Manual appraisal and manual claim workflow | Manual SIU investigation capacity, not the SIU |
| Runs alongside | Detection vendors, estimating platforms, an investigation layer | Snapsheet, Guidewire, Duck Creek, FRISS, Shift, Verisk |

The cycle-time row is the one most likely to be misread. Snapsheet's 3-5 days is a reduction on an appraisal that was always going to be completed. Hesper's minutes are the elapsed time of an investigation that, in most carriers today, does not happen at all on three out of four flagged files. Hold an investigation vendor to coverage rather than speed.

Two questions do most of the work in the RFPs.

- Workflow vendor: when a red flag fires mid-workflow, which queue does the file enter, who is notified, and does the payment step hold?
- Investigation vendor: what percentage of flagged claims will actually be investigated end to end, and does the output satisfy 10 CCR 2698.36(a)(5)?

So the decision is not Snapsheet or Hesper. It is which of the two duties is under-resourced. If claims settle slowly, Snapsheet is a credible answer. If flagged claims close without investigation, no amount of workflow speed addresses it. For the lifecycle view, see [the claims process end to end](/blog/claims-process-end-to-end-fnol-to-settlement/) and [the complete guide to automating the claims lifecycle](/blog/claims-automation-pillar/).

## Key takeaways

- Cycle time and investigation capacity are independent variables. Snapsheet's published 3-5 day reduction on auto physical damage appraisals does not change the share of flagged claims that get fully developed, which sits near ~25% on Hesper's internal benchmark.
- Celent placed six of 66 claims systems in its Luminary tier, Snapsheet among them. Investigation is not one of the three scored dimensions.
- Snapsheet has a real fraud posture and it is partner-delivered by design: OFAC and ISO screening inside Payments, an "AI, Analytics & Fraud" partner category, and the May 2020 Shift Force integration.
- Relief from the accept-or-deny clock is conditioned on a reasonable basis supported by specific information available for review by the regulator. Investigation is what earns the extra time.
- NAIC #902 section 4.B asks for an activity log, which Snapsheet ships as Transparent Claim History. 10 CCR 2698.36(a)(5) asks for a separate findings summary, which is the artifact the investigation layer exists to produce.

## Frequently asked questions

### What is the difference between Hesper AI and Snapsheet?

They sit at different layers. Snapsheet is a cloud-native claims management and virtual appraisal platform, measured on how fast and accurately a claim reaches settlement. Hesper AI is an investigation layer. It takes a claim flagged as suspicious, runs 15+ investigation phases in parallel, and produces an investigation summary with findings and the basis for them. Most carriers of any size need both.

### Does Snapsheet do fraud detection?

Not as a native product. Snapsheet ships OFAC and ISO compliance screening inside Payments, plus a partner category titled "AI, Analytics & Fraud" containing ClaimSearch, OFAC, Charlee.ai and CLARA Analytics. A May 2020 integration delivers Shift Technology Force alerts into the platform. Fraud signal reaches Snapsheet through partners by design. Developing the flagged claim into a defensible determination is a separate layer.

### Can Hesper AI replace Snapsheet?

No, and it is not designed to. Hesper does not take first notice of loss, write repair estimates, settle total losses or issue payments. It is not a claims adjudication tool either; the human SIU lead and adjuster make the call. What Hesper replaces is manual SIU investigation capacity, not the SIU itself and not the claims system of record.

### How much does Snapsheet cost?

Snapsheet publishes no price. There is no rate card, pricing page or public tier structure on snapsheetclaims.com. SelectHub lists the model as monthly and quote-based and prints a $100 to $500 starting range with no stated unit, which is a directory estimate rather than a vendor figure. Ask what the billing unit is and which modules sit inside the base.
