Blueprint Playbook for DentWizard

Who the Hell is Jordan Crawford?

Founder of Blueprint. I help companies stop sending emails nobody wants to read.

The problem with outbound isn't the message. It's the list. When you know WHO to target and WHY they need you right now, the message writes itself.

I built this system using government databases, public records, and 25 million job posts to find pain signals most companies miss. Predictable Revenue is dead. Data-driven intelligence is what works now.

The Old Way (What Everyone Does)

Your GTM team is buying lists from ZoomInfo, adding "personalization" like mentioning a LinkedIn post, then blasting generic messages about features. Here's what it actually looks like:

The Typical DentWizard SDR Email:

Subject: Quick question about your fleet maintenance Hi [First Name], I noticed your company manages a large vehicle fleet. Wanted to reach out because DentWizard offers paintless dent repair services that can save you time and money. We've helped companies like Hertz and Enterprise reduce repair costs by up to 50% while getting vehicles back on the road faster. Would you be open to a 15-minute call next week to discuss how we could help your fleet? Best, Mike

Why this fails: The prospect is an expert. They've seen this template 1,000 times. There's zero indication you understand their specific situation. Delete.

The New Way: Intelligence-Driven GTM

Blueprint flips the approach. Instead of interrupting prospects with pitches, you deliver insights so valuable they'd pay consulting fees to receive them.

1. Hard Data Over Soft Signals

Stop: "I see you're hiring fleet managers" (job postings - everyone sees this)

Start: "3,847 vehicles in your Denver locations got hit in the April 12th hailstorm according to NOAA severity maps" (government database with specific dates and locations)

2. Mirror Situations, Don't Pitch Solutions

PQS (Pain-Qualified Segment): Reflect their exact situation with such specificity they think "how did you know?" Use government data with dates, record numbers, geographic footprints.

PVP (Permissionless Value Proposition): Deliver immediate value they can use today - analysis already done, damage forecasts already pulled, patterns already identified - whether they buy or not.

DentWizard Intelligence Plays

These messages demonstrate precise understanding of prospects' current situations while delivering actionable intelligence. Every claim traces to specific data sources with verifiable evidence.

PVP Public + Internal Strong (8.7/10)

Vehicle Model Damage Propensity for Insurance Claim Optimization

What's the play?

Cross-reference internal repair cost data by vehicle make/model with public insurance claims data to show insurance adjusters exactly which vehicle models in their portfolio have the highest cost variance from PDR vs traditional body shop repair.

Why this works

Insurance adjusters manage claim costs daily but lack model-specific repair cost intelligence. When you show them "Nissan Altimas cost you 41% more than comparable sedans due to aluminum hood design," you're providing actionable underwriting and rate adjustment data they can't get anywhere else. The specificity of knowing their exact book composition (12,400 Altimas in Texas) proves this isn't a mass email.

Data Sources
  1. DentWizard Internal Repair Database - repair cost by vehicle make/model/year across thousands of repairs
  2. NAIC Auto Insurance Database Reports - collision claims by state, average repair cost per claim, insurer name
  3. State Vehicle Registration Data - vehicle counts by make/model/ZIP

The message:

Subject: Nissan Altimas costing you 41% more in PDR claims Our repair data shows 2019-2022 Nissan Altimas have 41% higher PDR claim costs than comparable sedans due to aluminum hood design. You're insuring 12,400 Altimas in your Texas book based on registration data. Want the full vehicle model cost variance report for your top 20 models?
DATA REQUIREMENT

This play requires aggregated PDR repair cost data by vehicle make/model/year across thousands of repairs, showing cost variance patterns and material construction differences.

This is proprietary data only you have - competitors cannot replicate this synthesis of repair costs with insurer portfolio composition.
PVP Public + Internal Strong (8.6/10)

Post-Hail Inventory Impact Forecasting for Rental Fleets

What's the play?

Cross-reference NOAA seasonal hail forecasts with rental company multi-state operations to provide proactive inventory impact planning. Deliver month-ahead probability forecasts with vehicle exposure calculations and capacity recommendations.

Why this works

