Blueprint Playbook for Cyara

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

Subject: Improve Your Contact Center CX Hi [FirstName], I noticed your company recently posted about customer experience initiatives on LinkedIn. At Cyara, we help enterprise contact centers ensure seamless omnichannel customer journeys. Our AI-powered platform enables continuous testing and monitoring across voice, digital, and messaging channels. We've helped Fortune 2000 companies reduce regression testing by 75%. Would you be open to a quick 15-minute call to discuss how Cyara could help [CompanyName] improve customer satisfaction and contact center performance? Best regards, Sarah SDR, Cyara

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 plan's call center answer time increased from 2.1 to 4.7 minutes over 3 quarters" (CMS Medicare Advantage Call Center Monitoring data with specific metrics)

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 metrics.

PVP (Permissionless Value Proposition): Deliver immediate value they can use today - analysis already done, patterns already identified, breakdowns already categorized - whether they buy or not.

Cyara's Highest-Impact Plays

These plays are ordered by quality score - the strongest messages appear first, regardless of data source type. Each demonstrates precise understanding backed by verifiable data.

PVP Public Data Strong (9.3/10)

I Tested Your Chatbot with 50 Member Questions

What's the play?

Proactively test the health plan's newly launched AI chatbot with realistic member questions and deliver the failure report before they ask. This works because health plans just launched AI without comprehensive quality baselines - they're blind to hallucination risks.

Why this works

You did work they should have done but didn't. Testing their live chatbot and finding 7 incorrect responses proves immediate brand risk. The specificity (coverage hallucinations, provider detail errors) makes this impossible to ignore.

Data Sources
  1. Website monitoring to detect chatbot launches
  2. Manual testing of public-facing chatbot with realistic questions
  3. Documentation of incorrect responses with screenshots

The message:

Subject: I tested your chatbot with 50 tricky member questions I ran 50 realistic member questions through your new AI chatbot covering claims, prior auth, and provider networks. 7 responses contained potentially incorrect information about coverage and 3 hallucinated provider details. Want the test results and failure patterns?
PVP Public Data Strong (9.2/10)

Your 6 New Markets Have 2.1x Higher Complaint Rates

What's the play?

Analyze FCC complaints by geographic market and identify that newly expanded markets show dramatically higher complaint rates than established markets. Trace the spike to specific onboarding IVR flows and service activation processes.

Why this works

Market-level analysis is sophisticated work most contact center leaders haven't done. The 2.1x multiplier is alarming and specific. Connection to onboarding flows gives them an immediate fix target. The geographic breakdown helps prioritize where to act first.

Data Sources
  1. FCC Consumer Complaints Database - company_name, state, complaint_type, date
  2. Press releases announcing market expansion timelines
  3. Per-market customer count estimates from public filings

The message:

Subject: Your 6 new markets have 2.1x higher complaint rates I analyzed FCC complaints by market and your 6 Q4 expansion markets show 2.1x higher complaint rates than your established markets (89 vs 42 per 100K customers). The complaint spike traces to new customer onboarding IVR flows and service activation processes. Want the market-by-market analysis and high-risk flows?
PVP Public Data Strong (9.1/10)

I Mapped Your 83 CFPB Complaints to IVR Failures

What's the play?

Download all CFPB complaints for the target bank, categorize them by failure point (IVR, agent transfer, authentication, resolution), and identify which complaints trace back to preventable IVR menu failures that could be tested.

Why this works

Deep analysis of THEIR specific complaints shows you did real research work. 28 preventable failures gives them an actionable number. Categorization by failure point is exactly the breakdown they need to prioritize fixes. Low-commitment ask to see the data makes it easy to respond.

Data Sources
  1. CFPB Consumer Complaint Database - company_name, complaint_narrative, issue, sub_issue, date
  2. Manual categorization of complaint narratives to identify IVR-related failures

The message:

Subject: I mapped your 83 CFPB complaints to IVR failures I analyzed all 83 of your bank's 2024 CFPB complaints and categorized them by failure point (IVR, agent transfer, authentication, resolution). 28 complaints trace back to specific IVR menu failures that could be tested and prevented. Want the breakdown by complaint type and IVR flow?
PVP Public Data Strong (9.0/10)

Your Chatbot Gave Wrong Prior Auth Info 4 Times

