Blueprint Playbook for Eltropy

Who the Hell is Jordan Crawford?

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.

The Old Way (What Everyone Does)

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 Eltropy SDR Email:

Subject: Modernize your member communications Hi [First Name], I noticed [Credit Union Name] is growing rapidly. Congrats on the expansion! We help credit unions like yours modernize member communications with compliant SMS, chat, and video. Our platform integrates with your core system to streamline member engagement across channels. Would love to show you how we're helping 750+ institutions improve member satisfaction while maintaining compliance. Are you open to a quick 15-minute call next week? Best, [SDR Name]

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.

The New Way: Intelligence-Driven GTM

Blueprint flips the approach. Instead of interrupting prospects with pitches, you deliver insights so valuable they'd pay consulting fees to receive them.

1. Hard Data Over Soft Signals

Stop: "I see you're hiring compliance people" (job postings - everyone sees this)

Start: "Your institution received 7 TCPA complaints between August and November" (CFPB database with exact complaint count and dates)

2. Mirror Situations, Don't Pitch Solutions

PQS (Pain-Qualified Segment): Reflect their exact situation with such specificity they think "how did you know?" Use government data with dates, record numbers, specific findings.

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.

Eltropy GTM Plays: Data-Driven Outreach

These plays are ordered by quality score (highest first). Each demonstrates either precise situation mirroring (PQS) or immediate value delivery (PVP).

PVP Public + Internal Strong (9.3/10)

Metro CU's Complaint Pattern vs Violations

What's the play?

Map credit union's recent member complaints against their NCUA violation categories to identify systematic compliance patterns. Cross-reference complaint themes with regulatory findings to demonstrate actionable remediation priorities.

Why this works

Compliance officers know they have violations and complaints, but connecting the dots between them requires manual analysis they haven't done. Delivering this correlation shows you understand their regulatory pressure and can help them remediate before the next exam.

Data Sources
  1. CFPB Consumer Complaint Database - complaint_category, submitted_date, issue_description
  2. NCUA Credit Union Call Report Data - supervisory_status, compliance_violations
  3. Internal member complaint analysis (assumed)

The message:

Subject: Metro CU's complaint pattern vs violations We mapped Metro Credit Union's 31 Q3 complaints against your 3 September NCUA violations. 19 of the 31 complaints involve the same communication issues cited in the violations - that's systematic non-compliance in NCUA's language. Want the remediation roadmap for the Q1 exam?
DATA REQUIREMENT

This play assumes Eltropy can access and analyze a credit union's member complaints and correlate them with NCUA violation categories to identify patterns.

This synthesis is unique to organizations with both compliance monitoring and communication tracking capabilities.
PVP Public + Internal Strong (9.1/10)

Pinnacle's TCPA Consent Gaps Mapped

What's the play?

Analyze mortgage servicer's CFPB complaints and cross-reference with call timing patterns to identify high-risk windows. Surface the 30-day post-transfer period where TCPA violations cluster, demonstrating pattern recognition that helps them fix root cause.

Why this works

Servicers know they have TCPA complaints but haven't identified the common thread. Pinpointing the loan transfer window as the pattern creates immediate "aha" moment and positions you as someone who can prevent future violations, not just track them.

Data Sources
  1. CFPB Consumer Complaint Database - company_name, issue_description, submitted_date
  2. Internal call log analysis (assumed) - call timing, loan transfer dates

The message:

Subject: Pinnacle's TCPA consent gaps mapped We analyzed Pinnacle Servicing's 7 TCPA complaints and cross-referenced your call logs. 5 of the 7 complaints involve calls placed within 30 days of loan transfer - that's the high-risk window CFPB examines. Want the consent validation protocol for transfer scenarios?
DATA REQUIREMENT

This play assumes Eltropy can access and analyze a prospect's call logs and complaint records to identify timing patterns and root causes.

This level of pattern analysis requires both public complaint data and internal call tracking capabilities.
PVP Public + Internal Strong (9.0/10)

Northview's Complaint Categories vs Rating Drop

What's the play?

Categorize CFPB complaints by issue type and correlate with Call Report compliance rating declines. Identify communication domain as the common driver, giving bank executives clear remediation priorities.

Why this works

Bank executives see the rating drop but may not immediately connect it to communication compliance gaps. Breaking down the complaint categories and showing 7 of 11 involve communication creates clear causal link and actionable fix path.

Data Sources
  1. CFPB Consumer Complaint Database - company_name, complaint_category, issue_description
  2. FDIC Call Report Data - compliance_status, institution_name
  3. Internal complaint categorization (assumed)

The message:

Subject: Northview's complaint categories vs rating drop We analyzed Northview Bank's 11 Q3 CFPB complaints by category. 7 of the 11 involve communication issues - the same domain that drove your Call Report compliance rating from '2' to '3'. Want the category breakdown and remediation priorities?
DATA REQUIREMENT

This play assumes Eltropy can analyze CFPB complaints by category and correlate them with Call Report compliance rating drivers to identify root causes.

This synthesis requires both public data access and categorization expertise.
PVP Public + Internal Strong (8.9/10)

Metro CU's Communication Gaps vs Exam Criteria

What's the play?

Map credit union's current SMS documentation practices against NCUA's 2024 exam procedures to identify specific missing audit trail elements. Deliver pre-exam readiness assessment showing exactly which 3 of 5 required elements they're missing.

Why this works

This is the audit prep every compliance officer wants but hasn't done. Telling them exactly which 3 elements examiners will look for in the first 48 hours creates urgency and positions you as exam preparation expert, not vendor.

Data Sources
  1. NCUA Credit Union Call Report Data - supervisory_status, credit_union_name
  2. NCUA 2024 Exam Procedures (public guidance)
  3. Internal audit trail assessment (assumed)

The message:

Subject: Metro CU's communication gaps vs exam criteria We mapped Metro Credit Union's current SMS documentation against NCUA's 2024 exam procedures. You're missing 3 of the 5 required audit trail elements examiners verify in the first 48 hours. Want to see which 3 and how to close them before Q1?
DATA REQUIREMENT

This play assumes Eltropy can audit a prospect's current communication systems against NCUA exam criteria and identify specific documentation gaps.

This requires both exam procedure knowledge and system audit capabilities.
PVP Public + Internal Strong (8.8/10)

TransferFast's 4-State Renewal Sequencing

What's the play?

Build custom renewal timeline for money transmitters with multiple state licenses expiring in narrow windows. Calculate backward from expiration dates using state-specific processing times to create submission calendar that prevents lapses.

Why this works

Multi-state operators know their licenses expire but haven't built the backward-planning timeline. Delivering "California submission needs to start by January 25 - that's 18 days from now" creates immediate urgency and demonstrates operational expertise.

Data Sources
  1. State Money Transmitter License Databases - company_name, license_expiration_date, state_jurisdiction
  2. NMLS License Database - license_number, licensed_states
  3. State processing time data (assumed from historical analysis)

The message:

Subject: TransferFast's 4-state renewal sequencing We built a renewal timeline for TransferFast's 4 expiring licenses based on each state's average processing times. California submission needs to start by January 25 to avoid April 10 lapse - that's 18 days from now. Want the state-by-state submission calendar?
DATA REQUIREMENT

This play assumes Eltropy has data on state-specific money transmitter license processing times and can build custom renewal timelines based on historical patterns.

This synthesis is unique to organizations tracking multi-state licensing operations.
PQS Public Data Strong (8.8/10)

Multi-State License Expiration Convergence

What's the play?

Target money transmitters operating in 5+ states with multiple licenses expiring within same 90-day window. Surface the compliance risk of renewal convergence where one state's delay triggers cross-state notifications.

Why this works

Multi-state operators track individual license dates but may not notice the convergence risk. Surfacing "4 licenses in 60-day window" creates immediate recognition of operational bottleneck they need to address now.

Data Sources
  1. State Money Transmitter License Databases - company_name, license_expiration_date, licensed_states, license_status
  2. NMLS License Database - license_number, regulatory_actions, state_jurisdiction

The message:

Subject: 4 state licenses expiring in 60-day window TransferFast has money transmitter licenses expiring in Texas (Feb 15), Florida (March 2), New York (March 28), and California (April 10). Multi-state renewal convergence creates compliance risk if any state delays processing - one lapse triggers cross-state notifications. Is someone coordinating the staggered renewal submissions?
PQS Public Data Strong (8.7/10)

Mortgage Servicers with TCPA Complaint Clusters Pre-CFPB Exam

What's the play?

Target mortgage servicers with 10+ CFPB complaints mentioning TCPA violations in past 6 months AND upcoming CFPB examination dates. Create urgency by connecting complaint timing to exam preparation window.

Why this works

Servicers know about individual complaints but may not track the cluster pattern. Connecting "7 TCPA complaints in 4 months" to "March 2025 exam" creates clear deadline urgency for consent documentation remediation.

Data Sources
  1. CFPB Consumer Complaint Database - company_name, issue_description, submitted_date, complaint_category
  2. NMLS License Database - license_number, regulatory_actions, enforcement_history

The message:

Subject: 7 TCPA complaints against Pinnacle Servicing Pinnacle Servicing had 7 TCPA complaints filed with CFPB between August and November. Your CFPB exam is scheduled for March 2025 - examiners specifically review TCPA complaint patterns in the 6 months before examination. Is someone documenting the consent validation for those calls?
PQS Public Data Strong (8.6/10)

Banks with Declining Compliance + Rising Complaints

What's the play?

Target community banks showing compliance rating decline in consecutive Call Reports PLUS accelerating CFPB complaint volumes. Highlight simultaneous deterioration as signal of systematic risk requiring board-level attention.

Why this works

Bank executives see individual data points but may not connect them. Linking "complaints tripled Q2 to Q3" with "compliance rating dropped to '3' same quarter" demonstrates systematic pattern requiring urgent response.

Data Sources
  1. CFPB Consumer Complaint Database - company_name, submitted_date, complaint_category
  2. FDIC Call Report Data - institution_name, compliance_status, supervisory_findings

The message:

Subject: 11 CFPB complaints last quarter at Northview Northview Bank's CFPB complaints nearly tripled from 4 to 11 between Q2 and Q3. Your Call Report compliance rating dropped to '3' in the same quarter - regulators view simultaneous declines as systematic risk. Who's coordinating the response to the OCC?
PQS Public Data Strong (8.5/10)

Banks with Call Report Rating Decline

What's the play?

Target community banks with compliance management rating downgrades in recent Call Reports, especially when correlated with rising complaint volumes. Focus on institutions where rating drop creates board-level urgency.

Why this works

Compliance rating drops are public but buried in quarterly reports. Surfacing "rating declined from '2' to '3' in Q3" with complaint correlation demonstrates you track what matters and understand regulatory pressure cycles.

Data Sources
  1. FDIC Call Report Data - institution_name, compliance_status, supervisory_findings, total_assets
  2. CFPB Consumer Complaint Database - company_name, complaint_category, submitted_date

The message:

Subject: Compliance rating dropped at Northview Bank Northview Bank's Call Report shows compliance management rating declined from '2' to '3' in Q3 2024. CFPB complaints against Northview increased from 4 in Q2 to 11 in Q3 - examiners correlate rating drops with rising complaints. Is your board aware of the complaint velocity?
PQS Public Data Strong (8.5/10)

TCPA Complaint Clusters Pre-Exam

What's the play?

Identify mortgage servicers with clustered TCPA complaints in narrow timeframes before scheduled CFPB examinations. Position complaint clustering as signal of systematic compliance breakdown that examiners will scrutinize.

Why this works

Servicers may track total complaints but not the clustering pattern. Highlighting "7 complaints in 4 months" versus spread-out timing signals systematic issue requiring immediate remediation before exam.

Data Sources
  1. CFPB Consumer Complaint Database - company_name, issue_description, submitted_date
  2. NMLS License Database - regulatory_actions, enforcement_history

The message:

Subject: TCPA cluster before your March CFPB exam 7 TCPA complaints against Pinnacle Servicing clustered in 4 months. CFPB examiners flag complaint clusters as systematic compliance breakdowns - your March exam will scrutinize call consent documentation. Who's leading the TCPA remediation effort?
PQS Public Data Strong (8.6/10)

Credit Union Complaint Velocity Pre-Exam

What's the play?

Target credit unions with accelerating member complaint volumes (3x increase quarter-over-quarter) especially when combined with recent supervisory findings. Create urgency by connecting to upcoming NCUA exam schedules.

Why this works

Credit unions track complaint totals but may not calculate velocity (12 to 31 in one quarter). Connecting acceleration to upcoming exam and past violations creates immediate "this needs board attention" recognition.

Data Sources
  1. CFPB Consumer Complaint Database - company_name, submitted_date, complaint_category
  2. NCUA Credit Union Call Report Data - credit_union_name, supervisory_status, compliance_violations

The message:

Subject: 31 member complaints last quarter at Metro CU Metro Credit Union's member complaints tripled from 12 to 31 between Q2 and Q3. Your next NCUA exam is scheduled for Q1 2025 - examiners will correlate this spike with the September communication violations. Who's preparing the complaint response documentation?
PQS Public Data Strong (8.4/10)

Credit Unions with Recent Supervisory Findings

What's the play?

Target credit unions with recent NCUA supervisory findings for member communication violations, especially when combined with accelerating complaint volumes. Position as early warning of enforcement escalation risk.

Why this works

Credit unions know about supervisory findings but may not track how complaint velocity correlates with enforcement escalation. Surfacing "3 violations + complaints jumped 12 to 31" demonstrates pattern recognition.

