Agentic claims adjudication layer for P&C insurtechs that auto-resolves routine losses under $5K with a full explainable audit trail.
P&C insurtechs automate quote-to-bind in hours but route every incoming claim to a manual adjuster, leaving claims expense ratios 5–10 points higher than they need to be. Routine low-severity losses—cracked windshields, minor hail, FNOL submissions with clear photos—consume the same adjuster time as complex disputed claims.
Why now
- Taktile's $110M Series C confirms AI claims automation is now an investable category—insurtechs shift from asking whether to automate to competing on deployment speed.
- The $90M+ claims efficiency proof point at a top insurer creates a concrete ROI benchmark that insurtech CFOs and COOs can use to justify budget and build the internal case for automation.
- Taktile's framing of "business control" over AI decisions signals that claims operations leaders—not IT departments—are the real buyers, opening a direct sales motion to heads of claims at insurtechs.
- Taktile's expansion into US, EMEA, and LATAM targets Tier 1 and Tier 2 enterprises first, leaving the $50M–$200M GWP insurtech segment without an enterprise-grade agentic claims platform during the critical 18-month market formation window.
Catalyst. Taktile's $110M Series C and its $90M claims-efficiency proof point at a top insurer make AI claims automation a credible, investable line item rather than an experimental IT project, shifting insurtechs from debating whether to automate claims to competing on how fast they can deploy.
The idea
An agentic claims adjudication platform that ingests FNOL submissions including photos, repair estimates, and policy data, runs automated coverage eligibility checks, applies computer-vision damage scoring, and issues payment authorizations for qualifying routine claims without adjuster involvement. Every decision is logged with the data inputs, model version, and plain-language rationale required by state insurance departments. Claims above the confidence threshold or dollar limit are escalated automatically to an adjuster with a pre-filled decision packet. The platform integrates with policy admin systems via a lightweight API middleware layer, avoiding rip-and-replace of Guidewire, Duck Creek, or insurtech-native core systems.
What's different. Unlike Taktile, which targets Tier 1 and Tier 2 financial institutions and requires enterprise integration cycles measured in months, this product is built for insurtechs that already run API-first policy systems and can deploy in weeks. The wedge is narrower and more opinionated—photo-evidenced property claims under $5K—which eliminates the configuration consulting phase and compresses time-to-first-auto-adjudication. Over time, the proprietary adjudication outcome dataset (damage type, fraud signal, settlement amount, appeal rate) becomes a durable moat that larger incumbents cannot replicate without years of claims data accumulation.
| Beachhead | US P&C insurtechs with $50M–$200M in gross written premium in personal property or small commercial lines, where routine losses under $5K represent 60–70% of claim count but consume the same adjuster time as complex claims |
|---|---|
| Wedge | Auto-adjudication of structured, photo-evidenced property claims under $5K— FNOL intake, coverage eligibility check, computer-vision damage assessment, and payment authorization—with a full explainable audit trail for state insurance regulators |
| Non-obvious insight | Insurtechs spent a decade automating underwriting while leaving claims manual, but Taktile's $90M efficiency number at a top insurer reveals that claims is now the bigger operations prize. The bottleneck has flipped—insurtechs are no longer constrained by policy acquisition but by claims-handling capacity, and the entire product category for insurtech-native agentic claims is still unbuilt. |
| Venture-scale path | From insurtech personal-lines auto-adjudication wedge, expand to small-commercial and specialty lines, then move upstream to mid-market regional carriers ($200M–$2B GWP), and ultimately build a cross-carrier claims intelligence layer that prices risk using actual adjudication outcome data. |
| Primary user | VP of Claims or Head of Claims Operations at a US P&C insurtech carrier with $50M–$200M in direct written premium |
|---|---|
| Secondary user | Chief Operating Officer at an insurtech carrier monitoring claims expense ratio as a key P&L metric |
| Economic buyer | VP of Claims or COO who owns the claims expense ratio budget line |
| First customer | A US homeowners or renters insurtech with $50M–$150M in direct written premium, 3–8 in-house adjusters, and 400–1,500 monthly claims, where the COO tracks claims expense ratio weekly and is already losing to better-capitalized peers on speed-to-pay |
|---|---|
| Buying trigger | Claims expense ratio exceeds 25% of earned premium, or a reinsurance treaty renewal adds a claims-handling performance covenant that forces operational improvement within 12 months |
| Current alternative | Manual adjuster workflow in spreadsheets and email, or a Guidewire ClaimCenter configuration that costs $500K+ to implement and was designed for carriers ten times their size—effectively meaning no systematic automation exists |
| Switching reason | Auto-adjudicates 60–70% of routine property claims without adjuster touch, cutting per-claim handling cost from $150–$250 to under $30, and delivers a state-regulator-ready explainable audit trail that manual workflows cannot produce |
| Pricing hypothesis | Per-claim fee of $8–$15 for each auto-adjudicated claim, plus a monthly platform fee of $3K–$8K for integration, dashboard, and adjuster escalation tooling |
Jobs to be done
| Job | Current alternative | Success metric |
|---|---|---|
| When handling 500+ monthly claims with only 4 adjusters, help a Head of Claims auto-triage and disposition routine property losses with photo evidence, so they can focus adjuster capacity on complex, disputed, and high-value claims that determine customer retention and brand reputation | Manual adjuster review queue in spreadsheets and email with no AI triage | 60–70% of eligible claims auto-adjudicated within 2 hours of FNOL, with zero state regulatory findings on AI decision auditability in the first year |
flowchart LR
FNOL[FNOL Intake] --> Ingest[Claim Ingestion Agent]
Ingest --> Coverage[Coverage Eligibility Check]
Coverage --> Vision[Computer Vision Damage Scorer]
Vision --> Gate{Confidence OK?}
Gate -->|Auto below $5K| Authorize[Authorize Payment]
Gate -->|Escalate| Adjuster[Adjuster Review Packet]
Authorize --> AuditLog[Explainable Audit Log]
Adjuster --> AuditLog
AuditLog --> PolicyAdmin[Policy Admin System]
- Signal · 4/5Taktile's $90M claims efficiency number at a top insurer directly validates the category; the insurtech segment is a derivative signal rather than primary, but strong enough to justify a 4.
- Pain · 5/5Claims expense ratio is a hard P&L line measured weekly at insurtechs; each manual touch costs $150–$250 in adjuster time; reinsurers and investors already use it as a KPI, making pain measurable and urgency real.
- Wedge · 5/5Photo-evidenced property claims under $5K is a narrow, specific workflow with clear success criteria—auto-adjudication rate, cycle time, and audit trail completeness—that can be prototyped and proved in a 60-day pilot.
- Defense · 3/5Computer vision damage scoring is increasingly commodity; defensibility accrues through proprietary adjudication outcome data (damage type, fraud signal, settlement amount) that compounds with volume and cannot be replicated quickly by new entrants.
- Scale · 4/5US P&C insurtechs represent a growing segment of a multi-hundred-billion- dollar claims market; the pathway to mid-market traditional carriers extends the addressable opportunity significantly, and Taktile's LATAM and EMEA expansion signals validate global demand.
- Policy admin platforms (Guidewire, Duck Creek) as integration partners
- Reinsurance brokers who influence insurtechs on operational performance metrics
- Third-party claims photo and repair estimate data providers
- Computer vision model training and accuracy maintenance per claim type
- Policy admin system integrations for Guidewire, Duck Creek, and insurtech APIs
- Carrier onboarding and claims-type scoping workshops
- Computer vision damage scoring pipeline trained on P&C claim photos
- Coverage eligibility rule engine with carrier-configurable thresholds
- Explainable decision record schema accepted by state insurance departments
- Auto-adjudicate 60–70% of routine property claims without adjuster touch
- Cut per-claim handling cost from $150–$250 to under $30
- State-regulator-ready explainable audit trail on every AI decision
- Deploy in weeks against existing API-first policy admin systems
- High-touch onboarding with policy admin integration and claims-type scoping workshop
- Self-serve claims dashboard and adjuster escalation management interface
- Quarterly claims expense ratio review with cross-carrier benchmarking data
- Direct outbound to VPs of Claims and COOs at Series B–D insurtech carriers
- Referrals from insurtech investors who monitor claims expense ratio
- Insurtech industry conferences and forums such as ITC Vegas and Insurtech Insights
- US P&C insurtechs with $50M–$200M in gross written premium
- Personal-lines and small-commercial insurtech carriers with 3–10 in-house adjusters
- Insurtech COOs and VPs of Claims managing claims expense ratio as a weekly KPI
- Computer vision inference cost per claim photo batch
- Policy admin integration engineering and ongoing maintenance
- Sales and customer success headcount for insurtech segment
- Per-auto-adjudicated claim fee at $8–$15 per claim
- Monthly SaaS platform fee at $3K–$8K based on policy count tier
- Optional reinsurance-ready reporting and carrier audit module
Market
| TAM | $141.8M 39.4M annual U.S. claims across homeowners, personal auto, commercial property, and commercial auto × 30% estimated low-severity/photo-evidenced eligibility × $12 estimated software spend per eligible claim = about $141.8M. |
|---|---|
| SAM | $28.4M Apply a 20% reachable-share constraint for API-friendly digital carriers and adjacent smaller regional adopters that can buy an overlay before a full core replacement: about $141.8M × 20% = $28.4M. |
| SOM | $2.8M A realistic year-3 target is roughly 12 live carriers at about $235K blended ARR each from usage plus a modest platform fee, enabled by fast-pilot, API-first deployments. |
Executive takeaways
- Claims AI has crossed from pilot to budgeted infrastructure, but buyers still want narrow, production-safe wedges rather than another full core replacement project.
- The sharpest opening is an explainable adjudication layer for low-dollar, photo-evidenced property claims, not a brand-new claims system.
- The beachhead is commercially real but thinner than the headline claims market, so early expansion into regional carriers or adjacent lines will matter.
- Auditability, human override, and compatibility with existing claim systems are the deal-winning requirements, not raw model novelty.
Market definition
This category is the decisioning layer for low-severity, photo-evidenced property claims: FNOL intake, document and photo interpretation, coverage checks, routing, payment recommendation, and audit logging that sits between carrier cores and human adjusters.
Customer and buyer
The economic buyer is a VP or Head of Claims Operations, sometimes paired with the COO at a digital P&C carrier. Claims operations owns the throughput and expense problem, while IT and compliance act as veto-holders because the workflow touches core systems and regulated claim decisions.
Buying triggers
- Long FNOL-to-payment timelines now visibly hurt customer satisfaction, making faster low-dollar claims handling a board-level operations issue. [12][13][14]
- Claims teams need throughput gains without proportional adjuster hiring, especially after portfolio growth, M&A, or catastrophe-related surges. [2][21][32]
- Governed AI and claims-modernization programs are creating budget windows for automation that is auditable and production-safe. [4][5][18][23]
Willingness to pay
Budget already exists inside claims-core, payments, and AI-modernization programs. A vendor that demonstrably removes manual validation work, shortens cycle time, and plugs into the current stack can sell into an existing operations budget rather than a speculative innovation carve-out. [2][19][21][27][28][32]
Category dynamics
Tailwinds
- Faster and more digital claims journeys materially improve satisfaction, retention, and perceived fairness.
- Claims teams still devote meaningful effort to low-value document and routing work, leaving clear automation headroom.
- Regulators and enterprise buyers now have clearer governance frameworks for AI, which rewards purpose-built vendors over ad hoc experiments.
Headwinds
- Incumbent cores and claims ecosystems are adding more embedded intelligence, shrinking whitespace for a generic standalone vendor.
- Most claims data remains unstructured, which keeps straight-through automation limited and raises exception-handling costs.
- Catastrophe volatility and litigated or unusual claim scenarios make blanket automation promises dangerous.
Validation signals
- A large insurer on Taktile is already projecting more than $90M of claims-processing efficiencies, validating that claims AI is now a budgeted category.
- Rhino + Jetty cut manual work by 50%, processed claims 80% faster, and absorbed 3x more volume without hiring through agentic claims automation.
- Property-claims satisfaction moves sharply with speed and digital experience, creating a clear ROI narrative for faster low-severity handling.
- The average straight-through baseline is still low because unstructured claim data remains hard to interpret, leaving whitespace for insurance-specific AI.
- Carriers already buy digital claims tooling that cuts cycle times and enables near-instant payments, showing willingness to fund workflow-level improvements.
Regulatory & technical constraints
- AI-supported claims decisions remain subject to unfair-trade and unfair-claims obligations, and regulators can request governance and documentation during examinations.
- Risk-management, explainability, fairness, and vendor-oversight controls are expected alongside any AI deployment in insurance.
- The straight-through baseline remains low because claims data is unstructured, so early scope has to be intentionally narrow.
- Standards-driven integrations are necessary to pull policy, billing, vendor, and payment data into a single decision flow.
Competition
Guidewire and Duck Creek anchor core claims suites; CCC and the Verisk/Tractable ecosystem own powerful estimating and network positions; Shift, Five Sigma, Snapsheet, and Sprout.ai push AI-native workflow automation. The whitespace is not “AI for claims” broadly, but a deployment-fast, explainable under-$5K property-adjudication layer for carriers that are too small or too impatient for a full-suite program.
| Competitor | Stage | Wedge | Pricing | Strength | Weakness vs. us |
|---|---|---|---|---|---|
| Guidewire ClaimCenter | incumbent | Enterprise claims core with workflow orchestration and a large partner marketplace. | Custom enterprise pricing; no public list price on fetched sources. | Deep incumbent distribution and end-to-end claims system control. | Broader suite scope and implementation burden make it slower than a focused low-dollar adjudication overlay for subscale digital carriers. |
| Duck Creek Claims | incumbent | Configurable cloud claims core with embedded intelligence and agentic applications. | Custom enterprise pricing; no public list price on fetched sources. | Embedded decisioning inside an insurer core plus explicit AI-governance posture. | Still sold as a broad intelligent-core platform rather than a narrow under-$5K property adjudication wedge. |
| CCC Intelligent Solutions | incumbent | AI-powered claims ecosystem spanning APD, casualty, payments, and provider connectivity. | Custom enterprise pricing; no public list price on fetched sources. | Large insurer footprint, claims-network connectivity, and operational scale in claims workflows. | Stronger in ecosystem and estimating positions than in a carrier-specific, explainable low-dollar property adjudication overlay. |
| Shift Technology | scale-up | Insurance-grade agentic claims platform for triage, decision support, automation, and recovery workflows. | Custom enterprise pricing; no public list price on fetched sources. | Purpose-built claims AI with strong articulation of unstructured-data and productivity pain points. | Broader enterprise platform story may still require more adaptation than a tight low-severity property adjudication product. |
| Five Sigma | scale-up | AI-native claims management platform for digital insurers, MGAs, TPAs, and reinsurers. | Custom quote; no public pricing on fetched sources. | Cloud-native fit for digital claims teams with centralized claim context and operational dashboards. | General claims operating platform rather than a dedicated, explainable photo-evidenced adjudication layer. |
Why incumbents do not win by default
- Core suites. Guidewire and Duck Creek can automate broadly inside the claims core, but midsize digital carriers still face suite breadth, configuration load, and longer implementation paths than a narrow adjudication overlay.
- Network and estimating ecosystems. CCC and the Verisk/Tractable stack own valuable repair, payment, and estimating touchpoints, but they do not automatically become the business-controlled adjudication layer for every smaller-carrier workflow.
- Insurance AI claims platforms. Shift, Sprout.ai and adjacent AI vendors prove demand for insurance-grade automation, but the startup can still win if it narrows to under-$5K property decisions with faster deployment and clearer audit outputs.
- Digital claims management platforms. Five Sigma and Snapsheet reduce workflow friction for digital carriers, yet they remain broader claims operating systems rather than a single-purpose low-severity property adjudication wedge.
- Cloud platforms. Generic AI infrastructure can supply OCR and models, but insurance ontology, regulated claim-state orchestration, and exam-ready control logic are not packaged by default.
Business plan
This company should start as an explainable claims-decision overlay for U.S. P&C insurtech carriers handling high volumes of low-severity, photo-evidenced property claims, not as a new claims core or broad insurance AI platform. The first customer is a homeowners, renters, or small-commercial carrier with $50M-$200M in written premium, 400-1,500 monthly claims, and a claims leader under pressure to reduce expense ratio without hiring more adjusters. The initial product should narrow to under-$5K property claims and launch in a recommendation-plus-human-approval posture, because auditability and regulatory comfort matter more than full autonomy in the first 12 months. The commercial logic is coherent: a claims VP or COO buys when cycle time and claims expense ratio worsen, the product plugs into the existing stack, and pricing can be tied to active claim workflows plus adjudicated volume rather than seats. The strongest reason to believe is that claims AI is already a budgeted category and large-carrier proof points show material efficiency gains, while smaller digital carriers remain too small or impatient for multi-quarter core-suite programs. The deliberate tradeoff is to win one narrow claims class first and defer adjacent lines, catastrophe-heavy states, and full straight-through payment promises until reopen rates, appeal rates, and compliance controls are proven in production. The biggest disconfirming risk is that too few target carriers will allow even recommendation-led automation on live claims, which would reduce ROI enough for incumbents and manual workflows to keep winning. Research also leaves open the exact state-by-state comfort level for automated payment authorization and the true share of sub-$5K claims with evidence quality high enough for first-wave automation, so the first 90 days must validate those assumptions directly.
Problem
- Claims teams at subscale digital P&C carriers still spend adjuster time on routine low-dollar property losses, keeping claims expense ratios elevated even when underwriting and servicing are already digitized.
- Existing alternatives are either manual queues in email and spreadsheets or broad claims platforms whose integration and configuration burden is too high for carriers that need proof in one workflow, not a core replacement.
Solution
- Provide an overlay that ingests FNOL data, photos, repair documents, and policy context, then runs coverage checks, evidence extraction, and decision recommendations for under-$5K property claims with an exam-ready audit trail.
- Start with human-approved adjudication packets and threshold-based escalation, then expand into higher automation only after each carrier proves acceptable reopen, appeal, and compliance outcomes.
Why we win
- The product is sold as a business-controlled adjudication layer for one measurable claims slice, which is faster to deploy and easier to justify than suite-wide modernization.
- Proprietary data linking images, policy wording, human overrides, settlement outcomes, and appeal behavior compounds into a carrier-specific decision graph that generic AI tooling and broader incumbents do not own by default.
| Beachhead | U.S. personal-property and small-commercial insurtech carriers with $50M-$200M in written premium, 3-10 adjusters, and recurring sub-$5K photo-evidenced property claims. |
|---|---|
| Wedge rationale | This workflow has a visible buyer, measurable unit economics, and clearer documentation patterns than broader claims automation, so the startup can prove cycle-time reduction and cost-per-claim improvement faster than if it started with all lines or all severities. |
| Sequencing | Start with recommendation-led adjudication, one claim class, and export or API overlays into existing systems before deeper write-back, partner distribution, or adjacent lines, because trust, state rollout discipline, and clean implementation matter more than feature breadth at pre-seed stage. |
| Not yet | Auto, liability, bodily injury, and litigated claims. · Catastrophe-heavy or multistate launches before the first state rollout and control package are proven. · A full claims core, broad fraud platform, or carrier benchmarking product before workflow adoption and outcome data exist. |
| Wedge | Sell a paid pilot to claims leaders at U.S. insurtech carriers whose sub-$5K property claims are clogging small adjuster teams, starting with one state and one claim class where cycle time and cost-per-claim are already measured. |
|---|---|
| Channels | Founder-led outbound to VPs of Claims, COOs, and claims transformation leaders at digital P&C carriers. · Co-sell and referral motions with claims-core implementers, modern claims-platform partners, and ecosystem consultants already trusted by the target carrier. · Design-partner conversion from carriers facing treaty renewal pressure, portfolio growth, or customer-satisfaction remediation programs. |
| Funnel targets | Discovery→qualified pilot 20-30%, qualified pilot→paid pilot 40%+, paid pilot→production 50%+, production→second claim class or second state within 12 months 50%+ |
| Pricing | Charge a paid pilot for one claim workflow, then convert to an annual platform fee plus usage-based per-adjudicated-claim pricing, because buyers care about cost-per-claim reduction and throughput rather than seat count and the researched pricing hypothesis already aligns with claims-volume economics. |
| MVP | MVP should cover one narrow property-claims class, ingest FNOL and photo evidence, run policy and threshold checks, generate an explainable recommendation packet, and route only in-policy low-risk claims for human approval while escalating exceptions to adjusters. Do not start with blanket autopay or a broad claims workbench; start with one measurable workflow that can prove lower touch cost and faster resolution. |
|---|---|
| 6 months | One design partner live on a single claims class with claim ingestion, evidence extraction, configurable thresholds, human-approval queues, audit logs, and baseline reporting on cycle time, touch rate, and reopen rate. |
| 12 months | Two to four production carriers live with two property-claim classes, state-specific control templates, limited write-back to claim systems, and dashboards for cost-per-claim, approval latency, and exception reasons. |
| 24 months | Expand into adjacent property lines and selected regional carriers, add carrier-specific learning from overrides and outcomes, and launch controlled straight-through adjudication where regulators and customers permit it. |
| Key bets | Enough under-$5K claims have clean photo and document evidence to support a narrow first release. · Recommendation-led deployment can create ROI before carriers approve straight-through payment authorization. · One reusable control and integration architecture can serve both API-first insurtechs and adjacent regional carriers. |
| Revenue streams | Annual workflow subscription for each live claims program. · Usage-based fees on claims processed or adjudicated through the platform. · Premium control, reporting, and adjacent-workflow modules once carriers expand beyond the first claim class. |
|---|---|
| Unit of value | Low-severity property claim processed with an explainable adjudication record. |
| Target gross margin | 70% |
| Expansion levers | Add more claim classes and states within the same carrier. · Expand from one line of business into adjacent property and small-commercial workflows. · Sell compliance reporting, override analytics, and eventually benchmarking once cross-carrier outcome data is large enough. · Move upmarket from insurtechs into regional carriers using the same control plane and integrations. |
| North-star metric | Eligible low-severity property claims resolved through the platform at or above human-baseline quality. |
|---|---|
| Input metrics | Share of eligible claims handled with recommendation-led or touchless automation. · Median FNOL-to-decision time for the first live claim class. · Reopen plus appeal rate versus carrier baseline. · Pilot-to-production conversion rate. · Days to go live for the dominant system stacks. |
| Moats to build | Carrier-specific graph linking evidence, policy checks, override behavior, and final settlement outcomes. · Repeatable state-control and audit-log templates that shorten compliance review. · Integration templates for modern claims systems, photo ingestion, and payment or repair-estimate partners. |
| Kill criteria | Fewer than 3 of the first 10 target carriers agree to a paid pilot after workflow review and claims-data diligence. · First two pilots fail to reduce median handling time by at least 30% for the target claim class. · Recommendation-led decisions produce reopen or appeal rates materially worse than the carrier's manual baseline. · State or carrier counsel requires human review on nearly every claim, preventing at least 25% recommendation-led throughput in production. |
Milestones
- Sign 5 design partners and close 2 paid pilots in one narrow property-claims class.
- Launch the first production deployment with human-approved recommendation workflows and audit logging.
- Prove at least 30% faster median resolution and 25% lower adjuster touch rate on the first live workflow.
- Build state-control templates and integrations for the dominant first-customer stack.
- Reach 3-6 production carriers and expand at least one account into a second claim class or second state.
- Add limited write-back, payment handoff, and override analytics to the production product.
- Establish one partner-led channel that consistently sources qualified pilots.
- Begin regional-carrier discovery using insurtech references and measured control outcomes.
- Reach roughly 12 live carriers consistent with the researched SOM.
- Expand into adjacent property workflows and selected regional carriers without rebuilding the control plane.
- Monetize reporting and adjacent workflow modules as a second revenue layer beyond the first claims wedge.
flowchart LR Wedge[Under-$5K property-claims wedge] --> MVP[Explainable recommendation and approval workflow] MVP --> Proof[Lower touch cost and faster claim resolution] Proof --> Expansion[More claim classes, more states, and regional carriers]
Founding team
| Role | Start timing | Rationale |
|---|---|---|
| Founder CEO | Month 0 | Own discovery, paid-pilot sales, carrier workflow design, and regulatory-boundary decisions in a market that buys on domain credibility. |
| Founding eng | Month 0 | Build the evidence-ingestion, recommendation, and audit-log infrastructure for the first live workflow. |
| Product lead | Month 3 | Turn design-partner requirements into a repeatable implementation playbook and prevent pilots from becoming custom services projects. |
| Integration engineer | Month 6 | Shorten time to go live across the first claims systems and enable limited write-back once trust is established. |
| Compliance and claims advisor | Month 6 | Translate state, counsel, and carrier governance requirements into deployment controls before multistate expansion. |
Experiment roadmap
| Horizon | Experiment | Hypothesis | Success metric | Owner |
|---|---|---|---|---|
| 0–90 days | Interview 15 claims leaders and collect historical claims samples from at least 5 design partners across homeowners, renters, and small-commercial property. | One narrow property-claims class has enough clean evidence and enough repeat volume to support a highly focused MVP. | Five carriers share sample data and the top initial claim class covers at least 20% of their low-severity property volume. | Founder CEO |
| 0–90 days | Build a recommendation engine and audit log on historical claims for one target claim class in one launch state. | Recommendation-led adjudication can classify and route low-risk claims accurately enough to reduce adjuster touches. | Historical backtest shows at least 30% lower manual touches with reopen and appeal proxies no worse than baseline. | Founding eng |
| 0–90 days | Complete compliance and counsel reviews for the first two launch states and define the required human-control posture. | State rollout can start with recommendation-led approvals without forcing a full human review on every claim. | Two states and one design partner approve a production-safe pilot design with explicit control requirements. | Founder CEO |
| 3–6 months | Launch two paid pilots on one claim class and measure before-and-after cycle time, touch rate, and exception rate. | A paid pilot tied to a live claims bottleneck will convert faster than a general AI transformation sale. | Two paid pilots close and at least one shows 30% faster median resolution plus 25% lower adjuster touch rate within 90 days. | Product lead |
| 6–12 months | Add limited write-back and payment-authorization handoff on the first production account. | Controlled system action increases stickiness and expansion potential once recommendation accuracy is proven. | One production customer adopts limited write-back and expands contract value by at least 25%. | Integration engineer |
| 9–15 months | Test one partner-led pipeline motion through a claims-core integrator or ecosystem consultant. | Trusted implementation partners can source qualified pilots more efficiently than pure founder outbound once a case study exists. | Partner-sourced opportunities become at least 20% of qualified pipeline with win rates comparable to founder-led outbound. | Partnerships lead |
Risk assessment
- R1Regulators or carrier counsel require human review on nearly every claim, limiting recommendation-led throughput. — Start with recommendation-led workflows, document controls state by state, and avoid autopay promises until each jurisdiction and carrier approves them.
- R2Evidence quality and image variability keep model performance below carrier trust thresholds. — Start with the narrowest claim class, enforce strict confidence thresholds, and escalate ambiguous cases automatically.
- R3The insurtech beachhead is too small or too concentrated to support venture-scale growth on its own. — Build integrations and controls that can extend into regional carriers and adjacent property lines after the first references are secured.
- R4Incumbent cores or claims-AI vendors bundle similar features before the startup has customer proof. — Compete on deployment speed, narrow workflow specificity, and superior audit outputs instead of generic AI claims.
- R5Integration differences across claims systems turn pilots into slow services projects. — Standardize on one stack and one claim class first, then productize only the integration patterns that recur across early accounts.
| Risk | Likelihood | Impact | Mitigation |
|---|---|---|---|
| Regulators or carrier counsel require human review on nearly every claim, limiting recommendation-led throughput. | High | High | Start with recommendation-led workflows, document controls state by state, and avoid autopay promises until each jurisdiction and carrier approves them. |
| Evidence quality and image variability keep model performance below carrier trust thresholds. | Medium | High | Start with the narrowest claim class, enforce strict confidence thresholds, and escalate ambiguous cases automatically. |
| The insurtech beachhead is too small or too concentrated to support venture-scale growth on its own. | Medium | High | Build integrations and controls that can extend into regional carriers and adjacent property lines after the first references are secured. |
| Incumbent cores or claims-AI vendors bundle similar features before the startup has customer proof. | Medium | Medium | Compete on deployment speed, narrow workflow specificity, and superior audit outputs instead of generic AI claims. |
| Integration differences across claims systems turn pilots into slow services projects. | Medium | High | Standardize on one stack and one claim class first, then productize only the integration patterns that recur across early accounts. |
| Title | VP-of-claims-led U.S. digital property carrier |
|---|---|
| Profile | A homeowners, renters, or small-commercial insurtech with 400-1,500 monthly claims, 3-10 adjusters, and an existing cloud or API-friendly claims stack that cannot absorb more volume through headcount alone. |
| Trigger | Claims expense ratio worsens, FNOL-to-payment times hurt satisfaction, or a renewal or growth event forces throughput gains within one budget cycle. |
| Buyer | VP of Claims or COO |
| Initial contract | $25k-$50k paid pilot for one state and one claim class, credited toward roughly $120k-$220k annual production ARR plus usage fees if the carrier hits cycle-time and touch-rate targets |
What must be true
- At least 30% of target carriers' property claims are under $5K, photo-evidenced, and clean enough for first-wave automation.
- Recommendation-led deployment can cut median handling time by at least 30% without worsening reopen or appeal rates.
- Claims leaders will buy from an operations budget before demanding a full claims-core modernization project.
- The company can go live in 90 days or less on at least one dominant target stack.
- The product can expand from insurtechs into regional carriers without a full rewrite of controls or data models.
Open diligence questions
- Which exact property-claim classes have the cleanest evidence and lowest compliance risk for the first release?
- How many target carriers already track cost-per-claim and cycle-time tightly enough to support a paid pilot ROI case?
- What documentation do carrier counsel and state reviewers require before approving recommendation-led adjudication?
- Which claims systems and data providers dominate the first 20 target accounts?
- Why will carriers buy this overlay instead of extending Guidewire, Duck Creek, Five Sigma, Shift, or manual BPO-heavy workflows?
| Call | Watch |
|---|---|
| Conviction | Strong buyer pain and credible workflow wedge, but conviction remains limited until state-by-state compliance posture and live recommendation accuracy are proven. |
| Why believe | Claims AI is already budgeted, and a narrower adjudication overlay for smaller digital carriers fits a real gap between manual workflows and heavyweight core-suite programs. |
| Why doubt | The beachhead is thinner than the headline claims market and may stall if carriers or regulators force human review on most low-dollar claims. |
| Next diligence | Verify one paid pilot with live claims data that shows faster resolution, lower touch cost, and acceptable reopen and compliance outcomes in a specific launch state. |
Financial model
| Year 1 revenue | $216K EBITDA $-764K · Cash EOP $1.24M |
|---|---|
| Year 2 revenue | $1.19M EBITDA $-584K · Cash EOP $652K |
| Year 3 revenue | $2.33M EBITDA $-218K · Cash EOP $434K |
| ARPU (annual) | $235K |
|---|---|
| Gross margin | 70% |
| CAC | $83K Payback 6.0 months |
| LTV / CAC | 11.0x LTV $914K |
| Round | pre-seed · $2.0M |
|---|---|
| Runway | 24 months |
| Milestone | Reach 6 live production carriers, win at least 1 second-state or second-claim-class expansion, and show partner-assisted pilot sourcing before raising the seed round. |
Model sanity
- Revenue engine. Base-case revenue comes from scaling from 2 paid accounts at Y1 exit to 12 live carriers at $235K blended annual ARPU by Y3 exit.
- Must go right. The first two paid pilots must convert into production references quickly enough to support 6 live carriers by Y2 exit without forcing a services-heavy delivery model.
- Model breaks if. If sales cycles lengthen and ARPU falls toward the downside case, cash can compress toward roughly $80K before the next round.
- Next-round proof. Seed readiness is tied to exiting Y2 with 6 live carriers, one second-state or second-claim-class expansion, and evidence that partner-assisted sourcing can supplement founder-led sales.
- Revenue (line, area)
- Cash EOP (dashed)
- EBITDA (bars, gray = loss)
- Founder CEO
- Founding eng
- Product lead
- Integration engineer
- Compliance and claims advisor
- Solutions engineer
- Account executive
- Applied ML engineer
| Y3 revenue | Y3 EBITDA | Cash low point | Description | |
|---|---|---|---|---|
| Downside | Recommendation-only workflows take longer to clear compliance review, so pilots convert slower, ARPU stays closer to pilot pricing, and delivery remains more service-heavy. | |||
| Base | Founder-led pilots convert into a repeatable narrow claims workflow, reaching 6 live carriers by Y2 exit and 12 by Y3 exit at the researched blended ARR level. | |||
| Upside | One reference account and partner referrals accelerate conversion into regional-carrier style deployments, lifting both account count and monetized usage without a large cost reset. |
| Variable | Downside | Upside | Cash impact | Revenue impact |
|---|---|---|---|---|
| sales cycle | Pilot-to-production timelines stretch from roughly 6-7 months to 9-12 months because compliance review drags. | A live case study shortens conversion by about one quarter. | ||
| CAC | Effective CAC rises above $110K as each carrier requires more founder time, travel, and custom security review. | Reference-led and partner-led sourcing pull CAC below $70K. | ||
| hiring pace | The company hires solutions and ML capacity two quarters early to unblock delivery, increasing burn before revenue catches up. | One later-stage hire is deferred until post-seed because implementation reuse proves stronger than expected. | ||
| ARPU | Blended annual ARPU settles at $220K because customers linger on pilot-like scopes longer. | Blended annual ARPU reaches $245K once usage and reporting modules attach faster. | ||
| churn | Monthly churn rises to 2.0% if early workflows fail to expand into second states or claim classes. | Monthly churn falls to 1.0% once the product is embedded in production claims operations. | ||
| gross margin | Gross margin slips to 67% because manual exception handling and cloud inference stay elevated. | Gross margin improves to 72% as templates and adjudication policies are reused across carriers. |
Scenarios
| Scenario | Y3 revenue | Y3 EBITDA | Cash low point | Description | Key changes |
|---|---|---|---|---|---|
| Downside | $1.68M | $-676K | $80K | Recommendation-only workflows take longer to clear compliance review, so pilots convert slower, ARPU stays closer to pilot pricing, and delivery remains more service-heavy. |
|
| Base | $2.33M | $-218K | $434K | Founder-led pilots convert into a repeatable narrow claims workflow, reaching 6 live carriers by Y2 exit and 12 by Y3 exit at the researched blended ARR level. |
|
| Upside | $3.05M | $356K | $900K | One reference account and partner referrals accelerate conversion into regional-carrier style deployments, lifting both account count and monetized usage without a large cost reset. |
|
Sensitivity
| Variable | Downside | Base | Upside |
|---|---|---|---|
| ARPU | Blended annual ARPU settles at $220K because customers linger on pilot-like scopes longer. | Blended annual ARPU stays at $235K as modeled. | Blended annual ARPU reaches $245K once usage and reporting modules attach faster. |
| CAC | Effective CAC rises above $110K as each carrier requires more founder time, travel, and custom security review. | Modeled CAC stays near $82.9K per new paid carrier account. | Reference-led and partner-led sourcing pull CAC below $70K. |
| churn | Monthly churn rises to 2.0% if early workflows fail to expand into second states or claim classes. | Monthly churn stays at 1.5%. | Monthly churn falls to 1.0% once the product is embedded in production claims operations. |
| sales cycle | Pilot-to-production timelines stretch from roughly 6-7 months to 9-12 months because compliance review drags. | Pilots convert on the modeled cadence. | A live case study shortens conversion by about one quarter. |
| gross margin | Gross margin slips to 67% because manual exception handling and cloud inference stay elevated. | Gross margin stays at 70%. | Gross margin improves to 72% as templates and adjudication policies are reused across carriers. |
| hiring pace | The company hires solutions and ML capacity two quarters early to unblock delivery, increasing burn before revenue catches up. | Hiring follows A19. | One later-stage hire is deferred until post-seed because implementation reuse proves stronger than expected. |
Key assumptions (24)
| ID | Name | Value | Unit | Source |
|---|---|---|---|---|
| A1 | Model start month | 2026-07 | YYYY-MM | [business-plan.yaml date] first full operating month after the 2026-06-25 plan date. |
| A2 | Opening cash after pre-seed close | 2000 | USDK | [business-plan.yaml fundingAsk.targetFundingRangeUsd] modeled at the low end of the stated $2-4M range because the wedge is intentionally narrow and the hiring plan stays lean through Y2. |
| A3 | Revenue unit | Active paid carrier account | definition | [business-plan.yaml investorMemo.firstCustomer.initialContract; gtm.pricing] one account can be a paid pilot or production workflow and is the customer unit used in the model. |
| A4 | Blended annual ARPU per active paid carrier account | 235 | USDK/account-year | [research.yaml market.som; business-plan.yaml investorMemo.firstCustomer.initialContract] anchored to the researched year-3 SOM of about 12 carriers at roughly $235K blended ARR each, which also fits the stated $120K-$220K platform ARR plus usage fees. |
| A5 | Revenue recognition timing | Midpoint customer count within each month or quarter | policy | [startup-finance heuristic] new paid pilots and production expansions land throughout a period, so revenue uses the average of beginning and ending paid customers. |
| A6 | Y1 month-end customer path | 0,0,0,0,1,1,1,1,2,2,2,2 | active paid carrier accounts | [business-plan.yaml milestones 0–12 months; experimentRoadmap] reaches 2 paid pilots by Y1 exit while the first account converts toward production. |
| A7 | Y2 quarter-end customers | Q1Y2 4; Q2Y2 6; Q3Y2 6; Q4Y2 6 | active paid carrier accounts | [business-plan.yaml milestones 12–24 months] lands at the top of the stated 3-6 production-carrier range by month 24. |
| A8 | Y3 quarter-end customers | Q1Y3 9; Q2Y3 10; Q3Y3 11; Q4Y3 12 | active paid carrier accounts | [business-plan.yaml milestones 24–36 months; research.yaml market.som] reaches roughly 12 live carriers, consistent with the researched SOM. |
| A9 | Gross margin target | 70 | percent | [business-plan.yaml businessModel.targetGrossMarginPct] modeled as 30% COGS on recognized revenue. |
| A10 | Monthly churn for unit economics | 1.5 | percent | [startup-finance heuristic] regulated vertical workflow software is typically sticky once embedded, but early accounts are still concentrated and reference-sensitive. |
| A11 | Founder CEO loaded cash compensation | 132 | USDK/year | [business-plan.yaml team Founder CEO] startup-finance heuristic for a below-market founder salary plus payroll tax and benefits. |
| A12 | Founding engineer loaded cash compensation | 192 | USDK/year | [business-plan.yaml team Founding eng] startup-finance heuristic for the senior technical builder owning the first adjudication workflow and audit infrastructure. |
| A13 | Product lead loaded cash compensation | 168 | USDK/year | [business-plan.yaml team Product lead] startup-finance heuristic for an early enterprise workflow product operator. |
| A14 | Integration engineer loaded cash compensation | 168 | USDK/year | [business-plan.yaml team Integration engineer] startup-finance heuristic for integration-heavy insurtech implementation work. |
| A15 | Compliance and claims advisor loaded cash compensation | 132 | USDK/year | [business-plan.yaml team Compliance and claims advisor] startup-finance heuristic for a domain and regulatory specialist supporting launch-state controls. |
| A16 | Solutions engineer loaded cash compensation | 156 | USDK/year | [business-plan.yaml product twelveMonth; operations] startup-finance heuristic for the first implementation and expansion hire once multiple carrier rollouts are live. |
| A17 | Account executive loaded cash compensation | 168 | USDK/year | [business-plan.yaml gtm.channels; experimentRoadmap 9–15 months] startup-finance heuristic for the first seller added only after founder-led pilot conversion shows repeatability. |
| A18 | Applied ML engineer loaded cash compensation | 180 | USDK/year | [business-plan.yaml product twentyFourMonth; risks] startup-finance heuristic for the later hire needed to improve accuracy, override learning, and adjacent-line expansion. |
| A19 | Hiring cadence | Founder CEO and founding eng in M1; product lead in M3; integration engineer and compliance advisor in M6; solutions engineer in M16; account executive in M19; applied ML engineer in M31 | timing | [business-plan.yaml team; strategicChoices.sequencingRationale] product, compliance, and implementation hires land before scaled GTM hiring. |
| A20 | Functional payroll allocation | Founder CEO 70% S&M / 30% G&A; founding eng 100% R&D; product lead 70% R&D / 30% G&A; integration engineer 80% R&D / 20% G&A; compliance advisor 25% R&D / 75% G&A; solutions engineer 40% R&D / 60% G&A; account executive 100% S&M; applied ML engineer 100% R&D | allocation | [business-plan.yaml team rationales; operations] allocation follows who sells the wedge, who builds the control plane, and who carries implementation or governance work. |
| A21 | Non-payroll operating spend | Y1 S&M 7K + 5% of revenue monthly, R&D 8K + 0.8K per average customer monthly, G&A 6K + 0.4K per average customer monthly; Y2 S&M 8K + 5% of revenue, R&D 9K + 0.9K per average customer, G&A 7K + 0.4K per average customer; Y3 S&M 10K + 5% of revenue, R&D 10K + 1.0K per average customer, G&A 9K + 0.5K per average customer | USDK/month | [startup-finance heuristic] covers cloud inference, audit storage, travel, security, legal, and insurer onboarding overhead for a regulated vertical SaaS motion. |
| A22 | Cash conversion policy | EBITDA approximates operating cash movement | policy | [startup-finance heuristic] no debt, capex, taxes, or material working-capital swings are modeled at this pre-seed stage. |
| A23 | Blended CAC per new paid carrier account | 82.9 | USDK/new paid account | Calculated from modeled Y2-Y3 sales and marketing spend of 829.3K divided by 10 net new paid carrier accounts. |
| A24 | Funding milestone | Reach 6 live production carriers, land at least 1 second-state or second-claim-class expansion, and prove partner-assisted pilot sourcing before the seed round | milestone | [business-plan.yaml milestones 12–24 months; fundingAsk.useOfFundsSummary] used to size the round plus a 6-month buffer. |
flowchart LR DesignPartners --> PaidPilots PaidPilots --> ProductionCarriers ProductionCarriers --> PlatformFees ProductionCarriers --> UsageFees PlatformFees --> Revenue UsageFees --> Revenue Revenue --> GrossProfit GrossProfit --> Cash
Flags: The researched SOM is only about $2.8M, so the next-round story still depends on regional-carrier or adjacent-line expansion rather than the insurtech wedge alone. · Y3 remains slightly EBITDA-negative in the base case, so management must hold hiring discipline until reference-led conversion improves. · The model assumes the 70% gross-margin target is achievable despite regulated deployment overhead; if human review or compliance labor stays embedded in delivery, payback worsens quickly.
Top risks
- State regulatory approval risk. Some state insurance departments may require pre-approval or filing of AI adjudication systems before they can authorize payments. Mitigation: Launch first in the 5–8 states with the most permissive AI adjudication guidance and position the product as a decision-support tool with human final authorization until full state-by-state approval pathways are mapped.
- Computer vision accuracy risk. AI misclassification of damage severity could cause systematic overpayment or underpayment, creating legal exposure and eroding carrier trust. Mitigation: Enforce strict confidence-score gates with mandatory human escalation for borderline cases; start with the narrowest structured claim type (windshield cracks with standardized photo templates) to maximize early accuracy before expanding to more complex damage categories.
- Thin beachhead market risk. The US P&C insurtech market has fewer than 50 meaningful targets in the $50M–$200M GWP range, creating customer-concentration risk if early adopters churn. Mitigation: Build the product architecture for a clear upgrade path to regional traditional carriers ($200M–$2B GWP) from day one, and use insurtech deployments as public reference cases to accelerate regional carrier outreach at the 18-month mark.
Evidence
Cited sources (36)
- Taktile. Taktile - Taktile Secures $110M in Goldman Sachs-led Series C to Power AI Transformation in Financial Institutions · https://taktile.com/articles/taktile-secures-110m-in-goldman-sachs-led-series-c-to-power-ai-transformation-in-financial-institutions
- Taktile. Taktile - Streamlining claims operations: How Rhino + Jetty integrated agentic AI to reduce manual work by 50% · https://taktile.com/articles/rhino-jetty-and-taktile
- Bain. The $100 Billion Opportunity for Generative AI in P&C Claims Handling | Bain & Company · https://www.bain.com/es-ar/insights/100-billion-dollar-opportunity-for-generative-ai-in-p-and-c-claims-handling
- Celent. Claims Analytics & Claims Modernization in Q2 2026 | Celent · https://www.celent.com/en/insights/claims-analytics-and-claims-modernization-in-q2-2026
- NAIC. NAIC Members Approve Model Bulletin on Use of AI by Insurers · https://content.naic.org/article/naic-members-approve-model-bulletin-use-ai-insurers
- NAIC. NAIC Model Bulletin: Use of Artificial Intelligence Systems by Insurers · https://content.naic.org/sites/default/files/call_materials/Model%20Bulletin%2010.23%20Clean.pdf
- NIST. AI Risk Management Framework | NIST · https://www.nist.gov/itl/ai-risk-management-framework
- III. Facts + Statistics: Homeowners and renters insurance | III · https://www.iii.org/fact-statistic/facts-statistics-homeowners-and-renters-insurance
- III. Facts + Statistics: Auto insurance | III · https://www.iii.org/fact-statistic/facts-statistics-auto-insurance
- III. Facts + Statistics: Commercial lines | III · https://www.iii.org/fact-statistic/facts-statistics-commercial-lines
- Insurance Journal. Verisk: Insurance Claims Volume Fell to 5-Year Low in 2025 · https://www.insurancejournal.com/news/national/2026/04/15/865901.htm
- Insurance Journal. JD Power: Customers Not Happy With Carrier Property Claims Service · https://www.insurancejournal.com/news/national/2025/03/20/816137.htm
- Insurance Journal. JD Power: Homeowners Claims Satisfaction Rises as Repair Times Improve · https://www.insurancejournal.com/news/national/2026/03/18/862324.htm
- Guidewire. How AI and Insurtech Are Transforming Claims Operations in P&C Insurance | Guidewire · https://www.guidewire.com/resources/blog/technology/how-ai-and-insurtech-are-transforming-claims-operations-in-pandc-insurance
- Guidewire. Insurance Claims Management Software - ClaimCenter | Guidewire · https://www.guidewire.com/products/core-products/insurancesuite/claimcenter-claims-management-software
- Duck Creek. Claims Management Software - Duck Creek · https://www.duckcreek.com/product/claims-management-software
- Duck Creek. Duck Creek Agentic Applications - Duck Creek · https://www.duckcreek.com/product/agentic-applications
- Duck Creek. Responsible AI Governance in Insurance: How Duck Creek Sets the Standard - Duck Creek · https://www.duckcreek.com/blog/responsible-ai-governance-in-insurance-how-duck-creek-sets-the-standard
- CCC Intelligent Solutions. AI-Powered Insurance Claims Software - CCC · https://www.cccis.com/insurance-carriers
- Tractable. Tractable teams up with Verisk to offer AI-powered estimates for property damage · https://tractable.ai/tractable-teams-up-with-verisk-to-offer-ai-powered-estimates-for-property-damage
- Shift Technology. How AI in claims is driving unprecedented speed and accuracy for top insurers · https://www.shift-technology.com/resources/reports-and-insights/ai-in-insurance-claims-for-faster-processing-and-increase-accuracy
- Shift Technology. Claims | Shift Technology · https://www.shift-technology.com/solutions/claims
- Shift Technology. Shift Technology Launches AI Claims Platform · https://www.shift-technology.com/resources/press/shift-technology-launches-ai-claims-platform
- Five Sigma. AI-Driven Insights & Decision-Making - Five Sigma · https://fivesigmalabs.com/claims-management-platform/ai-driven-insights-decision-making
- Five Sigma. Automation & Productivity - Five Sigma · https://fivesigmalabs.com/claims-management-platform/automation-productivity
- Sprout.ai. Claims automation vs claims AI: what's the difference? Sprout.ai · https://sprout.ai/resource/claims-automation-vs-claims-ai-whats-the-difference-and-why-does-it-matter
- Snapsheet. Snapsheet AI | Configurable AI for Claims Management · https://www.snapsheetclaims.com/products/snapsheet-ai
- Snapsheet. Clearcover | Snapsheet · https://www.snapsheetclaims.com/case-study/clearcover
- ACORD. ACORD Data Standards · https://www.acord.org/standards-architecture/acord-data-standards
- Deloitte Insights. Emerging trends in claims transformation | Deloitte Insights · https://www.deloitte.com/us/en/insights/industry/financial-services/insurance-claims-transformation.html
- Accenture. Transforming Claims and Underwriting with AI | Accenture · https://www.accenture.com/us-en/insights/insurance/ai-transforming-claims-underwriting
- IBM. The next era of claims operations | IBM · https://www.ibm.com/think/insights/next-era-claims-operations
- PLRB. Maximizing Efficiency: The Role of AI in Insurance Claims Processing – Property & Liability Resource Bureau · https://www.plrb.org/revolutionizing-insurance-claims
- EY. Tackling indemnity and leakage in P&C litigated claims | EY - US · https://www.ey.com/en_us/insights/insurance/claims-litigation
- Xceedance. Everest Group: Future-Proofing P&C Insurance Through Technology Adoption - Xceedance · https://www.xceedance.com/everest-group-future-proofing-pc-insurance-through-technology-adoption
- Swiss Re. How Generative AI Is Transforming Insurance Claims · https://www.swissre.com/risk-knowledge/advancing-societal-benefits-digitalisation/how-generative-ai-is-transforming-insurance-claims-claimsgenai.html