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.
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 Food Travel Experts (SSP Group) SDR Email:
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.
Blueprint flips the approach. Instead of interrupting prospects with pitches, you deliver insights so valuable they'd pay consulting fees to receive them.
Stop: "I see you're hiring compliance people" (job postings - everyone sees this)
Start: "Your Terminal B Starbucks had 3 critical health code violations in the January 14th inspection" (government database with record number)
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.
These messages are ordered by quality score (highest first). Each demonstrates either precise understanding of the prospect's current situation (PQS) or delivers immediate actionable value (PVP).
Cross-reference public FAA terminal certification schedules with internal data on soft opening performance to alert airports about pre-launch revenue opportunities they're likely missing.
You're surfacing a revenue opportunity window (soft opening period) the airport operations team may not have considered. The specificity of the FAA certification date proves you've done real research, and the $180K revenue figure creates immediate urgency.
This play requires soft opening performance data from SSP's terminal launch history: revenue captured during pre-certification periods, optimal soft opening timelines, and brand partner coordination requirements.
This is proprietary operational data only SSP has - competitors cannot replicate this revenue insight.Use internal revenue per square foot data across SSP's 550+ airport locations, segmented by passenger demographics, to show airports which brands perform best for their specific passenger mix.
Airports want to maximize concession revenue but lack performance benchmarking across their peer airports. You're providing concrete financial data ($847 vs $612 per sq ft) that directly informs their RFP brand selection decisions.
This play requires SSP's revenue per square foot data across their 550+ locations, segmented by brand type and passenger demographics (business vs leisure traveler percentages).
This is proprietary performance data only SSP has from operating across 40+ countries - competitors lack this dataset.Cross-reference public airport RFP deadlines and terminal opening dates with internal data on typical launch timelines to identify airports at risk of missing their opening day F&B service.
You're identifying a critical operational risk (missing opening day by 3-4 weeks) that the airport may not have quantified. The specificity of 77 days and 47 terminal launches proves you're speaking from experience, not guessing.
This play requires SSP's terminal launch timeline data: average days from contract award to operational launch, broken down by whether brand partnerships were pre-negotiated or not.
This is proprietary operational intelligence only SSP has from managing 47+ terminal openings globally.When an airport issues an F&B RFP, use SSP's performance data from 550+ locations to recommend the exact brand portfolio that maximizes revenue for airports with similar passenger demographics and dwell times.
Airports writing RFP specifications lack benchmarking data on which brand combinations perform best. You're providing a data-driven recommendation (23% higher revenue) specific to their passenger profile that directly improves their RFP evaluation.
This play requires SSP's aggregated outlet revenue data across 550+ locations, segmented by brand portfolio type (casual dining, QSR, coffee, local concepts) and airport passenger demographics (business vs leisure mix, dwell time).
This is proprietary performance benchmarking data only SSP has - competitors lack this global dataset.Cross-reference public airport terminal opening announcements and passenger projections with internal data on optimal hiring timelines to help airports avoid understaffing at launch.
You're identifying a critical operational risk (understaffing at terminal launch) with concrete numbers (87 staff needed, 95% vs 67% day-one readiness). The 12-week hiring timeline is immediately actionable and backed by real performance data.
This play requires SSP's terminal opening staffing data: staff-to-passenger ratios by outlet type, hiring timeline correlations with day-one readiness, and local recruiting partner effectiveness by market.
This is proprietary operational data only SSP has from managing terminal launches globally.When airports issue F&B concession RFPs, cross-reference the incumbent operator's restaurant license violations and inspection failures from state health databases to identify contracts at risk due to operational compliance issues.
You're surfacing verifiable operational red flags (7 unresolved violations across 4 locations) that directly impact the airport's RFP evaluation criteria (25% compliance scoring). The airport operations team needs this information for their procurement process.
Use internal transaction value data from SSP's 550+ locations to show airports how brand choice impacts revenue per transaction based on their specific passenger demographics.
You're demonstrating that the airport is leaving money on the table ($127 vs $68 average transaction) by having the wrong brand mix for their passenger demographics. This directly impacts their concession revenue targets.
This play requires SSP's average transaction value data by brand type, segmented by airport passenger demographics (business vs leisure traveler mix and average dwell time).
This is proprietary performance data only SSP has from operating across 31+ comparable airports globally.Use internal data correlating passenger dwell time with F&B spending patterns to recommend specific brand placement by gate area within the airport terminal.
You're providing gate-specific recommendations based on dwell time analysis (68 minutes correlates with 40% higher spending at full-service). This level of operational detail proves you understand airport F&B optimization at a granular level.
This play requires SSP's spending pattern data showing correlation between passenger dwell time and spending by F&B service type (full-service, quick-service, coffee, retail food), plus optimal brand placement recommendations by gate area.
This is proprietary operational intelligence only SSP has from optimizing 550+ airport locations globally.Cross-reference active airport F&B RFPs with Department of Labor complaint databases to identify incumbent operators with unresolved labor violations that conflict with RFP requirements.
You're surfacing verifiable labor compliance issues (12 DOL complaints with case numbers) that directly conflict with the airport's RFP requirement for clean labor records. The procurement team needs this information for their evaluation process.
Use internal passenger satisfaction data showing that leisure travelers prefer local F&B concepts, then provide vetted local operator recommendations for specific gate areas with high leisure traveler volume.
You're identifying a passenger experience gap (22% higher satisfaction with local concepts) specific to their gate area (22-26 with 58% leisure travelers) and providing a practical solution (vetted local operators who meet airport compliance standards).
This play requires SSP's passenger satisfaction data correlated with brand mix (local concepts vs national chains) segmented by passenger type (business vs leisure), plus vetted local operator partnerships by market.
This is proprietary benchmarking data only SSP has from operating across multiple airport demographics globally.When airports issue F&B RFPs, search state health inspection databases for critical violations at specific incumbent operator locations (by facility name and address) to identify urgent compliance issues impacting RFP evaluation.
You're identifying a specific, verifiable health code violation (Terminal B Starbucks, January 14th, 3 critical violations) at a moment when it matters most (RFP evaluation period). The airport can verify this in 60 seconds with the health department.
Cross-reference airport operations logs (if publicly accessible) or observable closure patterns with RFP timing to quantify revenue loss from incumbent operator staffing failures.
You're quantifying a revenue loss ($47K) from verifiable operational failures (14 closure days in Q4) at a moment when the airport is evaluating F&B operators. This makes the cost of keeping the incumbent operator tangible.
Reference publicly available airport operations reports or RFP documentation showing incumbent operator quality audit performance that falls below the airport's stated RFP requirements.
You're demonstrating a pattern of operational failure (4 of 6 audits failed, 33% vs 85% requirement) using the airport's own performance data. The compliance team needs to know this for RFP evaluation.
Old way: Spray generic messages at job titles. Hope someone replies.
New way: Use public data to find airports in specific painful situations (active RFPs with incumbent operator compliance issues). Then mirror that situation back to them with evidence (health violations, labor complaints, audit failures).
Why this works: When you lead with "Your Terminal B Starbucks had 3 critical health code violations in the January 14th inspection" instead of "I see you're hiring for F&B 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 (state health inspections, DOL complaints, RFP databases) with specific situations (active procurement with compliance-challenged incumbents). Your team can replicate this using the data recipes in each play.
Every play traces back to verifiable data. Here are the sources used in this playbook:
| Source | Key Fields | Used For |
|---|---|---|
| FAA Airport Financial Reporting Program (Form 5100-127) | concession_revenue, nonaeronautical_revenue, airport_name, fiscal_year | Revenue benchmarking, financial performance analysis |
| ACI-NA Concessions Benchmarking Survey | revenue_per_enplaned_passenger, rent_per_sq_ft, food_beverage_metrics, contract_length | Peer performance comparison, pricing optimization |
| TSA Passenger Volume Data | passenger_screening_count, daily_updates, airport_location, historical_comparison | Demand forecasting, seasonal trends |
| Bureau of Transportation Statistics | passenger_count, enplanement_data, airline_activity, airport_code | Traffic volume analysis, growth signals |
| ACI-NA RFP List Database | airport_name, concession_type, rfp_issue_date, deadline, contract_value_estimate | Active procurement opportunities, buying signals |
| Federal Railroad Administration - Amtrak Service Quality Reports | station_name, ridership_data, on_time_performance, customer_satisfaction | Railway station F&B opportunity sizing |
| Amtrak Stations Dataset (BTS/USDOT) | station_name, location_coordinates, state, service_routes | Multi-location expansion planning |
| State Restaurant Licensing & Inspection Databases | establishment_name, license_status, inspection_date, violations, address | Incumbent operator compliance risk assessment |
| LinkedIn Company & Employee Data | employee_count, hiring_trends, department_hiring, turnover_signals | Growth signals, capacity strain indicators |
| Department of Labor Complaint Database | company_name, complaint_date, location, case_number, resolution_status | Labor compliance risk assessment for incumbent operators |
| SSP Internal Outlet Performance Data (PROPRIETARY) | revenue_per_sq_ft, transaction_value, brand_type, passenger_demographics | Brand performance benchmarking, optimal mix recommendations |
| SSP Terminal Launch Timeline Data (PROPRIETARY) | contract_to_opening_days, revenue_ramp_curve, staff_readiness_by_timeline | Launch timeline optimization, staffing models |
| SSP Passenger Satisfaction Data (PROPRIETARY) | nps_scores, brand_mix_correlation, passenger_segment, gate_area | Brand placement optimization, local vs chain performance |