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 ShelfWise 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 September FDA citations at CVS Philadelphia stores show planogram violations with October 18 corrective action deadline" (government database with record number)
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 are ordered by quality score (highest first). Each demonstrates either precise situation mirroring (PQS) or delivers immediate actionable value (PVP).
Monitor public press releases announcing new product launches, then cross-reference against internal store execution performance data to identify the 120 highest-risk locations where new SKU placement historically fails. Build a complete 90-day pre-launch audit schedule prioritizing stores with 40% miss rates vs 12% chain average.
You're solving a problem the prospect didn't even know they had yet. The specificity of knowing which exact stores underperform on new SKU launches - before the launch happens - demonstrates proprietary intelligence they cannot get elsewhere. This is proactive consultative value, not reactive sales pitching.
This play requires tracking new SKU placement success rates by individual store location across retail chains, showing which stores chronically underperform on launch execution.
This synthesis of public launch data + proprietary store performance patterns is unique to ShelfWise.Cross-reference public NDC directory marketing_start_date with internal planogram compliance tracking to identify stores where new SKUs launched but never appeared on shelves. Calculate revenue impact using category velocity data. Deliver complete store list with district manager contacts.
Quantifying lost revenue from execution failures transforms this from "we think there's a problem" to "here's exactly how much money you're leaving on the table." The specificity of store count, revenue projection, and contact list makes this immediately actionable. This is consultative intelligence, not a sales pitch.
This play requires tracking shelf placement timing across retail chains and category-based revenue projection models to calculate lost revenue from missing SKUs.
Combines public NDC launch data with proprietary execution tracking - a synthesis only ShelfWise can deliver.Track new product category entries via NDC directory, then cross-reference against internal planogram tracking to identify stores where client's new SKUs are completely absent despite category resets completing. Show which competitor gained shelf facings during the same reset period. Deliver store list with planogram manager contacts.
Losing shelf space to a competitor during a portfolio expansion is painful and embarrassing. Quantifying the store count (340) and showing competitor gained facings during the same reset creates urgency - this isn't a delay, it's a competitive loss. The offer of planogram manager contacts makes this immediately actionable.
This play requires tracking planogram changes and competitor shelf share movements during category resets by store location.
Competitive intelligence synthesis only ShelfWise can provide through systematic shelf audits.Track new product launches via NDC directory marketing_start_date, then compare recipient's shelf compliance metrics against aggregated category benchmarks from internal ShelfWise data. Show them their percentile ranking vs peer brands in same category and regional market. Identify specific underperforming stores.
Competitive benchmarking is always valuable, but category-specific benchmarks during portfolio expansion create urgency. Showing them they're at 45th percentile when category median is 72nd percentile - with the exact underperforming store list - demonstrates proprietary intelligence they cannot get from any competitor.
This play requires aggregated shelf compliance metrics by OTC product category and regional market, with percentile benchmarks across 20+ brands in same category.
Proprietary benchmark data only ShelfWise possesses through systematic cross-brand audits.Cross-reference openFDA Drug Enforcement Reports API showing specific store locations with enforcement actions against internal audit frequency data. Compare audit visit patterns at cited stores vs compliant locations. Show correlation between low audit frequency and citation risk. Deliver store-level audit frequency recommendations.
This isn't just mirroring the problem (FDA citations) - it's diagnosing root cause through data analysis. Showing that cited stores averaged 4.2 audits/year vs 8.7 at compliant ones, with quantified prevention opportunity (70%), transforms this into strategic consultation. You're helping them prevent future enforcement actions, not just react to past ones.
This play requires audit visit frequency patterns by store location and correlation analysis between audit frequency and compliance outcomes.
Root cause analysis synthesis combining public enforcement data with proprietary audit patterns.Monitor NDC directory for new product marketing_start_date, then cross-reference against internal planogram compliance data showing which stores haven't completed shelf resets 30 days post-launch. Identify stores with historical slow execution patterns (45-60 days longer than chain average). Deliver complete store list with compliance manager contacts.
The specificity of knowing exact product name, launch date, store count, and regional breakdown demonstrates real research. Historical execution pattern data (47 stores taking 45-60 days longer) proves this isn't speculation - it's based on proprietary performance tracking. The offer of compliance manager contacts makes this immediately actionable.
This play requires planogram compliance tracking data from existing retail customers showing shelf reset timing patterns and historical store-level execution performance.
Combines public launch data with proprietary execution intelligence only ShelfWise possesses.Cross-reference openFDA Drug Enforcement Reports API showing specific stores with violations against inferred field team coverage patterns from audit frequency data. Identify stores falling outside active rep territories. Show structural gap causing compliance failures. Offer territory coverage optimization recommendations.
This isn't just listing FDA citations - it's diagnosing WHY the citations happened through territory analysis. Showing that 8 of 11 cited stores fall outside active coverage zones reveals a structural problem the prospect didn't know existed. The offer of territory adjustment recommendations positions this as strategic consultation, not sales outreach.
This play requires field team coverage patterns inferred from audit frequency data, showing which stores receive regular visits vs those outside active territories.
Territory analysis synthesis only possible through ShelfWise's systematic audit tracking.Query openFDA Drug Enforcement Reports API for recent warning letters and enforcement actions against OTC drug manufacturers. Filter for planogram violations and non-compliant shelf placement. Extract specific retail chain names, city locations, and store counts from enforcement records. Pull exact citation dates and corrective action deadlines (typically 30 days from warning letter date).
The specificity of city-level store locations (Philadelphia 3 stores, Boston 2 stores, Newark 1 store) combined with exact deadline dates creates verifiable urgency. This isn't generic FUD about FDA compliance - it's mirroring their exact regulatory pressure with documentary evidence. The simple yes/no question makes it easy to respond while acknowledging the situation.
Monitor press releases and NDC directory for new product launches with specific dates, then cross-reference against internal historical shelf reset timing data by retail chain. Identify launches at chains with slow execution (50+ days to complete resets). Calculate execution window vs seasonal sales peak to show timing risk. Question prompts field team pre-positioning.
Linking launch timing to seasonal sales peaks creates urgency - the 14-day execution window during allergy season is tight. Historical execution data (50+ days post-launch for these chains) proves this isn't speculation. The question about field team pre-positioning suggests a solution without pitching, making the recipient think "can we actually do that?"
This play requires historical shelf reset timing patterns by retail chain for category launches, showing median days to complete shelf placement after launch date.
Timing risk analysis combining public launch data with proprietary execution patterns.Track new product launches via NDC directory marketing_start_date showing portfolio expansion into new categories. Cross-reference against internal planogram compliance data showing stores where client's new SKUs are absent despite category resets completing chain-wide. Use Kroger's public reset completion rate to prove SKUs were excluded from resets, not just delayed.
The distinction between delay vs exclusion is critical - 85% reset completion chain-wide proves Kroger finished category resets, yet your SKUs are missing from 190 stores. This isn't a field execution problem, it's a merchandising relationship problem. The routing question targets the right person (merchandising contact) to fix it.
This play requires category reset completion verification and SKU-level presence tracking by store location to distinguish between execution delays and merchandising exclusions.
Reset completion analysis only possible through ShelfWise's systematic planogram tracking.Track new product category entries via NDC directory showing portfolio expansion. Cross-reference against internal shelf share tracking data showing loss of shelf facings to specific competitor during same quarter. Identify stores where new SKUs are absent from planograms. Question routing to person responsible for shelf execution.
Linking portfolio expansion to competitor shelf share gain creates competitive urgency - they expanded into pain relief but lost ground to Bayer during the same period. Specific percentages (34% to 26%, Bayer gained 6 points) and store count (180+ missing new product) make the problem concrete. Easy routing question makes response simple.
This play requires shelf share tracking by category across retail chains, showing changes in facings over time and competitor movements during same period.
Competitive shelf intelligence only ShelfWise can provide through systematic audits.Query openFDA Drug Enforcement Reports API for recent enforcement actions (recalls, warning letters) against OTC drug manufacturers. Filter for shelf placement and planogram compliance violations. Extract manufacturer name, retail chains mentioned in violation, and approximate timeframe. Reference 30-day corrective action deadlines typical of FDA warning letters.
FDA enforcement citations create real urgency with hard deadlines. Mentioning specific retail accounts (Walgreens, CVS, Rite Aid) and the 30-day response window demonstrates research and understanding of regulatory pressure. The routing question is easy to answer and helps reach the right person responsible for corrective actions.
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 September FDA citations at 6 CVS locations have October 18 corrective action deadlines" 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 or proprietary ShelfWise intelligence. Here are the sources used in this playbook:
| Source | Key Fields | Used For |
|---|---|---|
| openFDA National Drug Code (NDC) Directory API | manufacturer_name, product_name, ndc_code, active_ingredient, marketing_start_date, marketing_end_date | Identifying OTC manufacturers and tracking new product launches |
| openFDA Drug Enforcement Reports API | manufacturer_name, product_name, recall_reason, recall_date, distribution_pattern, status | Finding manufacturers with recent FDA enforcement actions and violations |
| ShelfWise Internal Audit Data | store_location, planogram_compliance_status, shelf_reset_timing, audit_frequency, SKU_presence | Tracking shelf execution performance, identifying underperforming stores, measuring compliance patterns |
| ShelfWise Category Benchmarks | category, regional_market, percentile_compliance, shelf_share_trends, out_of_stock_rates | Providing competitive benchmarking data showing how brands perform vs category peers |
| Company Press Releases | product_launch_date, retail_partners, expansion_announcements | Monitoring new product launches and identifying timing risks |