What's the play?

Test the health plan's chatbot specifically with prior authorization questions - a high-stakes use case where wrong answers lead to denied claims and member complaints. Document the specific errors with test transcripts.

Why this works

Focused testing of their live chatbot on high-stakes questions. 4 wrong answers out of 20 is a 20% error rate that's deeply concerning. Prior auth is where mistakes hurt members most. Test transcripts provide concrete evidence they can't dismiss.

Data Sources
  1. Public-facing chatbot testing with prior authorization questions
  2. Documentation of incorrect coverage information responses
  3. Screenshots or transcripts of error patterns

The message:

Subject: Your chatbot gave wrong prior auth info 4 times I tested your member services chatbot with 20 prior authorization questions and got 4 responses with incorrect coverage information. Those 4 wrong answers could lead to denied claims, member complaints, or regulatory issues. Want the test transcripts and error patterns?
PVP Public + Internal Strong (8.9/10)

Your Q2 Platform Migration Has 14 High-Risk IVR Paths

What's the play?

Based on knowledge of the bank's current IVR platform and the platform they're migrating to, identify customer journey paths with high failure risk during migration. Connect these to top complaint categories from CFPB data.

Why this works

Demonstrates knowledge of their specific migration timeline and target platform. 14 specific high-risk paths is concrete and actionable. Connection to top complaint categories (password resets, fraud alerts, account verification) proves you understand their pain points. Practical testing checklist offers immediate value.

Data Sources
  1. Job postings indicating contact center platform migration timing
  2. CFPB Consumer Complaint Database - complaint categories
  3. Platform architecture knowledge (current vs. target platform capabilities)

The message:

Subject: Your Q2 platform migration has 14 high-risk IVR paths Based on your current IVR structure and the platform you're migrating to in Q2, I identified 14 customer journey paths with high failure risk during migration. These paths handle password resets, fraud alerts, and account verification - your top complaint categories. Want the risk assessment and testing checklist?
DATA REQUIREMENT

This play requires knowledge of contact center platform architectures (current and target platforms) and ability to map known migration risk patterns based on platform capabilities.

Platform-specific failure pattern data from testing 350M+ journeys makes this analysis unique to Cyara.
PVP Public Data Strong (8.9/10)

I Categorized Your 847 FCC Complaints by Root Cause

What's the play?

Download all FCC complaints for the telecom carrier, analyze complaint narratives to trace failures back to root causes (IVR authentication, call routing, service quality), and identify which failures are testable and preventable.

Why this works

Deep analysis of THEIR specific complaints demonstrates serious research effort. 312 preventable complaints (37% of total) is a significant number that creates urgency. Root cause focus shows you're not just reporting data - you're providing insights. Prioritized fix list makes the value immediately actionable.

Data Sources
  1. FCC Consumer Complaints Database - company_name, complaint_type, issue_description, date
  2. Manual categorization of complaint narratives to identify IVR/routing root causes

The message:

Subject: I categorized your 847 FCC complaints by root cause I analyzed all 847 of your 2024 FCC complaints and traced 312 (37%) back to IVR authentication failures and call routing issues. These are testable, preventable failures that are driving customer complaints. Want the complaint breakdown by IVR flow and fix priority?
PVP Public Data Strong (8.8/10)

Your 47K Members Lost $180 Each in Quality Bonuses

What's the play?

Calculate the financial impact of star rating decline on quality bonus payments per member, then trace the percentage of decline attributable to controllable call center performance metrics. Present both the total loss and the controllable portion.

Why this works

Financial impact per member ($180) is more tangible than aggregate numbers. 63% controllable means most of the problem is fixable - that's encouraging. Exact enrollment (47,000) shows deep research into their specific plan. Practical recovery path offer provides immediate next steps.

Data Sources
  1. CMS Star Ratings - plan_name, star_rating, call_center_metric
  2. Medicare Advantage enrollment data by plan
  3. CMS quality bonus payment schedules

The message:

Subject: Your 47K members lost $180 each in quality bonuses Your Medicare Advantage plan's star rating drop cost approximately $180 per member in quality bonus payments across 47,000 enrollees ($8.46M total). I traced 63% of the star rating decline to call center performance metrics you can directly control. Want the call center metric breakdown and recovery timeline?
PVP Public Data Strong (8.7/10)

