Blueprint Playbook for Restaurant365

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

Subject: Restaurant accounting made simple Hi [First Name], I saw your post about managing multiple locations and thought Restaurant365 could help. We help restaurants like yours streamline accounting, inventory, and payroll in one platform. Our customers save 30+ hours per month on back-office tasks. Would love to show you how we integrate with 80+ POS systems. Are you free for a quick 15-minute call this week?

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 Austin location had 2 ABC violations in October" (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.

Restaurant365 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 + Internal Strong (8.1/10)

California/Texas Casual Dining with Liquor Violations + Labor Cost Spikes

What's the play?

Target casual dining restaurants in California or Texas that have recent liquor license violations (ABC/TABC enforcement actions) and cross-reference with labor cost data showing spikes during violation periods. The correlation between compliance failures and labor chaos (overtime, emergency scheduling, manager burnout) creates an urgent pain point.

Why this works

The specificity of the address, violation dates, and labor spike percentage proves you've done deep research. The insight that compliance incidents correlate with scheduling chaos resonates because it's a hidden cost most operators don't track. The easy routing question makes it safe to respond.

Data Sources
  1. California ABC Liquor License Enforcement Data - license_number, business_name, address, enforcement_actions, suspension_status, fine_amount
  2. Texas TABC License Violations Database - license_number, business_name, address, violations, administrative_actions, fine_amount
  3. Internal Restaurant365 Benchmarks - aggregated labor cost % by region for casual dining with/without violations

The message:

Subject: Your Austin location had 2 liquor violations in October Your restaurant at 456 Congress Ave had 2 liquor license violations in October - one for after-hours service, one for serving minors. Texas ABC escalates penalties on repeat violations within 12 months, and your labor costs spiked 18% that same month according to county wage filings. Who's coordinating compliance and scheduling right now?
This play assumes your company has:

Aggregated labor cost data from existing customers or county wage filings cross-referenced with public liquor violation records. Labor cost benchmarks should be computed across 100+ locations per region to ensure anonymity.

If you have this data, this play becomes highly differentiated - competitors can't replicate it.
PQS Public + Internal Strong (8.4/10)

California/Texas Casual Dining with Liquor Violations + Labor Cost Spikes

What's the play?

Same targeting as above but with stronger multi-location angle. Emphasize the pattern of violations correlating with labor chaos and ask about oversight across other Texas locations to trigger concern about systemic issues.

Why this works

The multi-location angle is highly relevant for operators managing 3+ restaurants. The insight about scheduling chaos during compliance incidents is valuable operational intelligence. The question naturally surfaces who owns this problem across the group.

Data Sources
  1. Texas TABC License Violations Database - license_number, business_name, address, violations
  2. Internal Restaurant365 Benchmarks - aggregated labor cost data by location and time period

The message:

Subject: 2 liquor violations + 18% labor spike at your Congress Ave location Your Austin location (456 Congress Ave) had 2 ABC violations in October and labor costs jumped 18% that same month. That pattern usually means scheduling chaos during compliance incidents - overtime to cover, untrained staff, manager burnout. Is someone tracking this across your other Texas locations?
This play assumes your company has:

Labor cost data from existing customers or county wage filing data cross-referenced with public ABC violation records. Requires aggregated benchmark data showing labor cost patterns during compliance events.

Combined with public compliance data, this creates a unique insight competitors cannot replicate.
PQS Public Data Strong (8.3/10)

New QSR/Fast Casual Franchisees in First 24 Months Post-FDD Registration

What's the play?

Target new franchisees who filed their Franchise Disclosure Document (FDD) within the last 8-18 months. These operators are approaching the critical month 10-12 period when pre-opening expenses need reconciliation with franchise reporting requirements.

Why this works

The specific filing date and brand name prove research. The timeline prediction (month 10-12 accounting backlog) feels credible because it's based on common franchise patterns. The question is easy to answer and non-threatening.

Data Sources
  1. Franchise Disclosure Document (FDD) Database - franchisor_name, item_19_financial_performance, item_21_financial_obligations, number_of_franchises

The message:

Subject: You filed your Chipotle FDD 8 months ago You registered your Franchise Disclosure Document for Chipotle on March 15th, 2024 - that puts you at month 8 of buildout. Most new franchisees hit their first accounting backlog around month 10-12 when pre-opening expenses need reconciliation with franchise reporting requirements. Who's handling your accounting setup right now?
PQS Public Data Strong (8.2/10)

