Financial Services Insurance Underwriting & Pricing

Usage-Based Insurance

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

Verisk LexisNexis Mitchell Cambridge Mobile Telematics
Inside this journey
  1. Pre-Discovery

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

    1. Stakeholder Alignment

      Confirm decision roles (actuary, CUO, CIO, legal), timeline, and target success metrics like opt-in rate and loss ratio improvement.

      Alignment Questions

      Quick Warm‑Up: What Brought You Here Today?

      • What prompted you to start exploring telematics now—what incident or insight moved this from a 'nice to consider' to 'we need to act'?
      • Which of these best describes the primary sponsor or business case for this initiative? Options: Loss ratio improvement, Customer retention / churn reduction, New product / pay-per-mile, Market differentiation / competitive response, Regulatory compliance / reporting, Other
      • Who is formally sponsoring or funding the project today? (select all that apply) Options: Chief Actuary, Head of Personal Auto/Product, CUO, CIO / CTO, Head of Legal / Privacy, Head of Marketing / Growth, Other
      • Where would you place the program on an internal maturity scale today? Options: We are curious / exploratory, Proof of concept planned, Pilot approved and funded, Deployment ready (org & ops in place), We already have a partial program, Unsure
      • What timeline do you have in mind to launch a pilot (not full rollout)? Options: 0–3 months, 3–6 months, 6–12 months, 12+ months, No set timeline

      If You Waited a Year, Would You Regret It?

      • If a competitor rolled out a high-performing telematics product in the next 6–12 months, how would that change your market position or retention risk? Options: Significant risk of losing low‑risk drivers, Moderate competitive pressure, Little immediate impact, Would accelerate our plans but not critical, Unsure
      • How much of your loss ratio gap do you believe is addressable by behavior‑based pricing vs other levers (e.g., underwriting rules, rate changes)? Options: >50%, 25–50%, 10–25%, <10%, Don't know yet
      • What keeps you awake at night about waiting—regulatory change, market share, rising claims, or internal momentum? Options: Competitive product launch, Regulatory openings or constraints, Loss ratio deterioration, Talent / org politics, Vendor lock‑in concerns, Other
      • Describe a worst‑case scenario that would make you wish you'd acted sooner (brief example of market or financial consequence).
      • How does your leadership team view the tradeoff between being a first mover vs. a fast follower on telematics? Options: Prefer first mover, Prefer fast follower, Depends by line/geography, No consensus yet

      What’s Really Broken in Your Current Rating?

      • Which current rating variables feel most like blunt instruments—pulling good and bad drivers together—rather than distinguishing true risk? Options: Age, Credit score, Territory, Vehicle type, Annual mileage, Other
      • Can you share a concrete example where current factors led to mis‑priced risk or customer churn?
      • How often do you see materially different loss patterns within segments that your current model treats as homogeneous? Options: Very often, Sometimes, Rarely, Never, Unsure
      • Which operational pain points tie back to rating accuracy (claims leakage, fraud, underwriting backlog, customer disputes)? Options: Claims leakage, Fraud false positives/negatives, Underwriting complexity, Customer complaints / disputes, Loss of profitable renewals, Other
      • When you think about fixing these issues, what feels most valuable: better segmentation, personalized pricing, or behavioral nudges to change driving? Options: Better segmentation, Personalized pricing, Behavioral coaching / engagement, All of the above, Other

      Who Holds the Keys—and Who Keeps Saying 'Not Yet'?

      • Who are the people or functions that must sign off for a pilot to proceed? List roles and their top concern in one sentence each.
      • Which stakeholder typically has the most influence over pricing / rating changes in your organization? Options: Chief Actuary, CUO, Product Head, Legal / Compliance, CIO / Data Office, Executive Committee
      • Which function is most likely to raise a veto or delay—what do they worry about most (e.g., legal: privacy, actuary: model stability)? Options: Legal / Privacy, Actuarial team, Regulatory affairs, IT/Integrations, Distribution / Agents, Other
      • What evidence or artifact would convince the skeptical stakeholders (examples: actuarial lift analysis, consumer opt‑in data, legal memo, regulator pre‑brief)? Options: Actuarial case study, Regulatory memo / precedent, Privacy impact assessment, Pilot results from comparable carrier, Consumer engagement metrics, Other
      • How have past initiatives been derailed—bureaucracy, procurement timelines, integration surprises, or results that didn’t meet expectations?

      Can We Trust the Data You Have—and the Data You’ll Need?

      • Which telematics source(s) are you most willing to adopt for a pilot (select all that apply)? Options: Smartphone app, OBD‑II device, Embedded OEM data, Third‑party fleet telematics, Combination / multi‑device
      • How would you describe your current data maturity for telematics‑style inputs (collection, storage, labeling, QA)? Options: Ready for production, Prototype / partial, Data exists but needs work, No internal telematics data yet, Unsure
      • Do you have existing integrations or vendors for mileage / trip data, and can you name them (or list 'none')?
      • What data governance and privacy constraints should we plan around (select all that apply)? Options: State privacy laws (e.g., CCPA equivalents), GDPR or cross‑border transfer limits, Data retention limits, Anonymization or pseudonymization required, Explicit consent for secondary use, Other
      • How sensitive is latency for you—do you need near‑real‑time scoring, daily batches, or is weekly acceptable for the pilot? Options: Near‑real‑time, Daily, Weekly, Monthly, Undecided
      • Describe the ideal consent and opt‑in UX you imagine we present to policyholders (brief).

      What Would Success Really Look Like—Beyond Buzzwords?

      • What are the quantitative targets that would make this project 'a success' for you? Please list targeted opt‑in %, loss ratio lift (points or %), retention lift, or ROI horizon.
      • Which of these KPI targets feels most critical to greenlight a broader rollout? Options: Loss ratio improvement, Policy retention / reduced churn, Sustained opt‑in rate, Customer NPS / satisfaction, Regulatory approval / no objections
      • What acceptance thresholds would you set for pilot success (e.g., minimum opt‑in, loss ratio change, statistical confidence)? Options: Predefined numeric thresholds (we have them), We need your help to define thresholds, Flexible — we'll iterate, No thresholds yet
      • How will you balance short‑term financial impact vs. long‑term strategic benefits when evaluating results? Options: Focus on short‑term P&L, Prioritize long‑term share & retention, Equal weight to both, Depends on board guidance
      • Who will be the final owner of these KPIs post‑pilot (actuarial, product, ops, or a cross‑functional board)? Options: Actuarial, Product / Head of Personal Auto, CUO, Operations, Cross‑functional governance, Other

      What Could Break the Pilot—and How Would You Recover?

      • If opt‑in falls below expectations, what are acceptable remedial steps (pricing incentives, broader device set, UX changes, pausing rollout)? Options: Increase discounts/incentives, Change opt‑in messaging or UX, Add device options (OBD/app/OEM), Pause expansion and analyze, Cancel pilot
      • How do you want to handle regulatory or consumer complaints during pilot—immediate pause, notify regulator, customer remediation, or escalate internally? Options: Immediate pause & notify regulator, Customer remediation plan, Internal incident review then decide, Continue with communication, Undecided
      • What rollback or remediation criteria should be documented up front (e.g., scoring instability, adverse selection beyond X%, legal risk)?
      • What SLAs or uptime / data quality targets are non‑negotiable for integrations during the pilot? Options: 99.9% availability, 99% availability, Daily data completeness >95%, Weekly reconciliation acceptable, Other
      • Who should be on the incident response team and how quickly must they be reachable (hours)?

      How Smooth Do You Need the Integration to Be?

      • Which core systems must the telematics platform integrate with for the pilot (select all that apply)? Options: Rating engine, Policy administration system, Claims system, Billing system, Data warehouse / analytics, Mobile app / customer portal, Other
      • Do you prefer a phased integration (start with analytics + side‑by‑side scoring) or end‑to‑end pricing integration for the pilot? Options: Phased (analytics first), End‑to‑end pricing, Hybrid approach, Undecided / need recommendation
      • What internal resources and estimated FTEs can you commit to integrations, testing, and deployment during the pilot?
      • Do you have sandbox/test environments available for safe end‑to‑end testing, and if so, how mature are they? Options: Full sandbox available, Partial test environments, Limited test data only, No sandbox available
      • Are there hard change windows, release blackout periods, or regulatory filing windows we must avoid? Options: Yes—specific blackout windows, No strict windows, Not sure / need to check

      What Will You Want to See Before You Sign?

      • Which commercial models would you consider for a relationship with us? Options: Per‑policy subscription, Revenue share on savings, Fixed fee + success bonus, Pilot discount then standard pricing, Other
      • What are your must‑have legal / commercial terms (data ownership, liability caps, exclusivity, audit rights)?
      • How important is vendor transparency into models (full actuarial disclosure vs. high‑level performance reporting)? Options: Full disclosure required, High‑level performance reporting is fine, Prefer partial transparency, Undecided
      • What procurement or contracting steps typically add the most time (insurance legal review, security review, executive approval)? Options: Insurance legal review, Security / IT due diligence, Procurement PO process, Executive sign‑off, Other
      • How soon after a satisfactory pilot would you expect commercial close / enterprise rollout to begin? Options: Immediately, Within 3 months, 3–6 months, 6–12 months, Depends on board sign‑off

      If This Works, How Will You Keep It That Way?

      • What monitoring cadence do you expect for scoring and model performance post‑pilot (daily, weekly, monthly)? Options: Daily, Weekly, Monthly, Quarterly
      • Who should own ongoing governance for telematics models once scaled (actuarial, model risk, product, or a new center of excellence)? Options: Actuarial, Model risk / validation team, Product / Pricing, Center of Excellence, Other
      • How do you want model drift and recalibration decisions to be made—automated alerts, scheduled reviews, or event‑driven? Options: Automated alerts + review, Scheduled periodic recalibration, Event‑driven only, Combination
      • Are you planning to expand telematics beyond personal auto (commercial, fleet, usage‑based other lines)? If so, which? Options: Personal auto only, Commercial auto, Fleet / usage billing, Other lines of business, Undecided
      • What capabilities would you want us to own long‑term vs. what you'd prefer to keep in‑house (modeling, data ops, UX, regulatory filing)?
    2. Current State Mapping

      Document existing rating variables, data sources, telematics readiness, integrations, and regulatory constraints.

      Current State

      Where You Stand Today — a quick snapshot

      • Briefly describe your current personal auto product portfolio and whether telematics is already part of any product.
      • Which internal stakeholders are currently involved in pricing, data, and telematics decisions? Options: Chief Actuary, Head of Personal Auto/Product, CUO, CIO/Head of IT, Legal/Compliance, Marketing/Retention, Distribution/Agency, Other
      • What primary rating variables are in your current base rate plan today? Options: Age, Gender, Credit score, Territory/zip, Vehicle year/make/model, Annual mileage (self-reported), Prior claims/loss history, Driving record (violations), Other
      • When was your most recent rating plan update or major filing (month/year)? Options: Within the last 6 months, 6-12 months ago, 1-2 years ago, More than 2 years ago, We can't recall
      • How do you currently measure pricing performance across products (list the specific metrics you look at and the cadence)?
      • Which one outcome are you most hoping telematics will influence (pick one primary focus)? Options: Improve loss ratio, Increase retention, Attract low-risk drivers, Price more competitively, Reduce fraud, Support new product (PAYD/PPO), Other

      Are We Still Pricing on Hunches?

      • How confident are you that your current demographic and vehicle proxies truly separate safe drivers from risky ones? Options: Very confident, Somewhat confident, Doubtful, Not confident at all
      • Which existing rating factors do you suspect are masking real driving risk rather than explaining it? Options: Age, Credit score, Territory, Vehicle value, Marital status, Prior claims, Other
      • Tell us about a segment you believe is consistently mispriced today—who are they and what feels wrong?
      • Have you run any retrospective analyses that estimate the incremental predictive value of telematics signals versus your current model? If yes, summarize key findings. Options: Yes — we have detailed results, Yes — high-level estimates only, No — but we plan to, No — not yet
      • How does it feel internally when pricing misses occur—who gets the heat and what are the typical consequences?

      Data Reality: What’s Actually in Your Hands?

      • What critical driving signals do you not have today that, if you did, would most change your pricing or segmentation? Options: Trip-level mileage, Time-of-day driving, Hard braking/acceleration events, Speeding frequency, Phone distraction, Brake/turn/cornering patterns, OEM vehicle telematics, None—we have most signals, Other
      • Which data sources are already available to feed modeling or BI (select all that apply)? Options: Policy administration system (PAS), Claims system, Telematics vendor feeds, OEM connected vehicle feed, Mobile app trip data, OBD-II device feeds, Third-party data (credit, DMV, socioeconomic), Data lake/warehouse, None of the above, Other
      • Describe the size and recency of any telematics or driving-signal dataset you already own (e.g., N drivers, last collection date, sampling frequency).
      • Do you currently store trip-level PII or only aggregated/hashed identifiers? If mixed, describe which datasets contain PII. Options: Trip-level PII retained, Only hashed/anonymous IDs, Aggregated metrics only, Varies by system — explain below
      • What internal data quality checks or thresholds do you apply today (completeness, GPS accuracy, event thresholds)?
      • Estimate what percent of your active policybase could be instrumented with telematics within 12 months (best estimate). Options: <10%, 10–25%, 25–50%, 50–75%, >75%, Unsure

      Integration Nightmares or Smooth Sailing?

      • If implementing telematics were likely to break a critical system, which single integration risk worries you most? Options: Rating engine changes, Policy admin sync, Billing/prorations, Claims linkage, Data pipeline throughput, Vendor security/compliance, Other
      • Which systems must telematics outputs feed into to realize value (select all that apply)? Options: Rating engine, Policy administration system, Billing system, Claims handling system, CRM/retention tools, Underwriting workflow, Business intelligence/analytics, Mobile policyholder app, Other
      • What integration methods do you prefer or require from vendors? Options: API (real-time), Batch SFTP exchanges, Message bus/Kafka, Direct DB writes, Pre-built connectors to our PAS, Other
      • What are your minimum non-functional requirements for integrations (latency, uptime, throughput, encryption)? Please be specific if possible.
      • Do you maintain an internal integration or middleware team, or do you rely on vendors/partners to handle end-to-end integration? Options: In-house integration team, Hybrid (in-house + vendor), Vendor-managed integrations, We would need assistance — no team
      • Are there specific security/compliance certifications or contractual clauses vendors must satisfy (SOC 2, ISO 27001, data residency)? Options: SOC 2 Type II, ISO 27001, HIPAA (if applicable), GDPR/CCPA considerations, Data residency requirements, No formal certification required, Other

      Regulators, Lawyers, and the Fine Print — candidly

      • What is your biggest unspoken regulatory or legal fear about using behavior-based telematics scoring?
      • Which states or jurisdictions in your footprint impose restrictions or have active scrutiny of telematics/use-based rating? Options: All states, Specific states — list below, No known restrictions, We are unsure
      • If you answered 'Specific states,' list them and note any unique constraints (e.g., disclosure requirements, banned factors).
      • Have you previously submitted rate filings or actuarial memos that reference telematics-derived factors? Options: Yes — approved, Yes — denied or modified, Filed and pending, No prior filings
      • What documentation or evidentiary support will your regulators expect for telematics factors (validation studies, fairness tests, privacy notices)? Select all that apply. Options: Actuarial validation study, Fairness/non-discrimination analysis, Privacy/consent documentation, Model governance/monitoring plan, Pilot results, None specified, Other
      • How comfortable is your legal/compliance team with vendor-held raw telematics data versus anonymized aggregated scores? Options: Prefer vendor holds raw data, Prefer anonymized/aggregated only, Comfortable with either if controls exist, Undecided — need guidance

      Tech Readiness: Can Your Stack Take the Load?

      • If we started sending daily trip-level records tomorrow, how quickly would your systems ingest, process, and make them available for pricing decisions? Options: Within 24 hours, 24–72 hours, Weekly batches, We cannot ingest such volumes today, Unsure — need to check
      • Where is your core infrastructure hosted? Options: Cloud — AWS, Cloud — Azure, Cloud — GCP, Hybrid cloud/on-prem, Fully on-premises, Other
      • Do you have an existing data schema or telematics ingestion pipeline (e.g., standard trip schema, event definitions)? Options: Yes — documented schema, Partial — ad hoc fields, No schema today, We use vendor-specific formats
      • How mature is your team's capability to operationalize model scoring and monitor model drift (alerts, retraining, ownership)? Options: Established MLOps and monitoring, Some monitoring but manual, No formal model monitoring, We outsource model ops
      • What SLAs or tolerance levels would you set for scoring latency, model uptime, and data completeness before pushing to production?
      • Who would be the day-to-day technical owner(s) for telematics data pipelines and scoring in your organization (roles, not names)?

      If Telematics Moved the Needle, Would You Recognize It?

      • What single KPI would make executives say "this telematics program is a success" within the first 12 months? Options: Loss ratio improvement (absolute points), Retention uplift, Opt-in rate, New low-risk policy acquisition, ROI / payback period, Other
      • Which metrics do you currently track at a cohort level and how often (select all that apply)? Options: Loss ratio — monthly, Loss ratio — quarterly, Retention/churn — monthly, Opt-in rates — weekly, Claims frequency/severity — monthly, Pricing error by segment — quarterly, We don't track cohort metrics regularly
      • What acceptance thresholds would you set for a pilot to be considered for production (e.g., X% loss ratio lift, minimum opt-in, stable score distribution)? Please be specific.
      • Who in your organization has final authority to approve moving from pilot to enterprise rollout? Options: Chief Actuary, CUO, Head of Personal Auto/Product, CIO/CTO, Legal/Compliance sign-off also required, Cross-functional steering committee
      • If opt-in is low in early months, which corrective actions would you be willing to deploy (select all you’d consider)? Options: Increase marketing incentives, Use OBD device offers, Simplify consent flows, Provide driving rewards, Adjust targeting/segments, Pause and re-evaluate
      • What reporting cadence and format would stakeholders find most actionable during a pilot (examples: weekly dashboard, executive snapshot, actuarial memo)? Options: Weekly operational dashboard, Bi-weekly executive summary, Monthly actuarial report with tables, Ad-hoc deep dives on demand, Other
  2. Outcome Discovery

    Define target KPIs (loss ratio lift, retention, opt-in, ROI), acceptance thresholds, and success signals for a telematics program.

    Discovery Questions

    Quick Check — What Brought You to Telematics Today?

    • What's the single most important reason you're exploring telematics right now? Options: Competitive pressure, Improve loss ratio, Increase retention, New product launch (UBI/PPM), Regulatory request, Cost reduction, Innovation/strategic initiative, Other
    • Who will own the business case and decision on your side? (select all who will be involved) Options: Chief Actuary, Head of Personal Auto/Product, CUO, CIO/CTO, Chief Legal/Privacy Officer, Head of Claims, Head of Distribution/Sales, Other
    • How mature is your data and analytics infrastructure for consuming telematics signals? Options: No pipelines — manual exports only, Proof-of-concept pipelines, Production-grade pipelines for analytics, Integrated with rating/underwriting systems, Unknown / needs assessment
    • Have you run any telematics pilots before? If yes, briefly summarize scope and headline results. Options: No prior pilots, Yes — small pilots (under 5k policies), Yes — medium pilots (5k–50k), Yes — large pilots (50k+)
    • What's your target decision timeline for moving from pilot to scale? Options: Immediate (30 days), Near term (3 months), Medium term (6 months), Longer term (12+ months), Undecided
    • Who else on your team should we include in discovery conversations over the next two weeks?

    If Small Gains Are All You Get, Is That Enough?

    • If telematics produced a steady 2–3 point lift in loss ratio, would you consider that a success, or would you need more? Options: Clear success, Marginal — depends on ROI, Insufficient — need >5 points, Unsure
    • Which of the following KPIs will carry the most weight in your go/no-go decision? (pick all that apply) Options: Loss ratio lift (pp), Retention / renewal rate, Policy opt-in rate, ROI / payback period, Claims frequency reduction, Average premium per risk, Customer satisfaction (NPS)
    • For each KPI you selected, please list the minimum acceptable improvement and your target improvement (e.g., Loss ratio: min 2pp / target 5pp).
    • Over what measurement window do you expect to see meaningful KPI movement for a pilot (choose the single most relevant)? Options: 30 days, 90 days, 6 months, 12 months, Other
    • How will you weight trade-offs between actuarial improvements and commercial metrics (e.g., opt-in, retention)? Options: Actuarial-heavy (loss ratio first), Commercial-heavy (retention/opt-in first), Balanced scorecard, Depends on business unit
    • Who ultimately signs off on KPI thresholds — actuarial committee, exec sponsor, or other? Options: Chief Actuary / Pricing Committee, CUO / Underwriting Committee, Executive Steering Committee, Legal/Compliance sign-off required, Other

    What Are You Most Afraid Will Go Wrong?

    • Which single regulatory, privacy, or reputational risk would cause you to pause the program entirely? Options: State regulator rejection of factor, Customer privacy incident/public backlash, Data security breach, Material adverse selection, Actuarial instability / model drift, Other
    • Describe your current regulatory posture for telematics-based rating in your primary states (open response — be specific about states and known constraints).
    • How concerned are you about selection bias (safer drivers opt-in) skewing results? Options: Very concerned — major issue, Somewhat concerned, Neutral — manageable, Not concerned
    • What maximum customer churn or opt-out during rollout would you tolerate before re-evaluating? Options: <1%, 1–3%, 3–5%, 5–10%, >10%
    • How do your legal/privacy teams feel about collecting telematics signals (supportive, cautious, or opposed)? Options: Supportive, Cautious but open, Skeptical/raising major issues, Not engaged yet
    • Share a real story or example of a prior initiative that failed because of privacy or regulatory pushback and what you learned.

    Imagine the Win — Paint Me the Boardroom Moment

    • If you had to describe success in a single slide to the board, what three metrics and one anecdote would you include?
    • Which outcomes would change how you prize customer segments or product features (select up to three)? Options: Lower loss ratio in new segments, Higher retention of profitable customers, Ability to launch PPM / PAYD, More competitive pricing for low-mileage drivers, Reduced claims frequency, Improved customer NPS
    • If the program materially improved segmentation, how would that change distribution and sales conversations with agents/brokers?
    • Who inside the company would be the biggest internal champion if the pilot succeeds, and who would be the biggest skeptic?
    • Which single KPI would you use to tell customers and regulators that the program is working? Options: Loss ratio lift (pp), Opt-in rate (%), Retention improvement (%), Claims frequency reduction (%), ROI / Payback months

    The Trade-offs — What You’re Willing to Live With

    • Would you prefer a conservative, explainable model with modest gains or a black-box model with higher upside but less interpretability? Options: Conservative & explainable, Higher upside black-box, Hybrid approach, Undecided
    • How much month-to-month score volatility is acceptable before actuarial demands re-calibration? Options: <1% re-ranking, 1–3% re-ranking, 3–5% re-ranking, >5% re-ranking, No tolerance defined
    • Are you willing to accept temporary adverse selection in early months to measure full behavioral lift long-term? Options: Yes — acceptable, Yes, with strict guardrails, No — unacceptable, Need more information
    • What consumer protections or customer communications are non-negotiable if pricing changes for enrolled policyholders?
    • How important is model feature transparency for regulators vs. speed-to-market for your competitive team? Options: Transparency prioritized, Speed prioritized, Balanced — both matter, Depends on state/regulator

    Concrete Signals — How We’ll Decide to Proceed

    • If you could let one metric decide a pilot's fate, which would it be? Options: Loss ratio lift, Opt-in rate, Retention uplift, ROI / payback period, Claims frequency reduction
    • For that primary metric, please specify baseline, target, and fail threshold (e.g., baseline 68% loss ratio; target 64%; fail 67%).
    • Which secondary signals would prompt investigation but not immediate termination? (select all that apply) Options: Rising opt-out rate, Unexpected severity increase, Data gaps or ETL failures, Model drift / stability issues, Regulatory feedback/questions, Customer complaints
    • What remediation steps should be mandatory if thresholds are missed (e.g., pause enrollments, revert to pricing holdbacks, recalibrate model)? Options: Pause enrollments, Rollback pricing changes, Increase monitoring cadence, Run root-cause analytics, Engage regulator/legal, Other
    • Who signs the 'stop the pilot' order — role and escalation path? Options: Chief Actuary, CUO, Executive Sponsor, Regulatory Counsel, Steering Committee

    Small First Steps — A Pilot We Can Launch Fast

    • If I could put one quick, high-signal experiment in place within 30 days, what would you most want to see?
    • Which pilot design would you prefer to start with? Options: Voluntary opt-in smartphone app, Auto-enroll with opt-out and notice, OBD-II device cohort, Embedded OEM data sample, Rewards-only engagement trial
    • What minimal sample size and geographic scope do you consider meaningful for an initial pilot? Options: <1k policies, 1k–5k, 5k–25k, 25k–50k, 50k+
    • Which internal datasets must we access in the first 30 days (select all that apply)? Options: Policy master and rating table, Claims history, Billing/retention data, Customer contact info, Existing telematics feed (if any), Telephony / IVR data
    • Who should be on a 1–2 week rapid decision team for pilot approvals (names/roles)?
    • What cadence for governance and check-ins will keep stakeholders comfortable during the pilot? Options: Weekly, Bi-weekly, Monthly, Ad-hoc as needed
  3. Solution Experience

    Apply the carrier’s data and scenarios to demonstrate how behavior-based scoring shifts segmentation, pricing, and expected losses.

    Experience Meetings

    • Current State & Consequence Alignment
    • Data Mapping & Readiness Workshop
    • Behavioral Scoring Application & Segmentation Shift
    • Pricing Impact, Expected Loss Modeling & Acceptance Scenarios
    • Validation, Acceptance Criteria & Sign-off
    • Agree a recommended pilot pricing ladder and clearly link it to acceptance KPIs.
    • Host: Produce a feature mapping document linking carrier fields to scoring inputs.
    • Carrier & Host: Confirm anonymization checklist and sign-off for modeling use.
    • Recap Preconditions (Current State, Consequence, Future State)
    • Demonstrate, using carrier data, how behavior scoring re-segments risk at the policyholder level.
    • Quantify the movement between risk bands and identify the population and premium impact of those shifts.
    • Validate that each identified segment shift addresses a specific current-state consequence.
    • Agree a short list of candidate segments for pilot testing or immediate pricing changes.
    • Host: Deliver a segment-shift report with example policy-level records and aggregate metrics.
    • Carrier: Review highlighted cohorts and confirm strategic interest in candidate segments for pilot.
    • Host & Carrier: List open questions requiring model recalibration or additional data.
    • Pricing Mapping Methodology
    • Quantify the financial impact (loss ratio, premium, ROI) of at least three pricing scenarios based on the score.
    • Introductions & Purpose
    • Surface regulatory or fairness risks for the chosen scenario and agree mitigation steps.
    • Align on decision points and timeline for moving from modeling to pilot execution.
    • Host: Deliver scenario modeling files showing loss ratios, premium changes, and sensitivity to opt-in.
    • Carrier: Confirm preferred pricing scenario and any internal approval steps required.
    • Host & Carrier: Draft a short rate-filing and regulatory checklist for the chosen pilot scenario.
    • Review Modeled vs. Target KPIs
    • Agree concrete pass/fail acceptance criteria and validation tests for the pilot.
    • Establish monitoring cadence, dashboard metrics, and alert thresholds tied to business KPIs.
    • Assign operational owners and obtain stakeholder sign-off to proceed to pilot readiness.
    • Carrier: Sign and return the KPI acceptance document with named approvers.
    • Host: Build monitoring dashboards and schedule the first post-launch checkpoint.
    • Carrier & Host: Agree on remediation playbook and owner contacts for each potential failure mode.
    • Produce a single, agreed one-sentence current state describing where the portfolio breaks and who is affected.
    • Agree and quantify the business consequence of not implementing behavior-based pricing.
    • Define the one-sentence future state and set the primary KPIs and acceptance thresholds for the Solution Experience.
    • Confirm exact data extracts, owner contacts, privacy constraints, and delivery dates required for modeling.
    • Carrier: Deliver sanitized sample dataset (policy, claims, rating variables, telemetry sample) per agreed schema.
    • Carrier: Provide documented target KPIs and acceptance thresholds for opt-in, loss ratio lift, and retention.
    • Host: Prepare modeling plan and required feature list mapped to the carrier fields.
    • Dataset Inventory Review
    • Confirm the modeling dataset is complete and usable or document required fixes.
    • Agree a clear mapping from carrier fields to model features used in scoring.
    • Identify and assign remediation for critical data quality issues and confirm timelines.
    • Ensure privacy/anonymization approach is acceptable for the carrier's legal/regulatory team.
    • Carrier: Correct or annotate any critical data quality issues and deliver an updated dataset.
    • Run Scenario Set: Conservative / Base / Aggressive
    • Modeling Method & Assumptions
    • Validation Tests & Stability Checks
    • Data Quality & Gap Analysis
    • One-Sentence Current State
    • Opt-in & Retention Sensitivity
    • Quantify Consequence
    • Live Score Execution Summary
    • Telemetry-to-Feature Mapping
    • Monitoring Cadence & Dashboards
    • Sample Record Walkthrough
    • Define One-Sentence Future State & KPIs
    • Before vs After Segmentation Analysis
    • Regulatory & Fairness Checks
    • Rollout Gates & Remediation Plan
    • Recommended Pilot Pricing Ladder & Rationale
    • Sign-off & Next Actions
    • Privacy & Anonymization Controls
    • High-Impact Cohort Identification
    • Stakeholders, Data Scope & Pre-Work Review
    • Agree Final Modeling Dataset & Timeline
  4. Solution Scope

    Define device options, captured data fields, scoring models, integrations, regulatory filing support, and monitoring cadence.

    Scope Configuration

    • Mobile SDK integration and deployment
    • OBD-II device provisioning and activation
    • OEM connected-vehicle data onboarding
    • Real-time driver scoring engine deployment
    • Telematics-to-rating API integration
    • Pay-per-mile billing and mileage metering
    • Behavior-based discount calculation engine
    • Trip data storage, transformation, and export
    • Privacy and consent flow implementation
    • Model monitoring, recalibration, and rollout
    • In-app coaching, feedback, and rewards delivery
    • Telematics event webhooks and alerting

    Scope Questions

    Mobile SDK integration and deployment

    • Which mobile platforms must the SDK support? Options: iOS, Android, Both, Other
    • Who owns the mobile app (carrier-owned, vendor-provided white label, or third-party)? Options: Carrier-owned, Vendor white-label, Third-party marketplace app, Not decided
    • What data collection modes are required (foreground-only, background tracking, trip-based, continuous)? Options: Foreground-only, Background tracking, Trip-based, Continuous (always-on)
    • What minimum data sampling frequency or latency is acceptable for driving events? Options: Real-time (sub-second), Near real-time (seconds), Periodic (minutes), Batch (hourly/daily)
    • Are there specific battery or performance constraints for the SDK in your policyholder population? Options: Yes, No
    • Do you require custom telemetry events or attributes beyond standard driving signals (e.g., phone distraction tags, road type)? If yes, list them.
    • Do you need code-level review, security scan, or compliance attestations for the SDK before integration? Options: Code review, SAST/DAST scan, Privacy impact assessment, None

    OBD-II device provisioning and activation

    • Which OBD-II device models or vendors are in scope (existing preferred vendors)?
    • Approximately how many devices will be provisioned for pilot and for full scale? Options: Pilot: <1,000; Full: <10,000, Pilot: 1-5k; Full: 10-50k, Pilot: 5-20k; Full: 50k+, Custom (describe)
    • What is your preferred device activation flow (dealer/agent handoff, mailed pre-provisioned, in-person installation, self-install paired via app)? Options: Dealer/agent, Mailed pre-provisioned, In-person install, Self-install via app
    • Do devices require embedded cellular, Bluetooth to phone, or both? Options: Embedded cellular, Bluetooth to phone, Both, Depends on device model
    • What provisioning identifiers and lifecycle events must be tracked (VIN, policy ID, IMEI, activation timestamp, swap/return)?
    • How should firmware updates and remote management be handled and who will own that process? Options: Vendor-managed OTA, Carrier-managed via vendor API, No OTA required, Not decided
    • Are there logistics or warranty considerations (returns, replacements, lost device handling) to incorporate? Options: Yes, No

    OEM connected-vehicle data onboarding

    • Which OEMs or telematics partners do you expect to integrate with initially?
    • Which vehicle-level data elements are required from OEMs (odometer, speed, ignition status, fault codes, advanced ADAS signals)?
    • Do you have existing OEM contracts or commercial relationships that simplify onboarding? Options: Yes, No, In negotiation
    • What data delivery model is preferred: push webhooks, OEM API pull, brokered feed, or batch file exports? Options: Push webhooks, API pull, Brokered feed, Batch exports
    • What acceptable data latency and freshness are needed for scoring and billing? Options: Real-time (<1min), Near real-time (minutes), Hourly, Daily
    • Are there specific contract or consent considerations with OEMs (data ownership, resale rights, usage restrictions)? Options: Yes, No
    • What security and credentialing approach is required for OEM integrations (mutual TLS, API keys, token rotation)? Options: Mutual TLS, OAuth2/token, API keys, Other

    Real-time driver scoring engine deployment

    • Do you require real-time scoring per trip, near-real-time per hour, or daily/batch scoring? Options: Real-time (per trip/event), Near-real-time (minutes/hours), Daily batch
    • Will scoring be performed entirely by vendor, by carrier, or hybrid (vendor model, carrier run-time)? Options: Vendor-hosted, Carrier-hosted, Hybrid
    • What maximum end-to-end latency is acceptable from event generation to score availability? Options: <1s, <1min, <15min, <24h
    • Which explainability or audit features are required (feature importance per driver, score drivers, model versioning)? Options: Feature importance, Score decomposition, Model version ID, Full audit logs, None
    • Do you need to support multiple concurrent scoring models (e.g., by product, state, occupant type)? Options: Yes, No
    • What throughput and scaling expectations do you have (events per second, concurrent users)?
    • Are there regulatory constraints on model transparency or embargoed features in any target states? Options: Yes, No, Unknown

    Telematics-to-rating API integration

    • Which systems must receive telematics outputs (rating engine, policy admin system (PAS), quoting tool, underwriting dashboard)? Options: Rating engine, PAS, Quoting tool, Underwriting dashboard, Other
    • Should score-to-rate mappings be calculated in the telematics platform or in the carrier's rating engine? Options: Platform calculates discounts/rates, Carrier rating engine applies mapping, Hybrid
    • Do you require synchronous quote-time API calls or asynchronous batch feeds for rating data? Options: Synchronous (quote time), Asynchronous batch, Both
    • What authentication and security standards are required for APIs (mutual TLS, OAuth2, IP allow-list)? Options: Mutual TLS, OAuth2, API Key, IP allow-list
    • What are your testing environment requirements (sandbox, sample data, replay capability)? Options: Sandbox with replay, Static sample files, No preference
    • What error handling and fallback behavior do you require if telematics data is not available at quote/billing time? Options: Use traditional rating factors, Defer discount, Manual underwriter review, Other
    • Are there specific mapping rules, tiers, or regulatory objectives that the integration must enforce? Options: Yes, No

    Pay-per-mile billing and mileage metering

    • Will pay-per-mile be billed as a standalone product or as an add-on credit/adjustment to standard premium? Options: Standalone product, Add-on adjustment, Both, Not decided
    • What billing cadence is required (monthly, biweekly, per-pay-period, real-time micropayments)? Options: Monthly, Biweekly, Per-pay-period, Real-time
    • What rounding, thresholds, or minimums should apply to recorded mileage for billing? Options: Round to nearest mile/km, Daily minimum, Weekly minimum, No rounding
    • Which billing systems must integrate (carrier billing system names) and what integration method is preferred?
    • How should disputes, mileage adjustments, and refunds be handled operationally? Options: Manual review, Automated adjustments, Customer self-service with audit trail, Other
    • Are anti-fraud measures required for odometer spoofing or device tampering detection? Options: Yes, No
    • Do you require separate metering for personal vs business miles, or exclusions (work miles)? Options: Yes, No

    Behavior-based discount calculation engine

    • Do you want static rule-based discounts, model-driven dynamic discounts, or a hybrid approach? Options: Rule-based, Model-driven dynamic, Hybrid
    • Should discounts be applied instantly in-app, at renewal, or after a validation window? Options: Instant (in-app), At renewal, After validation window, Other
    • Are discounts state-specific or uniform across jurisdictions? Options: State-specific, Uniform, Hybrid
    • What stacking rules should govern discounts when multiple programs apply (caps, prioritized discounts)? Options: Stackable with cap, Single best discount only, Priority-based stacking, Custom rules
    • Do you require automated rate-filing outputs and actuarial backup artifacts for each discount rule? Options: Yes, No
    • Should discount eligibility be re-evaluated continuously or at fixed intervals? Options: Continuous, Weekly, Monthly, At renewal
    • Do you need explainability to policyholders and regulators on how discounts were calculated? Options: Yes (policyholder-facing), Yes (regulator-facing), No

    Trip data storage, transformation, and export

    • What retention policy is required for raw trip data and aggregated metrics? Options: 30 days, 90 days, 1 year, Custom (specify)
    • Do you require pseudonymization or anonymization of stored trip data? Options: Pseudonymization, Anonymization, No
    • Which export formats and delivery methods are required (CSV, Parquet, S3, secure FTP, API)? Options: CSV, Parquet, S3, Secure FTP, API
    • What ETL cadence is needed for downstream analytics (real-time stream, hourly, daily)? Options: Real-time/stream, Hourly, Daily, Weekly
    • Are there schema or ontology standards you must adhere to for trip and event data? Options: Yes (provide schema), No, Prefer standard mapping assistance
    • Do you require a long-term analytics warehouse or BI-ready layer to be delivered as part of the scope? Options: Yes, No
    • What backup, archival, and disaster recovery SLAs are required for trip data? Options: Daily backup, Weekly archival, Geo-redundant storage, Custom

    Privacy and consent flow implementation

    • What consent model will you use (opt-in, opt-out, granular consents per data use)? Options: Opt-in, Opt-out, Granular consents
    • Do you require localized consent flows and disclosures for specific states/countries? Options: Yes, No
    • Should consent revocation be supported in-app and through customer service channels? Options: In-app, Customer service, Both, Not required
    • What personal data categories will be processed and need explicit disclosure (location, driving events, device identifiers)?
  5. Mutual Commit

    Agree commercial terms, data-sharing and privacy obligations, regulatory deliverables, and KPI-linked acceptance criteria.

    Agreement Modules

    • Master Services Agreement (MSA)
    • Statement of Work (SOW)
    • Commercial Terms & Pricing Schedule
    • Data Processing & Data Sharing Agreement (DPA)
    • Regulatory Filing & Compliance Plan
    • KPI Acceptance Criteria & Measurement Plan
    • Pilot Acceptance & Exit Criteria
    • Security & Compliance Addendum
    • Integration & Implementation Plan
    • Service Level Agreement (SLA) & Support Terms
    • Model Governance & Monitoring Agreement
    • Consent & Consumer Communications Approval
    • Subprocessor & Third-Party Risk Management
    • Audit Rights & Reporting Framework
    • Intellectual Property & Licensing
    • Insurance, Liability & Indemnification
    • Change Order & Governance Process
    • Termination, Data Return & Transition Plan
  6. Deployment

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

    1. Pre-Deployment Readiness

      Confirm data pipelines, anonymization and privacy controls, test environments, and regulatory/legal sign-offs for pilot launch.

      Readiness Questions

      Quick Snapshot: Who's in the Room and What You're Betting On

      • Which title best describes your role in shaping telematics strategy here? Options: Head of Personal Auto, Chief Actuary, Chief Underwriting Officer (CUO), Chief Information Officer (CIO), Legal/Privacy Lead, Product Lead, Other
      • How would you classify the scale of personal auto business this initiative would touch? Options: Pilot (under 10k policies), Small line (10k–50k), Mid (50k–250k), Large (250k–1M), Enterprise (1M+), Unsure
      • Where are you in your telematics journey today? Options: No program / starting from scratch, Exploratory pilots only, Active pilot(s) with limited scale, Live program in select states, Production at scale, Sunsetting previous program
      • Who are the core decision-makers who must sign off for a pilot and for a full-scale roll-out? Options: Chief Actuary, CUO/Head of Underwriting, Head of Personal Auto Product, CIO/CTO, Legal/Compliance, Distribution/Sales Lead, Other
      • What is the primary business driver for exploring telematics right now? Options: Improve loss ratio, Protect/earn back profitable drivers, Grow retention, Regulatory differentiation, New product (PAYD/PPO), Digital engagement/experience, Other

      What If Your Best Drivers Are Already Being Poached?

      • When you look at recent lapses or new-business cohorts, do you see evidence that safer drivers are being captured by competitors? Options: Strong evidence, Some evidence, No clear signal, We haven't investigated
      • Which customer segments do you suspect are most at risk of being mispriced today (and why)? Options: Low-mileage urban drivers, High-tech/connected-vehicle owners, Young safe drivers, Seniors with low mileage, Rural low-risk drivers, Other
      • How do you currently detect when competitive products are winning your best drivers? Options: Churn analytics, Agent feedback, Market research, Price shopping tools, We don't have a reliable detection method
      • If your top-performing drivers left at a 5–10% higher rate next year, what would that mean financially and culturally for the business?
      • On an emotional level, what worries you most about being late to telematics adoption? Options: Losing market position, Regulatory scrutiny, Operational complexity, Brand erosion, Internal resistance, Other

      Show Me Your Data — and Where It Breaks

      • What rating variables and data sources do you rely on today to predict driving risk? Options: Age/Gender, Credit score, Territory/ZIP, Vehicle make/model/year, Annual mileage estimate, Claims history, Telematics (limited), Other
      • Which systems hold that data (policy admin, rating engine, data lake, MDM)? Please list the primary platforms or vendors.
      • How complete and timely is the data you need for pricing and segmentation (e.g., mileage, claims linkage, VIN)? Options: High completeness & near real-time, Moderate completeness with delays, Fragmented and slow, Significant gaps
      • Which telematics capture options are you technically prepared to support for a pilot? Options: Smartphone app, OBD-II plug-in, OEM / embedded telematics, Third-party connected car feed, We are not prepared yet
      • Do you have accessible historical trips or telematics-like samples (even small) we could use to validate models quickly? Options: Yes — large dataset, Yes — small sample, No, but can get data from partners, No and difficult to obtain

      How Will You Know It Worked — Before We Build Anything?

      • If telematics went live tomorrow, which one metric would make you declare the program a success after the first 12 months? Options: Loss ratio improvement (aggregate), Loss ratio improvement (cohort), Net retention uplift, Opt-in rate, Return on investment (ROI), Regulatory acceptance
      • What minimum improvement/threshold would you need on that metric to move from pilot to scale? Please quantify if possible. Options: >10% relative improvement, 5–10% relative improvement, 1–5% relative improvement, Improvement is secondary to strategic value, Unsure / need guidance
      • Which set of KPIs will be monitored during the pilot (choose all that apply)? Options: Opt-in conversion, Policy retention by score, Claim frequency/severity shifts, Score distribution stability, Customer NPS/engagement, Underwriting throughput
      • Who within your organization will be the formal approver of pilot success (role, not name)? Options: Chief Actuary, CUO/Head of Underwriting, Head of Personal Auto Product, CIO, Legal/Compliance, Board/Executive Committee
      • How long of an observation window do you consider credible for telematics-driven loss ratio signals? Options: 3 months, 6 months, 12 months, 18+ months, Depends on cohort size

      If We Launched Tomorrow, What Would Fail First?

      • What are the top three scenarios you fear could derail a pilot (technical, regulatory, behavioral, commercial)? Options: Regulatory pushback, Low opt-in rates, Data integration failures, Score instability / poor predictive lift, Customer privacy complaints, Distribution resistance
      • Have you previously experienced regulatory objections to using behavior-based factors? If so, what happened? Options: Yes — formal objections/fines, Yes — informal pushback, No regulatory issues, Not sure / haven't engaged regulators
      • How comfortable are you with anonymization and privacy controls that remove PII but preserve utility for modeling? Options: Very comfortable, Somewhat comfortable, Skeptical, Need education
      • If a scoring model began to drift after deployment, what remediation or rollback process do you expect to be available? Options: Immediate rollback to benign score, Phased throttling, Manual hold-and-investigate, We don't have a defined process
      • What would be a showstopper issue that would force you to pause the pilot? Options: Regulatory cease directive, Data breach, Severe adverse selection, Unacceptable customer complaints, Material system outage

      The Policyholder Experience That Wins—and Keeps—People

      • Which opt-in model do you believe would be most acceptable to your customers and regulators? Options: Opt-in with incentives (discounts/rewards), Automatic enrollment with opt-out option, Voluntary opt-in with education only, Mandatory in specific products
      • What incentives have the best chance of driving enrollment in your book (and please list any you’ve tried)? Options: Upfront discount, Trial period discounts, Gamified rewards, Partner discounts, No incentives / rely on value proposition
      • How important is real-time feedback (app coaching, weekly score) versus periodic summary statements for engagement? Options: Real-time is critical, Both real-time and periodic are valuable, Periodic only is fine, Unsure
      • What communication channels resonate best with your customers for behavioral programs? Options: Mobile app + push, Email, SMS, Agent outreach, Customer portal, Direct mail
      • From a brand perspective, what tone and messaging have to be avoided when discussing behavior-based pricing?

      Integration Reality: How Deep and Fast Can We Go?

      • If we asked your IT team to integrate a streaming pipeline and a batch feed, what would you expect the realistic timeline to be? Options: <4 weeks, 4–8 weeks, 8–16 weeks, 16+ weeks, Depends on approvals
      • Which core systems must we integrate with for a pilot (select all that apply)? Options: Policy Admin System, Rating Engine, Claims System, Customer CRM, Data Lake/Warehouse, Identity/Access Management
      • Do you have a sandbox or test environment we can use, and how close is it to production data schemas? Options: Production-like sandbox available, Sandbox but with limited data, No sandbox; only production, Unsure / need to confirm
      • What security and compliance certifications or controls will we need to meet before ingesting telemetry? Options: SOC 2, ISO 27001, State-specific privacy standards, Vendor security assessment, Custom legal agreement
      • How much ongoing operational support can your team provide for monitoring and incident response during a pilot? Options: Dedicated cross-functional team, Partial support (limited hours), Ad-hoc support only, Minimal to no capacity

      Commitment & Next Steps: What Would Make You Say Yes?

      • Which commercial model aligns best with how you want to buy this capability? Options: Per-policy SaaS fee, Pay-for-performance tied to loss improvement, Upfront platform fee + integration, Revenue share on savings, Pilot-friendly fixed-fee
      • Would you be open to a limited pilot that ties some fee to early KPI performance? Options: Yes, Maybe — with guardrails, No
      • What pilot population size would give you credible statistical signals while remaining operationally manageable? Options: 1k–5k drivers, 5k–25k drivers, 25k–100k drivers, 100k+ drivers, Unsure — need help sizing
      • What are your expected legal/regulatory lead times before a pilot can launch in a given state? Options: <4 weeks, 4–8 weeks, 8–16 weeks, 16+ weeks, Varies significantly by state
      • What would success look like for you at the end of the discovery phase (deliverables, approvals, or decisions needed)? Options: Signed pilot statement of work, Regulatory pre-clearance, Internal executive approval, Data sharing agreement signed, Technical integration plan approved
      • Finally, what is the single biggest ask you need from a vendor during discovery to feel confident moving forward?
    2. Deployment Enablement

      Schedule and assign integration tasks, pilot rollout sequencing, policyholder engagement workflows, and operational owners.

    3. Validation Checklist

      Verify scoring stability, opt-in and retention metrics, claims impact, and document remediation and rollback criteria.

      Validation Questions

      Where We Start: A quick check-in

      • Briefly: how would you describe your organization’s current stance on telematics—exploring, piloting, scaling, or deployed at scale? Options: Exploring conceptually, Running pilots, Limited commercial deployments, Scaling across lines/products, Embedded program at scale
      • Who on your team has been most vocal about pursuing telematics—and why does this matter to them?
      • What’s one concrete thing you hope a telematics program will change for your business in the next 12 months?
      • When you picture a successful pilot, what’s the single metric you’d show your executive committee first? Options: Loss ratio improvement, Opt-in rate, Retention lift, New business conversion, Customer satisfaction (NPS), Other

      What's Getting Hidden by Your Current Pricing?

      • If your current rating toolkit actually captured true driving risk, why are your best drivers still overpaying or leaving?
      • How confident are you that your current variables (age, territory, credit) are identifying low-risk drivers accurately? Options: Very confident, Somewhat confident, Neutral, Somewhat doubtful, Not confident at all
      • Tell us about a recent surprise in your book—an apparently ‘low-risk’ cohort that produced worse-than-expected losses. What pattern did you notice?
      • What assumptions about policyholder behavior or selection do you suspect are wrong, and how long have you been tolerating them?
      • Which competitor moves or market shifts make you feel urgency about changing your approach now? Options: Competitors launching telematics offers, New product entrants, Regulatory changes, Channel partners pushing telematics, Evolving consumer expectations, Other

      If This Works, What Changes on Your P&L?

      • Imagine telematics delivered measurable benefit—what does ‘benefit’ look like to you: margin expansion, retention, new segments, or something else? Options: Loss ratio improvement, Retention lift, New business growth, Reduced volatility, Operational efficiency, Other
      • What minimum loss-ratio lift or ROI would make this program unambiguously worth scaling for you? Options: >5% lift, 3–5% lift, 1–3% lift, Break-even first year, Other
      • How do you plan to trade off acquisition versus retention benefits when evaluating success? Options: Prioritize retention, Prioritize acquisition, Balance both equally, Depends on line/product, Undecided
      • What time horizon do you require for a pilot to demonstrate success (months)? Options: <3 months, 3–6 months, 6–12 months, >12 months
      • Which KPIs beyond loss ratio must move to satisfy the board (select all that apply)? Options: Opt-in rate, Retention/renewal rate, Customer lifetime value, Claim frequency/severity, Model calibration/stability, Regulatory acceptance

      Who Carries the Risk—and Who Gets the Credit?

      • If this initiative fails publicly, whose career would be most exposed—and what would that pressure look like?
      • Which stakeholders must formally sign off at pilot go/no-go, and what is each person’s primary concern? Options: Chief Actuary, Head of Personal Auto/Product, CUO, CIO/CTO, General Counsel/Privacy, Regulatory Affairs, Distribution/Channels, Marketing
      • How do you prefer decisions to be made—consensus across functions, executive-level decision, or delegated to a program owner? Options: Consensus across functions, Executive committee decision, Delegated to program owner, Hybrid
      • Who will be the operational owner responsible for pilot execution (name + role) and who’s the backup?
      • What approval or documentation does Legal/Privacy require before you allow live data collection from policyholders?

      Your Data: The Good, The Messy, And The Missing

      • Which of the following data sources are available today and ready to connect for a pilot? Options: Policy system (rating/eligibility), Claims history, Telematics via mobile app, OBD-II data, OEM/connected vehicle feed, Third-party exposure data, None of the above
      • What proportion of your book is reachable for telematics through smartphone vs. device vs. OEM integrations? Options: Mostly smartphone, Mostly OBD/device, Mostly OEM, Even mix, Unknown
      • Where are your most fragile integration points (e.g., policy system, billing, rating engines) that could slow delivery?
      • How large a historically-labeled sample do you have to calibrate a driving score (number of policies or drivers)? Options: <5k, 5k–25k, 25k–100k, >100k, Unsure
      • What anonymization, PII minimization, or data retention rules must we design for from day one?

      How Will Policyholders React—And What Will Move Them?

      • What would you do if opt-in rates are 20% lower than your forecast—double down on incentives, change UX, or pause? Options: Increase incentives, Redesign UX/communications, Target different segments, Pause and reassess, Other
      • Which incentive levers have you considered or tested (select all that apply)? Options: Upfront discount, Guaranteed renewal benefit, Gamified rewards, Cashback/credits, Pay-per-mile savings, No incentives—behavioral nudges only
      • Describe a customer segment you believe will enthusiastically opt in—and why you think they'll respond.
      • How do your distribution partners (agents, direct channels) feel about telematics offers—supportive, neutral, or resistant? Options: Supportive, Neutral, Resistant, Not engaged
      • What are your biggest fears about customer privacy backlash, and do you have recent examples of similar initiatives that went well or poorly?

      Regulators, Filings, and The Things That Can Stop You Cold

      • Which regulatory or state-specific issues could force you to change or stop a telematics program? Options: Rate filing rejection, Usage restrictions on data, Privacy law constraints, Anti-discrimination concerns, Mandatory opt-in rules, Other
      • Do you have prior experience getting telematics-based factors accepted by regulators—if yes, where did you win or stumble?
      • What documentation will regulators expect from you (e.g., actuarial support, consumer disclosures, validation studies)? Options: Actuarial validation, Consumer-facing disclosures, Privacy impact assessments, Third-party audits, Model performance monitoring
      • How much lead time does your filing cycle allow between pilot results and a commercial rate change? Options: <3 months, 3–6 months, 6–12 months, >12 months, Varies by state
      • Are there states or lines where we should not even test telematics due to legal or company rules? Please list.

      Pilot to Production: What Would Make You Confident—or Hit the Brake?

      • What single failure mode would cause you to stop a pilot immediately (e.g., model instability, regulatory pushback, low opt-in)?
      • Define measurable 'go/no-go' criteria we should instrument from day one (select all that apply). Options: Model calibration metrics (PSI/KS), Opt-in rates, Retention delta vs. control, Claim frequency/severity change, Customer complaint volume, Operational SLA adherence
      • How will you evaluate statistical significance vs. commercial significance—what lift is actionable even if marginally significant?
      • What remediation or rollback playbook do you require (steps, owners, communication templates)?
      • Who will monitor the pilot daily/weekly and who signs off on each threshold breach?

      Integrations, Automation, and Operational Expectations

      • Which systems must be updated in real time versus batched (rating engine, policy admin, claims, CRM)? Options: Real-time rating engine, Policy admin/billing (daily), Claims system (batch), CRM/engagement (real-time), Other
      • What level of technical support and SLAs do you expect from a telematics vendor during pilot and post-launch? Options: 24/7 support with SLAs, Business hours support, Dedicated engineering support, Quarterly reviews only, Unsure
      • Which internal teams will own ongoing model monitoring, recalibration, and feature stewardship? Options: Actuarial, Data Science, Pricing/Product, Analytics/BI, Operations, Vendor-managed
      • How automated do you want scoring updates—manual approval, scheduled retrain, or continuous learning with guardrails? Options: Manual approval, Scheduled retrain (monthly/quarterly), Continuous learning with guardrails, Vendor-managed monitoring only
      • What reporting cadence and dashboarding detail will your executives require (weekly snapshot, monthly deep-dive, KPI owners)? Options: Weekly snapshot + monthly deep-dive, Bi-weekly updates, Monthly only, Quarterly executive reviews

      Commercial and Data-Sharing Boundaries

      • If a vendor promises a guaranteed loss-ratio improvement, would you accept a performance-based commercial model, or prefer fixed fees? Options: Performance-based (shared savings), Fixed fees, Hybrid, Undecided
      • What data-sharing constraints or proofs do you need before you allow an external partner to access raw telematics? Options: Anonymized data only, Data use agreements, On-premise processing, Third-party audit, Other
      • How comfortable are you with vendor-hosted analytics versus running models in your environment? Options: Prefer vendor-hosted, Prefer in-house, Hybrid approach, No preference
      • What contract terms (term length, audit rights, IP, liability) would be immediate blockers for you?

      Closing the Loop: What Would Make Us Partners, Not Vendors

      • If we delivered a pilot that hit your stated KPIs, what would a desirable next step look like to you? Options: Scale to full book, Phase-based rollout, Productize for specific segments, Renegotiate commercial terms, Other
      • How do you want knowledge transferred—embedded resources, joint governance, or fully handed-off operations? Options: Embedded vendor resources, Joint governance, Full handoff to internal teams, Combination
      • What would make you recommend our platform internally to peers or the board (one sentence)?
      • Realistically, when would you like to run a pilot if all blockers are cleared? Options: Immediately, In 1–3 months, In 3–6 months, 6+ months
  7. Success

    Review performance against KPIs, capture learnings, and maintain a shared channel for issues and enhancement requests.

    Success Reviews

    • Executive KPI Review
    • Model Performance & Monitoring Deep Dive
    • Policyholder Experience & Opt‑In / Retention Review
    • Lessons Learned, Backlog Prioritization & Roadmap Workshop
    • Operational Governance & Shared Channel Setup

    Issues & Enhancements

    • Agree owners, timelines, and acceptance criteria for the top prioritized items.
    • Ensure executive alignment on business consequences and investment priorities.
    • Introductions & Objectives
    • Produce a 1‑page executive summary showing KPI variances, P&L impact, and recommended decision.
    • If approved to expand, draft an expansion plan with enrollment targets and regulatory steps.
    • If remediation required, list top 3 fixes with owners and target dates.
    • Meeting Framing & Required Outcomes
    • Confirm whether the model is stable and defensible or requires remediation.
    • Agree a concrete remediation and validation plan with owners and timelines.
    • Establish monitoring thresholds and alerting cadence to prevent recurrence.
    • Run agreed out‑of‑time validation and deliver results within defined window.
    • Update monitoring rules (PSI/KS thresholds, alert recipients) and implement on dashboard.
    • Create a model change request package for actuarial and regulatory review if recalibration is chosen.
    • Opening & Objectives
    • Identify highest‑impact interventions to increase opt-in and retention and agree on tests.
    • Validate sample sizes and success metrics to ensure statistically meaningful tests.
    • Assign owners and timelines for experiment execution and measurement.
    • Create experiment briefs for top 2 interventions including sample sizes and instrumentation requirements.
    • Update product enrollment flow (prototype/copy) and schedule UX testing.
    • Prepare customer-facing FAQ and privacy messaging adjustments for legal review.
    • Publish a 90‑day roadmap for stakeholder review and sign‑off.
    • Workshop Goals & Rules
    • Produce a ranked backlog of enhancements tied to quantified business impact.
    • Assign clear owners and timelines for approved next steps.
    • Ensure regulatory and legal dependencies are flagged and scheduled.
    • Convert top 8 workshop outputs into enhancement tickets with impact/effort estimates.
    • Schedule follow‑up backlog grooming with engineering and actuarial to refine scope.
    • Purpose & Expected Outcomes
    • Stand up a shared communication channel with clear access and role definitions.
    • Agree triage workflow and SLAs to ensure predictable issue resolution.
    • Assign operational owners for ongoing monitoring, escalation, and backlog maintenance.
    • Create the shared channel and add required users with documented roles and permissions.
    • Publish the triage workflow and SLAs in the channel and link the operational runbook.
    • Schedule recurring operational review meetings and define the first month's reporting package.
    • Confirm whether program meets KPI-based acceptance criteria and secure an executive decision.
    • One‑sentence Current State
    • One‑sentence Current State
    • One‑sentence Current State
    • One‑sentence Current State
    • One‑sentence Current State
    • Capture Wins & Issues
    • Proof: Funnel & Cohort Metrics
    • KPI Dashboard Review
    • Consequence: Operational Risk
    • Proof: Quantitative Evidence
    • Channel Selection & Access
    • Consequence: Financial & Competitive Impact
    • Quantify Consequences
    • Consequence: Revenue & Lifetime Value Impact
    • Consequence: Risk & Regulatory Exposure
    • Future State & Acceptance Thresholds
    • Hypotheses & Interventions
    • Diagnosis: Root Cause Analysis
    • Triage Workflow & SLAs
    • Future State & Prioritization Criteria
    • Remediation Options & Tradeoffs
    • Decision & Commitment
    • Prioritization Exercise
    • Reporting & Escalation Cadence
    • Validation: Test Design & Success Criteria
First-Party AI

1-2 minutes please — Your AI agent is working

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