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 MX Technologies 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 CFPB consent order #2024-CFPB-0015 requires income verification compliance by March 15, 2025" (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, enforcement actions.
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.
Company: MX Technologies
Core Problem: Financial institutions and fintech companies struggle to reliably aggregate, normalize, and connect customer financial data across thousands of disparate banks and data sources, creating friction in account opening, lending decisions, and financial management workflows.
Industries: Regional and national banks, credit unions, mortgage lending, BNPL and consumer lending fintech, wealth management, digital banking platforms
Company Size: Mid-market to enterprise (serving 16,000+ banking partners, 85% of digital banking providers)
Context: Financial institutions managing consumer financial data, requiring secure aggregation, regulatory compliance, multi-institutional account linking, and data enrichment for lending and account opening workflows
Title: Head of Product (Digital Banking/Lending) or VP of Engineering
Key Responsibilities:
KPIs: Account connection success rates, authentication time, loan approval velocity, customer engagement metrics, data quality and transaction categorization accuracy
These messages demonstrate precise understanding of the prospect's situation (PQS) or deliver immediate value (PVP). Every claim traces to verifiable data sources.
Monitor real-time aggregation coverage changes across institutions and alert regional lenders when their key referral sources lose coverage - before loan approvals start failing.
You're telling them something they don't know yet but desperately need to know. Specific institution names, member counts, and dates prove this is real research, not generic prospecting. The impact calculation (% of pipeline) makes it urgent.
This play requires real-time monitoring of aggregation coverage status across competitor platforms (Plaid, Finicity, etc.) and the ability to map coverage gaps to customer lending footprints.
This is proprietary intelligence only MX can deliver - competitors cannot monitor their own coverage failures at this granularity.Use aggregated implementation data from enforcement-targeted customers to show banks what ACTUALLY happens during integration - not vendor promises, but real timelines showing what breaks first and when.
Banks under enforcement orders are stressed about deadlines. Showing them specific failure points (week 8-10) with concrete sample sizes (47 institutions) gives them actionable planning data they can't get elsewhere. This is genuine value delivery.
This play requires aggregated implementation timeline data from 50+ customers under regulatory enforcement, segmented by institution type and showing when specific workflows fail during integration.
This is proprietary implementation intelligence only MX can provide from their customer base.Target regional mortgage lenders when specific credit unions in their lending area lose aggregation coverage. Use exact institution names, member counts, and dates to prove you're monitoring their market.
The specificity of the institution name (First Community CU), exact member count (127,000), and precise date (December 3rd) proves this is real intelligence, not generic prospecting. The routing question makes it easy to respond.
This play requires real-time monitoring of aggregation coverage status across competitor platforms and the ability to identify when specific institutions lose coverage.
Combined with public member count data to quantify impact. This synthesis is unique to MX's monitoring capabilities.Target banks under CFPB enforcement orders by showing them when their loan workflow will fail during integration, based on patterns from similar institutions under enforcement.
The specific sample size (34 banks) and exact timing (week 8-10, early January) creates urgency. The routing question ("Who's owning the loan workflow integration plan?") makes it easy to forward internally. This is actionable intelligence.
This play requires implementation timeline data showing when specific workflows (loan approval, account opening) fail during integration across enforcement-targeted institutions.
This is proprietary implementation intelligence from MX's customer base that competitors cannot replicate.Target lenders by identifying all institutions in their primary lending counties that lost aggregation coverage within a specific date range. Use geographic specificity to prove you understand their market.
The specific county (Mecklenburg), exact date range (Nov 1 - Dec 15), and concrete number (11 institutions) proves this is real market intelligence. The offer to send the full list with member counts creates a natural next step.
This play requires geographic tracking of aggregation coverage changes, identifying institutions that lost coverage within specific counties and date ranges.
Combined with public institution location data to create targeted geographic intelligence.Monitor aggregation coverage changes across thousands of institutions and calculate pipeline impact for regional lenders when institutions in their lending area lose coverage.
The impressive monitoring scale (2,847 institutions) and specific number in their area (11) creates credibility. The pipeline impact calculation (18%) makes it urgent. However, the 18% calculation feels somewhat assumed rather than proven.
This play requires comprehensive aggregation coverage monitoring across competitor platforms and the ability to calculate pipeline impact based on customer lending geography and estimated market share.
This is large-scale proprietary intelligence only MX can provide from their industry monitoring.Target banks under CFPB consent orders by showing them the typical failure pattern: 68% miss their first deadline because they underestimate loan workflow integration time (14 weeks vs budgeted 8 weeks).
The specific data (47 banks, 68% miss rate, 14 weeks vs 8 weeks) feels credible and actionable. The routing question makes response easy. However, the use of "averages" is borderline generic and could be from any vendor.
This play requires tracking implementation timelines and compliance deadline performance across 50+ enforcement-targeted customers.
This is proprietary performance data from MX's customer base.Alert mortgage lenders when their top referral sources lose aggregation coverage. Use specific institution names and referral volume rankings to show deep research.
Identifying the prospect's #3 referral source by volume shows excellent research. The exact date and institution name add credibility. However, the "6-day average delays industry-wide" is a generic stat that weakens the message.
This play requires the ability to identify customer's top referral institutions by volume and monitor their aggregation coverage status in real-time.
This requires both internal monitoring data and analysis of customer referral patterns.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 CFPB consent order requires income verification compliance by March 15" instead of "I see you're hiring for compliance 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 |
|---|---|---|
| CFPB Enforcement Actions Database | institution_name, enforcement_type, violation_category, order_date, penalty_amount | Identifying lenders with income verification compliance failures and enforcement deadlines |
| OCC Enforcement Actions Database | bank_name, action_type, subject_matter, start_date, termination_date, status | Identifying national banks under enforcement with compliance gaps |
| NCUA Enforcement Actions Database | credit_union_name, camels_rating, enforcement_type, issue_date, asset_quality_score | Identifying credit unions with CAMEL downgrades and enforcement actions |
| NMLS Consumer Access Database | lender_name, license_status, license_expiration_date, enforcement_actions, state, nmls_id | State-licensed lenders and mortgage servicers with enforcement history and license status |
| FFIEC Central Data Repository | institution_name, rssd_id, balance_sheet_data, asset_quality_metrics, capital_ratios | Quarterly financial data revealing asset quality issues and compliance problems |
| MX Internal Data | implementation_timelines, aggregation_coverage_status, workflow_failure_patterns | Proprietary implementation intelligence and real-time coverage monitoring across 16,000+ institutions |