I Calculated Your Star Rating Recovery Scenarios

What's the play?

Model multiple scenarios showing how improving specific call center metrics (wait times, first-call resolution, abandonment rates) could recover star ratings to 4.0+ stars. Identify the fastest recovery path with timeline.

Why this works

Scenario modeling for THEIR specific plan shows sophisticated analysis. Timeline-based recovery path is actionable - they can plan around it. Focus on metrics they can actually control (vs. external factors) makes this feel achievable. Clear value delivery even before any purchase discussion.

Data Sources
  1. CMS Star Ratings - current and historical ratings by metric
  2. CMS Medicare Advantage Call Center Monitoring - performance thresholds
  3. Star rating methodology documentation for metric weights

The message:

Subject: I calculated your star rating recovery scenarios I modeled 4 scenarios showing how improving specific call center metrics could recover your 2026 star ratings to 4.0+ stars. The fastest path: Fix phone access wait times and first-call resolution rates by July 2025. Want the scenario models and timeline?
PVP Public + Internal Strong (8.6/10)

I Mapped Your Patient Portal to Communication Failures

What's the play?

Trace low HCAHPS communication scores to specific patient touchpoints in the hospital's current portal and phone system. Benchmark potential improvement against similar hospital recovery patterns.

Why this works

Connection between HCAHPS scores and specific touchpoints is valuable mapping work. 6 specific fixes is an actionable number - not overwhelming. Percentile improvement projection (23rd to 60th) is compelling and based on real hospital benchmarks. Roadmap offer provides immediate next steps.

Data Sources
  1. HCAHPS Hospital Patient Satisfaction Survey - communication_scores by category
  2. Patient portal analysis (public-facing portal testing)
  3. Benchmark data from similar hospitals' improvement trajectories

The message:

Subject: I mapped your patient portal to communication failures I traced your hospital's 23rd percentile HCAHPS communication scores to 6 specific patient touchpoints in your current portal and phone system. Fixing these 6 touchpoints could move you to 60th percentile based on similar hospital improvements. Want the touchpoint analysis and improvement roadmap?
DATA REQUIREMENT

This play requires ability to analyze patient portal flows (via public portal testing) and map them to HCAHPS communication categories, plus benchmark data from hospital improvement case studies.

Omnichannel failure pattern data from testing healthcare systems makes this mapping unique to Cyara.
PQS Public + Internal Strong (8.4/10)

Banks with Rising CFPB Complaints + Platform Upgrade Signals

What's the play?

Target banks experiencing rising CFPB complaints about phone system issues while simultaneously showing signals of contact center platform upgrades (job postings for platform-specific roles). The combination indicates infrastructure stress during technology transition.

Why this works

Specific numbers about THEIR bank (43 complaints, 38% increase) prove real research. Timing connection between complaints and platform upgrade creates urgency - they're about to make it worse if they don't test. Easy routing question makes response simple.

Data Sources
  1. CFPB Consumer Complaint Database - company_name, complaint_narrative, issue, sub_issue, date
  2. LinkedIn job postings - contact center platform roles, upgrade timing signals
  3. Platform-specific failure detection benchmarks

The message:

Subject: Your contact center CFPB complaints up 47% YoY Your bank's CFPB complaints increased 47% year-over-year (83 in 2024 vs 56 in 2023), with 34% citing phone/IVR issues. You're migrating to a new contact center platform in Q2 2025 according to your recent tech job postings. Who's handling pre-launch testing for the new IVR flows?
DATA REQUIREMENT

This play assumes access to job posting data indicating platform migration timing combined with aggregated failure detection rates by contact center platform from testing customer journeys.

Platform-specific failure benchmarks from Cyara's testing data make the risk assessment unique.
PVP Public + Internal Strong (8.4/10)

Your March Portal Launch Has 8 Communication Failure Risks

What's the play?

Based on the hospital's new patient portal launching in March, identify customer journey paths that could worsen already-low HCAHPS communication scores. Focus on high-volume patient interactions like appointment scheduling, test results, and medication questions.

Why this works

Knowledge of specific March launch timeline shows you're tracking their initiatives. 8 specific risks is concrete and manageable. Connection to HCAHPS categories they're already struggling with makes this personally relevant. Pre-launch timing creates urgency to act now.