New QSR/Fast Casual Franchisees in First 24 Months Post-FDD Registration

What's the play?

Same targeting but emphasizing the urgency of day 1 franchise reporting requirements. Most new franchisees underestimate how fast reporting starts and aren't prepared for the volume of data required immediately upon opening.

Why this works

The calculated opening timeline shows deep understanding of franchising. The day 1 reporting pressure creates genuine urgency. The simple yes/no question format makes it easy to engage.

Data Sources
  1. Franchise Disclosure Document (FDD) Database - franchisor_name, item_19_financial_performance, item_21_financial_obligations

The message:

Subject: Your Chipotle opens in 4 months - accounting ready? Your FDD registration (March 15, 2024) puts your opening around February 2025 based on typical Chipotle buildout timelines. Franchise reporting starts on day 1 - weekly sales, food costs, labor - and most new franchisees scramble to get accounting systems ready in the final 60 days. Is your accounting infrastructure already set up?
PQS Public Data Strong (8.5/10)

Multi-Location Restaurant Groups with Cross-State Liquor Compliance Failures

What's the play?

Target restaurant groups with liquor license violations in multiple states (California, Texas, Nevada, etc.) within a 4-6 month window. Cross-state compliance failures indicate systemic operational breakdown and lack of centralized tracking systems.

Why this works

The specificity of state counts and timeframes proves thorough research. The insight about decentralized tracking is accurate and painful for multi-state operators. The routing question naturally surfaces who owns this problem.

Data Sources
  1. California ABC Liquor License Enforcement Data - license_number, business_name, enforcement_actions
  2. Texas TABC License Violations Database - license_number, business_name, violations

The message:

Subject: Liquor violations in 3 states - California, Texas, Nevada Your restaurant group has liquor license violations in California (2 locations), Texas (1 location), and Nevada (1 location) between August and November 2024. Cross-state compliance failures usually indicate no centralized tracking system - each location managing their own renewals and training schedules. Who's overseeing liquor compliance across all your locations?
PQS Public Data Strong (8.6/10)

Multi-Location Restaurant Groups with Cross-State Liquor Compliance Failures

What's the play?

Same targeting but emphasizing the escalating penalty risk in California. The next violation triggers a 90-day suspension review, creating urgent need for compliance infrastructure.

Why this works

The California suspension threat is urgent and scary. Multi-state complexity is the exact pain point for regional operators. The question addresses the root issue of centralized oversight.

Data Sources
  1. California ABC Liquor License Enforcement Data - license_number, business_name, enforcement_actions, suspension_status
  2. Texas TABC License Violations Database - license_number, business_name, violations

The message:

Subject: 4 liquor violations across your CA, TX, NV locations Between August and November 2024, your group accumulated 4 liquor license violations across California (2), Texas (1), and Nevada (1). Each state has different penalty escalation schedules, and your next violation in California triggers the 90-day suspension review. Is someone tracking all your license renewal dates and training requirements?

Restaurant365 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 Internal Data Strong (9.1/10)

Seasonal Labor Cost Spike Forecast for Q4 High-Volume QSR Chains

What's the play?

Use aggregated transaction and labor data from 147+ QSR customer locations to forecast December labor cost spikes by ZIP code. Identify the prospect's 3 locations as high-risk based on historical patterns and offer a week-by-week forecast.

Why this works

The specific sample size (147 locations) and percentage creates credibility. Identifying the prospect's specific 3 locations as high-risk shows deep research. The forward-looking forecast is immediately valuable for planning. Easy yes/no question.

Data Sources
  1. Internal Restaurant365 Customer Data - aggregated transaction volume and labor cost data across 147+ QSR locations, segmented by ZIP code with Q1-Q4 trend analysis

The message:

Subject: Your labor costs will spike 22% in December Based on transaction data from 147 QSR locations similar to yours, December labor costs spike an average of 22% due to holiday volume and overtime scheduling conflicts. Your 3 locations are in the highest-risk ZIP codes for this spike based on historical patterns. Want the week-by-week forecast for your specific locations?
This play assumes your company has:

Aggregated transaction and labor cost data across 147+ QSR customer locations with ability to forecast seasonal patterns by ZIP code. Requires quarterly trend data showing median spike magnitude and percentile ranges.

This is proprietary intelligence competitors cannot access, making it extremely high-value for recipients.
PVP Internal Data Strong (9.3/10)

Seasonal Labor Cost Spike Forecast for Q4 High-Volume QSR Chains

What's the play?

Provide extremely specific dollar forecasts for the prospect's December labor costs based on their Q3 baseline and transaction patterns from comparable locations. Show exactly where the spike comes from (Dec 23-31, seasonal hires) and offer optimized schedule.

Why this works

Incredibly specific dollar amounts for the prospect's exact locations creates instant credibility. The Q3 baseline comparison makes it verifiable. The explanation of when and why the spike occurs is actionable. The recipient can implement this immediately.

Data Sources
  1. Internal Restaurant365 Customer Data - the prospect's Q3 labor cost data plus aggregated benchmark data from 147+ similar QSR customers

The message:

Subject: December overtime will cost you $18K extra Your 3 QSR locations averaged $82K monthly labor costs in Q3, but December will hit $100K based on transaction patterns from 147 similar locations. The $18K spike comes from holiday overtime (Dec 23-31) and undertrained seasonal hires working premium shifts. Want the daily breakdown showing exactly when the spike hits?
This play assumes your company has:

Labor cost data from the recipient's 3 locations (Q3 baseline) plus aggregated benchmark data from 147+ similar QSR customers showing December spike patterns. Requires daily granularity to show when spikes occur.

This level of specificity provides immediate financial forecast allowing proactive scheduling adjustments to reduce overtime costs.
PVP Internal Data Strong (8.7/10)

California/Texas Casual Dining with Liquor Violations + Labor Cost Spikes

What's the play?

Combine public ABC violation data with internal labor cost patterns from 23+ casual dining customers to show the correlation between compliance incidents and labor spikes. Offer proactive analysis of the prospect's other Texas locations.

Why this works

The causation explanation (manager overtime, retraining, schedule disruption) is insightful. Seeing the pattern across 23 other operators makes it credible. The proactive offer to check other locations creates immediate value.

Data Sources
  1. Texas TABC License Violations Database - violation dates by location
  2. Internal Restaurant365 Customer Data - labor cost and schedule data from 23+ casual dining customers, correlated with public compliance violation dates

The message:

Subject: Your October labor spike - here's what happened Your Austin location's 18% labor cost spike in October coincided with 2 ABC violations, and we've seen this pattern in 23 other casual dining operators. The spike comes from manager overtime covering compliance meetings, retraining staff, and schedule disruption during inspection periods. Want the compliance-labor correlation report for your other Texas locations?
This play assumes your company has:

Labor cost and schedule data from 23+ casual dining customers with ability to correlate spikes with public compliance violation dates. Requires aggregated patterns showing typical cost impact of compliance events.

Combined with public data, this creates a unique insight showing the hidden financial cost of compliance failures.
PVP Internal Data Strong (8.9/10)

California/Texas Casual Dining with Liquor Violations + Labor Cost Spikes

What's the play?

Provide extremely specific dollar amounts for overtime costs during compliance incidents at the prospect's location. Show the breakdown of why (hearings, retraining, chaos) and offer a solution that auto-adjusts schedules.

Why this works

The extremely specific dollar amount ($4,200) and percentage (47%) creates instant credibility. The breakdown of why resonates with operational reality. The solution offer is about utility, not a sales pitch.

Data Sources
  1. Internal Restaurant365 Customer Data - detailed labor cost and schedule data from the recipient's location with ability to calculate overtime during compliance event windows

The message:

Subject: Compliance incidents cost you $4,200 in October overtime Your Congress Ave location spent $4,200 in manager overtime during October's 2 ABC violations - that's 47% above your Q3 average. Compliance incidents always spike labor costs: managers covering shifts during hearings, retraining staff, schedule chaos. Want a system that auto-adjusts schedules during compliance events?
This play assumes your company has:

Detailed labor cost and schedule data from the recipient's location with ability to calculate overtime during specific compliance event windows. Requires Q3 baseline data for comparison.

This provides specific financial impact analysis that helps quantify the hidden cost of compliance failures.
PVP Internal Data Strong (8.4/10)

