Blueprint Playbook for Teletrac Navman

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 Teletrac Navman SDR Email:

Subject: Improve your fleet safety and compliance Hi [First Name], I noticed your company operates a fleet of commercial vehicles. At Teletrac Navman, we help companies like yours improve safety, reduce costs, and stay compliant with DOT regulations. Our platform provides real-time GPS tracking, driver behavior monitoring, and ELD compliance tools that have helped hundreds of fleets reduce accidents by up to 30%. Would you be open to a quick 15-minute call to discuss how we could help your operation? Best regards, [SDR Name]

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 compliance people" (job postings - everyone sees this)

Start: "Your fleet recorded 3 Hours of Service violations between September 15th and November 10th" (FMCSA database with specific dates and counts)

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, violation codes, and facility-specific records.

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

Teletrac Navman GTM Plays: Data-Driven Intelligence

These messages demonstrate precise understanding of the prospect's situation (PQS) or deliver immediate actionable value (PVP). Every claim traces to verifiable data sources.

PVP Public + Internal Strong (9.4/10)

Driver Behavior Risk Score with Violation Prediction

What's the play?

Cross-reference internal telematics data (harsh braking frequency, speeding patterns, HOS pressure) with public FMCSA violation records to identify specific drivers on trajectory toward citations. Deliver driver-specific risk scores with names, behaviors, and intervention recommendations.

Why this works

You're naming the specific driver at risk and showing the exact behavioral pattern that precedes violations. The 340-driver sample size creates credibility. The $2K citation cost quantifies immediate financial impact. You're offering a proven coaching protocol from similar cases - this is prevention they can implement TODAY.

Data Sources
  1. Internal Customer Telematics Data - harsh braking events per 1,000 miles, speeding events, consecutive drive hours, rest period patterns
  2. FMCSA Roadside Inspection Violations - violation codes, inspection dates, HOS violation patterns

The message:

Subject: Your Driver 4387 matches violation pattern Driver ID 4387 in your fleet shows the same telematics signature we've seen in 340 drivers who later got HOS violations - consecutive 13+ hour days, late-night pattern shifts, irregular rest periods. Intervening now could prevent a $2,000+ citation and CSA points. Want the coaching protocol that worked for the 340?
DATA REQUIREMENT

This play requires aggregated telematics data from your customer base showing harsh braking frequency, speeding events, and driving hour patterns, correlated with subsequent FMCSA violation outcomes across 1,000+ incidents to build a predictive risk scoring model.

This synthesis of internal behavioral data + public violation records is unique to your business. Competitors cannot replicate this insight.
PVP Public + Internal Strong (9.1/10)

Predictive Driver Risk List

What's the play?

Analyze fleet telematics patterns against 50,000+ DOT violation records to identify drivers showing behavioral markers that precede HOS citations. Deliver specific count of at-risk drivers with names, behaviors, and intervention recommendations.

Why this works

You're quantifying the exact number of at-risk drivers (12), explaining the massive data synthesis (50K violation records), and promising actionable names and behaviors. This helps them prevent violations BEFORE they happen - protecting safety ratings and insurance costs. The value is immediate and defensible.

Data Sources
  1. Internal Customer Telematics Data - driver behavior patterns, HOS compliance metrics, fatigue indicators
  2. FMCSA Roadside Inspection Violations - 50,000+ violation records with behavioral precursors

The message:

Subject: 12 drivers trending toward HOS violations Cross-referenced your fleet's telematics patterns against 50,000+ DOT violation records - 12 of your drivers show behavioral markers that precede HOS citations. I've got their names, specific behaviors, and intervention recommendations. Want the risk list?
DATA REQUIREMENT

Requires continuous telematics monitoring across customer fleet base with risk scoring algorithm trained on 1,000+ incidents correlating specific driver behaviors to subsequent FMCSA violations.

The predictive model combining internal behavioral data with public violation patterns is proprietary to your business.
PVP Public + Internal Strong (8.9/10)

Proven Onboarding Protocol for Scaling Fleets

What's the play?

