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 Toast 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 facility at 1234 Industrial Pkwy received EPA violation #2024-XYZ on March 15th" (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 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.
State ABC liquor license databases identify active bars and nightclubs by license number and location. Cross-referencing these against DOL Wage and Hour Division enforcement actions for NAICS 722 (Food Services) reveals bars with documented FLSA tip-credit violations and specific back-wage amounts owed. This combination targets establishments with proven, public payroll dysfunction that neither dataset alone reveals.
A bar owner who's been cited for tip violations feels exposed—the violation is public record, the back-wage amount is specific and verifiable, and they know fixing tip tracking is urgent. Naming their exact license number and DOL case signals you've done real research, not sent a template. The closing question (Is someone already fixing how tips get tracked?) feels conversational, not accusatory, and is easy to answer with one word.
DOL WHD data surfaces specific back-wage amounts and case IDs tied to FLSA tip violations at bars identified via state liquor license records. The combination allows you to reference the exact dollar figure owed and alert recipients to escalation risk (liquidated damages doubling the amount on a second citation), making the urgency concrete and actionable.
The prospect feels seen because you've named the exact amount they owe and explained a consequence they may not have fully considered (liquidated damages escalation). Offering to share the case ID adds utility—they can pull the DOL file themselves to verify and act. The tone is informative rather than threatening, which lowers defensiveness.
Restaurant health inspection open data (Socrata APIs across NYC, LA, King County, Austin) identifies establishments with 2+ critical violations in the trailing 12 months. Joining this against DOL WHD tip enforcement actions by establishment name and address reveals restaurants with simultaneous operational and payroll dysfunction. The two-source combination signals systemic breakdown that single-source targeting cannot reveal.
A restaurant owner facing both health violations and a DOL tip case feels the weight of compounded operational failures. When you connect the two publicly-available facts about their specific establishment, you demonstrate that their problems are interconnected—not isolated incidents. The inference that manual processes are the root cause is plausible and invites them to either confirm or correct your understanding, opening dialogue.
Health inspection data provides specific violation dates and counts; DOL WHD data surfaces parallel tip enforcement actions. Cross-referencing by establishment name and address identifies restaurants where operational and compliance risks have converged. Citing the exact inspection date and violation count adds credibility; framing both as symptoms of manual process overload opens the conversation without accusation.
The prospect is caught between two regulatory pressures. When you cite the exact inspection date and connect it to their payroll case, they recognize you've done homework. The question 'Who owns fixing the back-of-house workflow?' is low-effort to answer and positions the solution (unified POS and payroll integration) as the natural remedy, without explicitly pitching.
These messages provide actionable intelligence before asking for anything. The prospect can use this value today whether they respond or not.
For Toast customers operating 6+ locations with integrated delivery platforms, internal order management and kitchen-display system data reveals prep-time and cancellation-rate variance by location and platform. Benchmarking each location's performance against peer restaurants of similar size and cuisine type (privacy-safe aggregate) identifies locations with above-benchmark cancellation rates and quantifies the monthly revenue leakage in dollars. This play targets existing customers with specific operational intelligence no competitor can replicate.
The recipient hears their own exact numbers—6 locations, Midtown store, 5.1% DoorDash cancellation rate, $3,200/month leakage—which immediately signals credibility. The time-window insight (7-9pm clustering) feels like insider knowledge and anchors the root cause (8.4-min prep vs. 5.8-min peer average). Offering the per-location breakdown plus the three operational fixes their top store already uses positions Toast as a partner with solutions, not a vendor asking for a meeting.
Toast KDS prep-time data and payment cancellation data by location/platform, plus peer benchmark of 10+ comparable restaurant entities by cuisine/volume tier.
Competitive advantage: No POS or payments competitor has integrated kitchen-display system data and real-time cancellation tracking across platforms. The peer benchmark is privacy-safe (aggregated across 1000+ restaurants) but specific enough to isolate location-level performance gaps. This message is only valuable to existing Toast customers with delivery integrations.Toast customers with multi-location operations and delivery integrations can be benchmarked for prep-time variance by location and platform. Internal data reveals which locations underperform on Uber Eats, DoorDash, or other platforms relative to the restaurant group's own top performer and peer groups. Quantifying the monthly revenue impact isolates the operational (vs. market-driven) nature of the gap, enabling the prospect to prioritize fixes.
Naming the exact underperforming location and platform with specific prep-time and cancellation data creates immediate credibility—the prospect knows you have their data. The distinction between operational and market-driven causes (same neighborhood density as top performer, just slower during dinner rush) is a sharp insight that shows analytical depth. Offering the per-store report and the specific staffing-timing fix empowers immediate action without requiring a sales meeting.
Toast KDS prep-time data and payment cancellation data by location/platform; peer benchmark derived from 10+ comparable restaurant groups.
Competitive advantage: Toast's integrated kitchen display and payment processing data enables location-level performance comparison across platforms. The root-cause analysis (operational vs. market) requires both prep-time (KDS) and cancellation (order management) signals. Competitors using only payment data cannot isolate operational causes of cancellation variance.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 Dallas facility has 3 open OSHA violations from March" instead of "I see you're hiring for safety 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 public data. Here are the sources used in this playbook:
| Source | Key Fields | Used For |
|---|---|---|
| State ABC Liquor License Databases (Multi-State) | license_number, license_type, establishment_name, address, license_status | Identifying active bars and nightclubs eligible for targeted outreach; filtering by license type isolates bars/nightclubs from breweries or retail. |
| DOL Wage and Hour Division Compliance Action Data | violation_type, back_wages_due, employees_affected, case_id, establishment_name, naics_code, establishment_address | Surfacing FLSA tip violations and back-wage amounts in NAICS 722 (Food Services); joining with liquor license and health inspection data to identify establishments with documented payroll dysfunction. |
| Restaurant Health Inspection Open Data (Multi-City/State) | establishment_name, address, inspection_date, critical_violation_flag, violation_count, cuisine_type | Identifying restaurants with 2+ critical violations in trailing 12 months; joining with DOL data to detect stacked operational and payroll failures; enabling cuisine-type segmentation (fine dining vs. QSR). |
| Toast Internal Order and Payment Data | cancellation_rate_by_location_platform, prep_time_by_location_hour, platform_revenue_net_of_fees, location_id, timestamp, platform_name | Benchmarking multi-location customer performance against peer restaurants; isolating location/platform-level cancellation and prep-time gaps; quantifying monthly revenue leakage from delivery platform underperformance. |