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 Auctane (ShipStation Global) 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 facility at 1234 Industrial Pkwy received EPA violation #2024-XYZ on March 15th" (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 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.
Identifies Shopify merchants running Advanced or Plus plans (indicating 100+ orders/day volume) who have zero shipping automation apps installed across their entire tech stack. Detection uses DBShopi to find stores without ShipStation, Stamps, EasyPost, or competitors, then cross-validates via SellerDirectories that the same brand sells on Amazon simultaneously — proving they're managing two separate fulfillment portals with manual carrier/service selection for every single order.
The message works because it names the exact operational nightmare: copying orders across two dashboards and manually picking carriers order-by-order. This feels like surveillance (they know the channels), but the pain is undeniable and specific to the recipient's actual setup. A yes/no question about who handles labels is low-friction and moves to conversation without a sales pitch.
Targets Shopify stores running Recharge or Bold Subscriptions (subscription billing apps) without any shipping automation tool installed. DBShopi detects subscription-app presence + absence of ShipStation/competitors + revenue tier $500K-$5M. The play identifies a unique pain: on billing renewal dates, hundreds or thousands of labels must be generated in a single batch. A one-day delay or manual mistake in that batch directly triggers subscriber cancellations, making this a monthly reliability crisis.
Subscription merchants feel the renewal-date pressure acutely because they see churn spike immediately when boxes don't ship on time. The message mirrors the exact monthly nightmare: fixed date, batch generation, high cancellation risk if delayed. Asking 'Does this match what your billing-day crunch feels like?' is an empathetic open-ended question that invites the prospect to self-identify the pain rather than being told they have it. The insight that one day of slippage = subscriber loss is not obvious to businesses that haven't studied subscription economics.
Targets the same population (Shopify Advanced/Plus without automation apps, selling multi-channel) but leads with the operational cost angle: every label decision is a manual pick across separate platforms. This message emphasizes the repetition tax — not a one-time pain but hundreds of micro-decisions daily that automation could eliminate in a single rule.
Framing the pain as 'one-click vs. manual every time' gives the prospect a visceral sense of wasted labor. The offer of '3 automation rules' is concrete and suggests that the solution isn't complex — just unknown. It's answer-with-one-word low friction while positioning Auctane as the expert who already knows the right rules.
Same segment (Recharge/Bold + no automation) but leads with the churn consequence. This version emphasizes that delaying a batch by even one day has immediate business consequences — not just operational friction but revenue impact. It positions automation as a reliability insurance policy, not a time-saver.
Subscription merchants prioritize reliability over efficiency because a one-time fulfillment failure permanently loses that customer. The message frames delay as existential ('fastest way subscription customers cancel') rather than annoying. The offered solution ('batch-print rule setup that handles renewal day automatically') is concrete and positions the next step as configuration, not selling. One-word answerability and direct connection to a real KPI (churn) makes this high-friction-free.
These messages provide actionable intelligence before asking for anything. The prospect can use this value today whether they respond or not.
Uses Auctane's proprietary 3B+ annual shipment dataset to compute percentile cost benchmarks per (ZIP-origin, weight-band, product-category, service-level) cell. Matches recipient's DBShopi product category and estimated origin ZIP against internal benchmarks, then surfaces a recipient-specific overpayment insight: 'You're paying $9.80 where the median from your ZIP is $6.40 for apparel under-1lb.' This is competitive-proof because no third party has visibility into Auctane's aggregated shipment cost data across 50+ merchants per benchmark cell.
The message lands with shock-and-specificity: exact ZIP, exact dollar figures, exact product category. It feels like the sender has inside knowledge of the recipient's shipping behavior — which they do, but only their aggregate behavior, not proprietary data. The 53% overpayment number is concrete enough to verify independently, making it feel credible rather than a sales exaggeration. The ask ('want the breakdown for your other routes?') is a natural next step that requires zero effort to say yes to.
Aggregated shipment-level cost data segmented by ZIP origin, weight band, service level, and product category, with minimum 50 merchants per benchmark cell to ensure statistical validity.
This insight is defensible and competitors cannot reproduce it: no third-party vendor has visibility into Auctane's 3B+ annual shipments to compute ZIP-specific, category-specific carrier cost percentiles. The message doesn't expose internal customer data — only anonymized aggregate benchmarks — but it proves Auctane's scale and data advantage, making the ROI of switching platforms undeniable.Variant of the ZIP-benchmark play using percentile framing instead of median-only. Auctane computes 25th/75th/median cost ranges per (ZIP, weight, category, service) and flags recipients above the 75th percentile. This version emphasizes the gap to the top quartile performers, making the overpayment feel more severe and the fix more obvious. The per-box dollar figure ($3.40) is grounded in real cost difference, not a percentage.
Percentile framing adds rigor and makes the data feel non-arbitrary. 'You sit above every percentile we track' is stronger than 'above median' because it eliminates doubt — you're not in the normal range at all. The specific per-box savings ($3.40 × annual volume) becomes a concrete annual ROI number the merchant can calculate immediately. Asking for 'the exact USPS service and label setup' positions the next step as implementation, not a sales call.
Percentile cost ranges (25th/75th/median) per ZIP-origin/weight-band/product-category/service-level cell from internal shipment dataset, minimum 50 merchants per cell.
Percentile framing is even more defensible than median-only because it demonstrates statistical rigor and proves scale. No competitor can cite 'our 75th percentile for ZIP 75226 apparel is $7.10' without access to billions of transaction-level cost data.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 Dallas facility has 3 open OSHA violations from March" instead of "I see you're hiring for safety 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 |
|---|---|---|
| DBShopi — Shopify Stores List with Contact Data | store_name, domain, contact_email, shopify_plan, installed_apps, estimated_monthly_revenue, product_category | Identifying Shopify merchants running Advanced/Plus plans without shipping automation apps, and subscription box stores with Recharge/Bold installed but no fulfillment integration |
| SellerDirectories — Amazon and Shopify Brands Database | brand_name, marketplace, contact_info, product_category, estimated_monthly_revenue | Cross-validating Shopify sellers as multi-channel merchants also selling on Amazon, confirming high-volume complexity |
| Openmart E-commerce Stores Database | business_name, owner_name, owner_email, industry_category, estimated_annual_revenue, platform | Retrieving founder/owner-level contact data for subscription box and e-commerce merchants identified via DBShopi |