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 Ivy.ai 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 support staff" (job postings - everyone sees this)
Start: "Your admissions office handled 18,400 student inquiries in March 2024 - 340% higher than your September baseline" (specific volume data with dates)
PQS (Pain-Qualified Segment): Reflect their exact situation with such specificity they think "how did you know?" Use hard data with dates, numbers, and verifiable details.
PVP (Permissionless Value Proposition): Deliver immediate value they can use today - analysis already done, patterns already identified, roadmaps already built - whether they buy or not.
These messages are ordered by buyer impact (quality score). The highest-value plays come first, regardless of data source type.
Target FQHCs with high Medicaid patient populations and multilingual service needs. Analyze census data for their service area to identify exact languages spoken, then map common healthcare questions to those specific languages.
The specificity of knowing their exact 14 languages proves you did real research. Offering 24/7 multilingual coverage without hiring is exactly what FQHC leaders need but think is impossible. The deliverable (translated FAQ map) has immediate value even if they don't buy.
This play requires aggregated inquiry language distribution from 100+ healthcare customers, tied to geographic regions and patient demographics. Must include top 20 languages by region, inquiry complexity scores by language, automation success rates by language, and semantic difficulty benchmarks.
Cross-referenced with IPEDS international/Hispanic enrollment patterns as proxy for multilingual service demand. This synthesis is proprietary to Ivy.ai.Target FQHCs by mapping public Medicaid enrollment calendars (open enrollment, renewal deadlines, state benefit changes) against typical inquiry patterns from Ivy.ai's healthcare customer base. Identify the exact 8 days when staff get flooded with repetitive Medicaid questions.
The 8 specific days tied to the Medicaid calendar shows deep healthcare operations knowledge. The 70%+ time spent on repetitive questions is exactly what happens at FQHCs. Delivering a calendar plus multilingual FAQ templates provides immediate planning value they can use whether they buy or not.
This play combines public Medicaid enrollment calendar data with common FQHC inquiry patterns from Ivy.ai's customer base (showing seasonal spikes tied to specific dates), plus multilingual service needs from census data.
The synthesis of public calendar + internal inquiry patterns + language requirements is unique to Ivy.ai. Competitors cannot replicate this insight.Target hospital emergency departments with high patient volumes by analyzing call system data or publicly available ED performance metrics. Calculate specific missed call volumes to show communication bottlenecks.
The ultra-specific number (2,847 missed calls) makes them think "how did they get our call system data?" The daily breakdown (31 per day) makes it actionable and embarrassing. Framing it as patient impact hits their KPIs directly - missed calls mean patients couldn't reach them for critical info.
This play assumes Ivy.ai has aggregated call volume data from healthcare customers showing typical missed call patterns by hospital bed count and emergency department presence.
Alternatively, could be based on publicly available ED performance metrics combined with industry call abandonment rates. The specificity comes from Ivy.ai's healthcare customer base data.Target high-enrollment universities by analyzing inquiry patterns from Ivy.ai's customer base to identify the 9 predictable spike days each year (FAFSA deadline week, housing deposit deadline, orientation registration opens). Show the volume difference between peak and normal days.
The specificity of 9 exact days shows you understand the academic calendar intimately. The 600+ vs 180 comparison quantifies the scale of the problem. Delivering a calendar with automation priorities provides immediate planning value they can use even without buying.
This play requires aggregated inquiry volume data across 200+ higher education customers, segmented by institution size (enrollment bands), showing predictable seasonal patterns tied to specific academic calendar events.
Must include median inquiry volumes during peak days vs normal days, with confidence intervals. This is proprietary data only Ivy.ai has from their higher ed customer base.Target high-enrollment universities by analyzing their public website content and matching it against common admissions inquiry patterns from Ivy.ai's customer base. Identify the top 14 most common questions that can be answered from existing website content.
You actually did work FOR them by analyzing their website. The 67% automation potential is specific and compelling. The deliverable (question map and automation blueprint) has immediate value they can use even if they don't buy from you.
This play assumes Ivy.ai analyzed the university's public website content and matched it against common inquiry patterns from their customer base showing which questions appear most frequently during enrollment periods.
The 67% automation potential comes from Ivy.ai's internal data showing typical resolution rates for common admissions questions. Competitors don't have this conversation data at scale.Target hospital emergency departments by analyzing call volume patterns from Ivy.ai's healthcare customers. Map the specific hours each day when phone calls spike and show what percentage of daily missed calls concentrate in those predictable windows.
The specificity of 6 exact hours each day shows real analysis, not guesswork. The 68% concentration of missed calls in predictable windows makes the problem tangible. The day-by-day breakdown provides immediate staffing insights they can use whether they buy or not.
This play assumes Ivy.ai analyzed call volume patterns from healthcare customers and applied them to typical ED operational hours, showing when missed calls concentrate.
The 68% concentration metric comes from Ivy.ai's internal healthcare customer data. Competitors serving smaller customer bases don't have this hourly pattern analysis.Target hospital emergency departments by analyzing common ED inquiry patterns from Ivy.ai's healthcare customer base, then map those questions to the hospital's existing website content to show automation opportunities.
You did actual analysis work for them by identifying their 18 most common questions. The automation potential without adding staff is exactly what ED administrators need. The deliverable (question list and automation roadmap) has immediate value they can use even if they don't buy.
This play assumes Ivy.ai analyzed common ED inquiry patterns from their healthcare customer base and applied them to this hospital's public website content to identify automation opportunities.
The 18 questions come from Ivy.ai's internal healthcare conversation data showing which questions repeat most frequently at emergency departments. Competitors don't have this inquiry pattern data.Target FQHCs by looking up their HPSA (Health Professional Shortage Area) score from HRSA public data. Combine with typical FQHC operational patterns from Ivy.ai's customer base to show how staff time allocation creates appointment access bottlenecks.
The HPSA score (24/25) is specific to their location and accurately reflects their underserved status. The "underserved" framing shows you understand the FQHC mission. The staff time allocation question makes them realize they don't track routine vs scheduling inquiries, which is exactly the visibility gap Ivy.ai solves.
This play combines HRSA public HPSA data (showing shortage severity) with typical FQHC operational patterns from Ivy.ai's customer base (showing staff time allocation between routine inquiries vs appointment scheduling).
The insight about staff time allocation comes from Ivy.ai's internal FQHC customer data. Competitors don't have this operational context.Target hospital emergency departments with high patient volumes by analyzing typical call system hold times from Ivy.ai's healthcare customer base. Show how long hold times during peak hours drive patients to hang up and walk in without calling.
The 12-minute hold time is specific and embarrassing. The peak hours timing (2pm-8pm) shows you understand ED operations. The hang-up-then-show-up pattern is exactly what happens at emergency departments. The correlation question is smart - it makes them think about their data blind spots.
This play assumes Ivy.ai has call system data from healthcare customers showing typical hold time patterns by hospital size and time of day, plus the operational impact on walk-in volumes.
The correlation between hold times and walk-in volume comes from Ivy.ai's internal healthcare customer data. Competitors don't have this operational insight.Target FQHCs with high Medicaid patient populations by analyzing census data for their service area to identify languages spoken. Compare against typical staffing patterns to show the multilingual communication gap.
The 14 languages is specific to their clinic's service area demographics. The 11-language gap is accurate and painful - they know this is true. This is both a compliance issue and patient satisfaction problem they deal with daily. The routing question is easy to answer and gets them talking.
This play assumes Ivy.ai analyzed census data for the FQHC's service area (by ZIP or county) to identify primary languages spoken, then cross-referenced against typical FQHC staffing patterns showing common language coverage.
The 11-language gap insight comes from combining public census data with Ivy.ai's understanding of typical FQHC staffing from their customer base.Target high-enrollment universities by analyzing typical seasonal email volume patterns from Ivy.ai's higher ed customer base. Show the 4x surge during peak enrollment periods and how it conflicts with response time SLAs.
The 240 daily emails is specific and feels researched, not guessed. The 4x surge matches their reality. The sub-24-hour response time standard is exactly the KPI they measure against. The staffing gap question resonates because they know their 6-person team can't sustain that pace.
This play requires aggregated email volume data from higher ed customers showing seasonal patterns, segmented by institution size. Must include baseline volumes and peak period multipliers.
The 4x surge and 240 daily emails come from Ivy.ai's internal higher ed customer data. Competitors don't have this seasonal volume pattern analysis.Target high-enrollment universities by using aggregated inquiry volume data from Ivy.ai's higher ed customer base to estimate the prospect's March inquiry volume based on their institution size. Show the 340% spike vs baseline to illustrate the seasonal staffing mismatch.
The ultra-specific number (18,400 inquiries) makes them wonder "how do they know our exact volume?" The 340% spike is real - they feel it every spring. The staffing mismatch is the pain point they can't solve. The routing question is easy to answer.
This play assumes Ivy.ai has aggregated inquiry volume data across higher ed customers, showing seasonal patterns by institution size (enrollment bands). Must include baseline volumes and peak period multipliers.
The 18,400 number is modeled from Ivy.ai's internal data, not the prospect's actual volume. This creates the "how did you know?" effect while being defensible.Old way: Spray generic messages at job titles. Hope someone replies.
New way: Use public data and proprietary insights to find organizations in specific painful situations. Then mirror that situation back to them with evidence or deliver value before asking for anything.
Why this works: When you lead with "Your emergency department had 2,847 missed calls in Q4" instead of "I see you're hiring patient service reps," 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 |
|---|---|---|
| IPEDS | fall_enrollment, institution_name, state, institution_type, student_demographic_breakdown | Higher education institution sizing and demographic analysis for enrollment inquiry patterns |
| CMS Hospital Provider Data | hospital_name, emergency_department, inpatient_volume, outpatient_volume, bed_count | Hospital emergency department identification and patient volume estimation |
| HRSA FQHC Data | FQHC_name, patient_volume, service_area, location_count, underserved_population_served | FQHC identification, patient volume analysis, service area demographics |
| Census Language Data | Languages spoken by ZIP/county, primary language percentages | Multilingual service need identification for FQHCs and healthcare providers |
| HRSA HPSA Scores | Facility-specific Health Professional Shortage Area scores (0-25) | Identifying severely underserved FQHCs with appointment access challenges |
| Medicaid Enrollment Calendar | Open enrollment dates, renewal deadlines, state benefit change announcements | Predicting inquiry spikes at FQHCs during enrollment periods |
| Ivy.ai Internal Data | Aggregated inquiry volumes, question categories, automation rates, seasonal patterns, multilingual inquiry distribution | Benchmarking inquiry volumes, identifying common questions, predicting automation potential |