Data Sources
  1. HCAHPS Hospital Patient Satisfaction Survey - communication_scores
  2. Press releases or announcements about patient portal launches
  3. Patient portal flow analysis mapped to HCAHPS categories

The message:

Subject: Your March portal launch has 8 communication failure risks Based on your new patient portal launching in March, I identified 8 customer journey paths that could worsen your already-low HCAHPS communication scores. These paths handle appointment scheduling, test results, and medication questions - high-volume patient interactions. Want the risk assessment before launch?
DATA REQUIREMENT

This play requires ability to map patient portal flows to known communication failure patterns from HCAHPS data, based on testing similar healthcare portal deployments.

Omnichannel failure pattern data during digital transformation makes this risk assessment unique to Cyara.
PQS Public Data Strong (8.6/10)

Medicare Advantage Plans with Declining Call Center Performance + Star Rating Risk

What's the play?

Target Medicare Advantage plans showing declining call center performance metrics (answer time, abandonment rate) in CMS monitoring data while also experiencing star rating drops. These plans face member loss and reduced reimbursement if trends continue.

Why this works

Specific star rating category and year-over-year comparison proves deep research. Financial impact calculation ($180 per member) is relevant and creates urgency. Exact enrollment numbers (47,000) show you know their business. Easy routing question keeps it conversational.

Data Sources
  1. CMS Medicare Advantage Call Center Monitoring - answer_time_minutes, abandonment_rate, quarter, year
  2. CMS Star Ratings - plan_name, star_rating, call_center_metric
  3. Medicare Advantage enrollment data by plan

The message:

Subject: Your MA plan dropped to 2.5 stars for phone access Your Medicare Advantage plan's 2025 Star Rating shows 2.5 stars for 'Getting Needed Care' phone access metrics (down from 3.5 in 2024). That drop cost you roughly $180 per member in quality bonus payments across your 47,000 enrollees. Who owns the call center quality improvement plan?
PQS Public Data Strong (8.5/10)

Telecom Carriers with High FCC Complaints + Recent Service Expansion

What's the play?

Target telecom carriers with high and accelerating FCC complaint volumes (specifically IVR/automated phone system issues) while simultaneously expanding into new markets or launching new services. Indicates IVR infrastructure can't keep pace with growth.

Why this works

Very specific complaint breakdown by channel (347 IVR-related out of 847 total). 41% attribution to IVR is a major red flag that demands attention. Timing with new service launch creates immediate urgency. Straightforward testing question makes response easy.

Data Sources
  1. FCC Consumer Complaints Database - company_name, complaint_type, issue_description, date
  2. LinkedIn employee growth data or press releases about expansion
  3. Service expansion announcements (new markets, product launches)

The message:

Subject: 347 FCC complaints cite your IVR system failures Your carrier had 347 FCC complaints in 2024 specifically mentioning IVR or automated phone system issues. That's 41% of your total complaints and you're launching 5G home internet service next month. Is someone testing the new service activation IVR flows?
PQS Public Data Strong (8.3/10)

Telecom Carriers with High FCC Complaints During Rapid Growth

What's the play?

Target telecom carriers experiencing rising FCC complaints about customer service while simultaneously showing employee headcount growth and market expansion. The acceleration of complaints faster than customer growth indicates scaling problems with contact center infrastructure.

Why this works

Specific FCC complaint numbers and year-over-year comparison (52% increase) is alarming. Connection between rapid scaling (18% headcount growth) and accelerating service failures is insightful - proves IVR/chatbot infrastructure can't handle volume. Creates urgency to fix before further expansion.

Data Sources
  1. FCC Consumer Complaints Database - company_name, complaint_type, issue_description, date
  2. LinkedIn employee count growth data
  3. Press releases about service expansion or new customer additions

The message:

Subject: Your carrier had 847 FCC complaints in 2024 Your company received 847 FCC complaints in 2024, up 34% from 632 in 2023, with 41% citing customer service failures. You just expanded into 6 new markets in Q4 and added 180,000 new customers. Who's ensuring your contact center can handle the volume surge?
PQS Public + Internal Strong (8.2/10)

Health Plans Launching AI Chatbots Without Quality Baselines

What's the play?

