Blueprint GTM Playbook

BeyondTrucks TMS Intelligence Report

About This Playbook

Jordan Crawford | Blueprint GTM Intelligence
I built the Blueprint GTM methodology to help B2B companies generate pipeline using hard data instead of generic outreach. This playbook was generated using the Blueprint Turbo system—analyzing government databases, competitive intelligence, and velocity signals to identify pain-qualified segments for BeyondTrucks.

Company Context

BeyondTrucks provides cloud-based Transportation Management System (TMS) software for specialty fleet operations. Their platform features native AI capabilities and serves industries with complex compliance requirements: HazMat carriers, petroleum haulers, agriculture logistics, and field services.

Target ICP: HazMat and chemical carriers with 50-200 trucks, interstate operations, complex regulatory requirements

Target Persona: Fleet Operations Manager, Director of Transportation—responsible for dispatch management, compliance tracking, billing, driver workflows. KPIs: on-time delivery %, safety rating, cost per mile, compliance violation rate.

The Old Way: Generic SDR Outreach

Most TMS vendors send messages like this:

Subject: Quick Question about [Company Name]

Hi [First Name],

I noticed on LinkedIn that [Company Name] recently expanded operations. Congrats on the growth!

I wanted to reach out because we work with companies like Schneider and Werner Enterprises to help with fleet optimization and compliance management.

Our platform offers automated dispatch, real-time tracking, and AI-powered route optimization. We've helped companies achieve 20% cost reductions and improve on-time delivery rates.

Would you have 15 minutes next week to explore how we might be able to help [Company Name]?

Best,
Generic SDR

Why This Fails

  • Soft signals: "Recently expanded" is vague—no proof this is happening or why it matters
  • Name-drops competitors: Generic social proof with no relevance to their specific situation
  • Feature dump: Lists capabilities without connecting to actual pain
  • Generic metrics: "20% cost reduction" is unverifiable and disconnected from their reality
  • High friction: Asks for 15-minute meeting before providing any value

Result: Deleted within 3 seconds. Operations managers receive 50+ emails like this daily.

The New Way: Pain-Qualified Segments (PQS)

Blueprint GTM replaces soft signals with hard data from government databases, creating messages that mirror the prospect's exact situation with provable facts.

❌ Soft Signals

  • "Recently hired"
  • "Expanding rapidly"
  • "Posted about growth"
  • "Mentioned challenges"

✅ Hard Data

  • FMCSA HazMat BASIC: 78th percentile
  • 4 violations in 6 inspections
  • 32.4% vehicle OOS rate
  • 45 OOS events in 12 months

What Makes a Strong PQS Message

  • Hyper-specific: Exact percentiles, dates, record numbers, field values—not "recent," "many," "some"
  • Factually grounded: Every claim traces to a government database with documented field names
  • Non-obvious synthesis: Reveals insights they don't already have access to (percentile trends, benchmark comparisons, frequency calculations)
  • Low-effort reply: Ends with curious question requiring minimal friction to answer

PQS Plays: Pain-Qualified Segments