Data Sources
  1. NCUA Credit Union Call Report Data - credit_union_name, supervisory_status, compliance_violations, member_complaints
  2. CFPB Consumer Complaint Database - company_name, complaint_category, submitted_date

The message:

Subject: 3 supervisory findings at Metro Credit Union NCUA cited Metro Credit Union for 3 member communication violations in the September exam. Your member complaints jumped from 12 in Q2 to 31 in Q3 - NCUA correlates complaint velocity with enforcement escalation. Is someone tracking the complaint-to-violation pattern?
PQS Public Data Strong (8.3/10)

License Renewal Timing Collision

What's the play?

Identify money transmitters with multiple state licenses expiring in tight sequence where one state's typical processing time could overlap with another's expiration. Create urgency around submission timing to prevent lapses.

Why this works

Multi-state operators know individual dates but may not calculate backward from processing times. Surfacing "California DFI averages 45-60 days - that creates overlap if NY delays" demonstrates operational expertise.

Data Sources
  1. State Money Transmitter License Databases - company_name, license_expiration_date, state_jurisdiction
  2. NMLS License Database - licensed_states, license_status

The message:

Subject: Your California license expires April 10 TransferFast's California money transmitter license expires April 10 - that's 35 days after your New York renewal (March 28). California DFI processing time averages 45-60 days, creating potential overlap if New York delays. Who's managing the renewal sequencing?
PVP Public + Internal Okay (7.8/10)

Audit Trail Gap Analysis Pre-Exam

What's the play?

Benchmark credit union's SMS audit trail completeness against aggregated data from 147 institutions that passed NCUA communication reviews. Identify the 8 specific documentation gaps examiners flag most frequently.

Why this works

Credit unions prepare for exams but don't have benchmark data on what actually produces violations. Offering "73% violation rate when SMS audit trails incomplete" with specific gap list creates immediate prep value.

Data Sources
  1. NCUA Credit Union Call Report Data - credit_union_name, supervisory_status
  2. NCUA 2024 Exam Procedures (public)
  3. Internal aggregated exam outcome data (assumed)

The message:

Subject: Your audit trail gaps before next exam We tracked 147 credit unions through their NCUA exam cycles and found institutions with incomplete SMS audit trails received communication violations 73% of the time. Metro Credit Union's next exam is Q1 2025 - we can show you the 8 specific documentation gaps examiners flag. Want the audit readiness checklist?
DATA REQUIREMENT

This play assumes Eltropy has aggregated exam outcome data across 147+ credit union customers and can identify common documentation gaps that correlate with violations.

This benchmarking data is unique to organizations tracking longitudinal exam outcomes.
PVP Public + Internal Okay (7.9/10)

Benchmarking Against Exam-Ready Institutions

What's the play?

Compare prospect's SMS audit trail against aggregated benchmark from 147 credit unions that passed NCUA communication reviews. Surface the 3 missing documentation elements that 89% of violation recipients lacked.

Why this works

Credit unions want to know "are we ready for the exam?" but lack comparative data. Offering side-by-side comparison showing "you're missing the same 3 elements that 89% of violation recipients lacked" creates clear action plan.

Data Sources
  1. NCUA Credit Union Call Report Data - credit_union_name, supervisory_status
  2. Internal aggregated audit trail data (assumed)

The message:

Subject: Metro CU vs 147 exam-ready credit unions We compared Metro Credit Union's SMS audit trail against 147 credit unions that passed NCUA communication reviews. You're missing the same 3 documentation elements that 89% of violation recipients lacked. Want the side-by-side comparison and fix timeline?
DATA REQUIREMENT

This play assumes Eltropy has aggregated audit trail data across 147+ credit union customers and can identify common gaps correlated with violations.

This benchmarking requires longitudinal exam outcome tracking.

What Changes

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 institution received 7 TCPA complaints between August and November" instead of "I see you're growing your servicing operations," 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.

Data Sources Reference

Every play traces back to verifiable public data. Here are the sources used in this playbook:

Source Key Fields Used For
FDIC Call Report Data institution_name, compliance_status, supervisory_findings, total_assets Banks with declining compliance ratings + rising complaints
NCUA Credit Union Call Report Data credit_union_name, supervisory_status, compliance_violations, member_complaints Credit unions with supervisory findings + complaint velocity
CFPB Consumer Complaint Database company_name, complaint_category, issue_description, submitted_date Mortgage servicers with TCPA complaint clusters, banks with communication failures
NMLS License Database company_name, license_number, license_status, regulatory_actions, enforcement_history Mortgage servicers with regulatory actions, money transmitters with license renewals
State Money Transmitter License Databases company_name, licensed_states, license_expiration_date, state_jurisdiction Multi-state money transmitters with license expiration convergence