Blueprint Playbook for StarCompliance

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

Subject: Compliance challenges at [Company]? Hi [First Name], I noticed you're the Chief Compliance Officer at [Company]. Congrats on the recent LinkedIn post about regulatory changes! At StarCompliance, we help financial services firms monitor employee trading, manage conflicts of interest, and maintain audit-ready compliance records across 55+ countries. We work with firms like Invesco and Bain Capital to eliminate manual workflows and centralize compliance operations. Would you be open to a 15-minute call next week to explore how we could help [Company] achieve similar results? 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 Form ADV shows $2.3B AUM growth while SEC cited personal trading gaps in March" (specific government records with 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, firm identifiers.

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.

StarCompliance GTM Plays: Data-Driven Intelligence

These messages demonstrate precise understanding of the prospect's situation using verifiable government data. Every play is ordered by quality score - the highest-impact messages come first.

PVP Public Data Strong (9.4/10)

Phoenix Branch High-Risk Rep Analysis

What's the play?

Cross-reference FINRA BrokerCheck data for all registered reps at newly-opened branch locations against their individual disclosure histories. Identify reps with prior violations who require enhanced supervision under FINRA rules.

Why this works

You're surfacing compliance requirements they may have missed. FINRA mandates heightened supervision for reps with disclosure events - missing this creates exam findings. The specificity (3 reps, exact branch) proves you did the research they should have done.

Data Sources
  1. FINRA BrokerCheck Database - individual rep CRD numbers, disclosure events, employment history
  2. FINRA Firm Records - branch addresses, registered representative rosters

The message:

Subject: Your 12 Phoenix reps - 3 need enhanced supervision Pulled BrokerCheck for all 12 registered reps at your new Phoenix branch. 3 have prior disclosure events at other firms - FINRA requires heightened supervision for reps with history. Want their names and the specific supervision protocols FINRA expects for each?
PVP Public Data Strong (9.3/10)

Branch Expansion Compliance Gap Analysis

What's the play?

Map FINRA disciplinary events by violation type against the timing and location of new branch openings. Show how supervision failures at one location create identical risk at new branches opened during remediation periods.

Why this works

This is consultant-level analysis delivered for free. You're connecting dots they haven't connected - expansion during remediation creates compounding risk. The branch-by-branch breakdown makes remediation actionable instead of overwhelming.

Data Sources
  1. FINRA BrokerCheck Database - disciplinary events, violation types, dates
  2. FINRA Firm Records - branch opening dates, locations

The message:

Subject: I audited your 3 new branches against FINRA violations Mapped your Phoenix, Tampa, and Charlotte branch openings against your 4 FINRA disclosure events from the past 18 months. 2 of the 4 violations involved supervision failures - exact risk for new remote branches. Want the branch-by-branch compliance gap analysis showing what each location needs before the next exam?
PVP Public Data Strong (9.2/10)

State-Specific Crypto Compliance Requirements

What's the play?

Analyze FinCEN filing patterns against state MSB licensing requirements. Identify states with AML officer attestation requirements that may not align with federal CTR filing procedures.

Why this works

Multi-state crypto compliance is complex and most firms miss state-specific nuances. Texas and Florida have unique AML officer requirements that aren't obvious from federal filings. Pre-populating their attestation template saves hours and prevents violations.

Data Sources
  1. FinCEN Money Services Business Registrant Search - CTR filings, filing dates
  2. New York DFS Virtual Currency Licensees - BitLicense attestation requirements
  3. State MSB Regulations - Texas and Florida AML officer rules

The message:

Subject: I reconciled your crypto exchange activity across 15 states Analyzed your 23 Q4 FinCEN CTRs and mapped them to your 15 state MSB licenses. Texas and Florida MSB rules require separate AML officer attestations - your FinCEN filings don't show state-specific officer designations. Want the compliance checklist for TX and FL before your next state exam?
PVP Public Data Strong (9.1/10)

MNPI Access Control Gap Identification

What's the play?

Cross-reference Form ADV employee counts with SEC exam deficiency findings on insider trading controls. Identify specific roles with deal team or portfolio access that lack documented wall crossing procedures.

Why this works

This delivers the specific list compliance needs for remediation. Instead of "fix your controls," you're saying "these 12 roles need documented procedures." That's immediately actionable and shows deep understanding of their org structure.

Data Sources
  1. SEC Form ADV - employee count, organizational structure
  2. SEC Enforcement & Litigation Database - exam deficiency letters

The message:

