Blueprint Playbook for AutoSigma

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

Subject: Streamline Your Dealership Marketing Hi [Name], I noticed your dealership has been expanding - congrats on the growth! I wanted to reach out because AutoSigma helps dealerships like yours save time on marketing asset creation. We work with top dealership groups to deploy promotional campaigns 4x faster. Our platform syndicates offers across all your channels automatically, keeping your messaging consistent. Would you be open to a quick 15-minute call to discuss how we can help [Dealership Name] accelerate campaign deployment? Looking forward to connecting! Best, [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 Norman location shows $299/mo lease while Edmond shows $349 for the same trim" (verified pricing data from actual dealer websites)

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 verifiable data with dates, amounts, specific locations.

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.

AutoSigma GTM Plays

These messages are sorted by quality score. Each play demonstrates either precise situation awareness (PQS) or delivers immediate value (PVP).

PVP Public + Internal Strong (9.3/10)

Built 3-Store Offer Sync Audit

What's the play?

Scrape dealer pricing across all their locations and identify instances where identical vehicles show different pricing or terms. Deliver the completed audit before asking for anything.

Why this works

You've already done the work. The prospect gets immediate value - a pricing conflict report they can use today to fix internal inconsistencies. The specificity (14 instances, 6 cases over $500 variance) proves this isn't generic research.

Data Sources
  1. Dealer website inventory and pricing pages (scraped)
  2. Internal AutoSigma platform data (if available for multi-location variance detection)

The message:

Subject: Built you a 3-store offer sync audit Pulled your current offers across Norman, Edmond, and Tulsa - found 14 instances where identical vehicles show different terms. This includes 6 cases where the variance exceeds $500 on the same VIN class. Want me to send the audit spreadsheet?
DATA REQUIREMENT

This play requires scraping dealer website pricing across multiple locations and identifying variance by VIN/trim level.

Combined with internal platform data to detect patterns. This synthesis is proprietary to your business.
PVP Internal Data Strong (9.1/10)

Promotional Velocity Laggards vs Peer Groups

What's the play?

Use aggregated campaign deployment metrics from your customer base to show prospects exactly how their offer update frequency compares to peer dealerships of similar size, geography, and franchise type.

Why this works

Dealerships operate in competitive local markets. Showing them they're updating offers 40% slower than peers (18 days vs 11 days) creates urgency - they're losing competitive positioning every cycle. The peer comparison is data they cannot get elsewhere.

Data Sources
  1. AutoSigma Internal Platform Data - campaign deployment timestamps, offer update frequency by dealership

The message:

Subject: You're updating offers 40% slower than peers Based on promotional velocity data, your dealership updates offers every 18 days vs the 11-day average for Oklahoma dealer groups your size. That's 7 extra days competitors are running fresh offers while yours go stale. Want to see the velocity breakdown by channel?
DATA REQUIREMENT

This play requires aggregated promotional update frequency across 20+ dealerships, segmented by size, geography, and franchise type.

This is proprietary data only you have - competitors cannot replicate this play.
PVP Internal Data Strong (9.0/10)

OEM Launch Timeline Analysis

What's the play?

Track the prospect's historical performance on OEM asset deployment deadlines over their last 6-8 model launches. Show them the pattern: they're systematically missing deadlines by an average of 9 days, indicating an approval bottleneck.

Why this works

You're offering diagnostic data they likely don't track themselves. Showing a pattern (4 of 6 missed deadlines) reframes the problem from "bad luck" to "systematic bottleneck" - which has a fix. The analysis is already done; they just need to see it.

Data Sources
  1. AutoSigma Internal Platform Data - OEM asset deployment timestamps, approval workflow tracking
  2. OEM manufacturer launch calendars (public)

The message:

Subject: Tracked your last 8 OEM launches Analyzed your last 8 model year launches - average time from OEM asset drop to live deployment is 14 days vs 6-day dealer group average. That's costing you 8 days of first-mover advantage on every single launch. Want the launch timeline breakdown?
DATA REQUIREMENT

This play requires tracking customer OEM launch timelines and benchmarking against peer performance over multiple launches.

This is proprietary data only you have - competitors cannot replicate this play.
PVP Internal Data Strong (8.9/10)

Memorial Day Launch Timing Gap

What's the play?

Track when the prospect launched their holiday sale campaigns compared to peer dealerships. Show them they were 12 days late on Memorial Day, missing the peak shopping window and losing 40-60 potential units.

Why this works

Holiday campaigns are massive revenue drivers. Quantifying the late launch in lost units (40-60) makes the opportunity cost concrete. Offering Q3 holiday timeline data turns this into forward-looking value - they can fix it for the next cycle.

Data Sources
  1. AutoSigma Internal Platform Data - campaign launch dates by dealership
  2. Peer benchmark data from comparable dealership groups

The message:

Subject: Your Memorial Day launch was 12 days late Your Memorial Day sale went live May 29th - the average Oklahoma dealer launched May 17th, capturing 12 extra selling days. That's potentially 40-60 lost units based on typical holiday conversion rates. Want the launch timeline data for Q3 holidays?
DATA REQUIREMENT

This play requires tracking campaign launch dates across dealerships and identifying late launchers vs peer benchmarks.

This is proprietary data only you have - competitors cannot replicate this play.
PVP Public + Internal Strong (8.9/10)

Pricing Conflict Identification Across Locations

What's the play?

Scrape all dealership locations' inventory and pricing, then flag cases where identical models show mismatched lease/finance terms. Highlight internal cannibalization (one location undercutting another).

Why this works

Pricing conflicts across locations are embarrassing and costly - they erode customer trust and create internal competition. The specificity (9 conflicts, OKC undercutting Norman by $1,200+) proves you did the work. You're just offering to send the results.

Data Sources
  1. Dealer website inventory and pricing pages (scraped)
  2. AutoSigma internal platform data (if available for multi-location pricing monitoring)

The message:

Subject: Found 9 pricing conflicts across your stores Scraped your 4 locations yesterday - found 9 vehicle models where lease/finance terms don't match despite identical inventory. Including 2 cases where your OKC store undercuts Norman by $1,200+ on the same trim. Want the conflict list?
DATA REQUIREMENT

This play requires scraping dealer website pricing across locations and identifying internal pricing conflicts by VIN/trim.

Combined with internal platform data to monitor multi-location pricing consistency. This synthesis is proprietary to your business.
PQS Public Data Strong (8.8/10)

OEM Launch Asset Deadline Violation - Tahoe

What's the play?

Monitor OEM manufacturer launch calendars and cross-reference with dealer website/digital channel asset updates. Identify dealerships that missed the OEM-mandated launch deadline and are still showing outdated assets.

Why this works

OEM compliance is a massive pressure point for franchised dealers. Missing a deadline by 11 days is embarrassing and risks co-op reimbursement. Being singled out as one of 3 Oklahoma metro dealers still behind creates urgency - they're publicly lagging.

Data Sources
  1. OEM manufacturer launch calendars (public from manufacturer franchise documents)
  2. Dealer website asset verification (manual check or scraping)

The message:

Subject: Your Tahoe assets 11 days behind schedule GM mandated March 15th launch assets for the 2025 Tahoe refresh - your site still shows 2024 imagery as of March 26th. That's 11 days past the OEM deadline and you're one of 3 Chevy dealers in Oklahoma metro still behind. Who's handling the asset approvals?
PVP Internal Data Strong (8.8/10)

OEM Compliance Deadline Performance Pattern

What's the play?

Track the prospect's OEM compliance performance over their last 6 launches. Show them they missed 4 of 6 deadlines by an average of 9 days - indicating a systematic approval bottleneck, not random failures.

Why this works

Reframing repeated failures as a "systematic bottleneck" vs "bad luck" shifts the conversation to solutions. The timeline analysis is diagnostic data they likely don't track themselves. You're offering to help them fix the root cause.

Data Sources
  1. AutoSigma Internal Platform Data - OEM asset deployment timestamps, deadline compliance tracking
  2. OEM manufacturer launch calendars (public)

The message:

Subject: Mapped your last 6 OEM compliance deadlines Pulled your last 6 OEM asset deadlines vs actual deployment dates - you missed 4 of 6 by an average of 9 days. That pattern suggests a systematic approval bottleneck, not just bad luck. Want the timeline analysis?
DATA REQUIREMENT

This play requires tracking customer OEM compliance performance over time and identifying patterns of deadline misses.

This is proprietary data only you have - competitors cannot replicate this play.
PQS Public Data Strong (8.7/10)

OEM Launch Deadline Violation - F-150

What's the play?

Track OEM manufacturer launch deadlines and verify dealer digital channels still show placeholder or outdated content 8+ days after the deadline. Flag the co-op reimbursement penalty risk.

Why this works

Combining OEM deadline pressure with financial risk (co-op penalty) creates urgency. The 8-day delay is specific and verifiable. Asking "Is someone already working the approval backlog?" frames this as a helpful check-in, not a sales pitch.

Data Sources
  1. OEM manufacturer launch calendars (public from Ford franchise documents)
  2. Dealer website and digital channel asset verification (manual check or scraping)

The message:

Subject: Ford flagged your F-150 launch delay Ford's April 1st launch deadline for 2025 F-150 marketing assets passed 8 days ago - your digital channels still show placeholder content. That puts you at risk for Q2 co-op reimbursement penalties. Is someone already working the approval backlog?
PVP Internal Data Strong (8.7/10)

Promotional Offer Volume Gap vs Peers

What's the play?

Track the total number of promotional offers deployed by the prospect vs peer dealerships in the same quarter. Show them they deployed 8 offers while peers averaged 14 - that's 6 fewer chances to capture in-market buyers.

Why this works

Promotional volume is a proxy for market presence. Deploying 6 fewer offers than peers means 6 fewer opportunities to capture buyers actively shopping. Offering a gap analysis (which offer types they're missing) turns this into actionable intelligence.

Data Sources
  1. AutoSigma Internal Platform Data - promotional campaign count by dealership and quarter

The message:

Subject: Your Q1 offer count: 8 vs peer average of 14 You deployed 8 promotional offers in Q1 while comparable Oklahoma dealer groups averaged 14. That's 6 fewer chances to capture in-market buyers with timely incentives. Want to see which offer types you're missing?
DATA REQUIREMENT

This play requires tracking promotional campaign frequency across dealerships and benchmarking volume by quarter.

This is proprietary data only you have - competitors cannot replicate this play.
PQS Public Data Strong (8.6/10)

Multi-Location Pricing Variance - Different Silverado Offers

What's the play?

Scrape all dealer group locations and identify cases where the same vehicle model shows different rebate amounts or promotional terms across locations. Surface the customer confusion angle.

Why this works

Pricing inconsistency is embarrassing and erodes customer trust. The specificity (3 locations, Silverado 1500, $2,500 vs $3,000 vs $2,200 rebates) proves you did the research. Customers calling corporate about the variance makes it urgent.

Data Sources
  1. Dealer website inventory and promotional offer pages (scraped across all locations)

The message:

Subject: 3 different Silverado offers live right now Your Tulsa, Norman, and OKC stores are all running different Silverado 1500 offers - $2,500 vs $3,000 vs $2,200 rebates. Customers calling corporate are asking why the same truck costs different amounts at your locations. Is someone already standardizing these?
PQS Public Data Strong (8.6/10)

OEM Launch Deadline Violation - Honda Accord

What's the play?

Track Honda OEM launch deadlines and verify dealer digital channels (website, Google Ads) still show 2024 model imagery 28 days after the 2025 Accord asset deadline. Flag the lost search traffic opportunity.

Why this works

28 days late is brutally specific and verifiable. Framing the delay as "missing new model search traffic" ties it to lost revenue - competitors are capturing buyers searching for the 2025 model. The question "Is the approval process stuck?" is helpful, not salesy.

Data Sources
  1. OEM manufacturer launch calendars (public from Honda franchise documents)
  2. Dealer website and Google Ads asset verification (manual check or scraping)

The message:

Subject: Your 2025 Accord assets still pending Honda's March 1st asset deadline for 2025 Accord passed 28 days ago - your site and Google Ads still show 2024 model imagery. You're missing the new model search traffic spike while competitors capture it. Is the approval process stuck somewhere?
PQS Public + Internal Strong (8.5/10)

Multi-Location Pricing Variance - Same Yukon Config

What's the play?

Scrape dealer group websites and identify cases where the exact same vehicle configuration shows different monthly pricing across locations. Surface the trust erosion angle - customers calling to ask which price is real.

Why this works

Very specific - same vehicle, exact amounts ($847/mo vs $974/mo). The customer trust angle resonates because inconsistent pricing damages brand reputation. Offering to send the variance report is a low-commitment ask.

Data Sources
  1. Dealer website inventory and pricing pages (scraped)
  2. AutoSigma internal platform data (if available for real-time pricing monitoring)

The message:

Subject: Your Yukon pricing varies by $127/month Same 2025 Yukon Denali config shows $847/mo in Norman and $974/mo in Edmond as of today. Customers are calling asking which price is real - this erodes trust across your brand. Should I send you the variance report?
DATA REQUIREMENT

This play requires real-time monitoring of dealer pricing across locations to detect inconsistencies by VIN/config.

Combined with internal platform data to verify variance patterns. This synthesis is proprietary to your business.
PQS Public + Internal Strong (8.4/10)

Multi-Location Pricing Variance - Norman vs Edmond

What's the play?

Scrape dealer group websites and identify cases where the same vehicle model shows different lease pricing across locations. Surface the customer confusion angle - they're cross-shopping your stores and getting different prices.

Why this works

Specific to their dealerships - Norman vs Edmond locations, 2025 Camry, $299 vs $349. The customer confusion angle hits home because inconsistent pricing costs deals. The routing question is easy to answer.

Data Sources
  1. Dealer website inventory and pricing pages (scraped)
  2. AutoSigma internal platform data (if available for multi-location pricing monitoring)

The message:

Subject: Your 3 locations showing different pricing this week Your Norman location shows $299/mo lease on the 2025 Camry while Edmond shows $349 for the same trim. That's confusing customers cross-shopping your stores and likely costing you deals. Who's managing offer consistency across locations?
DATA REQUIREMENT

This play requires monitoring dealer website pricing across multiple locations to detect variance by vehicle trim.

Combined with internal platform data to identify multi-location pricing inconsistencies. This synthesis is proprietary to your business.
PQS Internal Data Strong (8.4/10)

Holiday Campaign Late Launch - July 4th

What's the play?

Track when the prospect launched their July 4th sale compared to peer dealerships. Show them they went live 22 days late (June 27th vs peer average June 5th), missing the entire pre-holiday shopping window.

Why this works

Holiday campaigns are revenue drivers. Launching 22 days late means missing the peak shopping window - the comparison to peers makes the gap concrete. The routing question is low-pressure and easy to answer.

Data Sources
  1. AutoSigma Internal Platform Data - campaign launch dates by dealership

The message:

Subject: You took 22 days to launch July 4th sale Your July 4th event went live June 27th - peer dealers launched June 5th, capturing 22 extra pre-holiday selling days. That's the entire peak shopping window for that holiday. Who manages the promotional calendar?
DATA REQUIREMENT

This play requires tracking campaign launch timing across customers and identifying late launchers vs peer benchmarks.

This is proprietary data only you have - competitors cannot replicate this play.

What Changes

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

New way: Use public data and internal platform intelligence to find dealerships in specific painful situations. Then mirror that situation back to them with evidence.

Why this works: When you lead with "Your Norman location shows $299/mo lease while Edmond shows $349 for the same trim" instead of "I see you're expanding," 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
AutoSigma Internal Platform Data deployment_speed, approval_cycle_duration, messaging_variance_percentage, campaign_launch_dates PVP plays - benchmarking promotional velocity, OEM launch performance, multi-location consistency
OEM Manufacturer Launch Calendars oem_announcement_date, preferred_launch_window, model_year PQS plays - identifying dealerships missing OEM asset deadlines
Dealer Website Inventory & Pricing vehicle_trim, monthly_pricing, rebate_amounts, location PQS plays - detecting multi-location pricing variance and inconsistent offers
State Motor Vehicle Dealer Licensing Databases dealer_name, license_number, location_address, license_status ICP targeting - identifying franchised and independent dealers by state
Automotive News Top 150 Dealership Groups Database group_name, store_count, total_units_sold, rank_change ICP targeting - identifying multi-location dealer groups
FTC CARS Rule Enforcement Actions enforcement_date, dealership_name, violation_type, penalty_amount Risk correlation - identifying dealerships with compliance pressure