About This Playbook
This playbook was generated using the Blueprint GTM methodology, which uses public data sources to identify pain-qualified prospects and craft hyper-personalized outreach messages.
Created by: Jordan Crawford, Blueprint GTM
Company Analyzed: Toast (Restaurant POS and Management Platform)
Target Persona: Restaurant Owners / General Managers at independent restaurants
The Old Way (Generic SDR Spray)
Most sales development emails look like this:
Subject: Quick Question about [Restaurant Name]
Hi [First Name],
I noticed on LinkedIn that [Restaurant Name] recently expanded. Congrats on the growth!
I wanted to reach out because we work with restaurants like [Competitor 1] and [Competitor 2] to help with operational efficiency and payment processing.
Our platform offers modern POS terminals, integrated online ordering, and streamlined payment processing. We've helped restaurants increase revenue by 15-20%.
Would you have 15 minutes next week to explore how we might be able to help [Restaurant Name]?
Best,
Generic SDR
Why This Fails:
- Zero specificity: "Recently expanded" could mean anything. No dates, no data, no proof of research.
- Obvious pain: Every restaurant knows they need "operational efficiency." This offers no new insight.
- Generic social proof: Competitor name-dropping without context is meaningless.
- Unmeasured value: "Increase revenue by 15-20%" is a vague industry average, not tied to THEIR situation.
- High friction ask: "15 minutes next week" requires calendar coordination before seeing any value.
The New Way (Blueprint GTM Methodology)
The Blueprint approach flips traditional SDR tactics:
1. Hard Data Over Soft Signals
Soft signals (OLD): "I saw you're growing" / "Congrats on the expansion" / "I noticed your LinkedIn post"
Hard data (NEW): Specific, verifiable facts from public databases: "Your restaurant has 142 Google reviews in the past 30 days" / "Your menu shows 28% average markup on DoorDash vs your website"
2. Pain-Qualified Segments (PQS)
Identify prospects in PROVABLE painful situations using external data. Not "are you interested in POS systems?" but "your current delivery dependency is costing you $4,200/month in commissions."
3. Permissionless Value Propositions (PVP)
Deliver value BEFORE asking for a meeting. Instead of "let me tell you about our product," send "here's your commission analysis across 47 menu items—want the full breakdown?"
The Texada Test (Quality Bar)
Every message must pass three criteria:
- Hyper-specific: Dates, numbers, record IDs—not "recently" or "many"
- Factually grounded: Every claim traces to a verifiable data source
- Non-obvious synthesis: Insights the prospect doesn't already have
⚠️ IMPORTANT: Limited Fit Assessment
Honest Assessment: Toast is an
operational efficiency platform that solves real problems (fragmented systems, high payment fees, manual processes), but these pains are
NOT externally detectable through public data sources.
The Blueprint GTM methodology excels when:
- Regulatory/compliance pain creates urgency (violations, deadlines, audits)
- External data PROVES the prospect is in a painful situation
- Buying the product directly resolves that documented pain
Toast's challenge: Most target pains (system fragmentation, training burden, manual reconciliation) are only visible INTERNALLY. Public data reveals delivery platform usage and review velocity, but not whether restaurants are frustrated with their current POS.
Result: This playbook contains 1 validated segment (below the ideal 2-3 minimum) focused on third-party delivery dependency—the ONE pain that IS externally detectable.
Play 1: Third-Party Delivery Dependency (PQS Messages)
Segment Definition: High-volume independent restaurants (100+ Google reviews/month) using DoorDash/Uber Eats without direct online ordering infrastructure, paying 25-30% commissions on all delivery orders.
Message Variant A: Commission Breakdown Analysis Strong PQS (8.0/10)
THE MESSAGE:
Subject: Your DoorDash commission breakdown
I tracked your menu across your website and DoorDash over 30 days—average markup is 28% on 47 items, running you roughly $4,200 monthly in platform fees based on your 142 Google reviews per month.
Your signature burger alone ($14 direct vs $18 on DoorDash) represents about $890/month in commissions at your review velocity.
Want the full item-by-item breakdown?
DATA SOURCES:
- Google Maps Places API - Review velocity (
reviews[].time field, filter to last 30 days)
- Restaurant website menu + DoorDash restaurant page (web scraping for price comparison)
- Commission calculation: (reviews/month ÷ 0.03 review_rate) × avg_ticket × commission_rate
Confidence Level: 60-70% (Hybrid approach combining API data + web scraping + industry proxies. Review velocity is verifiable; commission calculation requires disclosed assumptions about review-to-order conversion rate and average ticket size.)
WHY IT WORKS:
- Situation Recognition (8/10): Mirrors exact current situation with specific data ("28% on 47 items," "$890 burger")
- Data Credibility (7/10): Verifiable data with disclosed estimation ("tracked," "roughly," "based on")
- Insight Value (7/10): Per-item commission tracking is non-obvious synthesis they don't have
- Effort to Reply (10/10): One-word answer ("Yes") to simple question
- Emotional Resonance (8/10): $4,200/month + "$890 burger" creates curiosity and financial urgency
CALCULATION WORKSHEET:
- 142 reviews/month: Google Maps API
reviews[].time filtered to last 30 days, count results (85% confidence)
- 28% average markup: Web scraping 47 menu items from website + DoorDash, calculate (price_DD - price_web) / price_web, average (70% confidence)
- $4,200 monthly fees: 142 reviews ÷ 0.03 review_rate = 4,733 orders × $18 avg_ticket × 0.28 commission ÷ 1.28 = $4,187 (60% confidence, multiple assumptions)
- $890 burger commission: 4,733 orders × 0.20 menu_mix × $18 × 0.28 commission ÷ 1.28 = $890 (55% confidence, requires menu mix assumption)
Message Variant B: Order Volume Focus Strong PQS (7.8/10)
THE MESSAGE:
Subject: 142 reviews monthly
Your restaurant is pulling 142 Google reviews per month—that volume means you're processing roughly 4,700 orders monthly through DoorDash at their standard 25-30% commission rate.
At 28% average menu markup, you're likely leaving $4,000-4,500 on the table each month vs direct ordering.
Does this match your DoorDash statements?
Confidence Level: 60-70% (Review velocity is verifiable; order volume calculation relies on industry proxy for review rate; commission range accounts for uncertainty.)
WHY IT WORKS:
- Situation Recognition (8/10): Specific, verifiable metrics ("142 reviews," "4,700 orders")
- Data Credibility (7/10): Transparent estimation with disclosed assumptions
- Insight Value (7/10): Review → order conversion calculation frames opportunity cost
- Effort to Reply (10/10): Simple verification question (yes/no/close)
- Emotional Resonance (7/10): "$4,000-4,500 on the table" = significant money
Message Variant C: Direct Ordering Gap Solid PQS (7.0/10)
THE MESSAGE:
Subject: Direct ordering gap
I checked your website—no online ordering button, but you're active on DoorDash with 142 monthly reviews.
That means every delivery order is paying 25-30% platform commission vs capturing orders direct.
Who handles your tech decisions?
DATA SOURCES:
- Website inspection: Manual check for online ordering button/checkout presence (binary observation)
- Google Maps Places API - Review velocity
- DoorDash presence: HTTP check for restaurant listing at doordash.com/store/[name]/
Confidence Level: 90% (Direct observations, minimal inference. All claims are immediately verifiable.)
WHY IT WORKS:
- Situation Recognition (7/10): States verifiable facts about their current setup
- Data Credibility (8/10): All claims instantly verifiable (website, DoorDash, Google)
- Insight Value (5/10): Mostly restates obvious facts they already know (weak synthesis)
- Effort to Reply (9/10): Easy routing question (name/email)
- Emotional Resonance (6/10): Reminder of pain but no new crisis/urgency
Message Variant D: Dependency Awareness Solid PQS (7.0/10)
THE MESSAGE:
Subject: DoorDash dependency
Spotted your restaurant doing 140+ Google reviews monthly but routing all delivery through DoorDash—no direct ordering option on your site.
At that volume, you're paying roughly $4K-5K monthly in commissions that could be recaptured.
Is this on your radar?
DATA SOURCES:
- Google Maps Places API - Review velocity (140+ rounded from 142)
- DoorDash presence check + website ordering absence (direct observation)
- Commission calculation: Same methodology as Variant A/B with range to account for uncertainty
Confidence Level: 70% (Verifiable observations with disclosed estimation for commission range.)
WHY IT WORKS:
- Situation Recognition (7/10): Specific metrics with rounded numbers for accessibility
- Data Credibility (7/10): Verifiable with disclosed uncertainty ("roughly," range format)
- Insight Value (6/10): Restates obvious situation, weak new synthesis
- Effort to Reply (9/10): Simple yes/no awareness question
- Emotional Resonance (6/10): Financial impact stated but generic framing
Implementation Notes
Who Should Use This Playbook
- SDRs/BDRs: Use these message templates for outbound campaigns targeting restaurants with delivery dependency
- Account Executives: Reference commission analysis data in discovery calls to build credibility
- Marketing: Adapt these insights for case studies and value proposition messaging
How to Find Target Prospects
Step 1: Use Google Maps API to identify restaurants with high review velocity (>100 reviews/month)
Step 2: Check for DoorDash/Uber Eats presence (search "site:doordash.com [restaurant name]")
Step 3: Verify NO direct online ordering on their website (manual check or BuiltWith API)
Step 4: Scrape menu pricing from website + DoorDash to calculate markup % and commission estimates
Expected Conversion Rates
- Reply Rate: 8-15% (vs 1-3% for generic SDR emails)
- Meeting Booked Rate: 3-6% of outreach (vs 0.5-1% generic)
- Important: These are situation-based timing plays, not traditional pain-driven PVPs. Expect lower conversion than pure regulatory compliance segments (which can hit 15-20% reply rates).
Critical Disclaimer
⚠️ Single-Segment Limitation: This playbook contains only 1 validated segment (third-party delivery dependency). The ideal Blueprint playbook has 2-3 segments to cover different pain domains. Toast's operational efficiency value proposition does not map well to externally detectable data moats—most target pains (system fragmentation, manual processes, training burden) are only visible internally.
Recommendation: Use this playbook for the delivery dependency segment, but complement with traditional ICP + persona research for other operational efficiency plays (multi-location expansion, payment processor switching, legacy POS sunset). The Blueprint methodology excels at regulatory compliance pain; operational efficiency pain requires different GTM approaches.