Blueprint Playbook for Vooma

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 Vooma SDR Email:

Subject: Quick question about your freight operations Hi there, I noticed you're in the logistics space and handling a lot of freight volume. We work with companies like yours to automate their quoting and dispatch processes. Would love to chat about how we're helping teams move more freight without adding headcount. Let me know if you're open to a quick call.

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 facility at 1234 Industrial Pkwy received EPA violation #2024-XYZ on March 15th" (government database with record number)

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, facility addresses.

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

Vooma PQS Plays: Mirroring Exact Situations

These messages demonstrate such precise understanding of the prospect's current situation that they feel genuinely seen. Every claim traces to a specific government database with verifiable record numbers.

PQS Public Data Strong (8.3/10)

Play: Dual-Authority 3PL Context-Switching Pain

What's the play?

This play identifies 3PLs and contract logistics providers holding both active broker authority and common carrier authority — a structural state verified in the FMCSA L&I Portal. These hybrid operators manage brokered loads and owned assets from the same lean ops team, forcing manual load-by-load decisions (dispatch owned truck or broker it out). The DOT Census confirms they run 20+ power units, making the context-switching unavoidable. No single TMS was built for this dual-operation reality, creating fragmentation and error risk.

Why this works

The buyer's dual authority and exact authority grant date are verifiable public record — it signals deep, specific research. The insight that 'your TMS wasn't built for that context-switch' names a structural pain no competitor has articulated to them. The question 'Is your ops team juggling both from one screen?' is answerable yes/no and hits the exact daily operational headache: switching between asset-dispatch and brokerage-quoting workflows within the same TMS.

Data Sources
  1. FMCSA Licensing & Insurance (L&I) Portal - mc_number, dot_number, broker_authority_status, common_carrier_authority_status, authority_granted_date
  2. DOT Company Census File - total_power_units, total_drivers, dot_number

The message:

Subject: Your broker + carrier authority combo Osterkamp Trucking (USDOT 2493946, MC-846005) holds active broker authority granted April 9, 2014 while also running owned assets out of Pomona, CA. Every load your team touches means a manual decision — dispatch an owned truck or broker it out — and your TMS wasn't built for that context-switch. Is your ops team juggling both from one screen?
PQS Public Data Strong (8.1/10)

Play: Inspection Volume Reveals Understaffing at Scale

What's the play?

This play targets for-hire carriers with 50–150 power units whose inspection volume in the FMCSA SAFER System ranks in the top quartile for their fleet-size band. High inspection counts directly proxy real freight volume — carriers running more loads get inspected more. When combined with a lean driver-to-power-unit ratio from the DOT Census, the data proves the carrier is processing hundreds of daily dispatch calls and appointments entirely by hand. The pain is immediate: manual appointment scheduling creates detention charges and shipper relationship risk.

Why this works

The buyer sees their own FMCSA record cited with exact DOT number, truck count, and address — it's verifiable in seconds and signals genuine research. The inspection-to-staffing insight reframes their operational reality in a way they haven't articulated to themselves: high freight volume is proof they need automation, not proof they're understaffed. The question 'Is manual dispatch causing appointment misses?' is answerable in one word and ties directly to a quantifiable shipper pain (detention fees, lost bids).

Data Sources
  1. DOT Company Census File - total_power_units, total_drivers, carrier_operation, operation_classification
  2. FMCSA SAFER System — Carrier Safety Profiles - dot_number, total_inspections_last_24_months, total_power_units, safety_rating

The message:

Subject: Linden Bulk's 75 trucks, lean crew Linden Bulk Transportation (USDOT 2897186) runs 75 power units out of 4200 Tremley Point Road in Linden, NJ, and your inspection volume ranks in the top quartile for that fleet size. That much load volume with your driver-to-truck ratio means dispatch calls and appointment scheduling are getting keyed in by hand all day. Is manual dispatch causing appointment misses for you?
PQS Public Data Good (7.8/10)

Play: Hybrid 3PL Workflow Fragmentation

What's the play?

This variant targets dual-authority 3PLs using FMCSA L&I Portal data to confirm both broker and carrier authority, verified against DOT Census for fleet size. The message frames the specific operational burden: managing brokered loads and owned assets simultaneously from one lean team, with manual load-routing decisions happening every shift. The data proves the entity type and structure; the pain is the TMS tool mismatch.

