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 OnX SDR Email:
Why this fails: The CIO 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 Q2 Digital Banking contract expires March 2026 - 8 months after your planned FIS core go-live date" (contract filing with specific dates)
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 messages demonstrate precise understanding of the prospect's situation and deliver actionable value. Ordered by quality score - strongest plays first.
When banks publicly announce core banking modernization, immediately deliver realistic cost expectations based on OnX's actual project delivery data from similar banks - showing them what vendors exclude from initial quotes.
CFOs and CIOs know vendor quotes are always lowball estimates. By surfacing the specific hidden costs (like ancillary system integration) with real dollar amounts from comparable projects, you're preventing a budget disaster they haven't planned for yet.
This play requires aggregated project delivery data from 40+ OnX transformations including actual costs, timelines, and scope by customer asset size and industry vertical (financial services subset), with 10th/50th/90th percentile ranges.
Combined with public contract filings to identify initial quotes. This synthesis is unique to OnX's experience.Alert banks that their commercial lending platform integration isn't included in core banking migration scope - surfacing a major oversight that could derail the project timeline and budget.
Commercial lending is often treated as a separate system, but it has deep dependencies on core banking. Pointing out this gap with specific workflow counts and integration costs demonstrates you understand banking technology architecture better than their vendor.
This play requires OnX's knowledge of typical commercial lending integration complexity, estimated from bank commercial loan portfolio size. Workflow complexity is inferred from system age and bank size.
Combined with public data on platforms in use. This architectural knowledge is proprietary to OnX.Target banks that just issued core banking modernization RFPs with a timely warning about dependency mapping gaps that cause 9-14 month delays post-vendor selection.
The timing is perfect - they're in vendor selection mode RIGHT NOW. The specific RFP date proves you're tracking their procurement activity, and the delay warning addresses a real fear they have about hidden integration complexity.
Alert banks that treasury management integration isn't scoped in their core migration, risking commercial client relationships during the transition.
Treasury management clients are high-value commercial relationships. The threat of losing these clients during migration is a revenue risk that gets executive attention immediately.
This play requires identifying treasury management platforms through job postings or partnerships, with corporate client count estimated from bank commercial lending portfolio size.
Timeline and cost estimates based on OnX's integration experience.Target banks that lost key IT leadership during core banking vendor selection - highlighting the institutional knowledge risk that affects modernization success.
Losing IT directors during modernization is a nightmare scenario CIOs worry about constantly. Naming specific departed leaders with titles proves you're tracking their team changes, and the institutional knowledge concern is exactly what keeps them up at night.
Target banks using legacy fraud detection systems with years of custom rules that won't migrate automatically to new core banking platforms.
Fraud detection is critical operational infrastructure. The thought of losing 14 years of pattern learning and custom rules is terrifying - it represents institutional knowledge that can't be easily rebuilt.
This play requires identifying fraud detection platforms through job postings or regulatory filings. System age (14 years) is estimated from bank history and typical fraud platform lifecycles.
Migration complexity based on OnX's experience with fraud rule rebuilding projects.Alert hospital systems to EMR instance fragmentation across their facilities - showing them infrastructure inefficiency they likely don't have full visibility into.
Multi-site hospital systems often accumulate EMR instances through acquisitions without realizing the total count. The $2.1M maintenance savings is concrete and actionable, and offering the full instance map provides immediate value.
Target banks where digital banking platform contracts expire shortly after planned core migration go-live dates - creating integration timing conflicts.
This is a legitimate planning concern that could create service disruptions if not coordinated properly. The specific contract date and vendor shows detailed research, and the question is practical and easy to route.
Alert hospital systems to radiology PACS vendor fragmentation across sites - showing them hidden support costs and operational inefficiencies from running multiple systems.
Specific site names and vendor identification proves detailed research. The $340K per-system cost is concrete, and image transfer delays between sites is a patient care issue that matters to hospital leadership.
This play requires identifying hospital system sites through CMS data and inferring PACS vendor diversity through job postings, capital equipment filings, or RFPs.
Cost estimates based on OnX's experience with PACS consolidation projects.Alert hospital systems to LIS vendor fragmentation with specific site examples and interface cost savings from consolidation.
Specific site names and recent installation timing shows real research. The $890K interface cost is the kind of hidden expense that doesn't show up in vendor contracts but accumulates over time.
This play requires identifying LIS vendors through job postings, capital expenditure filings, or vendor press releases, combined with interface cost benchmarking from OnX projects.
Installation timing inferred from job postings or capital equipment purchases.Target hospital systems that acquired multiple facilities and inherited different patient portal platforms - creating patient experience fragmentation.
Specific hospital names from recent acquisitions shows you tracked the M&A activity. Patient experience fragmentation affects satisfaction scores, which hospital leaders care deeply about.
Target hospital systems that haven't integrated medical staff credentialing databases 6-9 months after acquisitions - creating compliance and operational risks.
Credentialing is a high-stakes compliance issue. The multi-site physician privileges concern affects care coordination, and the timeline (6-9 months post-acquisition) shows they've had time but haven't prioritized it yet.
Alert hospital systems to automated dispensing system fragmentation that prevents cross-site pharmacy inventory visibility and emergency drug transfers.
Specific site names and vendor identification demonstrates detailed research. The patient safety and operational efficiency angle (emergency transfers between sites) resonates with hospital leadership.
This play requires identifying pharmacy automation vendors through capital equipment filings, job postings, or vendor announcements.
TCO analysis based on OnX's pharmacy system consolidation experience.Map EMR instance fragmentation across hospital system sites and deliver the analysis showing infrastructure inefficiency.
Telling them something specific about THEIR infrastructure they might not have visibility into provides value. The cost reduction estimate is concrete, but the instance count feels slightly generic.
This play assumes OnX can map EMR deployments across hospital sites through public acquisition data combined with typical EMR deployment patterns from infrastructure assessments.
Instance counts are estimated based on acquisition history and typical multi-site complexity.Alert banks that custom loan origination workflows won't migrate automatically in core banking conversions - surfacing hidden migration costs and timelines.
The specific LOS platform (Encompass) and custom workflow concern is exactly the kind of hidden risk banks need to plan for. But the precision on workflow count (847) might feel like an assumption disguised as fact.
This play requires identifying current LOS through job postings or vendor relationships. Custom workflow count is an educated estimate based on bank size and system age (9 years).
Migration complexity and costs based on OnX's LOS conversion experience.When banks announce core migrations in earnings calls, immediately deliver cost benchmarking data from similar OnX projects showing typical underestimation patterns.
Tracking earnings calls shows you're monitoring their announcements. The asset size estimate feels credible, but "typically underestimate by 40%" edges toward generic industry benchmarking territory.
This play requires OnX's aggregated case study data from prior banking modernization projects with cost benchmarking by bank asset size, combined with public earnings call monitoring.
Underestimation percentage (40%) is based on OnX's project history.Alert hospital systems to scheduling platform fragmentation that prevents real-time OR availability visibility across sites.
Multiple scheduling platforms is plausible for multi-site systems, and the patient access impact is real. But this feels somewhat generic - could apply to many hospital systems without being uniquely about THEIR situation.
This play requires inferring scheduling system diversity through job postings and identifying utilization patterns through CMS data or prior OnX consulting work.
Platform count is estimated based on hospital acquisition history.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 FIS contract filing shows $4.2M but that excludes the 18 ancillary systems" instead of "I see you're modernizing your infrastructure," 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 |
|---|---|---|
| FDIC BankFind Suite | bank_name, charter_type, total_assets, merger_acquisition_history | Community bank asset growth tracking |
| CMS Hospital Provider Data | hospital_name, hospital_system_affiliation, bed_count, service_lines | Hospital system site mapping and acquisition tracking |
| Public Contract Filings | vendor_name, contract_value, scope, expiration_date | Core banking modernization vendor selection and costs |
| LinkedIn Profile Updates | job_title, employment_dates, company | IT leadership departures and transitions |
| Job Postings | technology_stack, platform_requirements, role_descriptions | Technology platform identification (LOS, fraud detection, EMR, etc.) |
| Public Procurement Portals | rfp_issuance_date, response_deadline, scope | Core banking RFP timing and vendor selection windows |
| Acquisition Announcements | acquired_entity, acquisition_date, integration_timeline | Hospital M&A activity and post-acquisition integration gaps |
| OnX Internal Project Data | project_costs, timelines, scope, customer_asset_size, industry_vertical | Cost benchmarking and hidden integration requirements |