New QSR/Fast Casual Franchisees in First 24 Months Post-FDD Registration

What's the play?

Offer new franchisees a proven accounting setup checklist used by 89 successful franchisees in their first year. Position it as preventive intelligence to avoid the month 10-12 accounting chaos that most new franchisees hit.

Why this works

The specific filing date shows research. The month 10-12 timeline prediction is credible. Sample size of 89 franchisees is strong proof. Low-commitment ask (just send the checklist) makes it easy to say yes.

Data Sources
  1. Franchise Disclosure Document (FDD) Database - filing date, franchisor name
  2. Internal Restaurant365 Customer Data - onboarding data and best practices from 89+ Chipotle franchisee customers

The message:

Subject: Your Chipotle franchise accounting checklist You're 8 months post-FDD (filed March 15, 2024) and most new franchisees hit accounting chaos at month 10-12 when pre-opening expenses need franchise reporting reconciliation. I pulled together the exact accounting setup checklist that 89 successful Chipotle franchisees used in their first year. Want me to send you the checklist?
This play assumes your company has:

Onboarding data and best practices from 89+ Chipotle franchisee customers showing common setup mistakes and optimal configuration for day 1 reporting. Can be packaged as a branded checklist resource.

This provides a practical tool the recipient can use immediately to avoid expensive mistakes during buildout phase.
PVP Public + Internal Strong (8.8/10)

Multi-Location Restaurant Groups with Cross-State Liquor Compliance Failures

What's the play?

Combine public liquor violation records with internal data about the restaurant group's 12 locations to create a complete renewal calendar showing which locations have renewals in Q1 2025 and which states require 60-day advance filing.

Why this works

Mapping all 12 locations shows impressive research effort. The Q1 2025 renewals with 60-day requirement creates urgency. State-specific requirements address the exact pain point of multi-state operations. Easy yes/no question.

Data Sources
  1. California ABC Liquor License Enforcement Data - violation records, renewal dates
  2. Texas TABC License Violations Database - violation records, renewal dates
  3. Internal Restaurant365 Customer Data - location count and renewal schedules for the restaurant group's 12 locations

The message:

Subject: Your liquor license renewal calendar - all 12 locations You have 4 liquor violations across CA, TX, and NV (August-November 2024), and I mapped all 12 of your locations' renewal dates. 3 renewals are coming up in Q1 2025, and California requires 60-day advance filing with clean compliance history. Want the renewal calendar with state-specific requirements?
This play assumes your company has:

Internal data about the restaurant group's 12 locations and their license renewal schedules, combined with public liquor violation records and state-specific filing requirements.

This hybrid approach creates a comprehensive compliance calendar the prospect cannot assemble themselves without significant manual effort.
PVP Public + Internal Strong (9.0/10)

Multi-Location Restaurant Groups with Cross-State Liquor Compliance Failures

What's the play?

Combine public ABC violation records with internal compliance data (training records, renewal filing dates) to identify which of the prospect's 2 California locations face 90-day suspension review risk. Offer a compliance checklist to prevent escalation.

Why this works

The specific violation timing and locations show deep research. The 90-day suspension threat is urgent and scary. March 2025 renewal timing creates immediate pressure. Offering a practical tool rather than a sales pitch makes it valuable.

Data Sources
  1. California ABC Liquor License Enforcement Data - violation dates, penalty escalation status, renewal dates
  2. Internal Restaurant365 Customer Data - compliance best practices and checklists from successful customers

The message:

Subject: California suspension risk - your next violation Your 2 California locations with August and October violations are now in the ABC's penalty escalation track. The next violation at either location triggers a 90-day suspension review, and you have renewals at both locations in March 2025. Want the compliance checklist that keeps you off the suspension review list?
This play assumes your company has:

Public ABC violation records combined with license renewal dates and internal compliance best practices from Restaurant365 customers who successfully avoided penalty escalation.

This hybrid approach creates urgent value by combining regulatory intelligence with proven operational solutions.
PVP Internal Data Strong (9.4/10)

Seasonal Labor Cost Spike Forecast for Q4 High-Volume QSR Chains

What's the play?

Provide incredibly specific week-level forecast showing the prospect's most expensive labor week of the year (Dec 23-30) with exact dollar amount above normal. Show why the spike happens and offer optimized staffing plan that cuts the spike in half.

