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 Smarsh 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 firm received FINRA case #2024061234567 on June 12th, still pending after 8 months" (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, case details.
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 quality score - the highest-scoring messages come first regardless of data source type. Each demonstrates either precise situation mirroring (PQS) or immediate value delivery (PVP).
Cross-reference SEC-registered investment advisors' Form ADV channel disclosures with their LinkedIn job postings to identify undisclosed communication channels. The gap between what they report to regulators vs what they advertise to candidates reveals compliance exposure that SEC examiners will find in 15 minutes.
This is an "oh shit" moment. The compliance officer can verify your finding in 2 minutes by checking their own LinkedIn. You're surfacing a regulatory gap they didn't know existed - and one that could result in SEC deficiencies. The specificity (6 channels vs 3, with job post excerpts offered) proves you did real research, not AI-generated guessing.
Scrape Glassdoor employee reviews for SEC-registered investment advisors and extract mentions of communication tools used for work. Compare this against their Form ADV disclosures to identify undisclosed channels. Provide specific mention counts and offer role-based breakdown to help them understand supervision design gaps.
This is borderline creepy but undeniably valuable. The compliance officer realizes you've done investigative work they couldn't easily replicate - scraping 127 reviews and counting specific channel mentions by role. The mention counts (23 for WhatsApp, 31 for personal text) are concrete evidence of hidden channels. The offer of role-based breakdown provides immediate utility for supervision policy updates.
Analyze broker-dealers' recent FINRA disciplinary cases for complaints citing "failure to supervise communications on unapproved channels." Cross-reference the complaint language with the firm's discovery response scope (typically public in case documents) to identify channels mentioned in complaints but excluded from discovery production. Offer to provide the channel gap analysis.
This is extremely specific to their actual FINRA case. The compliance officer can verify the March case details immediately. The insight that WhatsApp and Signal weren't in the production scope despite being mentioned in the complaint is actionable intelligence that could prevent a follow-up violation or enhanced penalties. This is genuinely valuable even if they never buy from you.
Map broker-dealer's FINRA cases to discovery response times, then identify which FINRA examiners handled which cases. Reveal patterns where a specific examiner flagged multiple slow-response cases for follow-up review. This helps compliance officers understand examiner-specific scrutiny and prioritize remediation strategically.
The specific examiner name and district (Sarah Chen, District 9) makes this feel like insider intelligence. The 6 of 8 pattern with one examiner is actionable - the compliance officer can verify this against their records and potentially address examiner relationship issues. The follow-up review flag creates urgency. This helps them prioritize remediation efforts strategically.
This play assumes FINRA case records include examiner names (some are public, some require synthesis from case documents) and that discovery response times can be estimated from case filing and resolution dates in public records.
The examiner pattern synthesis is unique intelligence that requires manual case review.Cross-reference RIA Form ADV approved communication channels with language on their website (especially careers pages) that suggests mobile or undisclosed channels. The gap between regulatory disclosure and public-facing communications indicates potential SEC examination exposure.
The cross-reference between Form ADV and their own website is smart synthesis that shows real research effort. The "mobile-first communication culture" language catch is sharp and concerning - it suggests channels they may not have disclosed. This is specific to their firm and immediately actionable. The compliance officer needs to verify this right away.
Map all FINRA discovery requests from broker-dealer's case history (2023-2024) to estimated response times based on case filing and resolution dates. Compare their average response time to industry median. Offer the spreadsheet showing which cases had delays and the specific gaps.
The compliance officer is shocked that you actually did the work mapping all 14 cases. The specific comparison (38 days average vs 22 days median) is actionable and verifiable against their internal records. The offer of a spreadsheet with case-by-case breakdown is low-commitment but provides immediate utility. They can use this to identify systematic delays and prioritize process improvements.
This play requires aggregated discovery response time benchmarks from industry peers, segmented by broker-dealer size. Response times are estimated from public case filing and resolution dates.
The case-by-case mapping and benchmark comparison is proprietary analysis.Compare RIA Form ADV Part 1 reported headcount of investment adviser representatives with LinkedIn employee counts showing "Financial Advisor" or "Wealth Manager" titles. Large discrepancies (35+ person gap) will trigger SEC questioning about supervision adequacy and registration status during examinations.
The specific numbers (12 vs 47) are immediately verifiable by the compliance officer. The LinkedIn cross-reference is smart synthesis. This is a real compliance gap that could be serious - misreporting headcount or having unregistered advisors. The routing question is simple and the intelligence is actionable.
Identify broker-dealer FINRA cases that have been in "pending response" status for longer than 6 months. Cases exceeding this threshold face automatic escalation to enforcement consideration with penalty multipliers. Use specific case numbers and filing dates to create urgency.
The specific case number (2024061234567) and filing date (June 12th) are verifiable and concrete. The 8-month timeline is concerning and creates immediate urgency. The enforcement escalation threat is real and motivates action. The simple yes/no question about case status prompts immediate response.
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 FINRA case 2024061234567 is still pending after 8 months" 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 public data or specified internal data assumptions. Here are the key sources used in this playbook:
| Source | Key Fields | Used For |
|---|---|---|
| FINRA Disciplinary Actions Online Database | firm_name, violation_type, disciplinary_action_date, fine_amount, case_number | Identifying broker-dealers with recent violations and pending cases |
| FINRA BrokerCheck (CRD Database) | firm_name, crd_number, registration_status, disciplinary_disclosures, regulatory_actions | Tracking enforcement actions and compliance violations |
| SEC Investment Adviser Public Disclosure (IAPD) | advisor_name, sec_number, form_adv_filings, regulatory_history, approved_channels | Form ADV analysis and channel disclosure verification |
| LinkedIn Company Pages & Job Posts | employee_count, job_titles, job_descriptions, communication_tools_mentioned | Cross-referencing headcount and identifying undisclosed communication channels |
| Glassdoor Employee Reviews | review_text, job_titles, communication_tools_mentioned, workplace_culture | Mining employee mentions of communication tools used at work |
| Company Website (Careers Pages) | job_descriptions, culture_language, communication_preferences | Identifying disclosure gaps between public messaging and regulatory filings |
| Internal Discovery Response Benchmarks | median_response_time, response_time_by_firm_size, case_count | Benchmarking discovery response times against industry peers (HYBRID plays) |