Analyze customer fleets that scaled 30%+ without safety metric decline. Extract their 28-day driver onboarding protocol with 6 specific checkpoints. Deliver this proven checklist to carriers showing rapid growth with deteriorating safety scores.

Why this works

You're addressing the root cause (onboarding quality) with a concrete, implementable solution (28-day protocol with 6 checkpoints). The 40-carrier sample creates credibility. Tying it directly to their 34 new drivers makes it immediately relevant. They can use this checklist TODAY to prevent further safety decline.

Data Sources
  1. Internal Customer Fleet Data - analysis of 40+ fleets that scaled operations 30%+ while maintaining safety metrics
  2. FMCSA Safety Measurement System - safety scores during growth periods

The message:

Subject: Onboarding checklist from stable growth fleets Studied 40 carriers who scaled 30%+ without safety metric decline - they use a 28-day driver onboarding protocol with 6 specific checkpoints. Your 34 new drivers in 10 months would benefit from the same structure. Want the onboarding checklist?
DATA REQUIREMENT

Requires analysis of customer fleets that maintained or improved safety metrics during significant growth periods, synthesized into documented onboarding best practices with specific checkpoints and timelines.

This analysis of successful scaling patterns across your customer base is proprietary intelligence competitors cannot access.
PVP Public Data Strong (8.8/10)

High-Risk Vehicle Identification

What's the play?

Pull FMCSA roadside inspection history to identify specific vehicles accounting for majority of Out-of-Service events. Map each vehicle's failure patterns to inspection categories (brakes, lights, HOS documentation). Deliver actionable vehicle list with failure patterns.

Why this works

You're providing specific vehicle counts (9 vehicles), quantifying their impact (67% of OOS events), and offering categorized failure patterns. This helps them focus maintenance resources on the highest-risk assets. The six-month timeframe is recent and actionable. Easy yes to receive the list.

Data Sources
  1. FMCSA Roadside Inspection Data - vehicle-specific OOS events, inspection categories, violation codes

The message:

Subject: OOS vehicle list for your Q1 inspections Pulled your fleet's roadside inspection history - 9 vehicles accounting for 67% of your OOS events in the past 6 months. I've mapped which inspection categories each vehicle fails (brakes, lights, HOS documentation). Want the vehicle list with failure patterns?
PVP Public + Internal Strong (8.8/10)

Conditional Rating Audit Preparation

What's the play?

Combine public FMCSA rating data with internal customer audit preparation timelines. Identify carriers with Conditional ratings facing typical 8-12 month compliance review window. Deliver proven 90-day audit prep plan used by fleets that passed reviews.

Why this works

You're creating urgency with specific timeframes (8-12 months typical, they're at month 3). The 25 fleets who passed creates credibility. The 90-day plan is concrete and actionable. This helps them prepare BEFORE the audit hits, increasing pass probability significantly.

Data Sources
  1. FMCSA SAFER System - safety rating changes, rating dates, Conditional status
  2. Internal Customer Data - audit preparation timelines and success rates from 25+ fleets who passed compliance reviews

The message:

Subject: Audit prep timeline for Conditional fleets Carriers with Conditional ratings typically face FMCSA compliance review within 8-12 months - you're at month 3 since your October rating change. I've got the 90-day audit prep plan used by 25 fleets who passed their reviews. Want the timeline?
DATA REQUIREMENT

Requires documentation of audit preparation timelines, compliance improvement actions, and success rates from customer fleets that successfully restored Satisfactory ratings after Conditional status.

This synthesis of internal audit success patterns with public rating data creates unique predictive guidance.
PQS Public Data Strong (8.7/10)

Rapid Scaling with Safety Decline

What's the play?

Use FMCSA Motor Carrier Registration Census to track fleet size changes (power units added). Cross-reference with FMCSA SMS data to identify carriers where crash rates increased during expansion. Calculate percentile movement to show relative safety decline.

Why this works

You're citing specific vehicle counts (85 to 119), exact timeframe (January to November), and quantified crash rate doubling (0.8 to 1.6 per million miles). The percentile movement (70th to 35th) shows clear relative decline. You're tying directly to root cause (onboarding quality) making it immediately actionable.

