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 Rocket Lab 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 FCC license expires March 14, 2025 - 4 months out" (government database with exact date)
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.
Company: Rocket Lab
Core Problem: Small satellite operators and space missions lack affordable, responsive access to orbit. Companies need dedicated launch vehicles with schedule control and flexible payload options that traditional launch providers cannot economically offer.
Target ICP: Commercial satellite constellation operators, government defense agencies, Earth imaging providers, IoT satellite operators, and scientific research institutions requiring dedicated small satellite launch services with mission-critical timelines.
Primary Buyer Persona: Satellite Program Manager / Constellation Deployment Lead responsible for sourcing launch vehicles, managing deployment timelines, ensuring government compliance, and coordinating mission-critical launches with tight fiscal year or program deadlines.
These plays are ordered by quality score (highest first). The best plays combine precise targeting with actionable value, regardless of data source type.
Defense contractors awarded NRO satellite contracts with September 30 fiscal year deadlines are operating under extreme timeline pressure. Cross-reference public contract awards with internal manifest data to offer specific launch dates that preserve schedule margin for government deadline compliance.
Specific dates and slots are immediately actionable. You're showing deep knowledge of their orbit requirements and security needs while providing the September 5 backup slot that's perfect margin before their deadline. This helps them TODAY whether they buy or not - they know their options.
This play requires internal launch manifest data showing available slots with orbit specifications and security clearance capabilities, cross-referenced with public procurement documents showing the contract's technical requirements.
This synthesis of internal availability with public contract requirements is unique to Rocket Lab's operational data.FCC-licensed constellation operators with government contracts face dual compliance deadlines that create scheduling conflicts. Map their DoD contract delivery requirements against their FCC filing commitments to identify operators at risk of violating either deadline, then offer launch slots that cover both obligations.
They mapped your government contract against your FCC obligations - this is genuinely valuable synthesis. The dual-deadline insight identifies a real strategic problem you're managing right now. It's immediately actionable - you can say yes and get launch slots that solve both compliance risks.
This play requires access to government contract award databases cross-referenced with FCC orbital debris mitigation filings, combined with internal knowledge of typical government launch timing patterns from 30+ executed missions.
The synthesis of dual compliance deadlines with launch scheduling is unique to operators with government mission execution data.Space Development Agency Tranche 1 contractors have September 2025 delivery deadlines for mesh network constellation satellites. Match internal launch manifest availability with SDA technical orbit requirements from public defense procurement documents to offer specific dates with security protocol support.
Demonstrates specific SDA program knowledge and understanding of mesh network orbit requirements. Three concrete dates with the last one providing good backup margin before the deadline. Security and government integration support shows deep understanding of defense contracting needs. Mission profiles are immediately useful for planning.
This play requires internal launch manifest data with available slots and security clearance capabilities, cross-referenced with SDA program technical requirements from public defense procurement documents.
Matching internal availability with specific SDA technical requirements requires operational knowledge of mesh network orbit specifications.Commercial operators planning 5+ satellite constellation deployments can unlock significant volume pricing. Cross-reference their public FCC filings showing planned launch schedules with internal multi-launch pricing tiers to provide specific dollar savings calculations and commitment deadlines.
Specific dollar savings you can take to your CFO immediately. The December 15 deadline creates urgency but feels reasonable. Concrete pricing comparison means you can verify value instantly. Actionable - contract template means you can move fast.
This play requires internal volume pricing tiers and promotional deadline dates, combined with public FCC filing data showing the customer's planned launch schedule.
Specific multi-launch pricing structures are proprietary to Rocket Lab's commercial terms.NASA-funded university CubeSat programs with May 2025 launch windows need delivery 90 days prior. Match internal mission planning data for April dates with NASA CSLI database showing university mission requirements to provide complete integration packages with backup windows.
You know their exact mission (specific form factor and orbit). Integration timeline and NASA coordination process is genuinely helpful for university programs. Backup windows show understanding of research mission risk management. The package is valuable whether they commit to this launch or not.
This play requires internal mission planning data for specific launch dates with payload specifications, combined with NASA CSLI database showing university CubeSat mission requirements and ELaNa program procedures.
Mission integration packages combining internal technical specs with NASA coordination processes are unique to launch providers with university mission experience.NRO satellite contractors with September 2025 delivery requirements need comprehensive launch window analysis. Map 6 available launch windows from internal manifest against NRO security and orbit requirements to provide comparison sheets with integration timelines and backup dates.
They mapped your specific requirements against actual availability. 6 options with details is immediately useful planning data. Security clearance inclusion shows understanding of government work. Low commitment to get valuable comparison data.
This play requires internal launch manifest showing available windows with technical specifications, cross-referenced with government contract requirements from public procurement databases.
Mapping internal availability against classified contract requirements requires operational experience with NRO missions.NASA-funded CubeSat programs with tight May 2025 windows need April launch opportunities to preserve schedule margin. Match their exact CubeSat specifications from NASA database with internal mission profiles to offer mission kits showing integration timelines and ELaNa coordination.
They know your exact CubeSat specs and orbit requirements. The April 18 date provides real schedule margin you need. Mission kit offer is immediately useful whether you commit or not. Very low barrier to say yes.
This play requires internal mission manifest data with payload capacity and orbit parameters, cross-referenced with NASA CSLI CubeSat database showing university mission requirements.
Mission matching requires operational knowledge of CubeSat integration requirements and NASA coordination processes.FCC-licensed constellation operators approaching March 2025 renewal face complex documentation requirements. Pull their specific FCC filing requirements and create compliance checklist showing current status for each of 7 filing requirements with timeline to renewal.
Specific renewal date and they've done prep work for you. 7 requirements with compliance status is genuinely helpful. This saves you time whether you buy or not. Very easy yes to get useful information.
This play requires access to FCC renewal requirements framework combined with the company's specific license filing to assess current compliance status against each requirement.
Compliance assessment requires expertise in FCC orbital debris mitigation requirements and constellation deployment documentation standards.Constellation operators planning 5+ launches face decisions between dedicated missions and rideshare options. Build custom cost comparison models showing schedule flexibility, orbit precision, and total program costs for both approaches based on their specific deployment timeline.
They built a custom analysis for your specific situation. Dedicated vs rideshare is exactly the trade-off you're evaluating. Schedule and precision factors show understanding of your decision criteria. Useful analysis whether you buy or not.
This play requires internal pricing models for multi-launch contracts and rideshare options, combined with public data about the customer's planned deployment schedule and orbit requirements.
Cost modeling requires proprietary knowledge of multi-launch pricing structures and rideshare market economics.Defense contractors awarded NRO satellite development contracts with September 30, 2025 delivery milestones are operating under extreme fiscal year deadline pressure. These contractors have 8 months to complete integration, testing, and launch with zero schedule margin for delays.
Specific contract number and date show real research. The fiscal year deadline pressure is exactly what government contractors are dealing with. The 8-month timeline analysis is helpful. Easy question to route internally.
Space Development Agency contractors with Tranche 1 satellite delivery requirements in Q3 2025 face government fiscal year deadline pressure. Launch delays push delivery into next fiscal year funding cycle, creating budget complications and contract performance risk.
Specific SDA contract number and tranche show very detailed research. The fiscal year funding risk is a real concern for government contracts. Q3 window specificity is helpful. Straightforward routing question.
FCC-licensed constellation operators with orbital debris mitigation licenses expiring March 14, 2025 are 4 months from renewal deadline. FCC renewal requires demonstrating active constellation deployment progress against original filing timeline, creating compliance pressure.
Specific date creates real urgency - you can verify this. The FCC deployment progress requirement is a real compliance risk that needs to be addressed. Easy routing question. This is genuinely helpful even if you don't buy - reminds you of a critical deadline.
This play assumes access to FCC license database with expiration dates cross-referenced with the company's constellation deployment timeline from their original application.
Mapping license renewal requirements against deployment commitments requires expertise in FCC orbital debris mitigation compliance.FCC-licensed operators with orbital debris plans committing to 12 satellites by October 15, 2025 who've launched only 4 satellites to date face extreme deployment cadence pressure. 8 remaining satellites in 9 months requires 1 launch every 6 weeks to maintain license compliance.
Specific numbers from their FCC filing - they did the math. The 6-week cadence insight is a helpful reality check. This highlights a real scheduling challenge they're managing. Easy question about internal planning status.
FCC-licensed operators with deployment commitments for 12 satellites by October 2025 who've completed 4 launches face scheduling pressure with 8 satellites remaining in 9 months. This requires 45-day launch cadence with no margin for delays or payload issues.
Accurate math from their FCC filing and current deployment status. The 45-day cadence with no margin is a real wake-up call. Highlights scheduling risk they need to address. Direct question about contracting status.
Constellation operators with FCC applications showing 5 planned launches between January 2025 and June 2026 (18-month deployment window) qualify for multi-launch contract pricing with significant cost reduction per launch versus individual mission contracts.
Specific number and timeline from their actual filing. The 23% savings number is compelling and concrete. They're offering you a volume discount you might not know exists. Easy yes/no question.
NASA ELaNa CubeSat missions with May 2025 launch windows must deliver 90 days before launch date per NASA requirements. This creates February 1, 2025 delivery deadline - only 2.5 months away - requiring urgent integration and testing schedule coordination.
Specific program and accurate NASA delivery requirement. The February 1 deadline calculation is helpful. 2.5 months creates appropriate urgency. Straightforward question about schedule status.
NASA CSLI-awarded CubeSat projects with designated launch windows May 1-31, 2025 per the ELaNa manifest have only 5 months to complete final integration and delivery to launch provider. Timeline pressure is significant for university programs.
Specific program name and launch window - they know your exact mission. The 5-month timeline pressure is real. ELaNa manifest reference shows deep knowledge of NASA CubeSat process. Simple routing question.
University CubeSats manifested on NASA ELaNa program for Q2 2025 deployment window per CSLI database must deliver 90 days before launch. NASA requires January 2025 delivery latest for May window, creating urgent deadline for university programs.
Specific program reference and database citation. The 90-day delivery requirement is accurate and important. January deadline creates clear urgency. Simple routing question.
Constellation deployment plans showing 4 launches scheduled between March 2025 and December 2025 (10-month window) qualify for block booking dedicated mission pricing versus rideshare rates. Operators should evaluate dedicated vs rideshare economics for deployment timeline.
They know your launch count and timeline. The dedicated vs rideshare comparison is a real decision you're making. Block booking benefit is clear. Good question about internal evaluation process.
This play assumes access to FCC filings or public announcements about constellation deployment schedules, combined with internal pricing data distinguishing dedicated mission vs rideshare economics.
Block pricing structures and rideshare rate comparisons require proprietary knowledge of launch market economics.Planned constellation expansion showing 5 launches scheduled from January 2025 through June 2026 (18-month deployment cycle) typically unlocks significant volume discounts versus individual mission contracts. Operators should analyze multi-launch commitment savings opportunity.
Accurate count and timeline from their planning. The 20-25% savings range is compelling. Multi-launch commitment trade-off is something they should evaluate. Good question about internal analysis.
This play assumes access to public constellation deployment announcements or FCC filings, combined with internal volume pricing tier knowledge.
Volume pricing structures are proprietary to Rocket Lab's commercial contract terms.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 FCC license expires March 14, 2025 - 4 months out" instead of "I see you're hiring for mission operations 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 public data. Here are the sources used in this playbook:
| Source | Key Fields | Used For |
|---|---|---|
| FCC Approved Space Station List | space_station_name, operator_name, orbital_location, call_sign, frequencies, launch_date | Federal Communications Commission Licensed Satellite Operators |
| FCC License View API | licensee_name, call_sign, license_status, service_type, frequency_ranges, license_expiration | FCC-Licensed Constellation Operators approaching renewal |
| NOAA Commercial Remote Sensing Regulatory Affairs (CRSRA) | operator_name, license_tier, satellite_resolution, data_distribution_restrictions, license_status | NOAA-Licensed Remote Sensing Satellite Operators |
| SAM.gov Contract Data Portal | contractor_name, contract_value, contract_description, naics_code, product_service_code, period_of_performance, agency | Department of Defense Space Acquisition Programs, NASA Mission Directorates |
| NASA Procurement Data View (NPDV) | contract_number, contractor_name, contract_description, contract_value, period_of_performance, contracting_office | NASA Mission Directorates with Launch Requirements, NASA-Funded University CubeSat Programs |
| Nanosatellite & CubeSat Database | mission_name, operator_organization, country_of_origin, satellite_mass, form_factor, launch_date, mission_objectives, status | NASA-Funded University CubeSat Programs, Constellation Deployment Tracking |
| FCC License Search System (ULS) | call_sign, licensee_name, service_code, radio_service, license_status, license_expiration, frequency_ranges | Federal Communications Commission Licensed Satellite Operators |
| Internal Launch Manifest Data | available_slots, orbit_parameters, security_clearance_capacity, payload_specifications | HYBRID plays showing available launch windows matched to customer requirements |
| Internal Volume Pricing Tiers | multi_launch_discounts, commitment_terms, dedicated_vs_rideshare_economics | HYBRID plays showing volume pricing opportunities for multi-launch commitments |
| Internal Government Mission Execution Data | mission_timing_patterns, deployment_windows, fiscal_year_concentration | HYBRID plays showing government contract execution timelines and launch scheduling patterns |