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 Atera 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 network scan shows 847 unpatched CVEs across 23 exposed endpoints" (external vulnerability scan with specific counts)
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 (PQS) or deliver immediate value (PVP). Every claim traces to specific data sources.
Use aggregated ticket and revenue data from the prospect's PSA tool to identify unprofitable client relationships - showing them which customers generate disproportionate support burden relative to MRR.
This is incredibly specific to THEIR business - not generic stats. The profitability insight is something they should know but probably don't track. Helps them make better pricing decisions immediately.
This play requires PSA integration providing ticket volume by client and MRR data to calculate distribution patterns.
Helps the MSP identify unprofitable client relationships and reprice services appropriately.Pull actual ticket metrics from the prospect's ConnectWise instance and compare their performance to top-quartile MSPs using Atera's platform - showing exactly where they're losing efficiency.
They pulled MY actual ConnectWise data. The 8.4 vs 5.2 comparison is specific and actionable. Low commitment ask - just want a list. This tells them something they didn't know about their own efficiency.
This play requires integration access to prospect's PSA tool (ConnectWise/Autotask) to pull actual ticket volumes and endpoint counts.
Benchmarking against aggregated customer data is proprietary - only Atera can deliver this insight.Cross-reference external vulnerability scanning of the prospect's network with HHS breach database correlation to identify highest-risk devices matching known breach patterns.
This is sophisticated analysis they couldn't do themselves. Specific to THEIR network vulnerabilities. The '8 of 12' creates urgency without being alarmist. Gives them actionable intelligence immediately.
This play requires HHS breach database pattern analysis combined with external vulnerability scanning of prospect's network to identify matching risk profiles.
If recipient is MSP, helps them protect healthcare clients; if internal IT, helps prevent breach.Pull actual ticket metrics (first-reply time, resolution time) from prospect's PSA and benchmark against aggregated customer data to show exactly where they're losing efficiency.
Specific to MY actual performance - verifiable. The comparison to top quartile is helpful context. Actionable - tells me exactly where I'm losing efficiency. Low commitment ask.
This play requires PSA integration providing ticket metrics (first-reply time, resolution time) and benchmarking against aggregated customer data.
Helps the MSP improve SLA compliance and client satisfaction scores.External vulnerability scanning of prospect's publicly visible IP ranges combined with HHS breach database correlation to identify vulnerabilities matching recent breach patterns.
Specific scan of MY network - verifiable and scary. 847 is a huge number - creates urgency. The HHS breach correlation is non-obvious synthesis. Easy routing question.
This play requires external vulnerability scanning of prospect's IP ranges combined with HHS breach database correlation analysis.
The synthesis of breach patterns with live network scanning is unique and defensible.Target skilled nursing facilities with recent CMS deficiency citations for medication errors (F755) - these typically stem from EHR documentation gaps that real-time monitoring addresses.
Specific facility name and month - they researched us. F755 citation is real and concerning for our rating. The EHR connection isn't obvious - makes me think. Easy routing question.
Combine external IP/firmware detection with HHS breach database analysis linking specific CVEs to reported incidents - alerting healthcare IT managers to actively exploited vulnerabilities on their firewalls.
Insanely specific - my exact IP and firmware version. The CVE and breach correlation is terrifying. But is this just fear-mongering? How do I verify the 12 breaches claim? The question is good but the tone feels slightly salesy.
This play requires external IP/firmware detection combined with HHS breach database analysis linking specific CVEs to reported incidents.
The synthesis of breach attribution with live network scanning creates urgency.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 network scan shows 847 unpatched CVEs" instead of "I see you're hiring for IT 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 data. Here are the sources used in this playbook:
| Source | Key Fields | Used For |
|---|---|---|
| CMS SNF Quality Reporting Program | facility_name, deficiencies, quality_measures, enforcement_actions | Skilled Nursing Facilities with medication error deficiencies |
| HHS HIPAA Breach Notification Database | covered_entity_name, breach_date, breach_description, individuals_affected | Healthcare breach patterns, CVE correlation |
| PSA Integration (ConnectWise/Autotask) | ticket_volume, resolution_time, first_reply_time, customer_mrr | MSP operational efficiency benchmarking |
| External Network Vulnerability Scanning | ip_address, cve_detections, firmware_version, exposed_endpoints | Healthcare network vulnerability identification |
| Internal Atera Benchmarks | aggregated_performance_metrics, automation_adoption_rates | MSP performance benchmarking |