Data Sources
  1. FMCSA Motor Carrier Registration Census - power units, driver counts, year-over-year changes
  2. FMCSA Safety Measurement System - crash rates, crash counts, percentile rankings

The message:

Subject: Fleet grew 40% but crash rate doubled Your fleet expanded from 85 to 119 vehicles between January and November 2024, but your crash rate went from 0.8 to 1.6 per million miles. That's moving you from the 70th percentile to 35th percentile in your category. Who's managing driver onboarding quality?
PVP Public + Internal Strong (8.7/10)

Vehicle Pre-Inspection Protocol

What's the play?

Combine public OOS data (identifying high-risk vehicles) with internal analysis of low-OOS-rate customer maintenance protocols. Extract the specific pre-inspection checklist used by carriers with 2% OOS rates. Deliver to carriers with 18%+ OOS rates.

Why this works

You're addressing their immediate pain (18% OOS rate vs 2% benchmark). Making it specific to their 9 problem vehicles creates urgency. The checklist is immediately usable by maintenance teams. This prevents roadside OOS events, vehicle downtime, and inspection delays starting TODAY.

Data Sources
  1. FMCSA Roadside Inspection Data - vehicle-specific OOS rates and patterns
  2. Internal Customer Data - maintenance protocols from fleets with 2% OOS rates showing pre-inspection checklists by vehicle class

The message:

Subject: Pre-inspection checklist for your 9 OOS vehicles Your 9 highest-OOS-risk vehicles need a pre-inspection protocol before they hit the road - I've got the checklist used by carriers with 2% OOS rates. It covers the exact items inspectors flag most in your vehicle class. Want the checklist for your maintenance team?
DATA REQUIREMENT

Requires documented maintenance protocols and pre-inspection checklists from customer fleets with consistently low OOS rates, analyzed by vehicle class and inspection category.

This synthesis of public OOS data with internal best-practice protocols creates actionable prevention guidance.
PVP Public + Internal Strong (8.6/10)

Proven Rating Recovery Sequence

What's the play?

Analyze customer fleets that successfully climbed from Conditional to Satisfactory ratings. Identify the common violation categories they fixed first. Cross-reference with prospect's current violation profile to show which 3 of 4 critical categories they have.

Why this works

The 180-carrier sample creates pattern credibility. Specific timeframe (12-18 months) sets realistic expectations. Showing they have 3 of 4 problem areas makes it specific to their situation. You're offering proven sequence not generic advice - this helps them restore Satisfactory rating and regain contract eligibility.

Data Sources
  1. Internal Customer Data - analysis of 180+ fleets that improved from Conditional to Satisfactory, showing violation category fix sequences
  2. FMCSA Safety Measurement System - violation categories by BASIC, rating changes

The message:

Subject: Rating improvement roadmap for your fleet Analyzed 180 carriers who climbed from Conditional to Satisfactory in 12-18 months - they all fixed the same 4 violation categories first. Your fleet has violations in 3 of those 4 categories right now. Want the priority fix sequence that worked for them?
DATA REQUIREMENT

Requires analysis of customer fleets that successfully improved safety ratings, documenting which violation categories were addressed in what sequence and the time to rating improvement.

This pattern analysis across successful rating improvements is proprietary intelligence.
PVP Public + Internal Strong (8.5/10)

Leading Indicator Dashboard for Growth

What's the play?

Identify the 8 leading indicators that predict safety decline during fleet growth by analyzing customer fleets that scaled successfully. Package as monitoring dashboard. Target carriers showing rapid vehicle expansion with deteriorating metrics.

Why this works

You're providing structure (8 specific leading indicators) tied to their growth (34-vehicle expansion). The 60 fleets using it creates proof. Weekly tracking is operationally useful. This prevents problems before they hit FMCSA scores - proactive protection during continued expansion.

Data Sources
  1. Internal Customer Data - leading safety indicators from 60+ fleets that scaled operations without safety metric decline
  2. FMCSA Safety Measurement System - safety scores during growth periods

The message:

Subject: Safety KPI dashboard for growing fleets Built a dashboard tracking the 8 leading indicators that predict safety decline during fleet growth - your 34-vehicle expansion would benefit from tracking them weekly. It's what 60 scaling fleets use to catch problems before they hit FMCSA scores. Want to see the dashboard?
DATA REQUIREMENT

Requires identification of leading safety indicators from customer fleets that scaled successfully, packaged as monitoring dashboard with weekly tracking metrics and alert thresholds.

The leading indicator identification from successful scaling fleets is proprietary analysis.
PQS Public Data Strong (8.5/10)

Recent Rating Downgrade Alert

What's the play?

Monitor FMCSA SAFER System for recent safety rating changes from Satisfactory to Conditional. Target carriers within 3 months of downgrade when urgency is highest and consequences are becoming clear.

Why this works

You're citing specific date (October 3rd) and exact rating change - verifiable in 30 seconds. Federal contract impact hits revenue for some carriers. Insurance audit mention creates financial urgency. Easy routing question. The combination creates immediate pain recognition.

Data Sources
  1. FMCSA SAFER System - safety rating, rating change date, carrier status

The message:

Subject: Your FMCSA rating dropped to Conditional Your FMCSA safety rating changed from Satisfactory to Conditional on October 3rd, 2024. Conditional status blocks federal contract eligibility and triggers shipper insurance audits. Who's leading your rating improvement plan?
PVP Public + Internal Strong (8.4/10)

Proactive Dispatch Risk Alerts

What's the play?

Offer weekly email alerts to dispatch teams showing driver risk scores before each week's routes - who's trending toward fatigue, HOS pressure, or inspection risk. Use same alert system 80 fleets use for route reassignment decisions.

Why this works

Weekly cadence is operationally useful for dispatch planning. Specific use case (route reassignment to shorter routes) is immediately actionable. 80 fleets using it creates social proof. This helps dispatch make better daily decisions to prevent violations. Easy yes/no with low commitment.

Data Sources
  1. Internal Customer Telematics Data - continuous monitoring with risk scoring algorithm for fatigue, HOS compliance, inspection readiness
  2. FMCSA Roadside Inspection Data - inspection risk factors

The message:

Subject: Weekly risk alerts for your dispatch team I can send your dispatch team a weekly email with driver risk scores before each week's routes - who's trending toward fatigue, HOS pressure, or inspection risk. It's the same alert system 80 fleets use to reassign high-risk drivers to shorter routes. Want me to set it up for your team?
DATA REQUIREMENT

Requires continuous telematics monitoring with predictive risk scoring algorithm, delivered as operational alerts via weekly email distribution system.

The real-time risk scoring and alert delivery system is proprietary to your platform.
PQS Public Data Strong (8.3/10)

Escalating Out-of-Service Rate

What's the play?

Track quarterly OOS rates from FMCSA roadside inspection data. Identify carriers with significant quarter-over-quarter increases (9% to 18%). Show how current rate compares to national benchmarks to create urgency.

Why this works

Specific quarters (Q3 to Q4) and percentages create credibility. The 2x increase (9% to 18%) is alarming. Comparison to national benchmark creates clear context. FMCSA compliance review threat is real. Ties to driver behavior which is actionable root cause.

Data Sources
  1. FMCSA Roadside Inspection Data - OOS rates, quarterly trends, inspection counts

The message:

Subject: Your roadside OOS rate jumped to 18% Your fleet's Out-of-Service rate hit 18% in Q4 2024 - up from 9% in Q3. At 18%, you're triggering FMCSA compliance review thresholds. Is someone already working the driver behavior issue?
PQS Public Data Strong (8.2/10)

Growth Outpacing Training Infrastructure

What's the play?

Track fleet size growth from FMCSA Motor Carrier Census. Cross-reference with driver inspection failure rates. Identify pattern where rapid vehicle addition correlates with declining driver inspection performance.

Why this works

Specific vehicle addition count (34 since January) shows you did research. Inspection failure rate change (12% to 23%) is measurable and alarming. "Growth outpacing training" is insightful framing that addresses root cause. Focuses on training capacity not just driver behavior.

