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 Arctic Glacier 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 Phoenix restaurant had 3 refrigeration violations on November 8th - your liquor license renews March 15th" (state inspection database with exact dates)
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 demonstrate precise understanding of the prospect's situation (PQS) or deliver immediate actionable value (PVP). All plays are ordered by quality score - highest impact first.
Use aggregated consumption data from your 75,000 customer locations to show convenience stores and restaurants how their ice consumption compares to similar businesses in their ZIP code. Flag under-ordering that indicates stockout risk and lost sales opportunities.
You're surfacing a competitive blind spot they didn't know existed. When you tell a convenience store manager "you're using 420 lbs/week but similar stores in your ZIP average 890 lbs" - that 470 lb gap represents lost beverage sales during evening rush. This is intelligence they cannot get from any competitor or consultant.
This play requires aggregated delivery volume data across 50+ similar customer locations (by type, size proxy, ZIP code) with percentile ranges (25th, 50th, 75th) and day-of-week/time-of-day patterns.
This is proprietary data only Arctic Glacier has - competitors cannot replicate this benchmark intelligence.Cross-reference major event calendars (festivals, sporting events, concerts) with Arctic Glacier's historical delivery patterns to alert convenience stores and restaurants 10-14 days before predictable demand surges. Offer pre-positioned inventory at normal pricing to avoid emergency order premiums.
You're giving them actionable intelligence with a specific deadline. "Last year ACL weekend, stores near Zilker spiked 540% ice demand" is a credible pattern they can't ignore. The day-by-day forecast makes it immediately useful, and pre-positioning offer removes all friction.
This play requires 3-5 years of historical delivery patterns correlated with major events, including spike magnitude (% increase vs baseline), event proximity impact radius, and day-by-day demand curves. Must geocode customer locations to identify those within impact zones.
Combined with public event schedules, this synthesis creates predictive intelligence unique to Arctic Glacier's operational footprint.Alert stores near major festival venues that competing bars/restaurants in their vicinity will create supply scarcity. Use Arctic Glacier's historical event data to show last year's spike magnitude and offer day-by-day surge forecasts.
The scarcity angle ("78 bars within 1 mile of your locations will surge demand") creates urgency. The 410% spike from last year's SXSW is a credible pattern, and the day-by-day forecast removes all guesswork about when to stock up.
This play requires historical delivery patterns around SXSW (3-5 years), geocoded customer and competitor locations within event impact zones, and day-by-day demand curves showing when surge peaks.
The competitor density mapping combined with your delivery history creates unique scarcity intelligence.Alert convenience stores near major sporting venues when playoff games create predictable demand surges. Use Arctic Glacier's historical data to show playoff game impact vs regular season baseline, with ranked list of bars by proximity to customer locations.
The specificity (62 bars, exact stadium capacity, playoff vs regular season comparison) proves you've done real analysis. The ranked list by distance makes it immediately actionable - they know exactly which accounts will surge first.
This play requires historical delivery data comparing playoff vs regular season game impact (3-5 years), geocoded bar/restaurant customer locations within 3-mile radius of stadiums, and proximity-ranked lists.
The playoff vs regular season comparison is unique intelligence from your operational history.Use aggregated consumption data from Arctic Glacier's beachfront restaurant customers to show Ocean Drive operators how their ice usage compares to peer restaurants. Connect the consumption gap directly to lost beverage sales during peak service hours.
Beachfront restaurants have unique consumption patterns (high beverage sales, tourist-driven volume). When you tell them "peer beachfront restaurants in 33139 average 3,400 lbs/week" and connect their 1,300 lb gap to lost beverage revenue, you're hitting their core KPI.
This play requires delivery data for beachfront restaurant customers segmented by location characteristics (beachfront, tourism density) and ZIP code, with consumption patterns by service period (lunch vs dinner).
The location-specific segmentation (beachfront vs inland) creates benchmark intelligence competitors cannot replicate.Alert distributors serving bars near playoff venues that demand will surge 6 hours before kickoff. Provide ranked list of bars by stadium distance so they can prioritize pre-positioning inventory.
The timing insight ("bars run out 6 hours before kickoff") is operationally valuable. The ranked list of 47 bars by distance removes all guesswork - they know exactly where to send inventory first.
This play requires historical delivery patterns during playoff games showing stockout timing (how many hours before kickoff demand peaks), geocoded bar locations within 2-mile radius, and proximity-ranked lists.
The stockout timing analysis is unique operational intelligence from your delivery history.Alert beach-adjacent convenience stores 10-14 days before Fourth of July weekend that demand will spike 450% vs normal summer weekends. Use Arctic Glacier's historical holiday data to provide store-by-store surge forecasts and pre-positioning recommendations.
Fourth of July is the biggest ice demand weekend of the year for coastal stores. When you tell them "last year July 4th weekend, coastal stores spiked 450%" and offer store-by-store forecasts with pre-positioning recommendations, you're removing all risk from their biggest sales opportunity.
This play requires 3-5 years of historical delivery data for July 4th weekend segmented by store proximity to beaches, with spike magnitude (% increase vs summer baseline) and store-level forecasting models.
The coastal vs inland segmentation and holiday-specific patterns are unique to your operational footprint.Use aggregated consumption data from Arctic Glacier's tourist hotel customers to show International Drive properties how their ice usage compares to peer hotels. Connect consumption gaps to specific guest amenity shortfalls (poolside ice stations, in-room amenities).
Hotels measure success by guest satisfaction scores. When you tell them "peer tourist hotels in 32819 average 8,200 lbs/week" and connect their 3,400 lb gap to poolside ice stations running empty or checkout peak shortfalls, you're hitting their core operational KPI.
This play requires delivery data for hotel customers segmented by property type (tourist vs business travel), location characteristics (tourist districts), and property size proxy (room count or weekly volume tier).
The tourist hotel segmentation creates benchmark intelligence specific to Orlando's hospitality market.Use Arctic Glacier's day-of-week consumption data to show convenience store chains that their Friday ordering is under-optimized compared to peer QT stores in same ZIP. Highlight that Friday evening drives majority of weekly ice sales.
The day-of-week insight is immediately actionable. When you tell them "peer QT stores in your ZIP order 2,100 lbs on Fridays" and connect it to "Friday evening drives 38% of weekly sales," they can optimize ordering today to prevent weekend stockouts.
This play requires delivery volume data tracked by day-of-week across convenience store customers, segmented by chain type (QT vs other brands) and ZIP code, with daypart analysis (time-of-day patterns).
The day-of-week and daypart patterns are proprietary insights from your delivery scheduling data.Cross-reference National Weather Service heat forecasts with Arctic Glacier's historical heat-driven demand patterns to alert stores in hottest ZIP codes 8 days before surge. Offer pre-positioning at high-risk locations.
You're identifying their specific store locations in hottest ZIPs and connecting it to last summer's 380% spike. The pre-positioning offer removes all friction - they just say yes and you handle the rest.
This play requires 3-5 years of historical delivery data correlated with temperature patterns at ZIP code granularity, showing spike magnitude (% increase) when temps exceed thresholds (100°F+, 103°F+).
Combined with NWS forecasts, this creates predictive intelligence unique to your operational footprint and delivery history.Use Arctic Glacier's consumption data for entertainment district bars to show Broadway honky-tonks how their usage compares to peers. Highlight that Friday/Saturday nights drive 68% of weekly consumption for this venue type.
Entertainment district bars have extreme weekend concentration patterns. When you tell them "peer honky-tonks on Broadway average 5,100 lbs/week" and connect it to "Friday/Saturday nights drive 68% of consumption," they can optimize weekend ordering immediately.
This play requires delivery data for bar customers segmented by location type (entertainment districts like Broadway) and venue type (honky-tonks vs other bar formats), with day-of-week and time-of-day consumption patterns.
The entertainment district and venue-type segmentation creates benchmark intelligence specific to Nashville's nightlife market.Use Arctic Glacier's consumption data from Strip casino properties to show operators how their usage compares to peer casinos. Connect the consumption gap to specific operational shortfalls (poolside amenities, convention center supply).
Strip casinos compete on guest experience and convention business. When you tell them "comparable Strip casinos average 32,000 lbs/week" and connect their 14,000 lb gap to poolside amenity shortfalls or convention center constraints, you're hitting operational pain points.
This play requires delivery data for casino customers segmented by location (Strip vs off-Strip) and property tier/size, with consumption patterns identifying amenity-driven demand (pools, conventions).
The Strip casino segmentation creates benchmark intelligence specific to Las Vegas hospitality market dynamics.Alert convenience store chains 12 days before National Weather Service heat dome forecasts that their stores in top heat zones will surge demand 340%. Offer to model store-level surge risk so they can pre-position inventory at highest-risk locations.
Multi-store chains need to allocate inventory across locations. When you tell them "your 7 stores are in the top heat zone" and offer store-level surge modeling, you're solving their distribution planning problem with data they don't have.
This play requires historical delivery data correlated with temperature thresholds (100°F+, 105°F+) showing spike magnitude and stockout timing (day 3 of heat wave). Must geocode customer store locations to map against heat zone forecasts.
The temperature-correlated demand patterns and stockout timing are unique operational intelligence from your delivery history.Alert convenience store chains 2-3 weeks before Memorial Day weekend that their Phoenix stores in top heat zones will spike 290% vs normal weekends based on last year's pattern. Offer store-level surge risk modeling.
Memorial Day is a predictable high-demand holiday. When you combine it with Phoenix heat (108°F forecast) and show last year's 290% spike with their 7 stores identified in heat zone, you're removing all uncertainty about inventory needs.
This play requires 3-5 years of Memorial Day weekend delivery data for Phoenix market, segmented by temperature conditions and store locations within heat zones. Must compare holiday weekend demand vs normal weekend baseline.
The holiday-specific patterns combined with heat correlation create predictive intelligence unique to your Phoenix market history.Target restaurants with refrigeration/temperature control violations in their last 1-2 inspections whose liquor licenses expire within 90 days. Arizona ABC cross-checks health department compliance before processing renewals - unresolved cold storage violations create renewal denial risk.
You're surfacing a hidden compliance deadline they may not know about. When you tell them "Arizona ABC cross-checks health dept compliance" and connect their open violation to March 15th renewal deadline, you create urgency with a specific consequence (renewal delay/denial).
Target restaurants with critical ice machine contamination violations (mold, inadequate maintenance) whose liquor licenses renew within 60-90 days. Arizona requires critical violations cleared 45-60 days before renewal.
Ice machine violations are critical category - immediate health risk. When you cite specific violation details (mold in dispenser) with exact inspection date and connect it to 60-day clearance deadline, you're highlighting urgent operational risk.
Target restaurants with refrigerator temperature violations (above 38°F safe threshold) whose liquor licenses renew within 60-90 days. Unresolved cold storage violations trigger automatic ABC renewal delays in Arizona.
The specific temperature reading (41°F) vs safe threshold (38°F) proves real research. Connecting it to "automatic renewal delays" creates consequence urgency with February 28th deadline approaching.
Target restaurants with critical ice machine mold contamination violations whose liquor licenses renew within 90 days. Arizona requires critical violations cleared 45 days before renewal processing begins.
Mold contamination is critical violation category - immediate health risk. The 45-day clearance deadline creates urgency, and asking "is replacement already scheduled" shows you understand the fix timeline.
Target restaurants with 2+ open refrigeration violations (walk-in cooler, prep cooler temps above threshold) whose liquor licenses renew within 90 days. Arizona ABC won't process renewals until all critical violations clear.
Multiple violations (walk-in at 44°F, prep cooler at 46°F) with specific temps proves thorough research. "ABC won't process renewal until violations clear" is a hard blocker with May 20th deadline creating urgency.
Target restaurants with walk-in cooler temperature violations (temps above 38°F safe threshold) whose liquor licenses renew within 90 days. Arizona ABC cross-checks health violations before processing July 1st license renewals.
The specific address, temp reading (48°F), and safe threshold (38°F or below) shows real inspection data research. "ABC cross-checks health violations" is concerning process detail that creates renewal urgency.
Use Arctic Glacier's consumption data for brunch-focused restaurants to show Montrose operators how their usage compares to peer brunch spots in same ZIP. Highlight that Saturday/Sunday brunch drives 55% of weekly consumption for this venue type.
Brunch restaurants have extreme weekend concentration patterns. When you tell them "peer brunch restaurants in 77006 average 2,600 lbs/week" and connect it to "Saturday/Sunday brunch drives 55% of consumption," they can optimize weekend ordering immediately.
This play requires delivery data for restaurant customers segmented by service type/cuisine focus (brunch-focused vs other formats), ZIP code, with day-of-week and daypart consumption patterns (brunch hours vs other periods).
The service-type segmentation and brunch-specific patterns are unique insights from your restaurant customer base.Target restaurants with open walk-in cooler violations in county inspection records whose liquor licenses renew within 90 days. Arizona ABC won't process renewals until health violations clear from county system.
Calling out "still open in Maricopa County records" proves you checked the official system. The ABC blocker ("won't process renewal until violations clear") creates hard deadline urgency with April 2nd renewal date.
Target restaurants with critical ice machine contamination violations whose liquor licenses renew within 90 days. Arizona requires violation clearance 30 days before liquor license renewal processing begins.
The specific address, exact inspection date, and critical violation type (ice machine contamination) proves thorough research. The 30-day clearance requirement creates clear deadline with April 10th renewal approaching.
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 Phoenix restaurant had 3 refrigeration violations on November 8th - your liquor license renews March 15th" instead of "I see you're hiring for operations 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.
Every play traces back to verifiable data. Here are the sources used in this playbook:
| Source | Key Fields | Used For |
|---|---|---|
| State Food Establishment Inspection Reports | violations_found, health_score, inspection_date, establishment_name, address, city, county, state | Restaurants with refrigeration violations approaching license renewal |
| State Liquor Authority License Databases | license_number, license_type, license_expiration_date, license_status, premises_name, address | License renewal timing for restaurants with health violations |
| National Weather Service Forecasts | temperature_forecast, heat_advisory_dates, ZIP_code_coverage | Heat wave surge alerts (combined with internal delivery patterns) |
| Public Event Calendars | event_name, event_dates, venue_location, expected_attendance | Festival and sporting event demand surge alerts (combined with internal patterns) |
| Internal Delivery Records | ice_consumption_lbs, customer_type, ZIP_code, day_of_week, delivery_date, customer_address | Peer consumption benchmarks, demand surge patterns, heat correlation, event impact analysis |
| Internal Historical Event Data | event_type, demand_spike_magnitude, stockout_timing, customer_locations, event_proximity | Predictive surge forecasts for festivals, sporting events, holidays |