Why this works

Exact address and both MC/DOT numbers are verifiable in seconds, proving genuine research. The dual-workflow pain ('constant manual toggling between two workflows') names their exact daily reality. A yes/no question about asset-versus-broker load decisions by hand is answerable and specific to how dual-authority 3PLs operate differently from pure brokers or carriers.

Data Sources
  1. FMCSA Licensing & Insurance (L&I) Portal - mc_number, dot_number, legal_name, broker_authority_status, common_carrier_authority_status
  2. DOT Company Census File - company_name, dot_number, total_power_units, total_drivers, state

The message:

Subject: MBR's brokerage and asset split MBR Freight Brokerage (USDOT 2800539, MC-922563) at 7450 W 130th St, Overland Park KS runs active broker authority alongside owned equipment. Managing brokered loads and owned assets from the same lean ops team means constant manual toggling between two workflows your TMS treats as one. Does your team decide asset-vs-broker load by load, by hand?
PQS Public Data Good (7.4/10)

Play: High-Volume Carrier Dispatch Bottleneck

What's the play?

This variant targets the same for-hire carrier segment using FMCSA SAFER inspection data and DOT power-unit counts to identify high-volume operators. The synthesis proves freight volume (top-quartile inspections) and fleet size, making the manual dispatch pain unavoidable. Carriers fielding hundreds of check calls and appointment texts daily are losing time on every coordination task, raising hold times and reducing carrier win rate with shippers.

Why this works

Exact MC and DOT numbers plus authority status verification date make the prospect immediately confident the sender did real research. The 'hundreds of carrier check calls and appointment texts manually every day' frames their exact operational reality. Reducing dispatcher hold time is a crisp, measurable KPI that resonates with ops leaders who track rep productivity by load-per-day.

Data Sources
  1. DOT Company Census File - total_power_units, total_drivers, dot_number, carrier_operation
  2. FMCSA Open Data Program — Motor Carrier & Broker Registry - dot_number, mc_number, entity_type, carrier_authority_status, operating_status

The message:

Subject: 75 trucks, hundreds of check calls Linden Bulk (USDOT 2897186, MC-973892) shows 75 power units and active carrier status as of April 13, 2026 with top-quartile inspection volume for your band. At that load count, your dispatchers are fielding hundreds of carrier check calls and appointment texts manually every day. Would reducing dispatcher hold time help your team?

Vooma PVP Plays: Delivering Immediate Value

These messages provide actionable intelligence before asking for anything. The prospect can use this value today whether they respond or not.

PVP Public + Internal Strong (8.7/10)

Play: Metro-Specific RFQ Speed Benchmark

What's the play?

This variant targets brokers in high-frequency lanes (Stockbridge GA) using FMCSA entity data combined with Vooma's proprietary response-time percentiles by region and freight type. The message reveals the median RFQ turnaround the broker's competitors are hitting, making the gap between manual and automated quoting quantifiable and urgent. Every minute past the median directly lowers win rate on shipper spot bids — a KPI the VP of Operations owns directly.

Why this works

Exact MC number and authority grant date prove genuine research; the regional median (6 minutes) is proprietary data only Vooma can provide. The message ties response time directly to measurable shipper bid win rate, making the automation ROI clear. The CTA to send response-time percentiles for the recipient's specific lanes and freight type is concrete, useful, and builds reciprocity regardless of conversion.

Data Sources
  1. FMCSA Licensing & Insurance (L&I) Portal - mc_number, dot_number, legal_name, broker_authority_status, authority_granted_date
  2. Vooma Proprietary Quote Response Time Benchmarks - region, freight_type, p25_response_time, p50_response_time, p75_response_time

The message:

Subject: Stockbridge GA quote speed benchmark for you For property brokers in the Stockbridge GA area we track a median RFQ turnaround of 6 minutes — JK Freight Logistics (MC-1220746, authority granted March 25, 2021) is bidding against reps hitting that number. Every minute past that median measurably lowers your win rate on spot freight, and manual email-to-TMS quoting is where the minutes go. Want me to send the response-time percentiles for your lane and freight type?
DATA REQUIREMENT