Data Sources
  1. FMCSA Motor Carrier Registration Census - power units, year-over-year changes
  2. FMCSA Roadside Inspection Data - driver inspection failure rates

The message:

Subject: 119 trucks now - safety program keeping pace? You added 34 vehicles since January but your driver inspection failure rate climbed from 12% to 23%. Rapid growth often outpaces safety training infrastructure - you're showing that pattern. Is someone already addressing the training capacity gap?
PQS Public Data Strong (8.1/10)

Dual-Agency Enforcement Trigger

What's the play?

Cross-reference EPA RCRAInfo hazmat handler compliance status with FMCSA safety ratings. Identify transporters with both EPA violations AND Conditional FMCSA ratings - this combination triggers enhanced DOT monitoring.

Why this works

Specific month for EPA violation (August 2024) shows research depth. Shows understanding of cross-agency enforcement pattern that most carriers miss. Conditional rating already verified. Question addresses coordination gap between EPA and DOT compliance efforts.

Data Sources
  1. EPA RCRAInfo - handler compliance status, violation dates, EPA ID numbers
  2. FMCSA SAFER System - safety rating, Conditional status

The message:

Subject: EPA violation + Conditional rating = audit Your fleet has an open EPA manifesting violation from August 2024 and FMCSA Conditional rating. That combination puts you on DOT's enhanced monitoring list for cross-agency enforcement. Is your compliance team coordinating across both agencies?
PQS Public Data Okay (7.8/10)

HOS Violation Pattern Triggering Audit Window

What's the play?

Monitor FMCSA roadside inspection violations for HOS citation patterns. Identify carriers with 3+ HOS violations within 90 days - this triggers DOT pattern enforcement and audit eligibility.

Why this works

Specific timeframe (September 15th to November 10th) and count (3 violations) shows research. DOT audit trigger at 3+ violations in 90 days is real and creates urgency. Easy routing question. However, doesn't specify which drivers or vehicles - that detail would strengthen it.

Data Sources
  1. FMCSA Roadside Inspection Violations - HOS violation codes, violation dates, inspection records

The message:

Subject: 3 HOS violations in 60 days - audit risk Your fleet recorded 3 Hours of Service violations between September 15th and November 10th. DOT pattern enforcement triggers at 3+ violations in 90 days - you're in the audit window now. Who's handling your HOS compliance documentation?

What Changes

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

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

Why this works: When you lead with "Your fleet recorded 3 HOS violations between September 15th and November 10th" instead of "I see you're hiring for safety roles," 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. Here are the sources used in this playbook:

Source Key Fields Used For
FMCSA Safety Measurement System (SMS) carrier_name, usdot_number, safety_rating, basic_scores, hos_violations, crash_count Identifying carriers with escalating HOS violations, deteriorating safety metrics, crash rate trends
FMCSA SAFER System carrier_name, usdot_number, safety_rating, roadside_inspection_data, out_of_service_violations, hazmat_flag Rating changes, OOS patterns, carrier snapshot data
FMCSA Motor Carrier Registration Census carrier_name, usdot_number, power_units, drivers, operating_authority, hazmat_flag Fleet growth tracking, scaling operations without proportional safety improvements
FMCSA Roadside Inspection Violations carrier_name, usdot_number, inspection_date, violation_code, out_of_service, severity_level Specific violation patterns, OOS events, vehicle-specific failure categories
EPA RCRAInfo - Hazardous Waste Handler Search handler_name, epa_id_number, compliance_status, permit_status, regulated_waste_types Hazmat transporter compliance status, dual-agency enforcement triggers
Internal Customer Telematics Data harsh_braking_events, speeding_patterns, consecutive_drive_hours, driver_risk_scores Predictive driver risk scoring, behavioral markers preceding violations (HYBRID/PRIVATE plays)
Internal Customer Fleet Data onboarding_protocols, safety_improvement_timelines, audit_prep_success_rates, maintenance_checklists Proven best practices from successful customer fleets (HYBRID/PRIVATE plays)