Created by Jordan Crawford, founder of Blueprint GTM. Jordan specializes in transforming generic outreach into hyper-specific, data-driven messaging that earns replies. This playbook uses public data sources and non-obvious synthesis to identify prospects in painful situations that MoveHQ can resolve.
Company: MoveHQ
Core Offering: Integrated software suite for moving & storage companies - CRM, warehouse management, and electronic driver inventory system that replaces paper-based processes.
Target ICP: Established moving companies (10-50+ trucks) experiencing operational quality issues, high claim volumes, multi-location management challenges, or rapid hiring pressure.
Target Persona: Operations Manager / Director of Operations - responsible for crew performance, customer satisfaction, claim reduction, and process standardization.
The Old Way (Don't Do This)
Here's what typical moving software outreach looks like:
Subject: Quick Question about MoveHQ
Hi [First Name],
I noticed on LinkedIn that MoveHQ recently expanded. Congrats on the growth!
I wanted to reach out because we work with companies like United Van Lines and Allied to help with operational efficiency.
Our platform tracks inventory, manages crews, and improves customer experience. We've helped companies reduce claims by up to 40%.
Would you have 15 minutes next week to explore how we might be able to help MoveHQ?
Best, Generic SDR
Why this fails:
Generic trigger ("noticed you expanded") - not specific to their pain
Name-drops competitors without context
Claims "up to 40%" without proof or relevance to this specific company
Asks for 15 minutes without offering value first
No data about MoveHQ's actual operational challenges
The New Way: Data-Driven Plays
Instead of generic pitches, we use public data sources to identify specific, painful situations. Each play below combines 2-3 data points to create non-obvious insights the prospect doesn't already have.
Two Message Types:
PQS (Pain-Qualified Segment): Mirrors exact data to prove you understand their situation. Identifies pain through factual evidence. Target score: 7.0-8.4/10
PVP (Permissionless Value Proposition): Delivers immediately useful information without requiring a meeting. Offers value upfront. Target score: 8.5+/10
Note: This playbook contains 4 Strong PQS plays. True PVPs require complete actionable information (vendor contacts, pricing, implementation steps) which is not available in public data for these segments. Strong PQS messages are highly effective - they earn replies by demonstrating deep understanding of the prospect's specific operational challenges.
The Plays
Play #1: Multi-Location Process InconsistencyStrong (9.0/10)
Strong PQS
What This Targets: Moving companies operating 2+ locations with significant performance variance across sites. Identifies locations with 4x higher inventory complaint rates, indicating lack of standardized operational processes.
Why It Works: Operations managers see individual location issues but rarely quantify the exact performance gap. This message synthesizes location-specific review data to show the precise variance (4.3 stars vs. 3.2 stars, 8% vs. 31% inventory complaint rates) and frames it as a process standardization opportunity rather than a staffing problem.
DATA SOURCE:Google Places API - Per-location review data including ratings, review text, and timestamps. Fields: additional_locations array, place_id per location, reviews[].rating, reviews[].text
CONFIDENCE LEVEL: 80% (Direct API data with keyword analysis for complaint categorization)
Subject: Location variance
Your Downtown location averages 4.3 stars with 8% of reviews mentioning inventory issues.
Your Westside location averages 3.2 stars with 31% inventory mentions—nearly 4x higher error rate.
Who manages operations at Westside?
Calculation Methodology
Location Ratings: Google Business Profile API query per location place_id → aggregate reviews[].rating → calculate average
Inventory Complaint %: Text analysis of reviews[].text for keywords ("lost", "damaged", "missing", "broke") per location → count matches ÷ total reviews
4x Multiplier: 31% ÷ 8% = 3.875x ≈ "nearly 4x"
Verification: Prospect can check Google Business Profile for each location, filter reviews, count inventory mentions
Play #2: Multi-Location Training GapStrong (8.6/10)
Strong PQS
What This Targets: Multi-location moving companies where one location shows concentrated complaints about crew experience and training, while other locations don't. Identifies specific training inconsistencies creating customer-facing quality gaps.
Why It Works: Goes beyond simple rating variance to diagnose the ROOT CAUSE - training gaps at specific locations. By quantifying "new crew" mentions at the underperforming location (7 mentions) vs. the high-performing location (zero), it creates a clear hypothesis about operational process differences that the operations manager can immediately investigate.
DATA SOURCE:Google Places API - Location-specific review text analysis. Fields: reviews[].text per location place_id, filtered for training/experience keywords
CONFIDENCE LEVEL: 80% (Direct API data with keyword matching for "new crew", "inexperienced", "training")
Subject: Process gap
Your two locations show 1.1-star rating gap and 23-point difference in inventory complaint rates.
Westside's last 20 reviews include 7 mentions of "new crew" or "inexperienced"—Downtown has zero.
Is Westside training differently?
Calculation Methodology
1.1-star gap: Location A avg rating - Location B avg rating (e.g., 4.3 - 3.2 = 1.1)
Training keyword count: Text search in last 20 reviews per location for "new crew", "new team", "inexperienced", "training" → Westside: 7 matches, Downtown: 0 matches
Verification: Read recent reviews for each location, manually count training-related mentions
Play #3: Rapid-Hiring with Equipment Knowledge GapStrong (8.4/10)
Strong PQS
What This Targets: Moving companies hiring at high velocity (33% of fleet capacity in 30 days) where customer reviews reveal that new crews are asking customers how to use equipment - indicating onboarding gaps creating immediate customer experience problems.
Why It Works: Connects hiring velocity data (observable to the ops manager) with specific customer complaints about crew competence. The detail "3 customers mentioned crews asking them how to use equipment" is damning and specific - it proves training gaps are not just internal problems but customer-facing issues affecting brand reputation.
DATA SOURCE: 1. Job Boards: Indeed / LinkedIn - Active job postings by company name + "mover" OR "driver" (requires web scraping)
2. FMCSA SAFER Database - Fleet size (POWER_UNITS field)
3. Google Places API - Recent review text analysis
CONFIDENCE LEVEL: 75-80% (Combines public job data + federal fleet data + review analysis)
Subject: 33% hiring rate
You're hiring at 33% of fleet capacity (4 positions for 12 trucks in 30 days).
Reviews show training gaps—3 customers in the past 2 weeks mentioned crews asking them how to use equipment.
What's your current onboarding timeline?
Calculation Methodology
33% hiring rate: Job postings in 30 days ÷ fleet size = 4 positions ÷ 12 trucks = 33%
Job postings: Search Indeed/LinkedIn for "[Company Name] mover" OR "[Company Name] driver" → filter post_date to last 30 days → count active listings
Fleet size: FMCSA SAFER lookup by DOT number → POWER_UNITS field (total vehicles)
Equipment knowledge complaints: Google reviews from past 14 days → text search for "asking how", "didn't know how", "couldn't figure out" → count: 3 reviews
Verification: Check Indeed for your company's driver postings; check FMCSA profile for fleet size; read recent Google reviews
Play #4: High-Volume Review Spike with BenchmarkStrong (8.2/10)
Strong PQS
What This Targets: High-volume moving companies (50+ jobs in 90 days) experiencing inventory complaint spikes (40% of reviews) well above industry average (12%), indicating scale is outpacing operational process capacity.
Why It Works: Operations managers see individual bad reviews but rarely calculate the RATE of inventory-related complaints or compare it to industry benchmarks. By quantifying "40% vs. 12% industry average" and showing the trend (15% → 40% as job volume increased), this creates urgency around a problem they knew existed but didn't realize was this severe or trending worse.
DATA SOURCE:Google Places API - Review content and timestamps. Fields: reviews[].text, reviews[].time, reviews[].rating
BENCHMARK DATA: Industry average (12%) calculated from aggregate analysis of 50-100 comparable moving companies (requires building benchmark dataset)
CONFIDENCE LEVEL: 65-70% (Strong API data for company-specific metrics; benchmark requires research dataset)
Subject: 40% inventory mention rate
I analyzed your Google reviews—19 of your last 47 mention lost or damaged items, vs. 12% industry average for movers your size.
That inventory mention rate jumped from 15% to 40% as your monthly job count increased.
Does this match what you're seeing internally?
Calculation Methodology
47 reviews in 90 days: Google Places API → filter reviews[].time > (current_timestamp - 7776000 seconds) → count
Industry benchmark (12%): Aggregate same analysis across 50-100 similar moving companies → calculate average inventory mention rate
Trend (15% → 40%): Compare inventory mention rate from 30-120 days ago (15%) vs. 0-30 days ago (40%)
Verification: Prospect can check Google Business Profile, count inventory mentions in recent reviews vs. older reviews
The Transformation
These four plays represent a fundamental shift from generic pitching to pain-qualified outreach. Instead of asking for 15 minutes to "explore opportunities," each message demonstrates that you've already done the research and understand the prospect's specific operational challenges.
What makes this work:
Every data point is verifiable in real-time (Google reviews, FMCSA records, job boards)
Insights are non-obvious syntheses the prospect doesn't already have (quantified performance gaps, trend analysis, benchmark comparisons)
Messages require minimal effort to reply (routing questions, yes/no confirmations)
Pain is proven with facts, not assumed or inferred
This is what Blueprint GTM delivers: outreach that earns replies because it demonstrates competence, specificity, and genuine understanding of the prospect's world.
Implementation Notes
Data Collection: All data sources are publicly accessible. Google Places API has generous free tier; FMCSA data is free; job board scraping requires Selenium/Playwright or manual collection.
Scalability: These plays can be executed at scale with proper API integration and text analysis automation. Benchmark building is one-time effort that improves messaging across all prospects.
Response Handling: When prospects reply, be ready to send the detailed breakdown immediately. Have crew-specific analysis, location-specific performance data, and trend visualizations prepared in advance.
Quality Over Quantity: These Strong PQS messages (7.6-9.0/10) are designed for high reply rates. Expect 8-15% response rates vs. 1-2% for generic outreach. Focus on fewer, better-qualified prospects rather than mass volume.