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 Nets 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: "You filed for Malta Gaming Authority approval on October 14th - that puts you 8-12 weeks from launch" (specific regulatory filing with exact date)
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 value (PVP). Every claim traces to verifiable data sources. Plays are ordered by quality score.
Gaming operators expanding into Germany need to select the right acquirer bank for Giropay processing. You have aggregated approval rate data across gaming customers by issuing bank - showing that Sparkasse approves at 91% vs Deutsche Bank at 78%. That 13-point spread equals €195K per €1.5M in transactions. This is proprietary data they cannot get elsewhere.
Highly specific data they can't get elsewhere. Direct financial impact calculation. Helps them optimize German market entry. Low-commitment ask.
This play requires aggregated Giropay approval rates across gaming customers, segmented by issuing bank.
This is proprietary data only you have - competitors cannot replicate this play.Gaming operators expanding to Malta need to choose the right payment methods. You process payments for 23 gaming operators in Malta and track approval rates by method. iDEAL converts at 89% vs Sofort at 76% for Dutch players - that's €140K difference per 1M transactions. This is proprietary performance data they need for vendor selection.
Specific data from actual Malta operators. Concrete financial impact they can calculate. Helps them make better vendor decisions. Low-commitment ask.
This play requires aggregated payment approval rates across 20+ gaming operator customers, segmented by payment method and player geography.
This is proprietary data only you have - competitors cannot replicate this play.Gaming operators launching in Netherlands need to select the right acquirer for iDEAL. You route payments for gaming operators in Netherlands and track which acquirers approve fastest. ING processes iDEAL 3.2 seconds faster than ABN AMRO on average - that's 18% higher completion rates. This is actionable data for vendor selection.
Specific performance data they don't have. Speed difference impacts their conversion. Actionable for vendor selection. Clear value even if they don't buy.
This play requires aggregated payment routing performance data across gaming customers, tracking approval speed by acquirer and payment method.
This is proprietary data only you have - competitors cannot replicate this play.Three gaming operators filed Malta licenses between October 10-22nd targeting Netherlands and Germany. They're all competing for the same iDEAL and Giropay integration slots with 8-week lead times. You track Malta Gaming Authority filings (public) and combine it with internal integration pipeline capacity data to proactively alert prospects when integration capacity opens up.
Shows they're tracking competitive timing. Integration capacity constraint is real pain. Proactive alert would actually help them. Easy yes/no response.
This play requires tracking Malta Gaming Authority filings (public) and combining it with internal integration pipeline capacity data.
This synthesis of public regulatory data with your internal capacity constraints is unique to your business.Gaming operators who filed for Malta Gaming Authority approval face specific payment method requirements before go-live. You track MGA filings and know the exact filing date (October 14th), which puts them 8-12 weeks from launch. Malta requires local payment method support (iDEAL, Sofort, Giropay) before approval. This is a verifiable deadline creating urgency.
Specific filing date shows real research about them. Malta payment requirements are accurate and urgent. Timeline pressure is real - they need this sorted. Easy routing question, not a sales pitch.
Malta Gaming Authority changed licensing requirements on November 1st - now requiring payment method proof-of-integration. Operators who filed before this date (like October 14th) are grandfathered but still need integration confirmation by January 15th. This is a specific regulatory change with exact deadline creating urgency.
Specific regulatory change with exact date. Directly impacts their timeline. Shows they're monitoring MGA requirements. Easy routing question.
Old way: Spray generic messages at job titles. Hope someone replies.
New way: Use regulatory filings and proprietary transaction data to find gaming operators at specific inflection points. Then deliver insights they cannot get elsewhere.
Why this works: When you lead with "German banks approve Giropay at wildly different rates - Sparkasse at 91%, Deutsche Bank at 78%" instead of "We help gaming operators optimize payment processing," you're not another sales email. You're the person who has the data.
The messages above aren't templates. They're examples of what happens when you combine regulatory data sources with proprietary transaction performance data. 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 |
|---|---|---|
| Malta Gaming Authority License Filings | operator_name, filing_date, target_markets, license_status | Malta license timing and payment method requirements |
| Nets Internal Transaction Data | payment_method, approval_rate, issuing_bank, operator_segment, geography | Payment method performance benchmarks by region and operator type |
| Nets Internal Integration Pipeline | payment_method, region, capacity_available, lead_time_days | Integration capacity alerts and lead time warnings |
| Malta Gaming Authority Regulatory Updates | requirement_change_date, new_requirements, affected_license_types | Regulatory deadline tracking and compliance urgency |