Target health plans launching AI chatbots for member services based on hiring signals (AI engineer roles) and product announcements, but showing no public documentation of quality baselines or hallucination testing before launch. High risk of brand-damaging AI responses.

Why this works

Specific volume number (2,400 conversations daily) shows impressive research. Hallucination risk framing is exactly what keeps CX leaders up at night. Scale (2,400 daily chances for failure) makes the urgency tangible. Easy yes/no question keeps response simple.

Data Sources
  1. LinkedIn job postings - AI engineer hiring count
  2. Website monitoring for chatbot launches or analytics reports
  3. AI hallucination detection benchmarks by industry

The message:

Subject: Your AI chatbot handling 2,400 member chats/day Your member services chatbot is handling approximately 2,400 conversations daily based on your January analytics report. That's 2,400 chances per day for AI hallucinations about coverage, claims, or provider networks. Is anyone continuously testing for brand-damaging responses?
DATA REQUIREMENT

This play assumes access to publicly disclosed chatbot usage metrics or ability to estimate based on plan size and AI hallucination detection rates from testing healthcare deployments.

Proprietary AI hallucination detection methodology from testing 350M+ journeys makes the risk assessment unique to Cyara.
PQS Public + Internal Strong (8.1/10)

Hospitals with Low HCAHPS Communication Scores + Digital Expansion

What's the play?

Target hospitals with low HCAHPS communication scores (nurse/doctor communication categories) while announcing digital expansion initiatives like patient portals or telehealth. Low communication scores + new digital channels often create more confusion rather than improvement.

Why this works

Specific HCAHPS category (23rd percentile for nurse communication) and connection to March patient portal launch shows deep research. Insight that digital expansion can worsen communication problems resonates with leaders who've seen this pattern. Timeline creates urgency to test before launch.

Data Sources
  1. HCAHPS Hospital Patient Satisfaction Survey - facility_name, communication_scores, measure_value
  2. Press releases about patient portal or telehealth launches
  3. Omnichannel failure patterns during digital expansion

The message:

Subject: Your hospital scored 23rd percentile for nurse communication Your hospital's 2024 HCAHPS scores show 23rd percentile for 'Communication with Nurses' and you're rolling out a new patient portal in March. Low communication scores + new digital channels often create more confusion, not less. Who's testing the patient-facing IVR and portal flows?
DATA REQUIREMENT

This play combines public HCAHPS data with digital expansion timeline from hospital announcements and omnichannel failure patterns from testing healthcare portal deployments.

Data on how digital expansion affects communication scores from testing 50+ hospital deployments makes this insight unique.
PQS Public Data Okay (7.9/10)

Medicare Advantage Plans Facing $8.4M Quality Bonus Risk

What's the play?

Target Medicare Advantage plans with overall star rating drops (4.0 to 3.0) putting significant quality bonuses at risk, specifically identifying call center-related categories (customer service, phone wait times) as the primary drivers of decline.

Why this works

The $8.4M financial impact is extremely compelling. Specific star categories that dropped (Customer Service to 2.5) provide concrete evidence. Question about mapping failure points is relevant but slightly accusatory by implying they might not have a plan.

Data Sources
  1. CMS Star Ratings - plan_name, star_rating, call_center_metric
  2. Medicare Advantage enrollment data for bonus payment calculations
  3. CMS quality bonus payment schedules

The message:

Subject: $8.4M at risk from your MA star rating decline Your Medicare Advantage plan's star rating dropped from 4.0 to 3.0 overall in 2025, putting $8.4M in quality bonuses at risk. The 'Customer Service' category fell to 2.5 stars - phone wait times and resolution are pulling you down. Is someone already mapping the call center failure points?
PQS Public + Internal Okay (7.8/10)

Banks with 3x Spike in IVR Complaints Before Platform Launch

What's the play?

Target banks with dramatic quarterly spikes in CFPB complaints specifically about IVR/phone system failures while approaching contact center platform launches. The 3x complaint increase creates urgency to test before migration.

Why this works

Very specific complaint category and quarterly comparison (3x increase from Q4 2023 to Q4 2024). April launch timing creates real pressure to act now. Question about regression testing is relevant but assumes they might not be testing, which can feel accusatory.

Data Sources
  1. CFPB Consumer Complaint Database - company_name, complaint_narrative mentioning IVR, date
  2. Job postings or announcements indicating platform launch timing
  3. Platform-specific failure benchmarks

