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 Shop By Payment 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 Fort Worth location averages 4.2 hours per deal vs 2.8 hours for comparable Texas BHPH dealers" (platform data with peer benchmarks)
PQS (Pain-Qualified Segment): Reflect their exact situation with such specificity they think "how did you know?" Use verifiable data with exact numbers, locations, and peer comparisons.
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 precise understanding of the prospect's situation and deliver actionable intelligence. Ordered by quality score (highest first).
Use aggregated shopping session data from your platform to show dealerships exactly which payment ranges their customers are filtering for, then identify which vehicles in their inventory could hit those payment targets with term adjustments.
This play reveals hidden conversion opportunities by matching existing inventory to actual customer demand patterns.
You're delivering an immediate action list (40 specific vehicles) based on their own customers' behavior. The specificity of the payment target ($289), shopper percentage (68%), and exact vehicle count creates instant credibility.
The dealer can implement this today without buying anything - just adjust term structure on identified VINs.
This play requires aggregated shopping session data showing payment filter preferences by geography, plus inventory payment modeling at different term lengths.
This is proprietary data only you have - competitors cannot replicate this play.Analyze actual shopping sessions on the dealer's website to identify payment filter preferences, then show them the inventory gap between what customers want and what's available at standard terms.
The play provides both the problem diagnosis (only 12 vehicles match the 68% demand) and the solution (specific VINs that would match with term adjustments).
This is their own website data reflected back to them with surgical precision. The session count (847), filter percentage (68%), and inventory mismatch (12 vehicles) proves you've done deep analysis they likely haven't.
The VIN list offer is concrete and immediately actionable - they can validate your analysis and implement the fix within hours.
This play requires shopping session tracking with payment filter preferences captured across dealer websites, plus inventory analysis capabilities.
This is proprietary data only you have - competitors cannot replicate this play.Track deal completion times for dealers using your platform, segment by dealer type (BHPH, franchise, size, geography), then identify where specific dealers are losing customers in their process.
This play pinpoints the exact stage where deals fall apart (F&I presentation) and quantifies the abandonment rate (23%).
You're revealing a hidden revenue leak with precise metrics. The 23% abandonment rate at a specific process stage is data they likely don't track themselves.
The peer comparison (15 similar dealers, 2.8 hour average) provides context that makes their 4.2 hours feel urgent. The stage-by-stage breakdown offer is exactly what they need to fix the problem.
This play requires deal flow tracking with stage-level timing and abandonment data, plus peer segmentation by dealer characteristics (type, size, geography).
Combined with state licensing data for dealer verification. This synthesis is unique to your platform.Cross-reference internal approval/decline data from your lender network with public delinquency statistics by geography to identify risk concentration patterns that dealers can't see in their own data.
This play reveals where dealers are approving customers in high-delinquency ZIP codes, creating portfolio risk exposure.
You're connecting two data points the dealer tracks separately (their approval behavior + regional delinquency trends) to surface hidden risk they would have missed.
The ZIP-level analysis offer is highly actionable - they can adjust underwriting criteria by geography or avoid specific territories to protect portfolio performance.
This play requires approval/decline tracking by geography and credit tier from your lender network, combined with CFPB public delinquency statistics.
This synthesis of internal approval patterns with public risk data is unique to your platform.Track payment filter behavior across dealer websites to identify shopper preferences by region and vehicle type, then model which existing inventory vehicles could match those preferences with term structure changes.
This play quantifies the exact conversion gap (68% demand vs 12 vehicles available) and provides a specific solution (40 vehicles that could fit with 78-month terms).
The specificity is overwhelming - 68% shopper preference, 12 current matches, 340-unit total inventory, 40 vehicles identified for term adjustment.
Every number is verifiable from their own data, and the solution (extend to 78 months) is immediately implementable without new inventory acquisition.
This play requires payment filter tracking across dealer websites with inventory matching capabilities and term structure modeling.
This is proprietary data only you have - competitors cannot replicate this play.Track deal completion times from test drive to signature across dealers using your platform, segment by true peer characteristics (dealer type, size, geography), then identify process bottlenecks for specific dealers.
This play provides peer benchmarking that's actually relevant (15 comparable Texas BHPH dealers) rather than generic averages.
The peer comparison is genuinely useful - not all dealers, but 15 comparable BHPH dealers in Texas. The 4.2 vs 2.8 hour differential is specific and actionable.
The 23% abandonment rate tied to a specific stage (F&I presentation) gives them a concrete target for improvement. The time breakdown offer is exactly what they need to diagnose the problem.
This play requires comprehensive deal flow timing data from quote through completion, with peer segmentation by dealer characteristics.
Combined with state licensing data for accurate peer matching. This synthesis is unique to your platform.Compare dealer approval rates by credit tier against regional delinquency patterns to identify risk mismatches - dealers approving customers at higher rates in geographies with elevated delinquency.
This play reveals a counterintuitive opportunity or hidden risk depending on the dealer's situation.
You're showing them a pattern they can't see in their own data - their approval rate differential (34 points above average) combined with geographic delinquency context (18.2% in Harris County).
The delinquency heat map offer provides immediate risk management value they can use to adjust underwriting criteria by territory.
This play requires approval rate tracking by credit tier and geography from dealers using your platform, combined with CFPB public delinquency data.
This synthesis of internal approval patterns with public risk metrics is unique to your platform.Track payment filter behavior across dealer websites to quantify shopper demand patterns, then mirror that data back to dealers with the inventory gap clearly identified.
This PQS variant focuses on reflection rather than solution delivery - showing the dealer their own data in a way that reveals the problem.
The session count (847) and filter percentage (68%) demonstrate you have visibility into their website behavior. The inventory gap (12 vehicles vs 68% demand) is a clear problem statement.
The routing question is straightforward and non-threatening - just asking if the inventory manager has this visibility, which they likely don't.
This play requires shopping session tracking with payment filter preference capture across dealer websites.
This is proprietary data only you have - competitors cannot replicate this play.Compare dealer deal completion times against peer benchmarks, identify the specific process stage where delays occur, then mirror that data back with a simple routing question.
This PQS variant focuses on reflection and awareness-building rather than delivering the full diagnostic.
The peer comparison (2.8 hours for comparable Texas BHPH dealers) provides useful context. The 84 extra minutes quantifies waste, and identifying the F&I presentation stage adds urgency.
The routing question is non-threatening and likely to surface an internal communication gap - the F&I manager probably doesn't know about the 2.8-hour peer benchmark.
This play requires deal completion metrics tracked across platform users, segmented by dealer type for accurate peer benchmarking.
Combined with state licensing data for dealer classification. This synthesis is unique to your platform.Mirror back the dealer's approval rate differential compared to market average, combined with regional delinquency context, to surface potential risk exposure they may not be monitoring.
This PQS variant asks a routing question to determine who owns the risk monitoring function.
The approval differential (34 percentage points) and delinquency statistic (18.2% in Q4) are both specific and verifiable. The question about monitoring correlation is reasonable and non-threatening.
Slight risk of sounding accusatory, but the data specificity should overcome that concern.
This play requires approval rate tracking by credit tier from dealers using your platform, combined with CFPB public delinquency data by geography.
This synthesis of internal approval metrics with public risk data is unique to your platform.Reflect the dealer's approval rate performance against regional benchmarks, paired with delinquency context, to surface risk patterns they may not be tracking.
This PQS variant focuses on mirroring the situation with a simple routing question about F&I team awareness.
The approval differential (34 points) and delinquency statistic (18.2%) provide specific context. The routing question about F&I team tracking is straightforward.
Slightly weaker than other variants due to the more generic question structure, but still demonstrates data visibility the dealer likely lacks.
This play requires approval rate data from dealers using your platform, combined with CFPB regional delinquency statistics.
This synthesis of internal approval patterns with public risk metrics is unique to your platform.Mirror the dealer's approval rate differential against market benchmarks, combined with regional delinquency context, to surface potential risk exposure.
This PQS variant asks who owns the monitoring function to determine organizational responsibility.
The specific approval differential (34 percentage points) and delinquency statistic (18.2%) demonstrate data visibility. The question about monitoring correlation is organizational and non-threatening.
Slight risk of sounding accusatory with the "who's monitoring" framing, but the data specificity should overcome that.
This play requires approval rate tracking by credit tier from your platform, combined with CFPB public delinquency statistics.
This synthesis of internal approval data with public risk metrics is unique to your platform.Old way: Spray generic messages at job titles. Hope someone replies.
New way: Use platform data to find dealerships with specific conversion gaps or process bottlenecks. Then mirror that situation back to them with evidence.
Why this works: When you lead with "Your Fort Worth location averages 4.2 hours per deal vs 2.8 hours for comparable Texas BHPH dealers" instead of "I see you're hiring for digital 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 data. Here are the sources used in this playbook:
| Source | Key Fields | Used For |
|---|---|---|
| Shop By Payment Internal Data - Shopping Sessions | payment_term_preferences, vehicle_class, price_range, geographic_region, quote_request_distribution | Payment Term Mismatch plays - identifying shopper demand patterns and inventory optimization opportunities |
| Shop By Payment Internal Data - Deal Flow | quote_to_deal_completion_time, dealership_type, abandonment_rates, stage_timing | Deal Completion Time plays - peer benchmarking and process bottleneck identification |
| Shop By Payment Internal Data - Lender Network | approval_rates_by_credit_tier, lender_network_funding_outcomes, geography | Deep Subprime Arbitrage plays - approval rate analysis and risk assessment |
| CFPB Auto Finance Data Pilot | delinquency_rates, credit_score_tier, geography, loan_performance | Deep Subprime Arbitrage plays - regional delinquency context and risk correlation |
| State Motor Vehicle Dealer Licensing Boards | dealer_name, license_status, business_address, dealership_type | Deal Completion Time plays - dealer classification for accurate peer matching |
| CFPB Consumer Complaint Database - Auto Loans | complaint_date, product_type, issue_description, company_name, state, complaint_narrative | Supporting data for identifying dealerships with customer friction around payment transparency |