Rental fleet managers live in constant fear of catastrophic damage events that pull hundreds of vehicles out of circulation. When you provide a multi-location hail forecast covering all their hail-corridor locations with specific vehicle exposure numbers (8,900 vehicles at risk June 1-30), you're giving them the planning tool they desperately need but don't have. The offer of "day-by-day probability forecast and pre-positioning recommendations" is pure gold for operational planning.

Data Sources
  1. NOAA Storm Events Database - seasonal hail outlooks, event probability, geographic footprint
  2. DentWizard Internal Data - historical damage rates by hail severity, turnaround times, capacity mobilization speed
  3. Rental Company Location Data - lot addresses, vehicle concentrations by ZIP

The message:

Subject: June hail forecast for your 6 hail-corridor locations NOAA's seasonal outlook shows elevated hail risk June 1-30 across all 6 of your hail-corridor locations (Denver, OKC, Dallas, Wichita, Kansas City, Omaha). That's 8,900 vehicles at risk based on your lot concentrations. Want the day-by-day probability forecast and pre-positioning recommendations?
DATA REQUIREMENT

This play requires historical hail damage data showing: damage rates by hail severity, vehicle counts affected per event, turnaround time patterns, and capacity mobilization timelines across multiple locations.

Combined with NOAA forecasts and rental location mapping, this synthesis is unique to your operational history.
PVP Internal Data Strong (8.6/10)

Sensor Recalibration Cost Intelligence

What's the play?

Use internal repair data to identify which newer vehicle models require ADAS sensor recalibration after PDR, adding unexpected costs. Provide insurance adjusters with a recalibration requirement matrix showing which models in their book have hidden cost factors they're not reserving for.

Why this works

Insurance adjusters are getting blindsided by ADAS sensor recalibration costs on 2022+ vehicles. When you tell them "GMC Sierras require sensor recalibration on 73% of PDR repairs, adding $280 per claim," you're surfacing a cost factor they're likely not tracking yet. The quantified annual impact ($151K across 540 claims) makes it immediately actionable for reserve accuracy and rate adjustments. The offer of a full matrix for their top 15 models positions you as the expert who understands the changing economics of auto repair.

Data Sources
  1. DentWizard Internal Repair Database - ADAS sensor recalibration requirements by vehicle make/model/year, frequency percentage, cost per recalibration

The message:

Subject: GMC Sierra sensor recalibration adding $280 per claim 2022+ GMC Sierras require ADAS sensor recalibration after PDR on 73% of repairs, adding $280 per claim. At 540 Sierra claims annually in your Texas book, that's $151K in additional cost. Want the sensor recalibration requirement matrix for your top 15 models?
DATA REQUIREMENT

This play requires repair completion data showing which vehicle models require ADAS sensor recalibration, frequency rates, and associated costs across thousands of repairs.

This is proprietary operational intelligence only you have from servicing 2022+ vehicles with advanced safety systems.
PQS Public + Internal Strong (8.5/10)

Urgent Hail Event Response

What's the play?

Monitor near-term severe weather forecasts (24-48 hours out) and cross-reference with rental fleet locations to deliver urgent damage prevention alerts. Provide specific vehicle counts and historical damage rates to create immediate action urgency.

Why this works