Why this works

Incredibly specific week and dollar amount creates instant credibility. The explanation (overtime rates, volume, seasonal staff) is verifiable. The concrete solution (cut to $3,200) is quantified and actionable. The value proposition is immediate and measurable.

Data Sources
  1. Internal Restaurant365 Customer Data - transaction volume and labor scheduling data from 147+ QSR customers with ability to forecast optimal staffing plans for peak periods

The message:

Subject: Week of December 23rd - your highest labor cost week December 23-30, 2024 will be your most expensive labor week of the year - $6,800 above your typical week based on transaction patterns from 147 QSR locations. The spike hits because of holiday overtime rates (1.5x) combined with 40% higher transaction volume and undertrained seasonal staff. Want the hourly staffing plan that cuts that spike to $3,200?
This play assumes your company has:

Transaction volume and labor scheduling data from 147+ QSR customers with ability to forecast optimal staffing plans for peak periods. Requires hourly granularity to show how to optimize schedules.

This provides a specific staffing optimization plan that saves $3,600 in a single week, directly improving profitability.
PVP Internal Data Strong (8.6/10)

New QSR/Fast Casual Franchisees in First 24 Months Post-FDD Registration

What's the play?

Provide new franchisees with an opening week accounting setup guide based on 89 successful franchisees. Emphasize the 15-20 hour time sink in week 1 that most operators face when accounting isn't connected to POS, and offer the solution that prevents it.

Why this works

The specific opening timeline based on FDD date shows research. The 15-20 hours pain point is real and scary for new franchisees. Sample size of 89 franchisees is strong proof. They're preventing a painful problem the prospect hasn't hit yet.

Data Sources
  1. Franchise Disclosure Document (FDD) Database - filing date, estimated opening timeline
  2. Internal Restaurant365 Customer Data - onboarding data from 89+ franchisee customers showing common setup mistakes and time spent in week 1

The message:

Subject: Day 1 franchise reporting - your opening week checklist Your Chipotle opens around February 2025 (based on March 15, 2024 FDD filing), and franchise reporting starts immediately - daily sales, food costs, labor percentages. Most new franchisees spend 15-20 hours in week 1 just trying to compile reports because accounting isn't connected to POS. Want the opening week accounting setup that 89 franchisees used to avoid the chaos?
This play assumes your company has:

Onboarding data from 89+ franchisee customers showing common setup mistakes and optimal configuration for day 1 reporting. Requires documentation of time spent in week 1 by franchisees without proper setup.

This prevents a painful problem during the most critical week of the franchise launch, creating high perceived value.
PVP Public + Internal Strong (8.8/10)

California/Texas Casual Dining with Liquor Violations + Labor Cost Spikes

What's the play?

Use public violation data from one location combined with internal labor scheduling and turnover data from the restaurant group's other Texas locations to forecast compliance risk. Show early warning signs (scheduling gaps, manager turnover) and offer proactive risk assessment.

Why this works

Analyzing all Texas locations, not just the problem one, shows proactive thinking. Early warning signs (scheduling gaps, turnover) are actionable indicators. Proactive prevention is more valuable than reactive fixing. Easy yes/no question.

Data Sources
  1. Texas TABC License Violations Database - violation data from one location
  2. Internal Restaurant365 Customer Data - labor scheduling and turnover data from the restaurant group's other Texas locations

The message:

Subject: Your other Texas locations - compliance risk forecast Your Austin location (456 Congress Ave) had 2 ABC violations + 18% labor spike in October, and I analyzed your 4 other Texas locations for similar risk patterns. 2 locations show early warning signs: late-shift scheduling gaps and manager turnover in the past 90 days. Want the risk assessment for your other locations?
This play assumes your company has:

Public violation data from one location combined with internal labor scheduling and turnover data from the restaurant group's other Texas locations to forecast compliance risk based on operational patterns.

This hybrid approach creates predictive intelligence that helps prevent future violations, which is more valuable than reactive solutions.
PVP Public + Internal Strong (9.1/10)

Multi-Location Restaurant Groups with Cross-State Liquor Compliance Failures

What's the play?

Combine public violation history with internal compliance data (training records, renewal filing dates) from the restaurant group's 12 locations to predict which 3 locations are most at risk for future violations. Offer violation risk forecast for all 12 locations.