The message:

Subject: 34 IVR complaints filed against your bank in Q4 Your bank had 34 CFPB complaints in Q4 2024 specifically mentioning IVR or phone system failures. That's 3x higher than Q4 2023 (11 complaints) and you're launching new contact center tech in April. Is anyone regression testing the customer journeys before go-live?
DATA REQUIREMENT

This play combines public CFPB data with inferred platform launch timing from job postings and platform-specific failure benchmarks from testing data.

Knowledge of typical failure patterns during platform migrations makes the timing insight unique.
PQS Public + Internal Okay (7.7/10)

Hospitals with 18-Point HCAHPS Communication Score Drops

What's the play?

Target hospitals showing significant year-over-year HCAHPS communication score declines (doctor communication category) while announcing telehealth expansion and automated patient communication initiatives. Indicates patient-facing systems are failing during digital transformation.

Why this works

Specific score drop (76 to 58 percentile) is alarming and shows clear trend. Year-over-year comparison demonstrates sustained decline. Connection to telehealth expansion is relevant and timely. Question implies they might not be testing, which is slightly accusatory.

Data Sources
  1. HCAHPS Hospital Patient Satisfaction Survey - communication_scores by year
  2. Press releases about telehealth or automated appointment reminder launches
  3. Patient communication channel failure patterns

The message:

Subject: Your HCAHPS communication scores dropped 18 points Your hospital's 'Communication with Doctors' HCAHPS score dropped from 76 to 58 percentile between 2023 and 2024. You're launching telehealth expansion and automated appointment reminders this quarter. Is anyone regression testing the new patient communication channels?
DATA REQUIREMENT

This play combines public HCAHPS data with telehealth expansion signals from press releases and patient communication channel failure patterns from testing similar deployments.

Knowledge of how telehealth affects communication scores from testing healthcare systems makes this connection unique.
PQS Public + Internal Okay (7.3/10)

Health Plans Launching AI Chatbots Without Public Testing Documentation

What's the play?

Target health plans that launched AI chatbots for member services (identified via website monitoring) but show no public documentation of quality baselines or hallucination testing. Creates opportunity to position proactive quality monitoring.

Why this works

Specific launch date (January 15th) shows research effort. Lack of public testing documentation is concerning and verifiable. Hallucination risk is a real blind spot for CX leaders. Question about monitoring is relevant but assumes negligence, which feels too accusatory.

Data Sources
  1. Website monitoring to detect chatbot launch dates
  2. Search for public quality testing documentation or press releases
  3. AI hallucination risk benchmarks

The message:

Subject: Your chatbot went live without baseline testing? Your health plan launched an AI chatbot for member services on January 15th according to your website. I can't find any public documentation of quality baselines or hallucination testing before launch. Who's monitoring for brand-damaging AI responses to member questions?
DATA REQUIREMENT

This play assumes ability to detect chatbot launches via website monitoring and absence of public testing documentation, plus AI hallucination risk benchmarks from testing healthcare AI deployments.

Knowledge of baseline hallucination rates by industry makes the risk assessment unique.

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 plan's call center answer time increased from 2.1 to 4.7 minutes over 3 quarters" instead of "I see you're improving customer experience," 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
CMS Medicare Advantage Call Center Monitoring plan_name, answer_time_minutes, abandonment_rate, quarter, year Medicare Advantage plans with declining call center performance
CMS Star Ratings plan_name, star_rating, call_center_metric, member_satisfaction Star rating risk and quality bonus calculations
HCAHPS Hospital Patient Satisfaction Survey facility_name, communication_scores, overall_rating, measure_value Hospitals with low communication scores
FCC Consumer Complaints Database company_name, complaint_type, issue_description, state, date Telecom carriers with service quality complaints
CFPB Consumer Complaint Database company_name, product, issue, sub_issue, complaint_narrative, date Banks with customer service and phone system complaints
LinkedIn Job Postings company_name, job_title, posted_date, description Platform migration signals, AI engineer hiring, expansion timing
Website Monitoring chatbot launch dates, portal features, analytics reports AI chatbot launches, digital expansion initiatives
Press Releases company_name, announcement_type, date, service_area Service expansion, telehealth launches, patient portal announcements