When you tell a fleet manager "2,890 vehicles in tomorrow's hail path" with specific location counts and historical damage rates (71% of vehicles damaged in last April's Tulsa storm), you're delivering time-critical intelligence they need RIGHT NOW. The action-oriented question "Is someone moving vehicles or securing indoor shelter tonight?" positions you as a partner thinking about their operational response, not a vendor pitching services. The extreme urgency (tomorrow's event) breaks through inbox noise.

Data Sources
  1. NOAA Storm Events Database - near-term severe weather forecasts, hail size predictions, geographic paths
  2. Rental Fleet Location Data - lot addresses, vehicle counts by location
  3. DentWizard Historical Data - damage rates by hail severity and location from previous events

The message:

Subject: 2,890 vehicles in tomorrow's hail path Tomorrow's forecast shows severe hail for Tulsa where you operate 2,890 rental vehicles across 6 locations. Last April's Tulsa storm damaged 71% of vehicles in the direct path. Is someone moving vehicles or securing indoor shelter tonight?
DATA REQUIREMENT

This play requires real-time monitoring of NOAA severe weather alerts and historical damage rate data by event severity and location.

The synthesis of near-term forecasts with rental fleet locations and historical damage patterns creates urgency competitors can't match.
PVP Internal Data Strong (8.5/10)

Year-Over-Year Repair Cost Trend Analysis

What's the play?

Track year-over-year PDR repair cost changes by vehicle model and identify which models have experienced significant cost increases due to design changes or new technology integration. Provide insurance adjusters with trend data they can use for rate filing justification.

Why this works

Insurance adjusters struggle to justify rate increases without actuarial-grade data. When you tell them "Ram 1500 PDR costs increased 38% vs 2023 due to new sensor integration in model redesign," you're providing the specific causal explanation and quantified impact ($186K additional exposure across 620 claims) they need for rate filing submissions. The offer of a "model-year cost variance report for rate adjustment" directly supports their regulatory compliance process. This isn't sales - it's data they need to do their job.

Data Sources
  1. DentWizard Internal Repair Database - year-over-year repair costs by vehicle make/model, design change tracking, technology integration notes

The message:

Subject: Ram 1500 repair costs up 38% year-over-year Our 2024 data shows Ram 1500 PDR costs increased 38% vs 2023 due to new sensor integration in model redesign. At 620 Ram claims annually in your Arizona book, that's $186K additional cost exposure. Want the model-year cost variance report for rate adjustment?
DATA REQUIREMENT

This play requires multi-year repair cost tracking by vehicle make/model with causal analysis of design changes and technology integration.

This is proprietary trend intelligence only you have from servicing thousands of vehicles across model years.
PQS Public + Internal Strong (8.4/10)

Post-Damage Verification Alert

What's the play?

Within 72 hours of documented hail events, send rental fleet managers specific vehicle damage estimates based on NOAA severity maps cross-referenced with their lot locations. Provide verifiable vehicle counts and revenue impact calculations.

Why this works

When a hailstorm just hit, fleet managers are in damage assessment mode. By telling them "3,847 vehicles in your Denver ZIP codes got hit in the April 12th hailstorm" with a specific date and NOAA-verified damage count, you're delivering immediate situational intelligence they need for capacity planning. The revenue impact calculation (14 days turnaround = $2.1M revenue loss) translates the damage into business terms they care about. The offer to provide damage forecasts for other locations positions you as someone monitoring their entire footprint, not just responding to this one event.

Data Sources
  1. NOAA Storm Events Database - recent hail events with dates, severity, geographic footprint
  2. Rental Fleet Location Data - lot addresses and ZIP codes
  3. DentWizard Historical Data - average turnaround times by damage severity

The message:

Subject: 3,847 rental cars hail-damaged in Denver last week NOAA confirms 3,847 vehicles in your Denver ZIP codes got hit in the April 12th hailstorm. At 14 days average PDR turnaround, that's potential $2.1M revenue loss if those cars sit idle. Want the damage forecast for your other hail-corridor locations?
DATA REQUIREMENT

This play requires rental fleet location mapping (GPS or addresses) and internal turnaround time data to calculate revenue impact.

The synthesis of NOAA damage data with specific rental locations and operational metrics is unique to your service history.
PQS Public + Internal Strong (8.4/10)

PDR Feasibility Audit for Insurance Claims

What's the play?

Analyze insurance claim photos from public records or data partnerships to identify cases where PDR was viable but traditional body shop methods (hood replacement) were approved instead. Show insurance adjusters specific examples of unnecessary parts and labor costs in their book.

Why this works

Insurance adjusters manage claim costs but often can't distinguish between PDR-viable damage and replacement-required damage without specialized knowledge. When you tell them "47% of Hyundai Sonata hail claims in your book resulted in hood replacement when PDR was viable according to severity photos," you're revealing a systematic process inefficiency costing them $840 per claim. The question "Is someone doing PDR feasibility checks before approving replacements?" positions this as a process improvement opportunity, not a sales pitch. The specificity (210 Sonata claims, severity photos) proves this is real analysis, not a generic claim.

Data Sources
  1. Insurance Claim Photo Databases - damage severity images, approved repair methods
  2. DentWizard Internal Data - PDR feasibility classification criteria by damage type
  3. NAIC Auto Insurance Database - claim volumes by vehicle model and insurer

The message:

Subject: Hyundai Sonata hood replacements avoidable with PDR 47% of Hyundai Sonata hail claims in your book resulted in hood replacement when PDR was viable according to severity photos. That's $840 per claim in unnecessary parts and labor costs across 210 Sonata claims last year. Is someone doing PDR feasibility checks before approving replacements?
DATA REQUIREMENT

This play requires access to insurance claim photos and internal PDR feasibility classification expertise to identify cases where PDR could have replaced traditional repair methods.

The synthesis of claim photo analysis with repair cost data is unique to your technical expertise.
PVP Public + Internal Strong (8.3/10)

Regional Hail Exposure Planning

What's the play?

Provide rental fleet managers with monthly hail probability forecasts covering their multi-state operations, with vehicle exposure calculations and capacity planning recommendations. Deliver this as a planning tool for the upcoming month.

Why this works

Rental companies operating across hail-prone states need regional risk visibility to optimize fleet distribution and pre-position repair capacity. When you provide "May outlook showing 68% probability of significant hail events across your OK-TX-CO-KS locations" with specific vehicle exposure (11,200 vehicles at elevated risk in 30 days), you're giving them the multi-state planning view their internal teams don't have. The offer of "weekly probability breakdown and repair capacity recommendations" turns this from interesting information into an actionable planning tool. This is consulting-grade intelligence delivered for free.

Data Sources
  1. NOAA Storm Events Database - seasonal hail outlooks, regional probability forecasts
  2. Rental Fleet Location Data - multi-state lot addresses and vehicle concentrations
  3. DentWizard Internal Data - capacity availability by region, mobilization timelines

The message:

Subject: May 2025 hail outlook for your 4-state footprint NOAA's May outlook shows 68% probability of significant hail events across your OK-TX-CO-KS locations. That's 11,200 vehicles at elevated risk in a 30-day window. Want the weekly probability breakdown and repair capacity recommendations?
DATA REQUIREMENT

This play requires rental fleet multi-state location mapping and internal capacity availability data by region with mobilization timelines.

Combined with NOAA seasonal forecasts, this creates a planning tool competitors can't offer.
PVP Internal Data Strong (8.3/10)

PDR Cost Efficiency by Vehicle Model

What's the play?

Identify vehicle models where PDR costs come in significantly lower than initial estimates due to favorable construction or panel accessibility. Provide insurance adjusters with positive variance data they can use to optimize reserve amounts and reduce loss adjustment expenses.

Why this works

Insurance adjusters focus heavily on cost overruns but rarely capture positive variance opportunities. When you tell them "Honda CR-Vs average $340 for PDR vs $520 typical, that's a $1.5M annual savings opportunity if you steer policyholders to PDR," you're showing them how to improve loss ratios through better claim handling. The specificity (8,400 repairs, 35% lower costs due to steel panel construction) demonstrates deep technical knowledge. The offer to provide cost breakdowns for their other high-volume models positions you as a strategic partner helping them optimize loss adjustment expenses.

Data Sources
  1. DentWizard Internal Repair Database - actual repair costs by vehicle make/model, construction materials, panel accessibility notes

The message:

Subject: Honda CR-Vs are your cheapest PDR repairs Across 8,400 repairs, Honda CR-Vs average $340 for PDR vs $520 typical - 35% lower due to steel panel construction. That's a $1.5M annual savings opportunity if you steer policyholders to PDR for CR-V claims. Want the cost breakdown for your other high-volume models?
DATA REQUIREMENT

This play requires repair cost data by vehicle make/model across thousands of repairs, showing favorable construction characteristics and cost efficiency patterns.

This is proprietary cost intelligence only you have from servicing high volumes of specific vehicle models.
PQS Public + Internal Strong (8.2/10)

Model-Specific Cost Overrun Alert

What's the play?

Identify vehicle models where actual PDR repair costs consistently exceed initial estimates due to construction complexity (like aluminum body panels). Alert insurance adjusters to specific models in their portfolio where reserves are systematically understated.

Why this works

Insurance adjusters live in fear of reserve inadequacy, which impacts loss ratios and regulatory reporting. When you tell them "Ford F-150s (2020-2023) are coming in 52% over initial estimates due to aluminum body complexity," you're alerting them to a systematic reserve problem in their book. The specificity (3,200 PDR claims analyzed, actual claim volume 840 F-150s in Texas region) proves you've done the analysis. The question "Is someone adjusting initial reserve amounts for these models?" positions this as a process improvement they should care about immediately.

Data Sources
  1. DentWizard Internal Repair Database - initial estimate vs actual cost variance by vehicle make/model
  2. NAIC Auto Insurance Database - claim volumes by vehicle model and insurer

The message:

Subject: Your Ford F-150 claims running 52% over estimate Analyzing 3,200 PDR claims, Ford F-150s (2020-2023) are coming in 52% over initial estimates due to aluminum body complexity. You processed 840 F-150 PDR claims last year in your Texas region. Is someone adjusting initial reserve amounts for these models?
DATA REQUIREMENT

This play requires repair completion data comparing initial estimates to actual costs by vehicle make/model, with construction material tracking.

The variance analysis is unique to your operational history of servicing thousands of vehicles.
PQS Public + Internal Strong (8.2/10)

Vehicle Configuration Cost Impact

What's the play?

Identify vehicle configurations (like convertible soft tops) that dramatically increase PDR repair costs due to additional damage vectors. Show insurance adjusters how capturing configuration details at first notice of loss (FNOL) can improve reserve accuracy.

Why this works

Insurance adjusters typically don't capture vehicle configuration details at FNOL, leading to reserve surprises later. When you tell them "Jeep Wranglers with soft tops average $920 in PDR costs vs $410 for hard tops due to interior damage from hail penetration," you're revealing a specific data point they're missing in their intake process. The quantified savings opportunity ($91K in reserve adjustment accuracy across 180 claims) makes this immediately actionable. The question "Who's capturing vehicle configuration details at FNOL?" positions this as a process improvement with clear ROI.

Data Sources
  1. DentWizard Internal Repair Database - repair costs segmented by vehicle configuration (soft top vs hard top, etc.)
  2. NAIC Auto Insurance Database - claim volumes by vehicle model and state

The message:

Subject: Jeep Wrangler soft tops driving up your PDR costs Jeep Wranglers with soft tops average $920 in PDR costs vs $410 for hard tops due to interior damage from hail penetration. At 180 Wrangler claims last year in your Colorado book, identifying soft vs hard top before estimating could save $91K in reserve adjustments. Who's capturing vehicle configuration details at FNOL?
DATA REQUIREMENT

This play requires repair cost data segmented by vehicle configuration details (convertible tops, sunroofs, etc.) showing cost impact patterns.

This is granular operational intelligence only you have from tracking configuration-specific damage patterns.
PVP Public + Internal Strong (8.1/10)

Localized Damage Estimate by ZIP

What's the play?

Within 48 hours of a documented hail event, send rental fleet managers vehicle-by-vehicle damage probability estimates based on NOAA severity maps layered with their specific lot locations. Provide actionable vehicle counts for logistics planning.

Why this works

After a hailstorm hits, fleet managers need to triage which locations were affected and how many vehicles need inspection. When you tell them "April 12th hailstorm damaged an estimated 892 vehicles in your Colorado Springs locations based on NOAA severity maps," you're providing immediate operational intelligence. The conversion to business impact (535 cars out of circulation for 2+ weeks if 60% need PDR) helps them quantify the problem. The offer of "vehicle-by-vehicle damage probability report" gives them the granular logistics data they need for scheduling inspections and coordinating repairs.

Data Sources
  1. NOAA Storm Events Database - hail event dates, severity maps, geographic footprint
  2. Rental Fleet Location Data - specific lot addresses in affected areas
  3. DentWizard Internal Data - damage probability by hail severity, typical repair needs

The message:

Subject: Your Colorado Springs fleet just got hit April 12th hailstorm damaged an estimated 892 vehicles in your Colorado Springs locations based on NOAA severity maps. If 60% need PDR, that's 535 cars out of circulation for 2+ weeks. Want the vehicle-by-vehicle damage probability report?
DATA REQUIREMENT

This play requires rental fleet location mapping and internal damage probability modeling by hail severity level.

The synthesis of NOAA severity data with specific lot locations creates immediate operational value.
PVP Internal Data Strong (8.1/10)

PDR Success Rate Benchmarking

What's the play?

Provide insurance adjusters with PDR success rate benchmarks by vehicle model, showing which models have the highest likelihood of successful repair without paint or panel replacement. Help them optimize claim steering policies based on model-specific success rates.

Why this works

Insurance adjusters want to maximize PDR utilization (lower costs) but lack data on which vehicle models are best candidates. When you tell them "Chevrolet Equinox has a 94% PDR success rate - highest in the SUV class," you're giving them confidence to steer claims to PDR for that specific model. The fact that you know their claim volume (380 Equinox claims last year in Michigan) shows this is tailored intelligence, not generic marketing. The offer of success rate benchmarks for other high-volume models helps them build systematic claim handling protocols.

Data Sources
  1. DentWizard Internal Repair Database - PDR success rates by vehicle make/model, showing percentage resolved without paint or panel replacement

The message:

Subject: Chevrolet Equinox PDR success rate: 94% Across 1,600 Equinox repairs, PDR resolved 94% of claims without paint or panel replacement - highest in the SUV class. You processed 380 Equinox claims last year in your Michigan book. Want the success rate benchmarks for your other high-volume models?
DATA REQUIREMENT

This play requires repair outcome data by vehicle make/model showing PDR success rates vs cases requiring paint or panel replacement.

This is proprietary outcome intelligence only you have from completing thousands of repairs per model.
PQS Public + Internal Strong (8.0/10)

Pre-Event Hail Warning

What's the play?

Send rental fleet managers 7-day advance warnings when NOAA forecasts show severe hail probability for their operating regions, with vehicle exposure calculations and historical damage rate context. Provide enough lead time for proactive response.

Why this works

Seven days advance notice allows fleet managers to actually do something about incoming hail risk - move vehicles, secure covered parking, pre-position staff. When you tell them "NOAA's 7-day forecast shows severe hail probability for Oklahoma City April 15-22 where you operate 2,100 rental vehicles," you're giving them actionable lead time. The historical context (last year's April storm damaged 68% of vehicles in the hail corridor) helps them understand the magnitude of potential impact. The question "Is someone coordinating pre-positioning or rapid response PDR capacity?" helps them route to the right internal stakeholder.

Data Sources
  1. NOAA Storm Events Database - 7-day severe weather forecasts, hail probability
  2. Rental Fleet Location Data - operating regions and vehicle counts
  3. DentWizard Historical Data - historical damage rates by region and hail severity

The message:

Subject: Oklahoma City gets hit with hail April 15-22 NOAA's 7-day forecast shows severe hail probability for Oklahoma City April 15-22 where you operate 2,100 rental vehicles. Last year's April storm damaged 68% of vehicles in the hail corridor. Is someone coordinating pre-positioning or rapid response PDR capacity?
DATA REQUIREMENT

This play requires rental fleet location identification and historical damage rate data from previous events in the same region.

The synthesis of forecast data with historical outcomes creates actionable planning intelligence.
PQS Public + Internal Strong (8.0/10)

Imminent Hail Impact Alert

What's the play?

Send same-day hail alerts when NOAA forecasts show severe hail hitting rental fleet locations within hours. Provide specific vehicle counts at risk and percentage of fleet exposure to create maximum urgency.

Why this works

When severe hail is hitting TONIGHT, the urgency is absolute. By telling them "Tonight's forecast shows golf ball-size hail for ZIP 75201-75204 where you have 1,240 vehicles," you're delivering time-critical intelligence they need in the next few hours. The conversion to fleet percentage (31% of DFW fleet at risk in a 4-hour window) helps them understand business impact. The routing question "Who handles your emergency damage response coordination?" acknowledges you might not be talking to the right person but need to get this intelligence to whoever IS responsible immediately.

Data Sources
  1. NOAA Storm Events Database - same-day severe weather alerts, hail size predictions, timing
  2. Rental Fleet Location Data - lot addresses by ZIP code, vehicle counts by location

The message:

Subject: 1,240 of your Dallas cars in hail zone tonight Tonight's forecast shows golf ball-size hail for ZIP 75201-75204 where you have 1,240 vehicles based on your lot addresses. That's 31% of your DFW fleet at risk in a 4-hour window. Who handles your emergency damage response coordination?
DATA REQUIREMENT

This play requires rental fleet location mapping by ZIP code and real-time monitoring of NOAA severe weather alerts.

The time-critical nature and specific ZIP-level targeting creates immediate urgency competitors can't match.
PQS Public + Internal Okay (7.9/10)

Rental Delay Cost Quantification

What's the play?

Identify vehicle models where PDR turnaround times are significantly longer than comparable vehicles, driving up rental reimbursement expenses for insurance adjusters. Quantify the exact rental day exposure and cost impact.

Why this works

Insurance adjusters track rental reimbursement costs closely but may not realize certain vehicle models drive disproportionate rental expenses due to longer repair times. When you tell them "Tesla Model 3 PDR repairs average 9 additional days vs comparable sedans due to technician certification requirements," you're surfacing a hidden cost driver. The calculation of exact exposure (4,320 extra rental days across 480 claims annually) makes this immediately quantifiable. The routing question "Who manages your rental reimbursement expense tracking?" helps get this to the right cost control stakeholder.

Data Sources
  1. DentWizard Internal Repair Database - turnaround times by vehicle make/model, certification requirements
  2. NAIC Auto Insurance Database - claim volumes by vehicle model and state

The message:

Subject: Tesla Model 3 PDR claims taking 9 days longer Tesla Model 3 PDR repairs average 9 additional days vs comparable sedans due to technician certification requirements. At 480 Model 3 claims annually in your California book, that's 4,320 extra rental days you're covering. Who manages your rental reimbursement expense tracking?
DATA REQUIREMENT

This play requires turnaround time tracking by vehicle make/model with causal analysis of delay factors (certification requirements, parts availability, etc.).

The synthesis of turnaround data with claim volumes creates specific cost impact intelligence.
PQS Public + Internal Okay (7.8/10)

Reserve Accuracy Opportunity

What's the play?

Identify vehicle models where actual PDR costs consistently come in under initial reserves, creating opportunities for loss adjustment expense optimization. Show insurance adjusters where they're over-reserving and can improve reserve release timing.

Why this works

While insurance adjusters worry about reserve inadequacy, they also care about reserve accuracy for financial reporting and loss ratio optimization. When you tell them "Subaru Outbacks are consistently coming in 22% under initial PDR estimates due to steel construction and panel accessibility," you're showing them where they can optimize reserve amounts. The specific numbers (reserving $520 but actual costs are $405 across 290 claims) proves this is real analysis. The question "Is someone capturing this reserve release for LAE optimization?" positions this as a financial reporting opportunity they should care about.

Data Sources
  1. DentWizard Internal Repair Database - initial estimate vs actual cost variance by vehicle make/model
  2. NAIC Auto Insurance Database - claim volumes by vehicle model and state

The message:

Subject: Subaru Outback repairs costing 22% less than estimates Subaru Outbacks are consistently coming in 22% under initial PDR estimates due to steel construction and panel accessibility. You're reserving $520 average but actual costs are $405 across 290 claims last year in your Colorado book. Is someone capturing this reserve release for LAE optimization?
DATA REQUIREMENT

This play requires comparison of initial reserve amounts to actual repair costs by vehicle make/model, showing favorable variance patterns.

The variance tracking is unique to your operational history of estimating and completing thousands of repairs.
PQS Public + Internal Okay (7.7/10)

Fleet Expansion Risk Monitoring

What's the play?

Track rental fleet location expansion in hail-prone regions and alert fleet managers when they're scaling into higher-risk geographies. Provide historical hail frequency data for their new markets.

Why this works

Fleet managers expanding into new markets may not realize the hail risk profile of their new locations. When you tell them "Your Austin locations added 420 vehicles in Q1, putting you at 2,100 total. Austin sits in the I-35 hail corridor with 7 severe events in the past 3 years," you're connecting their growth strategy to operational risk they need to plan for. The question "Who's managing damage preparedness as you scale that market?" positions this as a risk management conversation relevant to their expansion. The fact that you tracked their fleet growth (lot counts) shows you're paying attention to their business.

Data Sources
  1. Rental Fleet Location Data - lot addresses and vehicle counts tracked over time
  2. NOAA Storm Events Database - historical hail events by region

The message:

Subject: Your Austin fleet expanding into hail alley Your Austin locations added 420 vehicles in Q1 based on lot counts, putting you at 2,100 total. Austin sits in the I-35 hail corridor with 7 severe events in the past 3 years. Who's managing damage preparedness as you scale that market?
DATA REQUIREMENT

This play requires tracking rental fleet locations and vehicle counts over time to identify expansion patterns.

Combined with NOAA historical hail data, this creates risk planning intelligence for growing companies.
PVP Public + Internal Okay (7.2/10)

Near-Miss Event Tracking

What's the play?

After major hail events, identify rental fleet locations that narrowly avoided damage and quantify the potential cost impact they dodged. Demonstrate proactive monitoring of their entire footprint.

Why this works

Near-miss reporting is a novel approach that shows you're monitoring their fleet proactively, not just reacting to damage events. When you tell them "Last week's storm tracking showed Phoenix was 8 miles outside the hail corridor that damaged 2,400 vehicles," you're demonstrating that you're watching their risk exposure continuously. The quantification of what they avoided ($650 average per vehicle across 1,850 Phoenix vehicles = $1.2M) helps them understand the stakes. However, the immediate value is questionable - knowing they dodged a bullet is interesting but not immediately actionable. The offer of "near-miss report for other Sun Belt locations" is moderately compelling.

Data Sources
  1. NOAA Storm Events Database - hail storm paths and severity footprints
  2. Rental Fleet Location Data - lot addresses in nearby but unaffected areas
  3. DentWizard Internal Data - average repair costs by hail severity

The message:

Subject: Your Phoenix fleet dodged $1.2M in hail damage Last week's storm tracking showed Phoenix was 8 miles outside the hail corridor that damaged 2,400 vehicles. Your 1,850 Phoenix vehicles would have averaged $650 each in PDR costs based on severity. Want the near-miss report for your other Sun Belt locations?
DATA REQUIREMENT

This play requires rental fleet location mapping and tracking of NOAA hail storm paths to identify near-miss scenarios.

The proactive monitoring demonstrates risk management partnership but value is more contextual than immediately actionable.

What Changes

Old way: Spray generic messages at job titles. Hope someone replies.

New way: Use public and proprietary data to find companies in specific painful situations. Then mirror that situation back to them with evidence.

Why this works: When you lead with "3,847 vehicles in your Denver locations got hit in the April 12th hailstorm" instead of "I see you manage a large fleet," you're not another sales email. You're the person who did the homework.

The messages above aren't templates. They're examples of what happens when you combine real data sources with specific situations. Your team can replicate this using the data recipes in each play.

Data Sources Reference

Every play traces back to verifiable data sources. Here are the sources used in this playbook:

Source Key Fields Used For
NOAA Storm Events Database event_type, hail_size, county, state, property_damage_amount, event_date Hail event tracking, severity mapping, seasonal forecasts, geographic damage prediction
NAIC Auto Insurance Database Reports collision_claims_by_state, average_repair_cost_per_claim, claims_severity, insurer_name, repair_cost_trends Insurance claims cost benchmarking, insurer-specific claim volumes, repair cost trends
DentWizard Internal Repair Database repair_cost_by_vehicle_model, damage_severity, turnaround_time, PDR_feasibility, ADAS_recalibration_requirements Vehicle-specific repair intelligence, cost variance analysis, success rates, turnaround patterns
State Vehicle Registration Data vehicle_counts_by_make_model, registration_by_ZIP, insurer_portfolio_composition Insurer portfolio analysis, geographic vehicle distribution, model-specific targeting
Rental Fleet Location Data lot_addresses, vehicle_counts_by_location, ZIP_codes, fleet_size_tracking Geographic risk mapping, vehicle exposure calculations, expansion tracking
Insurance Claim Photo Databases damage_severity_images, approved_repair_methods, claim_outcomes PDR feasibility analysis, repair method optimization, cost efficiency identification