Subject: 233 employees - I found the 12 with MNPI access gaps Pulled your ADV employee count (233) and cross-walked against the SEC's March deficiency on insider trading controls. 12 roles have deal team access without documented wall crossing procedures based on your org chart. Want the list with recommended control frameworks for each?
PVP Public Data Strong (9.0/10)

Post-Violation Rep Transfer Compliance

What's the play?

Track registered representative transfers between branch locations using FINRA employment history. When reps move from a branch with supervision violations to a new location, flag the enhanced supervision requirements.

Why this works

This prevents the next FINRA exam finding. When reps transfer post-violation, FINRA expects documentation of enhanced oversight. The OSJ designation gap is a specific, fixable compliance miss that creates immediate value.

Data Sources
  1. FINRA BrokerCheck Database - rep employment history, transfer dates
  2. FINRA Firm Records - branch supervision structures, OSJ designations

The message:

Subject: Charlotte branch has 2 reps from your Phoenix violation Pulled your Charlotte branch roster - 2 registered reps transferred from Phoenix where supervision failures occurred. FINRA expects enhanced supervision when reps move post-violation - your CRD doesn't show updated OSJ designation. Want the FINRA compliance framework for post-violation rep transfers?
PVP Public Data Strong (8.9/10)

BitLicense Quarterly Attestation Deadline

What's the play?

Track NYDFS quarterly compliance officer attestation deadlines for BitLicense holders. Cross-reference recent FinCEN CTR filing volumes to identify transaction monitoring evidence needed for attestation.

Why this works

Specific deadline with pre-populated template delivers immediate time-saving value. NYDFS attestations are tedious administrative burden - doing the work for them (Q4 filing data ready to reference) saves hours and shows regulatory expertise.

Data Sources
  1. New York DFS Virtual Currency Licensees - quarterly attestation requirements
  2. FinCEN MSB Registrant Search - Q4 CTR filings

The message:

Subject: Your NY BitLicense requires quarterly attestation due Jan 15 NYDFS requires quarterly compliance officer attestations for BitLicense holders - next deadline is January 15, 2025. Your 23 Q4 CTRs (up from 8 in Q3) need to be referenced in that attestation with transaction monitoring evidence. Want the attestation template with your Q4 filing data pre-populated?
PVP Public Data Strong (8.8/10)

Retroactive Trading Review Requirements

What's the play?

Identify post-exam new hires from Form ADV headcount changes. When SEC exam finds historical trading review gaps, new employees hired after the exam need retroactive account screening to satisfy remediation.

Why this works

This surfaces remediation work compliance teams haven't considered. The 47 new employees represent uncompleted remediation scope - without retroactive reviews, they're vulnerable in the follow-up exam. Lookback periods by role shows expertise.

Data Sources
  1. SEC Form ADV - employee count changes, hire dates
  2. SEC Enforcement & Litigation Database - exam deficiency findings

The message:

Subject: 47 post-exam hires need backdated trading reviews Your firm hired 47 employees after the March SEC exam per Form ADV headcount changes. SEC's exam found gaps in historical trading review protocols - those 47 need retroactive account screening. Want the employee list with hire dates and recommended lookback periods for each role?
PVP Public Data Strong (8.7/10)

New Hire Onboarding Gap Analysis

What's the play?

Map Form ADV employee roster changes against SEC exam deficiency timelines. Employees hired after deficiency findings need different onboarding procedures than legacy employees to satisfy remediation requirements.

Why this works

This is synthesis work - combining employee data with exam findings to identify specific remediation scope. The 47 new employees angle creates actionable prioritization: these hires need updated workflows that legacy staff may not.

Data Sources
  1. SEC Form ADV - employee roster, hire dates
  2. SEC Enforcement & Litigation Database - exam deficiency letters, dates

The message:

Subject: I mapped your 233 employees to SEC deficiency gaps I cross-referenced your Form ADV employee roster against the March 2024 SEC exam deficiencies on personal trading. 47 employees were hired after that exam - they need different onboarding than your legacy 186. Want the breakdown showing which roles have trading access without documented pre-clearance workflows?
PQS Public Data Strong (8.6/10)

Broker-Dealers with Disciplinary Events During Branch Expansion

What's the play?

Target FINRA-registered broker-dealers with 2+ disciplinary events in 18 months AND 20%+ branch count increase. Expansion without compliance infrastructure upgrades creates systematic violation risk.

Why this works

This mirrors their nightmare scenario with precision. Specific violation count, exact branch locations, and timing shows you understand the pattern: they're scaling into compliance failure. The question targets the exact gap - new branch supervision.

