Financial Services Insurance Claims Operations

Auto Claims

Complex multi-party engagements where risk, regulation, and claim resolution require coordinated action.

Mitchell International CCC Intelligent Solutions Solera Audatex
Inside this journey
  1. Pre-Discovery

    Align the room on outcomes, decision process, and constraints before deeper discovery.

    1. Stakeholder Alignment

      Confirm decision roles, timeline, success metrics, and key constraints for claims, IT, and transformation sponsors.

      Alignment Questions

      Quick Introductions: Who's in the Room?

      • Who are the people we should consider part of the core decision team for this claims initiative? Options: VP of Claims, Head of Auto Physical Damage, Claims Transformation Lead, CIO/CTO, Head of IT Integrations, Head of Compliance/Legal, Procurement, Other (please name)
      • Which single role will have ultimate sign-off authority for a pilot and contract? Options: VP of Claims, Head of Transformation, CIO/CTO, Chief Procurement Officer, CEO/Board, Other (please specify)
      • Tell us who will be the operational day-to-day point of contact for discovery and what their title is.
      • Are there informal influencers (committees, regional leads, union reps, audit teams) who typically shape claims decisions? If so, who are they?
      • How do you prefer we coordinate communications with the team (weekly steering, biweekly working sessions, Slack, email)? Options: Weekly steering meeting, Biweekly working session, Ad-hoc as needed, Dedicated Slack/MS Teams channel, Email updates only, Other

      Who Really Decides — and How Fast Can They Move?

      • If everything aligned politically and technically, how quickly could your organization approve a pilot start date? Options: Immediately (under 2 weeks), Within 1 month, 1–3 months, 3–6 months, Longer than 6 months
      • Describe the approval path from pilot approval to production—who signs, who advises, and which committees meet along the way?
      • Which calendar constraints are non-negotiable for approvals (budget cycle, regulatory filings, board windows, fiscal year cutoffs)? Options: Budget cycle, Quarterly board reviews, Regulatory filing windows, Vendor procurement windows, No fixed constraints, Other
      • When prior projects ran late, what were the top two root causes (e.g., data access, security review, executive reprioritization)? Options: Data access delays, Security/compliance review, Integration complexity, Stakeholder reprioritization, Procurement/legal negotiations, Vendor readiness, Other
      • What single action from a vendor or partner has historically accelerated internal approvals the most?

      What Would Move the Needle for Leadership?

      • Which single metric—if improved—would change the conversation from ‘maybe’ to ‘go’ at the executive level? Options: Cycle time reduction (%), Loss Adjustment Expense (LAE) reduction ($), Estimate accuracy vs. adjuster (%), Supplement rate reduction (%), Straight-through processing rate (%), Customer satisfaction (CSAT/NPS)
      • Please share current baseline values for the top 3 metrics you care about (e.g., cycle time = X days; supplement rate = Y%).
      • Which of these metrics require auditable trails or regulatory reporting in your jurisdiction? Options: Estimate accuracy, Total loss valuation, Repair cycle time, Payment timing, Customer communications, None of the above, Other
      • How confident are you in the accuracy and consistency of your current metric measurements? Options: Very confident, Somewhat confident, Doubtful, Not confident
      • If a pilot improves your primary metric but causes a secondary KPI to worsen, which trade-offs would be acceptable and which are unacceptable?

      Where the Pain Really Hides in Your Workflow

      • Which stage of FNOL-to-settlement creates the most rework, cost, or delay for you today? Options: FNOL triage, Photo/virtual appraisal, Estimate generation, Supplement handling, Shop assignment/scheduling, Parts sourcing/delivery, Payment/finalization
      • Walk us through a recent claim that required multiple supplements or escalations—what caused the divergence from the initial estimate?
      • How frequently do initial estimates lead to at least one supplement, and what are the top 2 causes of those supplements? Options: <5%, 5–15%, 15–30%, >30%
      • Describe the current touchpoints and handoffs with body shops—where do most approvals or disputes occur?
      • How do your adjusters describe the emotional toll of rework and bad estimates (frustration, overtime, reduced morale)? Options: High frustration/overtime, Moderate stress, Occasional annoyance, Minimal impact

      Assumptions We Should Put on the Table

      • What’s one assumption about AI-based estimation or photo-first claims you’d be willing to challenge if given credible evidence otherwise?
      • Do you assume AI cannot meet adjuster-level accuracy on complex repairs—how have you tested that belief so far? Options: Yes, not achievable, Possibly achievable with caveats, We believe it can match adjusters, Not tested
      • Which integrations or data weaknesses have you labeled ‘too hard’ in previous projects? Options: Legacy claims system APIs, Body shop management systems (BMS), Parts pricing feeds, Telematics/vehicle data, Payment rails, None
      • Are there regulatory or audit assumptions you’ve made that might be more flexible than you think (e.g., scope of photo evidence, virtual appraisal acceptance)?
      • If we presented evidence that contradicted a key assumption, what internal barriers might still stop you from changing course? Options: Budget constraints, Political resistance, Procurement rules, Technical debt, Compliance concerns, Other

      The Practical Limits: Tech, Data, and Security

      • Which single system or data gap would be a showstopper for integration (i.e., without it a pilot cannot proceed)? Options: Core claims system access, Body shop management system (BMS) integration, Parts/pricing feed, Payment API, Identity/consumer data, Security/compliance certification (SOC2)
      • Please list the claims, billing, shop, and parts systems (with versions) we must integrate with and any access constraints.
      • Which data fields are available in real-time versus batched exports (photos, VIN, labor hours, estimates, parts lists)? Options: Real-time, Batched overnight, Manual export, Unavailable
      • Do you have security or privacy certifications and controls we must meet before receiving test or production data (SOC2, ISO27001, local privacy regs)? Options: SOC2, ISO27001, Local privacy law compliance (e.g., CCPA, GDPR), Internal security review only, No formal certification required
      • Have you tried similar integrations previously—what specific blockers or surprises came up during those projects?

      What Would Success Feel Like to Your Team (Beyond the Numbers)?

      • Beyond hard metrics, what cultural or operational changes would make leadership feel the project was worth it?
      • If adjusters regained X minutes per claim or saw fewer escalations, how should that manifest in their daily work and morale?
      • How should body shops signal acceptance—faster scheduling, fewer disputes, or explicit partnership metrics? Which do you trust most? Options: Faster scheduling, Fewer estimate disputes, Higher repair acceptance rate, Positive shop feedback, Other
      • What non-quantitative signals (e.g., fewer complaint escalations, improved internal narratives) would you include in a success report?
      • Which stakeholder groups will need visible, quick wins to stay engaged, and what would those wins look like for each group? Options: Claims leadership, Adjusters, IT/Integrations, Procurement/Legal, Body shops, Customers/Call centers

      Risk, Governance, and the Red Lines

      • What single operational, financial, or regulatory risk would cause you to halt the project immediately? Options: Regulatory non-compliance, Material overpayment risk, Data breach, Major shop pushback, Unacceptable customer complaints, Other
      • What governance structure and cadence do you require during pilot (steering committee, weekly ops, monthly exec review)? Options: Weekly ops + monthly steering, Biweekly working group + executive monthly, Ad-hoc as issues arise, Formal steering committee only
      • What contractual protections or KPIs (caps on overpayment, SLA penalties, indemnities) are essential before you sign?
      • What rollback or pause criteria must be defined for the pilot to protect your operations and customers? Options: Error rate threshold, Customer complaint threshold, Financial loss threshold, Security incident, None required
      • Who in legal/procurement/compliance should pre-review draft SOWs to avoid late surprises?

      Pilot Scope: Small Enough to Win, Big Enough to Prove

      • What minimum claim volume and composition (e.g., low-severity photo claims vs. complex desk-reviews) do you believe are required to demonstrate statistical validity? Options: <500 claims, 500–2,000 claims, 2,000–10,000 claims, >10,000 claims
      • Which lines, geographies, or repair types should we include or explicitly exclude from the first pilot? Options: Personal auto (comp/PD), Commercial auto, Glass-only, Total loss, High-value fleet, Specific regions/states to exclude
      • What acceptance criteria do you require at pilot close (accuracy thresholds, supplement rate cap, cycle time target, user satisfaction)? Options: Estimate accuracy threshold (%), Supplement rate target (%), Cycle time reduction target (days), Adjuster/shop satisfaction score, Other
      • Who will be responsible for daily pilot operations, and who signs the formal pilot completion approval?
      • What timeline (weeks/months) and sample size would you consider sufficient for a credible go/no-go decision? Options: 4–6 weeks, 6–12 weeks, 3–6 months, 6+ months

      Next Steps and How We'll Keep Momentum

      • If leadership said yes today, what is the earliest realistic start date for technical onboarding and data sharing? Options: Immediately (within 2 weeks), Within 1 month, 1–2 months, 2–3 months, 3+ months
      • What specific internal approvals must we help you prepare (security sign-off, data-sharing agreement, budget request)? Options: Security sign-off, Data-sharing agreement, Budget approval, Procurement contract, Legal review
      • What materials would make internal approvals easier (pilot SOW template, ROI model with your baselines, technical integration checklist)? Options: Pilot SOW template, Custom ROI model, Integration checklist, Legal/compliance FAQ, Executive one-pager
      • Who should attend the next working session from your side, and what should they bring (data extracts, system access, decision authority)? Options: Claims operations lead, IT/integration lead, Security/compliance, Procurement/legal, Body shop operations contact
      • Are there any unstated concerns or political dynamics we should anticipate so we can address them proactively?
    2. Current State Mapping

      Document existing FNOL-to-settlement workflows, system integrations, adjuster load, supplement patterns, and body-shop touchpoints.

      Current State

      Start: How Claims Usually Begin (Quick, real-world snapshot)

      • Walk me through the very first hour after FNOL on a recent claim that went well—what happened, who touched it, and how did it move?
      • Which channels do customers use to report FNOL most often? Options: Mobile app / photos, Web portal, Call center, Agent/Broker, Third-party shop intake, Other
      • How many first-notice claims does your team typically handle on an average business day? Options: Under 100, 100–500, 500–1,000, 1,000–5,000, 5,000+
      • How are photos and VIN data collected today (select all that apply)? Options: Customer-submitted photos via app, Adjuster-taken photos, Shop-provided photos, OEM/vehicle data feed, No systematic photo/VIN capture, Other
      • Tell us about one recent FNOL that surprised you—what made it stand out?

      Where Bottlenecks Hide (Which step quietly eats your time and margin?)

      • Which single step in your FNOL→settlement flow costs you the most time or money right now, and why do you think it's being tolerated?
      • What is your median end-to-end cycle time today for non-total-loss, repairable claims (FNOL → payment/repair start)? Options: <24 hours, 1–3 days, 4–7 days, 8–14 days, 15+ days
      • Where do claims most often stall—triage, appraisal, parts, shop scheduling, rental, or payment? Options: Triage / assignment, Appraisal/estimate, Parts sourcing, Shop scheduling, Supplements/rescoping, Payment/settlement
      • How often do you have a claims backlog or surge that requires overtime, temp adjusters, or vendor appraisers? Options: Daily, Weekly, Monthly, Quarterly, Rarely/Never
      • Describe a recent bottleneck in enough detail that we could replicate the root cause—what systems, people, and data were involved?

      Who's Doing the Heavy Lifting? (Are your adjusters set up to scale?)

      • Are your adjusters primarily field, desk, or a mix—and which group is currently most over-capacity? Options: Mostly field, Mostly desk, Balanced mix, Rely on vendor/contract adjusters, Other
      • On average, how many closed estimate-capable claims does an adjuster close per day? Options: <5, 5–10, 11–20, 21–35, 35+
      • Which tasks consume the bulk of adjuster time today (pick top three)? Options: Photos review, Estimate writing, Phone calls & coordination, Supplements handling, Data entry into CMS, Shop liaising, Other
      • How do adjusters feel about automated estimates—skeptical, cautiously optimistic, or eager? Any recent reactions or quotes? Options: Skeptical, Cautiously optimistic, Eager, Divided / mixed
      • What training or QA processes support adjuster estimation accuracy today (mentoring, calibration sessions, spot audits)?

      Systems and Integration Reality (If the tech layer falters, what breaks first?)

      • If your core claims system became unavailable for 24 hours, which downstream capability would you lose first and why?
      • Which systems currently integrate with claims workflows (select all that apply)? Options: Core Claims Management System (CMS), Body Shop Management System (BMS), Parts catalogs / vendor pricing, Rental / mobility platform, Payment processor, Telematics/EV data, Third-party estimate engines, None/Manual integrations, Other
      • What is the nature of those integrations—real-time APIs, nightly batches, manual CSVs, or spreadsheet handoffs? Options: Real-time APIs, Near-real-time webhooks, Nightly batch files, Manual CSV imports/exports, Screen-scrape/manual entry, Other
      • Do we have read/write access to claims records, images, and notes for a pilot? If not, what approvals or contracts stand in the way?
      • What data fields or feeds are most fragile or incomplete today (parts list, labor times, VIN decode, prior loss history)? Options: Parts pricing, Labor times, VIN / vehicle spec, Prior claims history, Photo metadata, Shop repair timelines, None / data is robust, Other

      Body Shops and Repair Partners: What's Their Truth?

      • Do your repair partners see your processes as helpful, neutral, or obstructive—and what is the most common shop complaint? Options: Helpful, Neutral, Obstructive, Varies by shop network
      • What percentage of repairs are handled by your preferred network versus arbitrary local shops? Options: 0–25%, 26–50%, 51–75%, 76–90%, 91–100%
      • Which shop workflows are most error-prone: estimate acceptance, scheduling, parts ordering, supplement submission, or final invoicing? Options: Estimate acceptance, Scheduling, Parts ordering, Supplement submission, Final invoicing, All of the above
      • Do your shops use a BMS—and if so, which vendor(s)? Are they connected to your CMS or are handoffs manual?
      • Share a concrete example of a shop-related delay that impacted cycle time or cost—what happened and how was it resolved?

      Supplements, Surprises and Escalations (Why do estimates get reopened?)

      • When a supplement occurs, what do you blame most: initial estimate error, unseen damage at repair, or shop behavior? Options: Initial estimate error, Hidden damage discovered at repair, Shop upcoding / overbilling, Parts availability delays, Policyholder behavior / late disclosures, Other
      • What proportion of repairable claims generate at least one supplement? Options: <5%, 5–10%, 11–20%, 21–35%, 36%+
      • Average additional days caused by supplements (from repair start to completion)? Options: <1 day, 1–3 days, 4–7 days, 8–14 days, 15+ days
      • Which types of damage or vehicle classes drive the highest supplement rates (e.g., EVs, heavy trucks, late-model cars, structural damage)? Options: EVs / high-voltage, Light commercial / fleet, Late-model collision vehicles, Structural / frame damage, Cosmetic-only, Other
      • Describe a memorable supplement dispute—how did it start, who escalated it, and what was the outcome?

      Data Quality: If the Input Is Flawed, the Output Lies

      • What percentage of claim photo sets would you classify as high-quality (clear angles, good lighting, required views present)? Options: <30%, 30–50%, 51–70%, 71–90%, 91–100%
      • Do you provide photo guidance or templates to customers or shops today? If so, what channels and adoption rates? Options: Yes—app guidance (high adoption), Yes—app guidance (low adoption), Yes—call center guidance, Yes—shop guidance, No formal guidance, Other
      • Which data elements are consistently missing or inaccurate that would impede automated estimating (VIN, mileage, prior damage, options package)? Options: VIN, Mileage, Prior damage history, Vehicle options / trim, Repair history, None—data is reliable, Other
      • Do you have labeled historical data (photos mapped to true repairs/invoice) available to share for model validation or training? Options: Yes—extensive, Yes—limited samples, No, but can collect, No and cannot share
      • How do you currently verify estimate accuracy—post-repair audits, desk reviews, shop invoices comparison, or another method? Options: Post-repair audits, Desk reviews, Invoice reconciliation, Third-party audits, No systematic verification, Other

      Regulatory, Audit, and Risk Appetite (Could a regulator pause this?)

      • Are there regulatory or state-specific restrictions that constrain virtual/photo-only appraisals in your book of business? Options: Yes—multiple states, Yes—a few states, No known restrictions, Unsure / need legal to confirm
      • What audit trail and reporting requirements would a new estimation tool need to satisfy for your compliance and audit teams?
      • What is your acceptable overpayment tolerance on pilot claims (e.g., $ per claim or % of claims)? Options: Zero tolerance, <$50 per claim, $50–$200, $200–$500, We evaluate on % basis
      • Have you had regulatory inquiries or litigation related to photo-based claims in the last 3 years? If yes, summarize. Options: Yes—detailed history, Yes—minor inquiries, No, Prefer not to say
      • How important is a fully auditable decision log (images, model scores, adjuster overrides) for rollout approval? Options: Critical, Important, Nice-to-have, Not necessary

      What Success Actually Looks Like (Numbers, leadership expectations, and blind spots)

      • If we returned to your executive team in 6 months, which three KPIs would convince them this project is successful? Options: Cycle time reduction, LAE / reserve reduction, Supplement rate reduction, Customer NPS / satisfaction, Shop acceptance rate, Straight-through processing rate, Other
      • What target reduction in cycle time or LAE would be considered a win for a pilot (give percentage or absolute numbers)?
      • What accuracy threshold for AI estimates would you require to let them be used for straight-through payment on low-complexity claims? Options: >95% parity with human, 90–95% parity, 85–90% parity, Lower if accompanied by controls
      • Who must sign-off to move from pilot to production (roles, not names)?
      • What hidden political or operational risks could sink a pilot even if the numbers look good?

      A Tiny, Low-Risk First Step (What would make leadership comfortable to try this?)

      • What would a low-friction pilot look like to you—volume, vehicle classes included, geographies, and timeline?
      • Which sample size feels reasonable for a pilot to be statistically meaningful but operationally contained? Options: 50–100 claims, 100–500 claims, 500–1,000 claims, 1,000+ claims
      • What data and system access would you be comfortable granting for a 90-day pilot (images, writeback rights, only read access)? Options: Read-only to claims & images, Read + write to estimate field (controlled), Read + write + BMS push, Limited sample via CSV exports, Other
      • Who on your side would we need in the room weekly during a pilot (roles and their primary decision/approvals)?
      • What would be an acceptable go / no-go decision gate at pilot end (single KPI or composite), and what thresholds matter?
  2. Outcome Discovery

    Define target reductions in cycle time and LAE, acceptable accuracy thresholds, pilot scope, and regulatory constraints.

    Discovery Questions

    Quick Snapshot — One‑Minute Baseline

    • Who are you and which claims domain do you own or represent? Options: VP of Claims, Head of Auto Physical Damage, CIO/CTO, Claims Transformation Lead, Product/Innovation, Other — please specify
    • Roughly how many vehicle damage claims does your organization handle annually? Options: <10k, 10k–50k, 50k–200k, 200k–500k, >500k
    • What is your current average end‑to‑end FNOL→settlement cycle time (desk review or photo-first claims)? Options: <24 hours, 1–3 days, 4–7 days, 1–2 weeks, >2 weeks, Don't know / need help measuring
    • Please provide your current baseline metrics (LAE per claim, supplement rate, current estimator accuracy vs. human) — list numbers or sources.
    • Which claims types do you prioritize for straight‑through or photo‑first workflows today? Options: Personal auto - low severity, Personal auto - moderate severity, Commercial fleet, Rental/short‑term vehicles, Glass only, Total loss, We don't currently prioritize by type

    Are We Being Too Modest About Targets?

    • When you hear vendors promise 20–40% faster cycle times or 10–25% LAE reduction, what’s your immediate reaction? Options: Skeptical — needs proof, Optimistic — plausible, Depends on claim mix, Unconvinced by vendor metrics
    • What reduction in cycle time would meaningfully change business outcomes for you (pick the best fit)? Options: <10%, 10–20%, 20–35%, 35–50%, >50%
    • What percent reduction in LAE (loss adjustment expense) would justify a technology-led pilot in your view? Options: <5%, 5–10%, 10–20%, 20–30%, >30%
    • What minimum estimation accuracy vs. your experienced adjusters would you require to run a production‑level straight‑through workflow (choose one)? Options: Parity (±1%), Within 3% of human, Within 5% of human, Within 10% of human, We need other signals besides accuracy
    • How tolerant are you of occasional overpayments from AI estimates if overall cycle time and customer satisfaction improve? Options: Very tolerant (net wins matter), Somewhat tolerant with guardrails, Low tolerance — cannot accept overpayment, Only acceptable with cost sharing
    • Describe any recent internal targets or board expectations tied to claims efficiency or LAE savings.

    What Would Winning Feel Like for Your Team?

    • Imagine it's 12 months after a successful pilot — what would you see that tells you this was worth doing?
    • Which stakeholder outcomes matter most when you think of 'winning' (select up to three)? Options: Lower LAE, Faster settlements, Higher customer satisfaction (NPS), Lower supplement rate, Reduced adjuster workload, Improved shop relationships, Regulatory compliance
    • How important is adjuster experience (reduced cognitive load, time per file) compared to hard dollar savings? Options: More important, Equally important, Less important, Unsure
    • What would an acceptable lift in CSAT or NPS look like for this program to count as a success? Options: +1–2 points, +3–4 points, +5–7 points, +8+ points, Don't measure by NPS
    • Which internal audiences must feel wins early for broader adoption (and why)? Options: Claims leadership, Adjuster teams, CIO/IT, Compliance/Legal, Finance, Network shops, Board/Executives

    What's Standing Between Us and That Outcome?

    • Which barrier worries you most about deploying photo-based AI estimation at scale? Options: Accuracy vs. humans, Integration complexity, Shop acceptance, Regulatory risk, Data quality, Change management
    • Tell the story of the last time a claims automation project hit a wall — what went wrong and how did it feel?
    • How would you rate the current quality and completeness of the photo submission experience from customers and repair partners? Options: Excellent — high quality, Good — usable with caveats, Variable — many failures, Poor — often unusable, Don't know / not measured
    • Which integrations do you anticipate being the hardest (select all that apply)? Options: Core claims system (CMS/TMS), Body Shop Management Systems (BMS), Parts pricing / catalogs, Rental and payment systems, Telematics / OEM data, None — integrations straightforward
    • How much internal capacity and executive patience do you have for iterative pilot cycles (weeks/months of tuning, re‑measuring)? Options: High — ready for multiple iterations, Moderate — 1–2 iterations, Low — need quick proof or stop, Unsure

    Pilot Reality Check — What Would Convince You?

    • What single data point or experiment result would cause you to greenlight production rollout?
    • For a pilot, which claim scopes are highest priority to test first? Options: Low severity personal auto, Moderate severity personal auto, Commercial fleet low/moderate, Glass & minor body, Rental & total loss separately
    • What pilot size would feel statistically persuasive to you (select one)? Options: N=100–250 claims, N=250–1,000, N=1,000–5,000, N>5,000, Prefer timeboxed duration over count
    • Which success metrics must the pilot meet to be considered a win (choose up to three)? Options: Estimation accuracy target, Supplement rate reduction, Cycle time reduction, Customer satisfaction, Adjuster effort reduction, Shop acceptance rate
    • What acceptance thresholds would you set for estimation accuracy, supplement rate, and cycle time to pass the pilot? Please specify numbers or ranges.
    • Who needs to sign the pilot off internally (list roles), and who will be the day‑to‑day owners?

    Regulators, Audit Trails and the Red Lines

    • If a regulator reviewed your photo‑first playbook, what would they ask for first? Options: Audit logs & explainability, Consumer consent flows, State‑specific exclusions, Human override rules, Data retention & security
    • Are there states, lines, or claim types where photo-only handling is forbidden or heavily restricted in your book of business? Options: Yes — list below, No, Unsure — need legal input
    • What documentation, explainability or human‑review controls does your compliance team expect for AI‑based estimates? Options: Full audit trail, Model explainability summary, Human review on threshold fails, Versioning & testing logs, All of the above
    • How would you like regulatory risk to be managed between carrier and vendor (options)? Options: Carrier retains all risk, Shared risk / limited vendor indemnity, Vendor takes primary risk for estimate accuracy, Undecided — need to discuss
    • Have you had any regulatory findings or fines related to claims automation in the past 3 years? Options: Yes — please summarize, No, Unsure

    Data & Integration Truths — The Unvarnished Picture

    • List the core systems we would need to connect to for a pilot (CMS, BMS examples) and any known integration blockers.
    • What is the typical latency and availability of the data feeds needed (claims images, policy data, parts pricing)? Options: Real‑time / API, Near real‑time (minutes), Batch daily, Batch weekly, Ad hoc / manual
    • How complete are your historical labeled datasets (photos + settled estimate) for model validation? Options: Extensive — thousands of labeled claims, Moderate — hundreds, Sparse — tens, None
    • Are there privacy, vendor access, or firewall requirements that typically add weeks to integration work? Options: Yes — strict (we'll share requirements), Some — standard process, No — few constraints, Unsure
    • What team will own data verification and labeling during the pilot (roles & FTE estimate)?

    Decision Rules, Governance & Commercial Boundaries

    • What is your preferred commercial model for pilots and production (select all that apply)? Options: Subscription / SaaS, Per‑claim pricing, Risk‑share on savings, Hybrid (setup + per‑claim), Other — specify
    • Which governance cadence would give you confidence in an iterative pilot (choose one)? Options: Weekly scorecard & tuning, Biweekly governance, Monthly steering committee, Ad‑hoc as needed
    • What decision gate criteria would trigger a stop, pause, or go‑to‑production decision? Options: Failing accuracy threshold, Rising supplement rate, Negative customer feedback, Integration instability, Budget exceedance
    • How quickly do you expect contractual and commercial terms to be agreed once a pilot proves successful? Options: <30 days, 30–60 days, 60–90 days, >90 days, Depends on procurement
    • What financial guardrails do you require (e.g., caps on overpayments, refund/credit mechanics, SLA credits)?

    Emotions, Resistance, and the Hidden Opponents

    • Who inside the organization is most likely to resist photo‑first automation and why? Options: Adjusters, Shop networks, Field appraisers, Compliance/legal, Procurement, Other — specify
    • How do adjusters tend to feel about automation pilots — curiosity, threat, indifference, or something else? Options: Curious / excited, Wary / threatened, Indifferent, Depends on role
    • What communication or change levers have worked best in your org to convert skeptics into adopters? Options: Hands‑on training, Shadowing & side‑by‑side validation, Incentives / compensation alignment, Clear governance & escalation, None have worked well
    • Have you had any cultural or political blockers in past automation projects (briefly describe)?
    • What would help you sleep better at night about people risk during the pilot? Options: Clear fallback to humans, Compensation protections, Transparent performance dashboards, Formal change management plan, Other

    Next Steps — Practical Commitments to Move Forward

    • If we could draft a minimally viable pilot plan right now, which of these start dates would be realistic for your team? Options: Within 2 weeks, 2–6 weeks, 6–12 weeks, >12 weeks, Need procurement/approval first
    • Which immediate resources can you commit to a pilot (select all that apply)? Options: Technical integration lead, Claims SME / adjuster time, Data engineering, Shop operations contact, Compliance review time, None currently available
    • What would be a reasonable first milestone we should aim for (choose one)? Options: Data readiness & connectivity, First 100 validated estimates, Initial accuracy report, Shop acceptance test, Executive review
    • Who should be the single point of contact (name & role) for day‑to‑day coordination if we proceed?
    • What outstanding concerns or questions must be resolved before you can greenlight a pilot?
  3. Solution Experience

    Walk through how the platform delivers agreed outcomes using the customer’s claims scenarios, focusing on estimation accuracy, integrations, and shop workflows.

    Experience Meetings

    • Solution Experience Kickoff — Current State & Consequence Confirmation
    • Claims Scenario Walkthrough — Proof of Estimation Accuracy
    • Integrations & Data Flow Workshop — Proving Operational Continuity
    • Shop Workflow Simulation & Body-Shop Acceptance
    • Validation & Pilot Success Criteria Alignment — Decision and Next Steps
    • Capture required shop onboarding and training items to ensure high initial acceptance.
    • One‑Sentence Integration Future State
    • Confirm the minimal data model and API interactions required to prove a closed-loop claim flow in the pilot.
    • Demonstrate a successful sample ingest/writeback using customer payloads to prove elimination of manual rekey.
    • Agree on SLAs, error-handling expectations, and integration responsibilities for pilot execution.
    • Customer to provide sandbox API credentials or a test payload schema and a dedicated integration contact.
    • Seller to produce an integration checklist with field mappings and test cases for sign-off.
    • Schedule an engineering pairing session to complete end-to-end test within agreed timeline.
    • Current Shop Process One-Sentence & Pain Points
    • Validate that the platform's shop workflows and BMS integrations meet pilot shop operational needs.
    • Agree measurable shop-level success signals to include in pilot acceptance criteria.
    • Introductions & Meeting Objectives
    • Customer to provide contacts and test credentials for 3 pilot shops and BMS vendors.
    • Seller to deliver a shop-training checklist and a 30-minute shop onboarding script.
    • Agree on shop KPIs for pilot (e.g., >80% acceptance within 24 hrs) and document them in the pilot charter.
    • Synthesis of Proof Findings
    • Obtain mutual agreement on pilot scope, sample size, duration, and measurable success criteria.
    • Secure commitments for required access, resourcing, and governance cadence to run the pilot.
    • Create a clear go/no-go decision process with owners and timelines.
    • Both parties to sign the pilot charter documenting scope, KPIs, and decision gates within 5 business days.
    • Seller to deliver a pilot project plan with milestones, owners, and required deliverables for the first 30 days.
    • Customer to allocate a single pilot owner and provide dedicated integration and shop operations points-of-contact.
    • A single agreed one-sentence current state describing where the process breaks and who is impacted.
    • A quantified consequence statement showing cost/time/risk of the current state.
    • A single agreed one-sentence future-state outcome the experience will prove.
    • A prioritized list of 3–5 customer claim scenarios to use for live proof.
    • Customer to deliver 10 representative claims (photos, adjuster estimates, final settlements) and 90‑day KPI baseline within 3 business days.
    • Seller to prepare one-page consequence calculation using provided KPIs and return within 48 hours.
    • Schedule the live scenario walkthrough and ensure sandbox and access are provisioned.
    • Recap Agreed Problem & Future State
    • Prove the platform produces estimates within the agreed accuracy thresholds on representative scenarios.
    • Identify and classify the root causes for any estimate variance and decide remediation (model tuning, rules, or process change).
    • Obtain SME validation or specific objections that must be addressed prior to pilot sign-off.
    • Seller to deliver side-by-side estimate comparisons and a variance report for all walked scenarios within 48 hours.
    • Customer to tag and return 20 additional claims of each failure-mode type to be used for model tuning and rules creation.
    • Agree numeric acceptance thresholds (e.g., average cost delta %, supplement rate ceiling) and record them for pilot criteria.
    • Facilitated One‑Sentence Current State
    • Finalize Pilot Scope, Duration & Sample Size
    • Live Simulation: Dispatch & Scheduling
    • Integration Topology Review
    • Live Estimate: Simple Repair Scenario(s)
    • Live Payload Simulation
    • Live Simulation: Supplement Discovery & Approval
    • Set Explicit Success Metrics & Decision Gates
    • Live Estimate: Complex / Edge Scenario(s)
    • Consequence Quantification
    • Governance, Reporting & Roles
    • Define Future State (One Sentence)
    • Error, Exception & SLA Handling
    • Discrepancy Analysis & Root Cause Mapping
    • Shop Acceptance Criteria & Training Needs
    • Validation & Agreement
    • Select & Prioritize Customer Scenarios for Proof
    • Capture Operational Changes & Communications Plan
    • Integration Rollout Plan & Responsibilities
    • Next Steps and Commitments
    • Pre-work & Logistics for Live Experience
  4. Solution Scope

    Define modules, integrations, data requirements, acceptance criteria (e.g., accuracy, supplement rate), and responsibilities for pilot and production.

    Scope Configuration

    • Automated Photo Damage Estimation
    • Triage and Severity Scoring
    • Total Loss Valuation (real-time market pricing)
    • Line-item Parts Identification and Labor Pricing
    • Alternative Parts Recommendation Engine
    • Supplement Identification and Lifecycle Tracking
    • Virtual Appraisal via Adjuster Portal
    • Mobile Photo Capture SDK with Guidance
    • Body Shop Management System Integration
    • Claims Management System Integration
    • Parts Sourcing and Procurement Fulfillment
    • Fraud and Anomaly Detection for Photo Claims
    • Adjuster Review Workspace with Editable Estimates
    • Repair Handoff Package for Repair Facilities

    Scope Questions

    Automated Photo Damage Estimation

    • Do you want automated photo-based damage estimation included in scope? Options: Yes, No, Undecided
    • What percent of inbound FNOL currently include claimant photos? Options: <25%, 25-50%, 51-75%, 76-100%, Unknown
    • What accuracy threshold vs. current human adjuster benchmarks do you require for automation to be acceptable (e.g., 90% parity)? Options: >95%, 90-95%, 85-89%, <85%, Need help defining
    • Which vehicle types must the estimator support initially? Options: Light passenger cars, Light commercial/LDV, Trucks/Heavy vehicles, Motorcycles, All of the above
    • What fallback workflow should trigger when automated estimate confidence is low (e.g., desk review, virtual appraisal, onsite inspection)? Options: Desk review by adjuster, Virtual appraisal via portal, Field/onsite inspection, Immediate manual routing to shop, Other
    • Are there regulatory or audit acceptance requirements for photo-based estimates we should design to meet (e.g., documented photo retention, timestamping)? Options: Yes - we will provide details, No, Unknown

    Triage and Severity Scoring

    • Do you want automated triage to route claims into straight-through, desk review, or field inspection cohorts? Options: Yes, No, Partial/only certain lines
    • What triage categories or severity bands do you currently use or want to use? Options: STP (straight-through), Low complexity desk review, High complexity desk review, Field inspection required, Total loss candidate
    • What business rules or thresholds should influence triage decisions (e.g., repair cost estimate, presence of injuries, reserve amount)?
    • What acceptable false-positive rate (claims escalated unnecessarily) can you tolerate for triage? Options: <1%, 1-3%, 3-5%, >5%, Need guidance
    • Which systems must be notified or updated when triage outcome is determined? Options: P&C Claims system (CMS), Triage dashboard, Adjuster inbox, Field inspection scheduler, Other
    • Who owns tuning triage models and updating severity rules post-deployment? Options: Carrier (claims ops), Carrier (data/ML team), Vendor (ongoing service), Shared responsibility

    Total Loss Valuation (real-time market pricing)

    • Do you want real-time market pricing integrated for total loss valuations? Options: Yes, No, Pilot only
    • Which valuation inputs are required by your teams/regulators (e.g., VIN, mileage, condition factors, market comps)?
    • Do you require support for salvage valuation and salvage disposition workflows? Options: Yes, No, Maybe - depends on line
    • What tolerance bands or acceptance criteria should be used for market-based valuations (e.g., within +/- X% of accepted comps)? Options: +/-2%, +/-5%, +/-10%, Flexible/varies by case
    • Which external data sources or partners must be used or are preferred for market pricing (e.g., VIN desks, auction feeds)? Options: Provider will recommend, Carrier provided feeds, Preferred vendors (list), No external feeds
    • Who should sign off on initial total loss rules and appeals (e.g., claims VP, salvage manager)? Options: Claims VP, Salvage Manager, Regional Adjuster Lead, Shared governance

    Line-item Parts Identification and Labor Pricing

    • Do you require automated line-item parts identification and standardized labor pricing? Options: Yes - critical, Yes - optional, No
    • Which parts catalogs or labor guides do you use/require (e.g., OEM parts catalog, Mitchell, Audatex, CCC)? Options: Mitchell/CCC/Audatex, OEM parts lists, Carrier-specific catalog, Other/Custom
    • Do you need differential pricing by region, shop network tier, or contract rates? Options: Yes - region, Yes - shop tier, No - uniform pricing, Other
    • What acceptance criteria for part-match accuracy and labor-time accuracy do you require for go/no-go? Options: >95% match, 90-95% match, 85-90% match, Need vendor recommendation
    • Are parts substitution rules (e.g., aftermarket vs OEM, remanufactured) governed by policy and should be enforced? Options: Yes - enforce, Yes - suggest only, No - allow shop choice
    • Who will maintain mapping between platform SKUs and your preferred parts/labor schedules? Options: Vendor, Carrier parts/pricing team, Shared maintenance, Third-party integrator

    Alternative Parts Recommendation Engine

    • Should the engine recommend alternative parts (aftermarket, reman, used) vs OEM automatically? Options: Yes - automatic, Yes - suggest only, No - OEM only
    • What substitution rules/policies must be enforced (e.g., safety-critical parts must be OEM)? Options: Enforce strict rules, Guidance only, No restrictions
    • Do you require ROI/cost-savings reporting on alternative parts usage? Options: Yes, No, Maybe - pilot
    • Which suppliers or parts channels must be included for sourcing alternatives? Options: Carrier's approved suppliers, Vendor marketplace, Open market, Other
    • Should shops be able to accept or override recommended alternative parts within the platform? Options: Allow overrides with justification, No overrides, Allow only for certain shops
    • Do you require provenance and warranty metadata for recommended alternative parts? Options: Yes - mandatory, Optional, No

    Supplement Identification and Lifecycle Tracking

    • Do you want automated supplement identification from photos and shop inputs? Options: Yes, No, Partial
    • Which supplement lifecycle stages must be tracked (identification, approval, parts order, repair update, settlement)? Options: All stages, Identification + approval, Identification only, Custom stages
    • What approval workflows and SLAs apply to supplements? Options: Auto-approve under threshold, Manual approval required, Hybrid rules by dollar amount
    • What metrics should be captured for supplements (e.g., supplement rate, time-to-approval, cost impact)? Options: Supplement rate, Avg approval time, Avg supplement value, All of the above
    • Should the platform push supplement notifications into your CMS or email/workflow tools? Options: Yes - CMS integration, Yes - email only, No push required
    • Who is responsible for supplement adjudication during pilot and production (vendor vs carrier adjusters)? Options: Carrier adjusters, Vendor-assisted adjudication, Shared model

    Virtual Appraisal via Adjuster Portal

    • Do you require a web-based adjuster portal for virtual appraisal and collaboration? Options: Yes - mandatory, Yes - pilot, No
    • What user roles and permissions should the portal support (e.g., desk adjuster, supervisor, appraisal manager)?
    • Which features are required in the portal: editable estimates, photo annotation, chat, video conferencing, audit trail? Options: Editable estimates, Photo annotation, Chat, Video conferencing, Audit trail, All
    • Do you need integration of portal actions back into your CMS with specific field mappings? Options: Yes - bi-directional, Yes - one-way to CMS, No integration required
    • What performance or SLA expectations exist for adjuster response times in virtual appraisal? Options: Same day, Within 4 hours, Within 24 hours, Custom SLA
    • Will adjuster training or change management be required prior to portal go-live? Options: Yes - mandatory, Optional, No

    Mobile Photo Capture SDK with Guidance

    • Do you plan to embed a mobile SDK in your apps/portals to guide claimants or shops when capturing photos? Options: Yes - claimant app, Yes - shop app, Both, No
    • What capture guidance features are required (e.g., framing overlays, lighting checks, step-by-step workflow, VIN capture)? Options: Framing overlays, Lighting/quality checks, Step-by-step capture, VIN/odometer capture, All of the above
    • Which mobile platforms must be supported initially (iOS, Android, web)? Options: iOS, Android, Web (mobile browser), All
    • Do you require secure photo transmission, PII redaction, or encrypted storage per compliance requirements? Options: Yes - encryption & PII controls, Yes - encryption only, No special requirements
    • Are there branding or UX requirements that the SDK must conform to? Options: Yes - provide guidelines, Minor customization, No
    • What performance metrics will determine SDK acceptance (e.g., % usable photos, capture completion rate)?

    Body Shop Management System Integration

    • Which Body Shop Management Systems (BMS) must be integrated for dispatching and repair updates? Options: Mitchell/CCC integrations, Vendor-specific BMS list, Carrier-managed shop network, Other
    • What integration patterns are required (real-time API, batch CSV, EDI, webhooks)? Options: Real-time API, Webhooks, Batch CSV, EDI, Other
    • What data elements must flow to/from the BMS (e.g., estimates, repair status, parts orders, RO numbers)?
    • Do shops need the ability to edit estimates, accept assignments, or submit supplements via the integration? Options: Yes - full edit, Yes - accept/acknowledge only, No - read-only
    • Are there existing EDI or contractor gateways we must use or replace? Options: Use existing gateways, Replace with new integrations, Unknown - need assessment
    • Who will own troubleshooting and escalation for BMS integration issues? Options: Carrier IT, Vendor support, Third-party integrator, Shared

    Claims Management System Integration

    • Which Claims Management System(s) must be integrated (vendor and version)?
    • What integration scope is required: create/update claim, push notes/attachments, update reserves, close claim? Options: Full CRUD (create/read/update/delete), Create + updates only, Read-only for enrichment, Custom
    • What authentication and security models does your CMS require for API integrations (e.g., OAuth2, mutual TLS, API keys)? Options: OAuth2, mTLS, API Key, SAML/JWT, Other
    • Is real-time sync required or is a scheduled batch acceptable for your workflows? Options: Real-time, Near real-time (webhooks), Scheduled batch
    • Are there field mapping or data governance constraints (PII handling, field length limits) we should know about? Options: Yes - will provide mapping, No special constraints, Unknown
    • Who is the primary owner for CMS integration sign-off and testing on the carrier side? Options: Claims IT, Integration/ESB team, Claims Ops, Vendor/PM
  5. Mutual Commit

    Finalize commercial terms, SLAs, pilot success metrics, decision gates, and governance cadence.

    Agreement Modules

    • Statement of Work (SOW)
    • Order Form & Commercial Terms
    • Service Level Agreement (SLA)
    • Pilot Success & Acceptance Criteria
    • Governance & Decision Gates
    • Data Processing Agreement (DPA) & Privacy
    • Security & Compliance Addendum
    • Integration & API Access Agreement
    • Implementation & Onboarding Plan
    • Change Order & Scope Management
    • IP License & Usage Rights
    • Termination, Exit & Data Return Plan
    • Insurance, Indemnity & Liability Schedule
    • Shop Adoption & Field Enablement Agreement
  6. Deployment

    Operationalize rollout with readiness checks, enablement, and outcome validation.

    1. Pre-Deployment Readiness

      Confirm data feeds, claims system access, shop/BMS integrations, test environments, and compliance controls are in place.

      Readiness Questions

      Quick Orientation: Who's In the Room?

      • Who will be our primary day-to-day deployment contacts from your team (name, role, email)?
      • Which executive or committee has final sign‑off authority for pilot go/no-go and production roll‑out? Options: VP of Claims, Head of Auto PD/Physical Damage, CIO, Claims Transformation Lead, Chief Risk Officer, Other
      • What is your target window for pilot start and for first production cutover? Options: Within 30 days, 30–60 days, 61–90 days, 3–6 months, 6+ months
      • What business outcomes will justify moving from pilot to production for you (select all that apply)? Options: Estimation accuracy delta vs adjuster (%), Reduction in average cycle time, Lower supplement rate, Lower LAE per claim, Shop/claimant NPS or acceptance, Reduced touchpoints per claim, Other
      • Are there non‑negotiable constraints or blackout dates we should plan around (e.g., blackout for seasonality, regulatory reporting windows)? Please list.

      If Deployment Fails, What's the Real Cost?

      • What single outcome would make you escalate the program immediately if it occurred during pilot? Options: Significant overpayment trend, Major integration outage, Regulatory complaint, Shop refusal to participate, Security breach, Other
      • Tell us about one past claims technology deployment that didn’t meet expectations—what went wrong and why?
      • How often have integrations with vendors or shops caused schedule slippage in previous projects? Options: Almost always, Often, Sometimes, Rarely, Never
      • What is the maximum tolerable outage or data loss window during deployment before leadership requires a stop? (hours/days) Options: <1 hour, 1–4 hours, 4–24 hours, 1–3 days, 3+ days
      • If the pilot delivered expected accuracy but shops pushed back, which consequence would hurt you most (operational cost, claimant satisfaction, reputational risk, regulatory exposure)? Options: Operational cost, Claimant satisfaction, Reputational risk, Regulatory exposure, Other

      Where Does Your Data Live—and Is It Ready?

      • How confident are you that your claims records, images, and VIN/parts data are production‑quality for automated estimation without major cleansing? Options: Very confident, Mostly confident with some gaps, Mixed quality across lines/regions, Significant cleansing required, Unknown
      • Which data feeds will we need to ingest for pilot (select all that apply)? Options: Claims Management System (CMS) records, Policy data, Policyholder images/photos, Shop/BMS updates, Parts/catalog data, Vehicle valuation feeds, Telematics/connected car data, Other
      • What formats and transport methods do those feeds use today (e.g., REST JSON, SOAP XML, SFTP CSV, flat files, Kafka)? Options: REST/JSON, SOAP/XML, SFTP/CSV, Secure FTP with certificate, Message bus (Kafka/RabbitMQ), Direct DB replica, Other
      • What is the expected daily volume of claims and images in the pilot scope, and how many sample claims can you provide for pre‑integration testing?
      • Are there common data quality issues we should expect (missing VIN, low‑res images, incorrect loss codes)? Please provide examples and frequency.
      • Do you have a canonical mapping for parts and labor codes that must be preserved, or will mapping be required? Options: Canonical mapping exists and is stable, Mapping required and maintained internally, Mapping required and will be co‑developed, Unknown

      Who Owns the Systems We'll Need to Touch?

      • Which internal teams or vendor partners are absolute gatekeepers for integrations and credentials (name teams/contacts)?
      • Which claims management systems and versions does your organization use in the pilot population? Options: Guidewire ClaimCenter, Duck Creek, Crawford, In‑house/Custom, Other
      • Which body shop management systems (BMS) and shop portals will we need to integrate with for the pilot?
      • What integration authentication methods are acceptable for your security team (select all that apply)? Options: OAuth2, Mutual TLS certificates, Static API keys, SFTP with keypair, VPN/IP allowlist, Other
      • Who will own change control and approvals for schema or endpoint changes during the pilot? Options: Carrier IT/Integration team, Vendor integration owner, Shared governance, Other
      • Are there third‑party middleware or ESBs that requests must route through (and do they add transformation rules we need to know)? Options: Yes — details will be provided, No

      Can You Imagine a Smooth Test Run? Tell Me About It.

      • What would a credible pilot test plan catch before go‑live that current plans might miss?
      • Which test environments are available and how closely do they mirror production? Options: Full staging mirror of prod, Partial staging (subset of data), Sandbox with synthetic data, No pre-prod environment available, Other
      • How many real claims (and images) should we run through the pilot to feel statistically comfortable with accuracy and supplement rate signals? Options: <100 claims, 100–500 claims, 500–1,000 claims, 1,000–5,000 claims, 5,000+
      • Which acceptance criteria will you apply at pilot closure (choose up to three and specify thresholds in the next question)? Options: Estimation accuracy vs adjuster (%), Supplement rate, Cycle time reduction, Shop acceptance rate, Claimant satisfaction/NPS, Integration uptime
      • Please specify the numeric thresholds for the acceptance criteria you selected (e.g., accuracy ≥ 90%, supplement rate ≤ 5%).
      • Who from claims operations and shops will participate in UAT and sign off on functional acceptance?

      What Keeps Your Security & Compliance Team Up at Night?

      • Which compliance or regulatory regimes must we satisfy for data handling and AI estimation in your jurisdiction(s)? Options: State insurance regulations, GDPR, CCPA/CPRA, HIPAA, SOC2/ISO27001 expectations, Other
      • Do you require evidence of third‑party certifications (SOC2 Type II, ISO27001) or penetration test results prior to production access? Options: Yes — SOC2 required, Yes — ISO27001 required, Pen test required, We will accept vendor attestation, No formal requirement
      • Are there data residency or localization constraints for images, PII, or valuation data? Options: Yes — must remain in specific country/region, No residency constraint, Some feeds constrained; details to follow
      • What are your encryption requirements for data at rest and in transit? Options: TLS 1.2+ in transit, AES‑256 at rest, TLS in transit, AES‑128 at rest, Only in transit required, Other / custom requirement
      • What is your breach notification SLA and escalation path we must accept contractually? Options: <24 hours, 24–48 hours, 48–72 hours, As soon as reasonably practicable
      • Are there mandatory privacy controls (PII redaction, consent logging, data retention windows) we must implement for the pilot?

      Plan B and Post‑Launch: Who's Ready to Act?

      • If week one of production shows an unacceptably high supplement rate, what immediate action would you expect us to take? Options: Pause automated settlement, Throttle to manual review, Rollback to previous process, Adjust model thresholds, Other
      • What monitoring and reporting would you like to see daily during pilot (select all that matter)? Options: Estimate accuracy by vehicle type, Supplement rate by shop, Time‑to‑estimate, Integration error rates, Shop acceptance/decline rate, Claimant satisfaction signals
      • What SLA do you require from us for response and resolution during the pilot? Options: 4 hours, 8 hours, 24 hours, 48 hours, Other
      • Who will run daily governance—triage calls, backlog prioritization, and incident reviews—during pilot operations? Options: Carrier governance owner, Vendor deployment manager, Joint governance, Other
      • What training and enablement do your adjusters and shops need before go‑live (e.g., role‑based sessions, quick reference guides, co‑pilot support)? Options: Live training sessions, On‑demand videos, Quick reference guides/Cheat sheets, Onsite shadowing, Ongoing office hours
      • Describe your rollback/runbook expectations—who initiates rollback, what triggers it, and how do we validate recovery?
    2. Deployment Enablement

      Schedule tasks, assign owners, coordinate integrations, and train adjusters and pilot shops for go-live.

    3. Pilot Validation

      Execute pilot, measure estimation accuracy, supplement rates, cycle times, and claimant/shop acceptance against acceptance criteria.

      Validation Checklist

      Getting Comfortable — a quick share

      • Which of the following best describes your primary role in the claims organization? Options: VP of Auto Claims, Head of Auto Physical Damage, CIO/CTO, Head of Claims Transformation/Innovation, Compliance/Legal, Other
      • Tell us briefly about the parts of your book you oversee (personal vs commercial, vehicle types, annual claim volumes, regions).
      • Approximately how many vehicle damage claims does your organization handle per year? Options: <10k, 10k–50k, 50k–200k, 200k–500k, >500k
      • Who normally attends vendor or pilot decision meetings at your company (select all that apply)? Options: VP Claims, Head PD/Auto, CIO/IT, Procurement, Compliance/Legal, Shop Network Lead, Finance, Other

      Are We Missing Millions in Plain Sight?

      • When was the last time your team tried to quantify leakage from estimates, supplements, cycle time or shop rework—and what surprised you most?
      • Which of these do you believe creates the largest hidden cost today? Options: Initial overpayment due to estimation inaccuracy, High supplement frequency, Excessive rental days / cycle time, Rework and shop disagreements, Incorrect total loss valuations, Other
      • Can you describe a recent claim where an estimate went materially wrong—what happened and what downstream impact did it cause?
      • If you had to pick one cost you can’t currently measure but suspect is large, what would you choose and why?
      • How does missing that visibility make you feel when you brief your leadership or Board? Options: Anxious about financial exposure, Frustrated at lack of progress, Confident we can solve it, Neutral / It’s expected, Other

      Show Me the Hard Numbers

      • If someone asked you to prove your estimation process is efficient, which three metrics would you hand them—and why might those still be misleading?
      • What is your current baseline for average estimation accuracy (estimate vs final paid) today? Options: >98%, 95–98%, 90–94%, 80–89%, <80%, We don’t measure this
      • What is your typical supplement rate (supplements per 100 repairable claims)? Options: <5, 5–10, 11–20, 21–40, >40, Unknown
      • What is your average cycle time from FNOL to settlement (days)? Options: <3 days, 3–7 days, 8–14 days, 15–30 days, >30 days, Varies widely
      • How confident are you in the integrity and completeness of the data that produces these metrics? Options: Very confident, Somewhat confident, Doubting key gaps, Data is poor/unreliable
      • How often do you reconcile estimates against final paid amounts and root-cause the differences? Options: Continuous / monthly, Quarterly, Annually, Rarely, Never

      Who’s Driving — and Who’s Nervous?

      • Which stakeholder in your org would be most likely to block photo-based straight-through processing—and what’s the core fear behind that stance?
      • Which stakeholders should be considered essential decision-makers for a pilot (pick up to three)? Options: VP Claims, Head PD/Auto, CIO/IT, Compliance/Legal, Finance/CFO, Shop Network Lead, Customer Experience/CS
      • How does compliance or internal audit typically evaluate new claims automation (biggest red lines)?
      • How do your partner body shops typically react to new digital workflows or remote estimates? Options: Quick adopters, Cautious but cooperative, Resistant without incentives, Split by shop size/chain, Unknown
      • Who would own day-to-day pilot success (name/role) and who controls the budget for scaling?

      When Tech Breaks Trust

      • Tell me about the last time a technology pilot eroded trust—what triggered the loss of confidence and how quickly did it spread?
      • Which potential failure modes keep you up at night with AI estimation? Options: Systematic overpayment, Missed safety-critical damage, Poor integration with claims system, Data security/privacy exposure, Shop/customer dissatisfaction, Regulatory non-compliance
      • How do you currently resolve disputes between shop repair estimates and carrier estimates? Options: Adjuster adjudication, Arbitration with shop, Re-inspection, Accept supplement, Other
      • What acceptance controls (audit sampling, human-in-loop thresholds, financial recourse) would you require before allowing STH on a segment of claims?
      • If a high-profile claimant complaint arose during a pilot, who would be pulled into the response and what outcomes would be unacceptable?

      What Would 10% Better Actually Feel Like?

      • If estimation accuracy improved by 10% and cycle time fell by 20%, what would be different in your daily operations, team morale, and P&L?
      • Which KPIs would you celebrate first as proof the solution is working? Options: Average cycle days, LAE per claim, Supplement rate, Customer satisfaction (CSAT/NPS), Straight-through processing rate, Shop turnaround time
      • What are realistic numeric targets you’d accept in a pilot for: estimation accuracy improvement, supplement reduction, and cycle time improvement?
      • What hard constraints (regulatory limits, SLAs, audit windows) would prevent you from acting on those gains immediately?
      • If the pilot met targets, which rollout path would you prefer? Options: Immediate enterprise-scale, Phased by region/product, Pilot-extension for more evidence, Limited feature rollout, Undecided

      Trial Without Theater — Designing a Pilot That Actually Proves Value

      • What would a pilot need to look like to survive executive scrutiny and a regulator audit—be specific about controls and artifacts?
      • Which claim segments would make the most defensible pilot (select all that apply)? Options: Simple repairable FNOL with photos, Glass-only claims, Commercial fleet small dents, High-frequency low-severity, Total loss candidates, Complex/third-party claims
      • What minimum sample size and duration would your leadership accept as credible evidence? Options: <500 claims / 1 month, 500–2,000 claims / 2–3 months, 2k–10k claims / 3–6 months, >10k claims / >6 months, Undecided
      • Which system integrations are non-negotiable for the pilot to be believable? Options: Core claims system (CDR/CMS), Body Shop Management System (BMS), Parts catalog / labor guide, Payment system, Rental booking, Telematics / OEM data
      • What concrete acceptance criteria (numeric thresholds, audit rules, escalation paths) would end the pilot as a success?
      • Who must sign the pilot off (name/role) and what governance cadence would you require during the pilot? Options: Weekly, Bi-weekly, Monthly, Ad-hoc as needed

      People, Training, and Shop Adoption

      • What would have to be true for your adjusters and partner shops to welcome — rather than resist — this change?
      • Which training formats produce the fastest and most durable behavior change for your adjusters? Options: Live instructor-led workshops, Hands-on shadowing, Micro e-learning modules, Scenario-based assessments, Job aids/cheat-sheets
      • How do you typically incentivize shops to adopt new workflows or systems? Options: Financial incentives, Preferred shop placement, Operational support/training, Service-level commitments, We don’t incentivize
      • Which adoption signals from shops and claimants would prove behavior change (pick top 3)? Options: % shops using tool, Reduction in shop disputes, Claimant NPS improvement, Decrease in rework/supplements, Faster repair lead times
      • What ramp timeline feels realistic for training and shop adoption to reach meaningful usage? Options: 2–4 weeks, 1–3 months, 3–6 months, 6–12 months, Longer/uncertain

      Data & Security — the Quiet Gatekeepers

      • If your data feeds were evaluated tomorrow for a pilot, what single gap would disqualify you?
      • Which of these data feeds can you realistically provide within 30 days? Options: Policy/claim metadata, Photos (policyholder / adjuster) with timestamps, Repair orders/ROs, Parts & labor detail, Payment history, Telematics/OEM data, None of the above
      • Are any of your feeds subject to special consent or regulatory restrictions we need to plan for? Options: Yes — requires explicit claimant consent, Yes — restricted by regulator, No special restrictions, Unsure
      • Which security or privacy certifications do you require for vendors? Options: SOC2 Type II, ISO27001, PCI-DSS, GDPR-compliance, State-level insurance/data controls, None required/undecided
      • What is your preferred approach to test environments and synthetic data during pilot validation? Options: Sandbox with anonymized production data, Fully synthetic dataset, Controlled redaction of live data, On-premise isolated environment, Other

      Deciding Together — Next Steps & Hidden Risks

      • What’s the single question your CFO or legal will ask after this conversation that we should answer first?
      • What remaining objections—internal or external—could realistically derail a pilot in the next 30 days?
      • Which artifacts would make the decision easy for you (pick all that apply)? Options: Tailored ROI model with carrier data, Detailed pilot plan and timeline, Security & compliance documentation, Integration technical spec, Customer references and case studies, Sample audit reports
      • Who should be included in the next meeting to clear those objections (name/role) and what is their availability in the next 2 weeks?
      • What would make you feel confident committing to a pilot within 30 days (concrete must-haves)?
  7. Success

    Confirm outcomes vs. success signals, capture learnings, and maintain a shared backlog for issues and enhancements.

    Success Reviews

    • Pilot Success Review & Validation
    • Lessons Learned & Retrospective
    • Shared Backlog Grooming & Prioritization
    • Executive Outcomes & ROI Review
    • Governance Rhythm & Continuous Improvement Cadence

    Issues & Enhancements

    • Confirm executive sponsor and formalize the steering committee membership.
    • Ensure each backlog item maps to a clear business consequence and expected benefit when resolved.
    • Define the release plan and SLAs for addressing high-severity items.
    • Create epics/tickets in the delivery tool for all prioritized items, including evidence and acceptance criteria.
    • Assign delivery owners and draft timelines for the next two sprint/releases.
    • Set up an automated dashboard feed for backlog health and SLA adherence.
    • Schedule targeted validation sessions for each major fix with sample claims and metric checks.
    • One-sentence Current State & Consequence
    • Secure executive-level decision to proceed with production rollout, extend pilot, or halt.
    • Obtain commitment for required funding, resources, and governance support.
    • Align on high-level rollout timeline, success metrics, and executive sponsor responsibilities.
    • Deliver a board-ready ROI and risk summary deck with recommended decision and ask.
    • Introductions & Objectives
    • Finalize commercial amendments or SLAs required for production contract.
    • Schedule the production kickoff date contingent on executive approval.
    • Proposed Governance Model & RACI
    • Establish clear governance, reporting, and escalation paths to sustain and improve outcomes.
    • Agree a repeatable continuous-improvement process tied to measurable KPIs and backlog management.
    • Lock in meeting cadence and owners so decisions and actions move forward without delay.
    • Publish governance RACI and distribute to all stakeholders.
    • Implement the production KPI dashboard with automated feeds and alerts.
    • Create the CI process documentation (SOP) and integrate it with the backlog tool.
    • Schedule recurring governance meetings and invite confirmed owners.
    • Determine whether the pilot met each agreed success signal and acceptance criterion.
    • Validate platform outputs against real claims samples and secure stakeholder confirmation.
    • Agree on clear next steps (remediate, extend pilot, or move to production) with owners and deadlines.
    • Publish final pilot results report with variance analysis and distribute to stakeholders.
    • Create remediation tickets for any failing acceptance criteria and assign owners with target dates.
    • Schedule a follow-up validation run (date and scope) if pilot extension is required.
    • Prepare executive summary for decision-makers (one-page ROI + risks) ahead of the executive review.
    • Purpose & Timeline Review
    • Create a prioritized list of root causes with clear corrective actions and owners.
    • Quantify the consequence of failures so remediation can be prioritized by business impact.
    • Agree a validation plan to confirm corrective actions resolve the underlying issues.
    • Publish a formal Lessons Learned document with root causes, actions, owners and target completion dates.
    • Update operational runbooks and adjuster/shop training materials to reflect agreed process changes.
    • Create measurement tests to validate fixes (sample claims, metric thresholds) and schedule validation sessions.
    • Log all lessons as backlog items with severity, expected ROI, and test acceptance criteria.
    • Backlog Intake & Triage Criteria
    • Produce a prioritized backlog with owners, effort estimates, and agreed acceptance criteria for top items.
    • Review New Items from Pilot
    • Recap of Agreed Success Signals
    • What Worked / What Didn't (Data-driven)
    • Pilot Outcome Summary vs Business Case
    • KPIs & Dashboard Cadence
    • Prioritization & Costing
    • CI Process: Backlog → Release → Validation
    • Pilot Metrics Presentation
    • Risk, Compliance & Shop Adoption Status
    • Consequence Assessment
    • Define Acceptance Criteria & Test Plans
    • Gap Analysis & Root-Cause Highlights
    • Escalation Paths & SLA Targets
    • Root Cause Analysis (5 Whys / Fishbone)
    • Scale Recommendation & Investment Ask
    • Release Planning & SLAs
    • Meeting Cadence & Action Owner Scheduling
    • Define Preventive & Corrective Actions
    • Decision Gates & Governance
    • Live Sample Validation (Diagnosis → Proof → Validation)
First-Party AI

1-2 minutes please — Your AI agent is working

First-Party AI™ can make mistakes. Always check important information.