Why this works

Analyzing all 12 locations for predictive patterns shows deep analysis. Early indicators (expired certs, late filings) are specific and actionable. Preventing the next violation is extremely valuable. The risk forecast concept is compelling.

Data Sources
  1. California ABC Liquor License Enforcement Data - violation history
  2. Texas TABC License Violations Database - violation history
  3. Internal Restaurant365 Customer Data - compliance data (training records, renewal filing dates) from the restaurant group's 12 locations

The message:

Subject: Your 12 locations - which ones are next for violations? You've had 4 liquor violations across CA, TX, NV in the past 4 months, and I analyzed all 12 of your locations for risk patterns. 3 locations show the same early indicators that preceded your August violations: expired training certifications and late renewal filings. Want the violation risk forecast for all 12 locations?
This play assumes your company has:

Public violation history combined with internal compliance data (training records, renewal filing dates) from the restaurant group's 12 locations to predict future violations based on operational patterns.

This hybrid approach creates predictive intelligence showing which locations are at highest risk, enabling proactive intervention.
PVP Internal Data Strong (9.5/10)

Seasonal Labor Cost Spike Forecast for Q4 High-Volume QSR Chains

What's the play?

Analyze the prospect's November schedule pattern and project it to December volume to identify 47 overtime shifts scheduled between Dec 20-31. Calculate exact cost ($16,920) and show that 31 shifts could be eliminated with better seasonal hire allocation. Offer optimized December schedule.

Why this works

Incredibly specific: 47 shifts, exact dates, exact dollar amount. They analyzed the prospect's November schedule and projected forward. The solution (31 shifts eliminated) is quantified and actionable. The recipient can implement this immediately.

Data Sources
  1. Internal Restaurant365 Customer Data - the prospect's November scheduling data with ability to project December needs based on transaction volume forecasts and optimal staffing models

The message:

Subject: Your December schedule - 47 overtime shifts flagged I analyzed your November schedule pattern and projected it to December volume - you're scheduled for 47 overtime shifts between Dec 20-31. At $24/hour base rate, those shifts cost $16,920 extra, and 31 of them could be eliminated with better seasonal hire allocation. Want the optimized December schedule that cuts those 31 shifts?
This play assumes your company has:

Access to the recipient's November scheduling data with ability to project December needs based on transaction volume forecasts and optimal staffing models. Requires ability to identify which specific shifts can be eliminated.

This provides an optimized schedule that saves $11,160 in a single two-week period, directly improving December profitability.

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 Austin location had 2 ABC violations in October" instead of "I see you're hiring for compliance 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 or proprietary internal benchmarks. Here are the sources used in this playbook:

Source Key Fields Used For
NYC Restaurant Inspection Results Database establishment_name, camis_number, inspection_date, violation_code, grade QSR Chains with Health Department Violations
California ABC Liquor License Enforcement Data license_number, business_name, address, enforcement_actions, suspension_status Casual Dining with Liquor License Compliance Requirements, Multi-Location Restaurant Groups with Cross-State Violations
Texas TABC License Violations Database license_number, business_name, address, violations, fine_amount Casual Dining with Liquor License Compliance Requirements, Multi-Location Restaurant Groups with Cross-State Violations
Franchise Disclosure Document (FDD) Database franchisor_name, item_19_financial_performance, item_21_financial_obligations, number_of_franchises New QSR/Fast Casual Franchisees in First 24 Months Post-FDD Registration
FDA Enforcement Reports & Recalls recall_number, recall_initiation_date, product_description, reason_for_recall Multi-Unit QSR Franchises, Multi-Location Casual Dining Groups
Restaurant365 Internal Benchmarks - Labor Cost aggregated_labor_cost_percentage_by_segment, seasonal_spike_magnitude, restaurant_type_segmentation Seasonal Labor Cost Spike Forecasts, Compliance + Labor Cost Correlation
Restaurant365 Internal Benchmarks - Food Cost aggregated_food_cost_percentage_by_segment, violation_status_correlation Multi-Unit QSR Franchisees with Health Violations + Above-Peer Food Costs
Restaurant365 Customer Onboarding Data franchise_type, setup_time, common_mistakes, best_practices New Franchisee Accounting Setup Checklists and Opening Week Guides