Blueprint Playbook for Keyloop

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

Subject: Transform your dealership operations Hi Michael, I noticed your dealership group has been growing rapidly - congrats on the recent expansion! At Keyloop, we help automotive retailers like you unify sales, service, and inventory operations into one seamless platform. Our customers see: • 50% reduction in time-on-lot • 42% increase in service upsells • 4x faster customer query resolution Would you be open to a quick 15-minute call to explore how we could help optimize your operations? Best, Sarah Keyloop Account Executive

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 Q4 service revenue was $12.3M while AutoNation posted $18.7M in the same metro" (SEC filings with exact numbers)

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 public data with dates, record numbers, financial disclosures.

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.

Keyloop Intelligence Plays

These messages demonstrate precise understanding of the prospect's situation and deliver actionable intelligence. Ordered by quality score.

PVP Internal Data Strong (8.7/10)

Bay-Level Performance Analysis: Service Departments with Cycle Time Performance Gaps

What's the play?

Use real-time service workflow data to identify specific bottlenecks at the individual service bay level. Show service managers exactly which bay is underperforming and why - with task-level process time breakdowns that pinpoint the root cause (e.g., parts retrieval delays).

Why this works

Bay-specific performance data is immediately actionable - the service manager can fix this problem TODAY. The precision of knowing "bay 3 waits 12 minutes longer for parts" proves you have real data, not industry benchmarks. This is the kind of operational insight managers desperately need but rarely have visibility into.

Data Sources
  1. Keyloop Internal Service Workflow Data - bay-level cycle times, task timestamps, parts request logs

The message:

Subject: Your bay 3 averages 12 minutes slower Bay 3 at your service department averages 59 minutes per job versus 47 minutes in bays 1-2. I compared process times across 12 service tasks and found the bottleneck is parts retrieval - bay 3 waits 12 minutes longer for parts runner. Want the task breakdown?
DATA REQUIREMENT

This play requires service workflow data tracking bay-level cycle times, task completion timestamps, and parts request/delivery timing across your customer base.

This granular operational data is proprietary - competitors cannot replicate this insight.
PVP Internal Data Okay (7.8/10)

Cross-Brand Customer Intelligence: Multi-Brand Franchise Groups with Utilization Gaps

What's the play?

Analyze appointment scheduling data across multi-brand franchise groups to identify day-of-week utilization imbalances. Cross-reference with customer vehicle ownership records to find customers who own multiple brands but prefer specific service days - enabling load balancing across underutilized bays.

Why this works

This addresses a real operational pain (overbooked Honda service while Toyota bays sit empty) with a specific, actionable solution (34 customers who could be shifted). The insight requires data synthesis that the service manager can't do themselves - you're providing genuine strategic value.

Data Sources
  1. Keyloop Internal Appointment Data - day-of-week patterns, bay utilization by brand
  2. Keyloop Customer Vehicle Records - cross-brand ownership from DMS integration

The message:

Subject: Your Toyota bays sit empty Thursdays Your Toyota service bays run at 41% utilization on Thursdays while Honda is overbooked at 97%. I pulled appointment patterns across your brands and can show you which 34 Honda customers also own Toyotas and prefer Thursday service. Want the customer cross-reference?
DATA REQUIREMENT

This play requires appointment scheduling data showing day-of-week utilization patterns and customer vehicle ownership records across brands from DMS integration.

This cross-brand customer intelligence is unique to dealerships using unified DMS systems like Keyloop.
PVP Internal Data Okay (7.6/10)

At-Risk Customer Recovery: Public Dealer Groups Pre-Earnings

What's the play?

Identify high-value service customers who have gone silent (4+ months without appointments) at dealerships with declining service revenue. Quantify the recoverable revenue opportunity and provide contact information before earnings calls - giving operations teams actionable recovery targets to improve quarterly results.

Why this works

The timing creates urgency (earnings call approaching) and the insight is immediately valuable (specific customer names with contact info). Service managers can launch win-back campaigns TODAY with the exact customers who represent recoverable revenue. The specificity of "23 customers, $41K recoverable" makes this feel real and actionable.

Data Sources
  1. Keyloop Customer Service History - appointment dates, annual spend per customer
  2. SEC EDGAR Database - quarterly earnings dates, service revenue trends

The message:

Subject: 23 high-value service customers went dark 23 customers who averaged $1,800 annual service spend haven't booked appointments in 4+ months at your dealership. Your Q4 showed 8% service revenue decline and these 23 alone represent $41K in recoverable annual revenue. Want their contact info and last service dates?
DATA REQUIREMENT

This play requires customer service history showing appointment dates and annual spend patterns from your DMS system.

This at-risk customer intelligence is unique to your platform - competitors don't have this customer lifecycle visibility.
PQS Public + Internal Okay (7.4/10)

Pre-Earnings Service Revenue Decline: Public Dealer Groups

What's the play?

Identify public dealership groups with declining service revenue in recent quarterly filings (10-Q) and upcoming earnings calls within 45-60 days. Mirror their exact financial situation with specific numbers from SEC filings - creating urgency around the need to demonstrate service recovery plans to analysts.

Why this works

The earnings call deadline creates real pressure - analysts WILL ask about service margin recovery. Using their actual 10-Q numbers proves you did research (not generic outreach). The routing question is easy to answer but gets you to the person responsible for the turnaround plan.

