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 Fignos 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 Wilmington facility got cited for inadequate design controls on 3 separate device lines in the March and September 483s" (FDA inspection 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 demonstrate such precise understanding of the prospect's current situation that they feel genuinely seen. Every claim traces to a specific government database with verifiable record numbers.
Target medical device manufacturers who received FDA warning letters citing the same violation type across multiple device lines. This pattern indicates systemic compliance process failures rather than isolated incidents.
Cross-reference FDA Warning Letters Database with GUDID to identify manufacturers with 2+ warning letters for identical violation types affecting different products.
Most compliance officers see each warning letter as an isolated product issue. By surfacing the pattern across their device portfolio, you're revealing a systemic risk they may have missed. FDA escalates to consent decrees when violations appear systemic, creating genuine urgency.
Identify manufacturers with FDA citations across multiple product lines for design control deficiencies. Surface the systemic vs. separate CAPA decision that determines escalation risk.
The question "systemic or separate?" reveals deep understanding of FDA enforcement strategy. Quality teams often default to product-specific CAPAs without recognizing when FDA expects a systemic quality system fix.
Target manufacturers with 510(k) clearances granted 10-14 months ago who are approaching their first annual post-market surveillance reporting deadline. Missing this deadline triggers automatic FDA inspection priority listing.
Many manufacturers don't realize the 12-month surveillance window exists until it's too late. By surfacing the exact device name and specific deadline, you demonstrate you're tracking their regulatory calendar better than they are.
Identify devices cleared 11-12 months ago and surface the 90-day countdown to post-market surveillance deadline with specific requirements list.
The 90-day countdown creates immediate urgency. Listing specific requirements (adverse event analysis, complaint trending, MDR summary) shows you understand exactly what's required.
Target manufacturers with design control citations across 4+ device lines in multiple inspections. Surface the SOP-level deficiency versus product-specific issues.
The insight that the SOP itself may be deficient (not just execution) is a strategic observation most quality teams miss when they're focused on individual CAPAs.
Target manufacturers with devices cleared in April 2024 approaching the April 15, 2025 surveillance deadline. Surface specific reporting requirements.
Using the exact device name and specific deadline date demonstrates you're tracking their regulatory calendar. The routing question is tactical and easy to answer.
Target manufacturers with the same specific CFR citation (21 CFR 820.30) across 5+ different device lines. Surface FDA's systemic quality system failure interpretation.
Citing the specific regulation number shows deep familiarity with FDA enforcement. The coordinated master CAPA question reveals understanding of proper remediation strategy.
Target devices cleared in February 2024 with 60-day countdown to surveillance deadline. Surface all required reporting components.
The 60-day urgency is real and actionable. The tactical question about data gathering shows you understand the actual work required, not just the regulatory deadline.
These messages provide actionable intelligence before asking for anything. The prospect can use this value today whether they respond or not.
Use aggregated audit completion time data across 200+ medtech customers to benchmark individual company performance. Surface massive efficiency gaps that justify compliance platform investment.
The prospect has no way to benchmark their audit efficiency against peers. Revealing they took 4x longer than the median is both embarrassing and immediately actionable - this becomes ammunition for internal budget justification.
Anonymized audit completion time data across 200+ medical technology customers, with median and percentile benchmarks segmented by framework type (SOC 2, HIPAA, ISO 13485) and company size.
If you have this data, this PVP becomes highly differentiated - no competitor can replicate this benchmark intelligence.Track evidence collection frequency across multiple audits to identify companies pulling the same reports 6+ times annually for different frameworks instead of centralizing evidence management.
Most compliance teams don't realize they're duplicating effort because each audit feels isolated. Revealing the 6x duplication rate versus 1.2x benchmark quantifies waste they didn't know existed.
Platform usage data showing evidence collection frequency per control across multiple audit cycles, with ability to identify redundant pulls for the same evidence across different frameworks (HIPAA, SOC 2, ISO 13485).
This requires tracking when the same evidence artifact is pulled multiple times rather than being mapped once to multiple frameworks.Calculate total manual evidence pulls across all frameworks and compare to automated collection benchmark. Offer to show exactly which 644 items could be automated.
Pure PVP - you're offering to show them their automation opportunity whether they buy or not. The 644-item breakdown is immediately actionable for building internal business case.
Detailed logging of every evidence collection activity across customer audits, with classification of manual vs. automated collection methods and ability to calculate total counts and benchmark against top-performing customers.
This is the strongest PVP in the set - it provides immediate ROI calculation whether they respond or not.Cross-reference customer device portfolios (from FDA Devices@FDA database) against new EU MDR regulatory updates. Offer pre-completed gap analysis showing which devices need additional clinical data.
You've already done the mapping work they would need to do manually. Offering the completed gap analysis before they ask demonstrates you're tracking regulatory changes on their behalf.
A maintained regulatory guidance database tracking EU MDR, FDA, and other framework updates, with ability to cross-reference customer device portfolios from public FDA databases against new requirements to identify gaps.
This combines public device data with internal regulatory intelligence to create unique value.Track FDA guidance updates and cross-reference against customer warning letter response submission dates. Identify when responses were submitted before new guidance was published, creating compliance risk.
This prevents a secondary violation. The prospect likely doesn't know new guidance was published after their response. You're catching a compliance landmine before FDA does.
A regulatory guidance change tracker that monitors FDA publications with effective dates, and ability to identify when customer warning letter responses were submitted between the violation date and new guidance publication, creating retroactive compliance gaps.
This is defensive value - you're helping them avoid escalation to consent decree.Identify manufacturers with open 483 observations that overlap with new FDA sterility guidance. Flag when CAPA plans reference outdated guidance versions.
Reinspection is coming. Showing up with a CAPA plan that references 2019 guidance when 2024 guidance exists will embarrass them in front of FDA investigators. You're preventing that.
Version control tracking for FDA guidance documents with ability to identify when customer CAPA submissions reference outdated guidance versions, cross-referenced against open 483 observations and reinspection timelines.
This prevents the prospect from walking into reinspection with outdated documentation.Calculate total audit preparation time and convert to dollar cost using industry-standard loaded rates. Compare to benchmark to show exact efficiency gap in budget terms.
CFOs care about dollars, not hours. Converting the 251-hour efficiency gap to $86K makes this an executive-level business case conversation, not just operational improvement.
Time tracking data across customer audit preparation cycles with ability to calculate total hours by framework type and benchmark against similar company size/complexity segments using anonymized data.
This translates operational pain into financial impact for budget justification.Identify when companies document the same security controls multiple times for different frameworks instead of mapping once. Offer to show exactly which 23 controls are being duplicated.
The multi-framework problem is their daily pain. Quantifying that they're documenting the same 23 controls 4 separate times makes the waste tangible and creates immediate appetite for unified compliance platforms.
Control-level documentation tracking across multiple frameworks with ability to identify when the same underlying control (e.g., access logging) is documented separately for HIPAA, SOC 2, ISO 27001, and FDA rather than mapped once.
This is pure efficiency waste visualization - helping them see where they're duplicating effort.Track when customer CAPA submissions reference outdated ISO 13485 versions. Cross-reference against warning letter responses to identify compliance gaps before reinspection.
They likely don't realize ISO published updated guidance after their response. Surfacing the 3 missing validation steps prevents embarrassment at reinspection and shows you're tracking standards updates on their behalf.
A standards version tracker monitoring ISO, FDA, and other framework updates with ability to identify when customer CAPA submissions reference outdated standard versions and map which new requirements are missing from their remediation plans.
This catches standards version gaps that could trigger reinspection failures.Calculate total compliance effort in dollar terms using loaded rates and compare to benchmark. Offer CFO-level ROI breakdown showing exactly where the $86K efficiency gap comes from.
This is executive-level insight. Converting 2,340 hours to $127K annual cost versus $41K benchmark creates immediate budget justification for compliance platform investment.
Comprehensive time tracking across all compliance activities (evidence gathering, audit prep, documentation) with ability to calculate total annual hours and convert to cost using industry-standard loaded rates for compliance professionals ($65-85/hour fully loaded), benchmarked by company size.
This is the ultimate CFO pitch - pure ROI in dollars, not operational improvements.Identify when multiple FDA guidance updates were published between the customer's 483 observation and their response submission. Offer to map which parts of their response are now outdated.
The prospect likely doesn't realize 3 guidance documents changed between their 483 and response submission. This could trigger escalation if FDA sees they're using outdated validation requirements.
A timeline tracker that monitors FDA guidance publication dates and can identify when customer 483 responses were submitted during windows where multiple guidance updates occurred, creating risk that responses reference outdated requirements.
This is defensive compliance intelligence - preventing escalation before it happens.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 Wilmington facility got cited for inadequate design controls on 3 separate device lines in the March and September 483s" instead of "I see you're hiring for compliance 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 |
|---|---|---|
| FDA Devices@FDA Database | device_name, 510(k)_number, applicant, approval_date, product_code | Tracking device approvals and surveillance deadlines |
| FDA Warning Letters Database | manufacturer_name, violation_type, date_issued, correction_requirements | Identifying compliance violations and patterns |
| Global Unique Device Identification Database (GUDID) | device_identifier, device_description, regulatory_information, manufacturer_details | Device identification and regulatory tracking |
| Internal Customer Data (Private) | audit_completion_times, evidence_collection_frequency, framework_coverage, efficiency_metrics | Benchmarking customer efficiency against peer data |
| Internal Regulatory Tracker (Private) | guidance_version_history, requirement_changes, publication_dates | Tracking regulatory guidance updates and mapping to customer submissions |