About This Playbook
Created by Jordan Crawford, founder of Blueprint GTM. This playbook demonstrates how to use hard government data to identify prospects in acute pain—before your competitors even know they exist.
The methodology: Find prospects whose publicly documented situations create urgent need for your product. No guessing, no soft signals, no spray-and-pray. Just surgical precision backed by verifiable data.
The Old Way (Generic SDR Outreach)
- Generic trigger: "Recently expanded" is vague, unverified, and doesn't indicate pain
- Feature dumping: Lists capabilities without connecting to specific problems
- Unverifiable claims: "15-20% savings" is an industry average, not their situation
- High friction: Asking for 15-minute meeting before proving value
- No urgency: Nothing suggests they need to act now vs. next quarter
The New Way (Data-Driven Pain Identification)
What Makes a Strong Message?
Hard Data vs Soft Signals:
- ❌ SOFT: "I saw you're hiring" / "Congrats on the funding" / "Noticed your growth"
- ✅ HARD: EPA violation #2024-RCRA-08821 from November 15, 2025 / DOT incident report with $47,200 damages / FDA Class I recall #F-2025-08821
PQS (Pain-Qualified Segment) Messages:
Identify prospects in acute pain using government data. Goal: Make them reply "how did you know that?" These messages mirror exact situations with specific details the prospect can verify.
Strong PQS Criteria (7.0-8.4/10):
- Hyper-specific details (violation numbers, dates, facility addresses)
- Government data sources (EPA, FMCSA, FDA, OSHA, DOT)
- Non-obvious synthesis (connects data points they don't track)
- Low-effort reply (yes/no or "send details")
The Plays
Target chemical manufacturers with EPA violations who are unknowingly using carriers with recent DOT hazmat incidents. They selected carriers based on price without checking PHMSA incident reports or FMCSA safety ratings. This cross-database synthesis reveals compounding compliance risk they can't see in their own systems.
Why This Works:
- Situation Recognition (9/10): Exact violation numbers, carrier DOT numbers, incident dates, damage amounts
- Data Credibility (10/10): EPA ECHO + DOT PHMSA + FMCSA = all verifiable government records
- Insight Value (9/10): They know about their EPA violations but don't track PHMSA incident reports for contracted carriers—high-value synthesis
- Emotional Resonance (9/10): Same-month correlation (facility violation + carrier incident) creates immediate urgency
- EPA ECHO - Facility violations, RCRA/NPDES programs (API: data.epa.gov/efservice/)
- DOT PHMSA Incident Reports - Hazmat carrier incidents, damages, dates (CSV downloads)
- FMCSA SAFER - Carrier safety ratings, OOS rates (API: mobile.fmcsa.dot.gov)
Confidence Level: 95% (pure government data, no inference required)
Calculation Worksheet (Internal Documentation)
- Source: DOT PHMSA Incident Reports CSV
- Fields: CARRIER_NAME, DOT_NUMBER, INCIDENT_DATE, HAZMAT_CLASS (Class 8 = corrosive), DAMAGES_AMOUNT
- Method: Filter CSV by carrier DOT number and date range, extract incident details
- Verification: Download PHMSA data, search DOT #2847392, view incident report
- Source: EPA ECHO API
- Fields: REGISTRY_ID, VIOLATION_ID, VIOLATION_DATE, RCRA_FLAG
- Method: Query EPA ECHO for facility, filter RCRA violations, match date range
- Verification: Visit echo.epa.gov, search facility, view violations tab
Target facilities with EPA violations that are using carriers with bottom-percentile hazmat out-of-service (OOS) rates. They selected carriers based on price and availability without checking FMCSA safety data. TMS provides carrier safety ratings during rate comparison to prevent compliance risk.
Why This Works:
- Situation Recognition (9/10): Exact EPA violation number, facility address, carrier DOT number, specific OOS percentage
- Data Credibility (9/10): EPA and FMCSA are trusted government sources, easy to verify
- Insight Value (9/10): Most logistics teams don't track carrier hazmat OOS rates—they select on price. Connecting facility violations to carrier risk is non-obvious synthesis.
- Emotional Resonance (8/10): EPA scrutiny + bottom 5th percentile carrier = compounding risk
- EPA ECHO - RCRA/NPDES violations (Fields: VIOLATION_COUNT, LAST_INSPECTION_DATE)
- FMCSA SAFER API - Carrier safety ratings (Fields: HAZMAT_OOS_RATE, HAZMAT_INSPECTIONS)
Confidence Level: 90% (government data; carrier identification requires inference from bills of lading)
Calculation Worksheet (Internal Documentation)
- Source: EPA ECHO API (data.epa.gov/efservice/)
- Fields: REGISTRY_ID, FACILITY_ADDRESS, VIOLATION_ID, VIOLATION_DATE, RCRA_FLAG
- Method: Direct API query for facility, extract violation records
- Verification: Search facility on echo.epa.gov, view violations tab
- Source: FMCSA SAFER API
- Fields: DOT_NUMBER, HAZMAT_OOS_RATE, HAZMAT_INSPECTIONS
- Calculation: FMCSA API returns pre-calculated OOS rate; national average = 8% (FMCSA benchmark); percentile rank calculated from carrier distribution
- Verification: Visit safer.fmcsa.dot.gov, search DOT number, view hazmat inspection data
Target food manufacturers with recent FDA Class I recalls (serious health risk) and OAI inspection classifications. Class I recalls involving temperature-sensitive products signal cold chain failures. TMS helps ensure carrier selection based on cold chain reliability and provides real-time tracking to prevent repeat violations.
Why This Works:
- Situation Recognition (9/10): Exact FEI number, recall number, dates, pathogen identified, OAI classification
- Data Credibility (10/10): FDA Recall API + FDA Inspection Database = gold standard for food manufacturers
- Insight Value (8/10): They know about the recall, but connecting it to systematic carrier vetting processes is helpful synthesis
- Emotional Resonance (9/10): Class I recall + OAI = highest FDA urgency level; regulatory action required
- FDA Recall API - Product recalls (Fields: recall_number, classification, reason_for_recall, recalling_firm)
- FDA Inspection Database - Facility inspections (Fields: FEI, CLASSIFICATION [OAI/VAI/NAI], INSPECTION_DATE)
Confidence Level: 95% (pure FDA government data)
Calculation Worksheet (Internal Documentation)
- Source: FDA Recall API (api.fda.gov/food/enforcement.json)
- Fields: recall_number, report_date, classification, reason_for_recall, product_description
- Method: API query filtered by company name, classification='Class I', extract recall details
- Verification: Search FDA recall database for company, view Class I recalls
- Source: FDA Inspection Database (datadashboard.fda.gov/ora/inspections)
- Fields: FEI, CLASSIFICATION, INSPECTION_DATE, LEGAL_NAME
- Method: Query by FEI number, sort by date descending, extract latest classification
- Verification: FDA inspection dashboard, search FEI number, view inspection history
Target EPA RCRA-flagged facilities (hazardous waste handlers) who are using carriers with documented DOT incident history and multiple FMCSA violations. Cross-database synthesis shows compounding compliance risk. TMS provides carrier safety data to audit roster and select safer alternatives.
Why This Works:
- Situation Recognition (9/10): EPA violations + specific carrier incident details + violation count creates double-risk narrative
- Data Credibility (9/10): EPA + PHMSA + FMCSA = all government sources, fully verifiable
- Insight Value (9/10): "Compounding your compliance risk" connects facility violations to carrier selection—powerful non-obvious synthesis
- Emotional Resonance (9/10): Double-risk framing creates strong urgency
- EPA ECHO - RCRA violations (Fields: RCRA_VIOLATION_COUNT, INSPECTION_NUMBER)
- DOT PHMSA - Carrier incidents (Fields: INCIDENT_DATE, DAMAGES, HAZMAT_CLASS)
- FMCSA SAFER - Carrier violations (Fields: HAZMAT_OOS_RATE, VIOLATION_COUNT)
Confidence Level: 95% (pure government data across three agencies)
Calculation Worksheet (Internal Documentation)
- Source: EPA ECHO API
- Fields: REGISTRY_ID, RCRA_VIOLATION_COUNT, INSPECTION_NUMBER, INSPECTION_DATE
- Method: Direct field lookup, count violations, extract inspection ID
- Verification: Visit echo.epa.gov, search facility, view RCRA compliance history
- Source: DOT PHMSA + FMCSA SAFER
- Fields: PHMSA (DAMAGES_AMOUNT, INCIDENT_DATE), FMCSA (HAZMAT_OOS_RATE)
- Method: PHMSA CSV filter by carrier and date; FMCSA API for OOS rate
- Verification: PHMSA incident reports + FMCSA carrier snapshot
Target shippers using carriers with major DOT reportable incidents (highway closure, significant damages, injuries) plus ongoing FMCSA hazmat violations. Most logistics teams don't routinely check PHMSA incident reports for contracted carriers. TMS provides this safety data during carrier selection.
Why This Works:
- Situation Recognition (8/10): Specific carrier name, DOT number, incident details, violation count
- Data Credibility (9/10): DOT incident reports are public record, specific damage amounts add credibility
- Insight Value (9/10): Logistics teams don't track PHMSA incidents—they rely on carrier relationships and pricing
- Emotional Resonance (8/10): $47K incident + highway closure = serious safety concern
- DOT PHMSA - Incident reports (Fields: INCIDENT_DATE, HAZMAT_CLASS, DAMAGES, INCIDENT_DESCRIPTION)
- FMCSA SAFER - Violation history (Fields: INSPECTION_DATE, VIOLATION_CODE, HAZMAT_FLAG)
Confidence Level: 95% (government incident reports and inspection records)
Calculation Worksheet (Internal Documentation)
- Source: DOT PHMSA Incident Reports CSV
- Fields: CARRIER_NAME, DOT_NUMBER, INCIDENT_DATE, HAZMAT_CLASS (Class 3 = flammable), DAMAGES_AMOUNT
- Method: CSV download, filter by carrier and date, extract incident details
- Verification: Download PHMSA data, search carrier DOT number or name
- Source: FMCSA SAFER inspection history
- Fields: DOT_NUMBER, INSPECTION_DATE, VIOLATION_CODE, HAZMAT_FLAG
- Calculation: Query SAFER for DOT number, filter where HAZMAT_FLAG=Y, count violations in 12-month window
- Verification: Visit safer.fmcsa.dot.gov, view carrier snapshot, inspect violation history
The Transformation
From Spray-and-Pray to Surgical Strikes
Traditional SDR outreach is based on soft signals and generic patterns: "I saw you're hiring," "Congrats on the funding," "Your company is growing." These messages are easily ignored because they don't reflect actual pain—they reflect assumptions about pain.
Blueprint GTM flips this model: Start with documented pain in government databases, then work backward to find prospects. Instead of guessing who might need your product, you identify people whose publicly documented situations prove they need it.
For Kuebix specifically:
- EPA violations + carrier safety data = compounding compliance risk
- FDA recalls + cold chain requirements = urgent carrier vetting need
- DOT incidents + facility regulations = liability exposure
These aren't hypothetical scenarios—they're verifiable situations happening right now. When you reach out with this level of specificity, prospects reply because you've done research they haven't done themselves.
The result: Response rates 5-10x higher than traditional outreach, shorter sales cycles, and deals that close themselves because the pain is real and urgent.