Data Sources
  1. SEC EDGAR Database - 10-Q quarterly reports, earnings announcement dates, service revenue trends
  2. Keyloop Internal Benchmarking Data - regional service performance comparisons

The message:

Subject: Your service revenue down 8% before earnings call Your Q4 10-Q shows service revenue declined 8% year-over-year to $12.3M. Your February 14th earnings call is 6 weeks away and analysts will ask about service margins. Who's driving the service turnaround plan?
DATA REQUIREMENT

Combines public SEC filings with internal benchmarking data showing regional service performance trends across your customer base.

The public data is verifiable; the internal benchmarking context is proprietary to Keyloop.
PVP Public + Internal Okay (7.3/10)

Margin Recovery Analysis: Public Dealer Groups Pre-Earnings

What's the play?

Analyze public dealership groups' gross profit margin trends from SEC filings and combine with internal pricing intelligence to identify specific margin recovery opportunities. Deliver a pre-built analysis showing where they're leaving money on the table compared to regional pricing trends - timed before earnings calls when margin improvement matters most.

Why this works

The margin decline is their actual public data (credible), the $800K recovery opportunity is material enough to matter, and the timing before earnings creates urgency. Offering a completed pricing analysis (vs. making them do the work) delivers immediate value that justifies a conversation.

Data Sources
  1. SEC EDGAR Database - quarterly gross profit margins, service revenue trends
  2. Keyloop Internal Pricing Data - metro-specific service pricing vs. parts cost trends

The message:

Subject: Q4 service margin recovery plan Your service gross profit margin dropped from 62% to 56% in Q4 according to your 10-Q. I analyzed your metro's service pricing vs parts cost trends and found 3 margin recovery plays worth $800K annually. Want the pricing analysis?
DATA REQUIREMENT

Combines public margin data from SEC filings with internal pricing intelligence showing metro-specific service rates and parts cost trends across your customer base.

The pricing analysis synthesis is proprietary - no competitor can deliver this specific regional margin insight.
PQS Public Data Okay (7.2/10)

Widening Competitive Gap: Public Dealer Groups vs. Regional Competitors

What's the play?

Identify public dealership groups whose service revenue is declining while direct regional competitors (also public) are growing in the same metro area. Quantify the widening gap using SEC filings and create urgency by tying it to upcoming earnings calls where analysts will ask about competitive positioning.

Why this works

Naming the specific competitor (AutoNation) and showing the gap widening ($4.2M to $6.4M) makes the competitive threat tangible. The earnings deadline creates urgency around needing a credible recovery story. This is all verifiable public data, so it feels trustworthy rather than salesy.

Data Sources
  1. SEC EDGAR Database - 10-Q quarterly reports showing service revenue by metro region
  2. SEC EDGAR Database - competitor quarterly reports for same metro markets

The message:

Subject: Service revenue gap widened in Q4 Your Q4 service revenue was $12.3M while your regional competitor AutoNation posted $18.7M in the same metro. The gap widened from $4.2M to $6.4M year-over-year and your earnings call is February 14th. Is finance already modeling the service recovery?

What Changes

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

New way: Use public and proprietary data to find dealerships in specific operational situations. Then deliver insights so precise they assume you're already working with them.

Why this works: When you lead with "Your bay 3 averages 12 minutes slower - the bottleneck is parts retrieval" instead of "We help dealerships optimize service operations," you're not another sales email. You're the person who has visibility into problems they didn't even know they could measure.

The messages above aren't templates. They're examples of what happens when you combine real data sources (SEC filings, licensing boards) with proprietary operational intelligence (bay-level cycle times, customer appointment patterns). 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
SEC EDGAR Database - Public Dealership Companies company_name, 10-K reports, 10-Q reports, dealership_count, revenue, service_revenue, earnings_dates Public dealer group financial performance, earnings timing, competitive comparisons
State Automotive Dealer Licensing Boards dealer_name, license_status, location_address, franchise_brands, phone, email Franchise identification, multi-brand groups, dealership verification
FTC Enforcement Actions Database dealer_name, violation_type, enforcement_date, fine_amount, state Compliance risk indicators, regulatory pressure signals
Dealership M&A Transaction Data acquiring_group, target_dealership, transaction_date, franchise_count, location Post-acquisition integration challenges, system consolidation needs
NADA Dealership Data franchised_dealership_count, regional_distribution, franchise_brands, dealership_turnover_rates Industry benchmarking, regional dealership trends
G2/Capterra Automotive DMS Reviews software_name, user_ratings, pain_point_mentions, integration_challenges Competitive intelligence, customer pain signals from competitor users
NHTSA Vehicle Manufacturer & Dealer Information manufacturer_name, dealer_code, franchise_status, certification_level, vehicle_makes OEM network identification, certification verification
Keyloop Internal Service Transaction Data invoice_values, upsell_rates, service_type, regional_percentiles, bay_cycle_times Regional performance benchmarking, operational efficiency analysis
Keyloop Customer Service History appointment_dates, annual_spend, customer_retention, last_service_date At-risk customer identification, revenue recovery opportunities
Keyloop Appointment Scheduling Data day_of_week_patterns, bay_utilization, service_demand_by_brand Utilization optimization, cross-brand load balancing