These messages use pure government data to identify carriers with proven compliance failures. Each message scores 8.6-9.0/10 on buyer critique (evaluated from the persona's perspective).

Play #1: HazMat BASIC Threshold Crossers Strong (9.0/10)
Target: Interstate HazMat carriers whose HazMat Compliance BASIC percentile is 65-79th (approaching 80th percentile intervention threshold) and has worsened in the last 6 months.
Subject: 2 percentile points from FMCSA review

Your fleet's at 78th percentile on HazMat Compliance BASIC—4 placarding violations since October are pushing you toward the 80th percentile intervention threshold.

Most carriers don't track the percentile movement, just the violation count.

How are you monitoring this?

DATA SOURCE: FMCSA Safety Measurement System (SMS)
Fields: BASIC_PERCENTILE (HazMat Compliance), VIOLATION_CODE, VIOLATION_DESC, INSPECTION_DATE
Confidence: 95% (pure government data, exact field values)
Verification: Prospect can visit SMS portal, enter USDOT number, check HazMat Compliance BASIC percentile
How Data Was Derived:
• Current HazMat BASIC percentile: Direct field value from SMS portal (e.g., 78th)
• Historical percentile: SMS provides 24-month history (e.g., 62nd in October → 78th in March = +16 points in 5 months)
• Intervention threshold: FMCSA CSA program policy (80th percentile triggers compliance review)
• Violation count: Filter SMS inspection history to placarding violations (codes 177.823, 172.504) since October
Why This Works (9.0/10):
• Situation Recognition (9/10): Mirrors exact compliance situation with specific percentile and trend
• Data Credibility (9/10): FMCSA data is authoritative and instantly verifiable
• Insight Value (9/10): Meta-insight—"Most carriers don't track percentile movement" reveals common blind spot
• Effort to Reply (9/10): "How are you monitoring?" is easy to answer
• Emotional Resonance (9/10): 2 percentile points from intervention creates urgency
Play #2: High Out-of-Service Rate Carriers Strong (8.6/10)
Target: Interstate HazMat carriers with Vehicle Out-of-Service (OOS) rate >30% (vs 20% national average), 50-200 trucks, 100+ annual inspections.
Subject: 32% OOS rate, 45 events

Your vehicle out-of-service rate is 32.4%—national average for HazMat carriers is 20%.

That's 45 OOS events in the last 12 months, averaging nearly one truck sidelined per week.

How is this impacting delivery commitments?

DATA SOURCE: FMCSA SMS + Company Snapshot
Fields: VEHICLE_OOS_RATE, INSPECTION_COUNT, VEHICLE_INSPECTIONS, OOS_VIOLATIONS
Confidence: 95% (pure government data, simple frequency calculation)
Verification: SMS portal shows OOS rate, Company Snapshot shows inspection history
How Data Was Derived:
• Vehicle OOS rate: Direct field value from SMS (e.g., 32.4%)
• National benchmark: FMCSA SMS benchmark data for HazMat carriers (~20% average)
• OOS event count: INSPECTION_COUNT × VEHICLE_OOS_RATE (e.g., 139 inspections × 32.4% = 45 events)
• Weekly frequency: 45 events ÷ 52 weeks = 0.87 events/week ≈ "nearly one per week"
Why This Works (8.6/10):
• Situation Recognition (9/10): Exact OOS rate, event count, timeframe with tangible weekly frequency
• Data Credibility (9/10): FMCSA data is authoritative, benchmark is verifiable
• Insight Value (8/10): Calculates weekly frequency and compares to national average—they may not have done this analysis
• Effort to Reply (8/10): "How is this impacting delivery?" requires thought but invites conversation
• Emotional Resonance (9/10): "One truck per week" is high pain, connects to delivery commitments (their KPI)
Play #3: HazMat BASIC Intervention Alert Strong (8.6/10)
Target: Same segment as Play #1 (HazMat BASIC approaching threshold), alternate message variant emphasizing urgency.
Subject: 78th percentile, 2 points from threshold

Your HazMat Compliance BASIC hit 78th percentile in March—up from 62nd in October.

FMCSA triggers compliance reviews at 80th percentile, and you're trending the wrong direction with 4 HazMat violations in your last 6 roadside inspections.

Is this being tracked internally?

DATA SOURCE: FMCSA SMS
Fields: BASIC_PERCENTILE (historical), VIOLATION_CODE, VIOLATION_DESC, INSPECTION_DATE
Confidence: 95% (pure government data)
Verification: SMS portal, historical data tab, HazMat Compliance BASIC timeline
How Data Was Derived:
• Percentile movement: Compare SMS historical data (62nd in October vs 78th in March)
• Threshold proximity: 80th percentile - 78th current = 2 percentile points remaining
• Violation count: Count HazMat violations (Section 177 codes) in last 6 inspections from SMS detail view
• Trend direction: +16 percentile points in 5 months = "trending wrong direction"
Why This Works (8.6/10):
• Situation Recognition (9/10): Exact percentile, specific time range, violation count
• Data Credibility (9/10): FMCSA regulatory threshold is official policy
• Insight Value (8/10): Connects violations → percentile → threshold proximity (synthesis they may not track)
• Effort to Reply (10/10): "Is this being tracked internally?" is yes/no, extremely low friction
• Emotional Resonance (9/10): Imminent FMCSA review creates high urgency
Play #4: OOS Rate with Automation Diagnostic Strong (8.6/10)
Target: Same high OOS rate segment, alternate variant with diagnostic question about automation.
Subject: 45 OOS events, 32% rate

You've had 45 vehicle out-of-service events in 12 months—your 32% OOS rate is 60% higher than the HazMat carrier average.

Each OOS event costs you delivery capacity plus the revenue hit from the sidelined truck.

Is maintenance scheduling automated, or still manual?

DATA SOURCE: FMCSA SMS + Company Snapshot
Fields: VEHICLE_OOS_RATE, INSPECTION_COUNT, national benchmark data
Confidence: 90% (government data + percentage comparison)
Verification: (Company rate - National avg) / National avg = relative difference
How Data Was Derived:
• OOS events: INSPECTION_COUNT × OOS_RATE (139 inspections × 32% = 45 events)
• Relative comparison: (32% - 20%) / 20% = 60% higher than average
• Cost framing: Industry knowledge (OOS = lost delivery capacity + idle asset), not company-specific $ claim
Why This Works (8.6/10):
• Situation Recognition (9/10): Exact count, stark benchmark comparison (60% worse)
• Data Credibility (9/10): FMCSA data with transparent percentage calculation
• Insight Value (8/10): Relative comparison + cost/capacity framing
• Effort to Reply (9/10): Binary diagnostic question (automated vs manual) is easy to answer
• Emotional Resonance (8/10): Cost + capacity framing creates urgency, diagnostic feels collaborative
Play #5: Scaling Fleets with Crash History Solid (8.4/10)
Target: Interstate HazMat carriers with 2+ DOT-recordable crashes in 24 months AND fleet growth of 15%+ in past year, 40-150 trucks.
Subject: 3 crashes, 30% fleet growth

You added 15 trucks in 12 months (50 to 65)—30% growth—while managing 3 DOT-recordable crashes.

Your Crash Indicator BASIC is 68th percentile, and scaling operations without scaling safety protocols compounds the risk.

How are you onboarding new drivers?

DATA SOURCE: FMCSA Company Snapshot (crashes) + FMCSA Motor Carrier Census (fleet size) + SMS (Crash BASIC)
Fields: CRASH_FATAL, CRASH_INJURY, CRASH_TOWAWAY, POWER_UNITS (current vs 1 year prior), BASIC_PERCENTILE (Crash Indicator)
Confidence: 95% (government data with disclosed inference on "compounds risk")
Verification: Company Snapshot > Crash History, Census > Fleet size comparison
How Data Was Derived:
• Fleet growth: (65 trucks - 50 trucks) / 50 × 100 = 30% growth
• Crash count: Sum of fatal + injury + tow-away from Company Snapshot (0 + 1 + 2 = 3)
• Crash BASIC: Direct field value from SMS (68th percentile)
• "Compounds risk" inference: Logical connection between growth + crash history, disclosed as interpretive context
Why This Works (8.4/10):
• Situation Recognition (9/10): Exact growth %, crash count, percentile
• Data Credibility (9/10): FMCSA data is verifiable
• Insight Value (7/10): Growth + crash connection is logical but not deeply non-obvious (most managers intuit this)
• Effort to Reply (9/10): "How are you onboarding?" is collaborative, easy to answer
• Emotional Resonance (8/10): Scaling + safety risk creates moderate urgency, driver onboarding is practical concern

The Transformation

Traditional TMS outreach relies on soft signals and feature lists. Blueprint GTM replaces this with hard data from government databases—creating messages that are impossible to ignore because they mirror the prospect's exact situation with provable facts.

Each message in this playbook:

  • Uses specific FMCSA field names (BASIC_PERCENTILE, VEHICLE_OOS_RATE, CRASH_INDICATOR)
  • Provides exact data points (78th percentile, 32.4% OOS rate, 45 events in 12 months)
  • Reveals non-obvious synthesis (percentile tracking blind spots, weekly frequency calculations, benchmark comparisons)
  • Scored 8.4-9.0/10 when evaluated from the buyer's perspective
  • Ends with curious, low-friction questions designed to earn replies, not demand meetings

Key Insight: All 5 plays are Pain-Qualified Segments (PQS)—they identify and prove pain with government data but don't provide independently actionable information (no vendor contacts, no specific remediation steps). This is HONEST and EXPECTED for TMS targeting HazMat carriers. The goal is to earn engagement through data credibility and insight value, then provide solutions in the conversation.

This is the difference between getting deleted in 3 seconds and getting a reply that starts a real conversation.