Data Sources
  1. FINRA BrokerCheck Database - disciplinary events, violation types, dates
  2. FINRA Firm Records - branch count, branch addresses, opening dates

The message:

Subject: 4 FINRA violations while opening 3 new branches Your CRD shows 4 disclosure events in the past 18 months across unsuitable recommendations and supervision failures. FINRA records show you opened branches in Phoenix, Tampa, and Charlotte during that same period. Who's ensuring the new branch managers have real-time trading oversight?
PQS Public Data Strong (8.4/10)

RIAs with Post-Exam Headcount Growth

What's the play?

Target SEC-registered investment advisers with exam deficiency findings AND 25%+ employee growth since the exam date. Scaling headcount without remediation creates compounding compliance risk.

Why this works

Combines two specific data points showing their exact situation. The timing is concerning - growing after being flagged means new employees may lack the controls SEC demanded. Shows understanding of scaling compliance challenges.

Data Sources
  1. SEC Enforcement & Litigation Database - exam deficiency letters, dates
  2. SEC Form ADV CSV Historical Data - employee count, filing dates

The message:

Subject: SEC cited your trading controls - you added 47 employees SEC's March 2024 exam flagged insufficient personal trading oversight at your firm. Your Form ADV shows you grew from 186 to 233 employees since that exam - 25% headcount increase. Is compliance bandwidth keeping pace with the hiring?
PQS Public Data Strong (8.3/10)

Crypto MSBs with Multi-Jurisdictional Complexity

What's the play?

Target FinCEN-registered money services businesses with 15+ state MSB licenses AND quarter-over-quarter CTR filing increases. Each state has different transaction monitoring thresholds creating coordination complexity.

Why this works

Specific CTR count and quarter-over-quarter comparison shows you analyzed their filings. 15-state compliance is their exact burden. Real-time monitoring question hits the actual gap - they're manually tracking across jurisdictions.

Data Sources
  1. FinCEN Money Services Business Registrant Search - CTR filings, filing dates
  2. State MSB Registration Records - license counts, jurisdictions
  3. New York DFS Virtual Currency Licensees - BitLicense status

The message:

Subject: 15 state MSB licenses + new FinCEN filing pattern FinCEN records show you filed 23 CTRs in Q4 2024 versus 8 in Q3 2024 - nearly 3x increase. Your firm holds MSB licenses in 15 states including NY BitLicense - each with different transaction monitoring thresholds. Is someone tracking crypto exchange transactions across all 15 jurisdictions in real-time?
PQS Public Data Strong (8.2/10)

FinCEN Filers with Volume Scaling

What's the play?

Target crypto firms with BitLicense AND 10+ other state MSB registrations where FinCEN CTR filings tripled quarter-over-quarter. Volume scaling creates proportional state reporting burden.

Why this works

Tripled volume angle shows understanding of their workload explosion. Multi-state tracking is exactly their coordination nightmare. Question assumes they might not be caught up (probably true) without being accusatory.

Data Sources
  1. FinCEN Money Services Business Registrant Search - quarterly CTR counts
  2. State MSB Registration Records - license jurisdictions

The message:

Subject: Your FinCEN filings tripled this quarter FinCEN shows you went from 8 CTRs in Q3 to 23 in Q4 2024. With BitLicense plus 14 other state MSB registrations, each filing needs jurisdiction-specific review protocols. Who's managing the cross-state transaction monitoring as volume scales?
PQS Public Data Strong (8.1/10)

RIAs with AUM Growth Post-Deficiency

What's the play?

Target SEC-registered investment advisers with 30%+ AUM growth in the 12 months following an SEC exam that cited personal trading control deficiencies. Growth without remediation creates scaling exposure.

Why this works

Specific numbers from actual ADV filing shows research depth. SEC deficiency + growth combination is real risk they're managing. The connection between AUM growth and compliance risk scaling is obvious to compliance professionals.

Data Sources
  1. SEC Form ADV CSV Historical Data - AUM totals, filing dates
  2. SEC Enforcement & Litigation Database - exam deficiency letters, dates

The message:

Subject: Your Form ADV shows $2.3B AUM jump after SEC deficiency Your latest Form ADV filing shows AUM grew from $8.1B to $10.4B in the past 12 months. The SEC cited inadequate personal trading controls in your March 2024 deficiency letter - that exposure scales with your growth. Who's upgrading the employee trading monitoring to match the new scale?
PQS Public Data Strong (8.0/10)

FinCEN Volume Scaling with State Deadline Pressure

What's the play?