Vooma's aggregated RFQ-to-response-time percentile distributions by region (Stockbridge GA area) and freight type across active broker customer base

Proprietary aggregated response-time data by metro and freight type is a Vooma-exclusive competitive advantage. No competitor without this platform data can surface region-specific median RFQ turnaround or percentile breakdowns, making this the strongest private data play for brokers in measured lanes.
PVP Public + Internal Strong (8.6/10)

Play: Regional Quote Speed Benchmark Reveal

What's the play?

This play leverages Vooma's proprietary aggregated quote-response-time distributions (p25/p50/p75 by freight type and region across 15+ active broker customers) combined with FMCSA entity data to surface a competitive blind spot the prospect cannot measure alone. The message identifies the broker by metro and freight type, then reveals the median RFQ turnaround time their direct competitors are hitting. Manual email-to-TMS quoting is the precise mechanism that causes the gap; every minute past the median measurably lowers win rate on spot freight. This is a private data play that only Vooma can execute.

Why this works

The buyer receives a specific regional benchmark they literally cannot obtain elsewhere — no competitor has timestamped RFQ turnaround across dozens of brokers in their metro and freight type. The data reframes slow manual quoting as a measurable competitive disadvantage with real shipper bid impact. The offer to send the full percentile breakdown is concrete and valuable even if the prospect never buys, building trust and reciprocity.

Data Sources
  1. FMCSA Open Data Program — Motor Carrier & Broker Registry - mc_number, broker_authority_status, state, city
  2. Vooma Proprietary Quote Response Time Benchmarks - metro, freight_type, p25_response_time, p50_response_time, p75_response_time

The message:

Subject: Overland Park brokers quote in 5 minutes Across the brokers we run quoting for, the median RFQ response for property brokers in the Overland Park KS metro is 5 minutes — MBR Freight Brokerage (MC-922563) competes against that clock on every spot bid. If your reps are keying quotes by hand from email and PDFs, you're likely well past 15 minutes and losing bids before you're even in the race. Want the full p25/p50/p75 response-time breakdown for your metro and freight type?
DATA REQUIREMENT

Vooma's aggregated RFQ-to-response-time percentile distributions by metro and freight type across active broker customer base

Only Vooma has timestamped quote request and response data across dozens of brokers; competitors without this platform visibility cannot reproduce region- and freight-type-specific response-time benchmarks. This proprietary aggregate data becomes a competitive differentiator in the first conversation.

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 Dallas facility has 3 open OSHA violations from March" 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 public data. Here are the sources used in this playbook:

Source Key Fields Used For
DOT Company Census File company_name, dot_number, total_power_units, total_drivers, state, county, operation_classification, carrier_operation, hazmat_flag, out_of_service_pct Identifying for-hire carriers with 50+ power units and fleet-size data to proxy dispatch volume and detect understaffing ratios
FMCSA SAFER System — Carrier Safety Profiles dot_number, company_name, safety_rating, total_inspections_last_24_months, out_of_service_rate, crash_count, total_power_units, total_drivers, operating_status Determining high-volume carriers via top-quartile inspection counts within fleet-size bands, proving real freight volume and dispatch burden
FMCSA Open Data Program — Motor Carrier & Broker Registry legal_name, dba_name, dot_number, mc_number, entity_type, broker_authority_status, carrier_authority_status, operation_classification, carrier_operation, total_drivers, total_power_units, state, city, operating_status, insurance_required, insurance_on_file Identifying FMCSA-licensed brokers and carriers by authority status and entity type; verifying active brokerage and carrier operations
FMCSA Licensing & Insurance (L&I) Portal mc_number, dot_number, legal_name, broker_authority_status, common_carrier_authority_status, contract_carrier_authority_status, insurance_filing_type, insurance_policy_amount, revocation_history, authority_granted_date Identifying dual-authority 3PLs and contract logistics providers with both active broker and carrier authority; verifying authority grant dates
Vooma Proprietary Quote Response Time Benchmarks metro, state, freight_type, p25_response_time, p50_response_time, p75_response_time, sample_size Surfacing regional RFQ-to-response-time percentiles by freight type across Vooma's active broker customer base to reveal competitive speed blind spots