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 De Boer Tool 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 October NADCAP audit had 2 non-conformances related to coating adhesion on titanium components" (government database with specific findings)
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 combine hard data sources with specific situations to demonstrate genuine understanding. Each play provides actionable intelligence before asking for anything.
Track FAA Part 145 repair stations when they file for expanded repair scope (visible in FAA directory updates). Cross-reference with internal lead time data for custom tooling requirements to alert them to capacity constraints before they hit production delays.
You're surfacing a risk they haven't considered yet. They know they filed for expanded scope, but they don't know that custom tapered reamers have 14-22 week lead times. The specificity of the filing date and competitive intel from other shops proves you did real homework.
This play requires lead time tracking data segmented by custom tool complexity (standard vs specialty coatings vs custom geometries), combined with FAA repair scope expansion monitoring.
This synthesis of public regulatory filings with proprietary lead time intelligence is unique to your business.Proactively build standardized tool kits for common Part 145 repair scope expansions based on customer patterns. Alert facilities immediately after their scope expansion approval with ready-to-ship solutions.
You're not just identifying a problem - you've already solved it. The 6-week vs 18-week comparison is a massive competitive advantage they can't ignore. Specificity of their filing date plus immediate solution creates urgency and trust.
This play requires development of standardized tool kits based on historical customer patterns for common repair scope expansions, with inventory ready for rapid deployment.
Proactive solution development based on proprietary customer intelligence creates defensible competitive advantage.Analyze NADCAP audit findings for coating adhesion failures and correlate with internal testing data showing which drill geometries cause pre-coat burr formation. Deliver material-specific failure pattern analysis that recipients can't get elsewhere.
You're synthesizing audit data they can see (public findings) with root cause analysis they can't (your proprietary coating tests). The $113K cost per non-conformance is specific and believable. Asking if they want the drill spec comparison gives immediate actionable value.
This play requires proprietary coating performance testing database with 200+ PVD coating combinations tested across tool geometries, substrate materials, and aerospace applications.
Aggregated customer performance data showing tool life multipliers by coating type cannot be replicated by competitors without similar testing infrastructure.Pull specific audit findings from individual facilities and correlate with internal data on drill-induced coating failures. Offer drill geometry specifications that solved the problem for similar suppliers.
You researched their specific October audit findings, identified the material (Ti-6Al-4V), and synthesized pattern analysis across 31 suppliers. The offer of drill specs that worked for 3 similar suppliers provides competitive solution intelligence they can't get elsewhere.
This play requires internal data on which drill geometries prevent burr formation in Ti-6Al-4V, combined with tracking of customer audit findings and performance outcomes.
Synthesis of public audit patterns with proprietary tooling solutions creates defensible competitive intelligence.Monitor FAA directory for repair scope expansion filings and immediately reach out to alert facilities about custom tool lead time risks before they discover the constraint themselves.
The specific filing date (November 18th) demonstrates real research. Lead time concern is valid and relevant to their business. Easy routing question removes friction from response.
Use FAA repair scope expansion filings combined with industry lead time data to create urgency around custom tool ordering for new capabilities.
Specific filing date shows research effort. Lead time concern is legitimate for repair operations. The question about whether they've already ordered creates urgency without being pushy.
Track NADCAP chemical processing recertification schedules and alert facilities approaching audits when they have recent coating-related non-conformances, tying it to substrate prep tool quality issues.
Knowing their specific audit date (March 12th) demonstrates research. The non-conformance pattern is relevant industry intelligence. Easy yes/no question reduces friction.
Reference specific facility audit findings from NADCAP database and connect to industry-wide failure patterns in titanium component coating processes.
Specific to their October audit findings shows research effort. The 68% statistic provides context, though it's more generic than ideal. Question is reasonable and low-friction.
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 October NADCAP audit had 2 non-conformances related to coating adhesion on titanium components" instead of "I see you're hiring quality engineers," 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 |
|---|---|---|
| NADCAP Accreditation Database | company_name, accreditation_type, scope, audit_findings, non-conformances, certification_date | Identifying aerospace suppliers with coating quality issues and upcoming recertification |
| FAA Part 145 Repair Stations Directory | facility_name, certificate_number, repair_scope, scope_expansion_date, repair_capabilities | Tracking repair stations expanding capabilities requiring specialized tooling |
| Company Internal Tool Performance Data | tool_life_metrics, failure_rates, coating_performance, application_type, material_type | Benchmarking tool performance and identifying optimization opportunities |
| Company Internal Lead Time Data | custom_tool_complexity, lead_times_by_type, historical_order_patterns, capacity_constraints | Predicting capacity risks for facilities expanding operations |
| Company Internal Coating Testing Database | coating_combinations, tool_geometries, substrate_materials, performance_outcomes, burr_formation_data | Providing material-specific coating performance recommendations |