Target crypto MSBs where FinCEN filing volume tripled quarter-over-quarter AND they hold 15+ state MSB licenses. Each state has independent reporting deadlines creating coordination burden.

Why this works

Tripled volume shows workload explosion. 15-state tracking is their exact coordination challenge. Practical operational question about deadline management resonates with overwhelmed compliance teams.

Data Sources
  1. FinCEN Money Services Business Registrant Search - quarterly filing counts
  2. State MSB Registration Records - license jurisdictions, reporting requirements

The message:

Subject: FinCEN volume tripled - are state MSB reports caught up? Your CTR filings went from 8 to 23 quarter-over-quarter per FinCEN records. Each of your 15 state MSB licenses has independent reporting deadlines - tripled volume means tripled state filings. Is someone tracking which state reports are due when?
PQS Public Data Okay (7.9/10)

Broker-Dealers with Post-Settlement Branch Opening

What's the play?

Target FINRA-registered firms that opened new branches within 6 months of settling a supervision-related disciplinary action. New branches need updated frameworks that address the cited deficiencies.

Why this works

Exact settlement amount and timing shows deep research. New branch timing relative to settlement is specific concern. Question is pointed but fair - did they implement fixes before launching new location?

Data Sources
  1. FINRA BrokerCheck Database - settlement dates, amounts, violation types
  2. FINRA Firm Records - branch opening dates, locations

The message:

Subject: Your Phoenix branch opened 4 months after FINRA settlement FINRA records show you settled a supervision failure case in February 2024 for $125,000. Your Phoenix branch opened June 2024 with 12 registered reps - 4 months after that settlement. Did the new branch get the updated supervision framework before going live?
PQS Public Data Okay (7.8/10)

RIAs with Extended Remediation Timelines

What's the play?

Target investment advisers where 9+ months have elapsed since SEC exam deficiency findings without observable remediation signals in subsequent filings. Extended timelines suggest implementation challenges.

Why this works

Timeline pressure is real - 9 months is long time. AUM growth during remediation period shows scale risk. Direct question about implementation status is fair but feels slightly aggressive on timing.

Data Sources
  1. SEC Enforcement & Litigation Database - exam dates, deficiency types
  2. SEC Form ADV CSV Historical Data - AUM totals, filing dates

The message:

Subject: $10.4B AUM with March SEC exam gaps unfixed Your Form ADV shows AUM at $10.4B as of December 2024. SEC's March exam cited personal trading control gaps - that was 9 months ago with $2.3B growth since. Have the trading monitoring upgrades gone live yet?
PQS Public Data Okay (7.6/10)

Branch Expansion During Active Remediation

What's the play?

Target broker-dealers that opened 3+ branches during an 18-month period when they simultaneously had 4+ FINRA disciplinary events under review or remediation.

Why this works

Timeline of violations vs expansions is stark. $125K settlement shows material penalty. Question is fair but feels judgmental about prioritization. Could trigger defensive response.

Data Sources
  1. FINRA BrokerCheck Database - violation dates, settlement amounts
  2. FINRA Firm Records - branch opening dates, locations

The message:

Subject: 3 branches in 18 months during compliance remediation FINRA shows 4 violations over 18 months including $125K February settlement. You opened Phoenix (June), Tampa (August), Charlotte (November) during that same period. Did compliance sign off on each branch launch or did growth outpace controls?

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 Form ADV shows $2.3B AUM growth while SEC cited trading gaps" 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.

Data Sources Reference

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

Source Key Fields Used For
SEC Form ADV Data firm_name, crd_number, aum_total, employee_count, jurisdictions_served Identifying RIAs by AUM, employee growth, multi-jurisdictional operations
SEC Enforcement & Litigation Database respondent_name, violation_type, enforcement_date, settlement_amount Finding firms with recent violations for MNPI, conflicts, custody breaches
FINRA BrokerCheck Database firm_name, crd_number, disciplinary_events, arbitration_awards, branch_count Identifying broker-dealers with violations and branch expansion patterns
FinCEN MSB Registrant Search legal_name, msb_activities, states_of_operation, registration_date Finding crypto exchanges and MSBs with multi-state compliance requirements
NY DFS Virtual Currency Licensees firm_name, license_status, license_issue_date, regulated_activities Identifying BitLicense holders with highest crypto compliance requirements
FDIC Bank Data & Statistics bank_name, asset_size, state, number_of_branches, regulatory_status Finding banks with trading operations requiring employee conduct monitoring
Office of Financial Research Hedge Fund Monitor fund_name, fund_aum, strategy_type, leverage_ratio Identifying hedge funds by AUM and strategy requiring MNPI controls