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 Medius 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 plays are ordered by message quality score. Each demonstrates specific understanding or delivers immediate value to prospects.
Cross-check your prospect's top vendors against multiple financial distress signals including credit downgrades, late trade payments, and debt covenant breaches. Deliver a list of at-risk vendors before they disrupt the supply chain.
You're protecting them from real business risk independent of whether they buy your AP software. The synthesis of multiple financial signals (credit ratings + payment behavior + SEC filings) to THEIR specific vendor base is something they cannot easily do themselves. This is consultation-grade value delivered upfront.
This play requires customer vendor spend data (top 20 vendors) combined with external financial distress databases (credit ratings, trade payment behavior, SEC filings).
The synthesis of external financial signals to a specific customer's vendor base is proprietary intelligence only you can deliver.Monitor credit rating agencies for downgrades affecting your prospect's specific vendors, then alert them with their exact PO exposure. Include specific vendor name, credit rating change, and date to prove you're tracking their supply chain.
Extremely specific - you know their actual vendor name and their exact PO exposure. The credit downgrade is verifiable public information but synthesized to THEIR situation. This protects them from real financial risk and proves you've done deep research on their business, not generic outreach.
This play requires customer vendor/PO data combined with external credit rating monitoring services.
The synthesis of public credit events to a specific customer's vendor exposure is proprietary intelligence.Cross-reference your prospect's vendor list with financial distress signals like late supplier payments, credit downgrades, and bankruptcy warning signs. Deliver a list of at-risk vendors with specific dollar exposure.
You're delivering genuinely valuable intelligence even if they never buy. The specificity of analyzing THEIR vendor list for financial risk proves this isn't generic outreach. This helps them avoid supply chain problems before they happen.
This play requires customer vendor lists combined with external financial distress databases (Dun & Bradstreet, credit rating agencies).
The synthesis of external financial signals to a specific customer's vendor base creates proprietary intelligence.Monitor credit watch alerts from rating agencies for major healthcare/pharma vendors, then alert prospects with their specific PO exposure. Use verifiable public credit events combined with their internal vendor spend data.
Credit watch placements are verifiable public information (Moody's ratings), but the $123K in open POs is specific to THEIR organization and actual exposure. This protects them from real supply chain risk independent of buying, and the easy routing question makes it non-threatening.
This play requires customer PO/vendor spend data combined with public credit rating data.
The synthesis of public credit events to specific customer exposure is proprietary intelligence.Monitor state WARN notice databases for mass layoffs at major vendors (food distribution, pharma, etc.), then alert prospects with their specific PO exposure. WARN notices often precede bankruptcy filings.
WARN notices are verifiable public data (state labor departments), but the $67K exposure is specific to THEIR organization. Connecting the WARN notice to their supply chain risk is genuinely helpful. The routing question is easy and non-threatening.
This play requires customer PO/vendor spend data combined with public WARN notice data to identify supply chain risk.
The synthesis of WARN notices to specific customer vendor exposure is proprietary intelligence.Monitor external payment behavior databases to identify when your prospect's vendors are paying THEIR suppliers late. Late supplier payments are the #1 leading indicator of bankruptcy within 12 months.
This is genuinely valuable - helps them avoid vendor bankruptcy before it happens. The claim about late supplier payments being a bankruptcy predictor is a real insight. The synthesis of external payment behavior to THEIR specific vendors is valuable intelligence they cannot easily get themselves.
This play requires customer vendor lists combined with external payment behavior databases (Dun & Bradstreet, trade payment data).
The synthesis of external payment behavior to specific customer vendors is proprietary intelligence that protects them from supply chain disruption.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 or proprietary internal aggregations. Here are the sources used in this playbook:
| Source | Key Fields | Used For |
|---|---|---|
| Credit Rating Agencies (Moody's, S&P, Fitch) | company_name, rating, rating_change_date, credit_watch_status, outlook | Vendor bankruptcy risk alerts, credit downgrades |
| Trade Payment Behavior Databases (D&B) | company_name, days_beyond_terms, payment_trends, credit_score | Late-paying vendor detection, financial distress signals |
| UCC Filing Databases | debtor_name, filing_type, filing_date, secured_party, collateral | Financial distress signals, vendor bankruptcy risk |
| State WARN Notice Databases | employer_name, location, affected_employees, filing_date, closure_type | Vendor bankruptcy early warning, supply chain disruption |
| SEC EDGAR Filings | company_name, filing_type, debt_covenants, financial_statements | Debt covenant breaches, vendor financial distress |
| Internal Customer Vendor/PO Data | vendor_name, annual_spend, open_po_amount, vendor_category | Customer-specific vendor exposure analysis |
| Internal Invoice Processing Metrics | exception_rate, processing_time, approval_time_by_tier, vendor_category | AP efficiency benchmarking, cost-per-invoice analysis |
| Internal Payment Terms Data | vendor_category, payment_terms, early_discount_capture, time_to_pay | Payment optimization benchmarking by vendor category |
| Internal Fraud Detection Data | vendor_category, fraud_flag_frequency, duplicate_patterns, exception_types | Vendor fraud risk scoring, duplicate invoice detection |