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 Circana 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 March 2024 recall traced to 3 suppliers with prior FSIS citations" (government database synthesis with dates)
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, benchmarks already pulled, patterns already identified - whether they buy or not.
These messages demonstrate both precise understanding (PQS) and immediate value delivery (PVP). Ordered by quality score.
Alert CPG brands when competitors launch similar products at their shared retailers with aggressive pricing, then provide tactical counter-recommendations based on historical promotional lift data.
This is the intelligence every brand wishes they had but can't get anywhere else. You're not just warning about a competitive threat - you're quantifying the share risk and providing the exact playbook to defend it. The specificity (competitor name, SKU count, pricing gap, predicted share loss) proves you're not guessing.
This play requires new product tracking, retailer pricing feeds, historical launch impact modeling, and shelf set placement intelligence from your platform.
This level of competitive intelligence synthesis is unique to Circana - competitors cannot replicate this play.Identify when competitors enter with significant price undercutting, quantify the share capture risk using historical price-gap models, and offer strategic pricing options.
Pricing decisions involve massive margin implications. Showing the exact dollar gap ($0.75), the timeline (April 2nd), and the modeled share loss (25-30%) gives them everything needed to make an informed decision. The offer to see "pricing strategy options I modeled" positions you as strategic advisor, not vendor.
Requires new product launch tracking, retailer pricing intelligence, historical price-gap impact modeling, and predictive share capture analysis.
This pricing intelligence and predictive modeling is proprietary to Circana's platform.Cross-reference competitive promotional calendars with recipient's planned promotions to identify timing gaps that will cause them to lose market share during critical launch windows.
Promotional planning is done quarters in advance. Surfacing a 3-week gap between their competitor's BOGO launch and their own promotional calendar gives them time to fix it. The specificity (BOGO, weeks 1-3, February 25th launch vs March 15th response) makes the vulnerability undeniable.
Requires competitive launch tracking, retailer promotional calendar partnerships, and analysis of recipient's promotional gaps.
Only Circana has visibility into both competitive launches and retailer promotional windows simultaneously.Monitor competitive product launches at shared retailers and alert brands when direct competitors enter with promotional pricing during periods when the recipient has no promotional activity scheduled.
Brands are blindsided by competitive launches all the time. Giving them advance notice (March 18th launch) with specific promotional details (15% discount, 4 weeks) and pointing out their vulnerability (no promo scheduled) creates urgency. The offer of a "counter-tactic playbook" positions you as the advisor who can help them defend.
Combines public product launch tracking, retailer promotional calendar intelligence from partnerships, and analysis of recipient's promotional schedule.
This synthesis of competitive intelligence is unique to Circana's platform coverage.Track new SKU launches against historical velocity curve benchmarks and alert brands when their launch is tracking significantly below expected trajectory, diagnosing whether the gap is demand or execution.
New product launches represent massive investment. Brand teams are desperate to know if their launch is succeeding or failing in real-time, not 6 months later. Showing exact week tracking (week 8, 340 units vs 850 expected) with urgency framing (60% below curve, missing adoption window) creates immediate need for intervention.
Combines public product launch announcements with proprietary POS velocity tracking and historical launch curve benchmarks.
Only Circana has the historical launch data to build accurate velocity curve benchmarks across categories.Compare new product distribution reach against category benchmarks and diagnose when limited distribution is capping velocity before promotional spend can be effective.
Brands often throw promotional dollars at struggling launches without realizing the root cause is distribution, not demand. Showing the exact distribution gap (2,200 stores vs 10,000 benchmark, 22% of target) and explaining why promotional spend won't work yet saves them wasted budget and redirects to the real fix.
Combines public store count data with retailer distribution tracking and historical launch success benchmarks for store expansion.
Circana's retailer partnerships provide distribution tracking that competitors cannot access.Use aggregated velocity data to show CPG brands exactly where their SKUs are underperforming category benchmarks at specific retailers, quantifying the weekly revenue loss.
Every SKU matters to brand performance. Showing exact velocity gap (127 vs 210 units/week) at a specific retailer (Walmart) with quantified dollar impact ($18K/week) makes the problem undeniable and urgent. The offer for "full velocity report across your top 6 SKUs" creates immediate value expansion opportunity.
This play requires aggregated POS velocity data across retail partners with SKU-level granularity and category benchmarks.
This is proprietary data synthesis only Circana has - the ability to benchmark a brand's velocity against category across major retailers.Alert brands when their SKU velocity drops quarter-over-quarter at specific retailers and correlate the decline with competitive SKU entries on exact dates.
Velocity declines often happen gradually and go unnoticed until quarterly reviews. Showing exact decline (1,240 to 890 units/week, 28% drop) and connecting it to a specific competitive event (2 new SKUs on January 15th) turns a vague concern into an actionable diagnosis. The offer to show "which SKUs are capturing your velocity" positions you as the investigator who's already done the work.
Requires weekly POS velocity tracking with historical comparison capability and new SKU launch monitoring at shelf-set level.
Circana's real-time velocity tracking combined with competitive SKU monitoring is proprietary to the platform.Compare current product launch performance to the same brand's previous successful launch to identify replicable issues in pricing, distribution, or promotional strategy.
Using their own past success as the benchmark is more powerful than category averages. Showing exact week-over-week comparison (410 vs 920 units/week at week 6, 55% gap) makes the underperformance undeniable. Framing it as "replicable issues" rather than random failure suggests there's a fixable pattern.
Requires tracking of the same company's historical product launches with velocity curves stored longitudinally.
Only possible with Circana's multi-year tracking of brand launch performance across products.Use shelf-level velocity data to compare recipient's SKUs against adjacent products in the same shelf position, diagnosing pricing or packaging issues causing velocity gaps.
Comparing performance to adjacent shelf neighbors (not just category average) isolates execution issues. Showing exact velocity gap (340 vs 620 units/week) and identifying likely causes (pricing premium, packaging) demonstrates diagnostic capability. The offer for "shelf performance analysis with fix recommendations" positions you as problem-solver, not data vendor.
Requires POS data with shelf-level positioning intelligence, pricing feeds, and adjacent SKU performance benchmarks.
Circana's shelf-level granularity with pricing context is proprietary competitive intelligence.Identify when multiple SKUs from the same brand are tracking 35-50% below category benchmarks at a specific retailer, suggesting systemic pricing, placement, or promotional issues.
One underperforming SKU might be a product issue. Three underperforming SKUs at the same retailer (35-50% below benchmarks) signals a systemic execution problem that's fixable in Q1. The specificity (3 SKUs, Target, same shelf position) makes the pattern undeniable. Offering "SKU breakdown with recommended fixes" positions you as the diagnostic expert.
Requires retail POS data with category benchmarking capability and shelf placement intelligence.
Circana's ability to benchmark multiple SKUs simultaneously against category at specific retailers is proprietary.Identify when new product launches peak earlier than category benchmarks and then decline, diagnosing promotional timing or distribution depth issues.
An early peak followed by decline (week 4 vs expected week 6-7) is a specific failure pattern that suggests fixable execution issues. Showing exact velocity (620 units/week) with expected timing (40% higher at week 6-7) demonstrates diagnostic capability. The offer for "diagnostic breakdown" positions you as the expert who understands what went wrong.
Combines public launch announcements with proprietary weekly velocity tracking and historical category launch curve benchmarks.
Only Circana has the historical launch data to identify early peak patterns across categories.Cross-reference FDA recall trace-back data with FSIS inspection records to identify food manufacturers whose March 2024 recalls traced to suppliers with prior non-compliance citations, revealing supplier vetting gaps.
This is forensic-level data synthesis. You're connecting their recall to suppliers who had red flags 6-18 months before the incident. The implication is clear: their supplier vetting process missed something obvious. The routing question ("Who owns supplier compliance audits now?") is easy to answer and creates urgency.
Identify food manufacturers whose current suppliers (based on recall trace-back) have ongoing FSIS citations in the past 12 months, including recent violations within 6 weeks, creating immediate compliance risk.
This isn't about a past recall - it's about ongoing risk RIGHT NOW. Showing exact location (Tennessee processor), citation count (4 times in 12 months), and recency (6 weeks ago, sanitation violations) creates urgency. The routing question ("Is your quality team aware of their recent inspection history?") implies they might not be monitoring this proactively.
Identify FDA-regulated food manufacturers whose March 2024 recalls traced to 3 suppliers, where 2 of those suppliers had prior FSIS non-compliance citations in the 18 months before the recall.
This is highly specific public data synthesis across FDA and USDA databases. You're showing exact recall date (March 2024), contaminant (listeria), supplier count (3), and compliance pattern (2 had prior citations in 18 months). The routing question is easy to answer and creates urgency about current supplier auditing processes.
Old way: Spray generic messages at job titles. Hope someone replies.
New way: Use public data and proprietary benchmarks to find companies in specific painful situations or with quantified performance gaps. Mirror that situation back to them with evidence or deliver immediate value.
Why this works: When you lead with "Your SKU #4782 at Walmart is moving 127 units/week while category average is 210 units/week" instead of "I see you're focused on retail analytics," 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 (public compliance databases, proprietary POS data, competitive launch tracking) with specific situations. Your team can replicate this approach using the data recipes in each play.
Every play traces back to verifiable data. Here are the sources used in this playbook:
| Source | Type | Key Fields | Used For |
|---|---|---|---|
| USDA FSIS Inspection Directory | Public | establishment_name, establishment_number, production_activities, inspection_status, citation_history | Identifying meat/poultry processors with compliance issues and citation patterns |
| FDA Recall Database | Public | company_name, recall_date, contaminant, supplier_trace_back, recall_scope | Connecting recalls to supplier compliance history and identifying vetting gaps |
| Circana POS Velocity Data | Private | sku_velocity_by_retailer, weekly_units, category_benchmarks, shelf_position, regional_performance | Benchmarking brand SKU performance against category at specific retailers |
| Circana Launch Tracking Database | Private | launch_date, week_by_week_velocity, distribution_reach, promotional_activity, velocity_curves | Comparing current launches to historical benchmarks and identifying early failure patterns |
| Competitive Launch Monitoring | Hybrid | competitor_product_announcements, launch_timing, promotional_tactics, retailer_calendars | Alerting brands to competitive threats with quantified share risk predictions |
| Retailer Pricing Feeds | Private | sku_pricing_by_retailer, pricing_changes, promotional_discounts, price_gaps | Identifying pricing gaps vs competitors and adjacent shelf SKUs |
| Retailer Promotional Calendars | Hybrid | promotional_windows, tactic_types, duration, retailer_specific_schedules | Cross-referencing competitive promotional timing with brand's planned activity |