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 Casper Shipping 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 MV Chemstar was detained at Southampton on November 8th with 14 deficiencies" (Paris MOU database with vessel name and detention date)
PQS (Pain-Qualified Segment): Reflect their exact situation with such specificity they think "how did you know?" Use government data with dates, record numbers, vessel names.
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 precise understanding of the prospect's situation using verifiable data sources.
Use aggregated demurrage settlement data from 400+ North Sea energy calls to show operators which terminal operators pay above claimed amounts versus below.
Aberdeen terminal operators settle at 123% of claimed amounts versus other terminals at 94-100%, meaning operators routing to the wrong ports are leaving money on the table.
Settlement rate benchmarks directly impact route economics and profitability. When you reveal that Aberdeen pays 123% of claimed amounts (meaning operators get MORE than they claim), you're delivering intelligence that changes commercial routing decisions immediately.
The specificity of knowing their actual routing patterns (8 Aberdeen calls vs Peterhead at 94%) proves you've done deep research, not just pulled industry reports.
This play requires aggregated demurrage settlement outcomes by terminal from North Sea port agency services - minimum 400+ claims across 12+ months to ensure statistical validity.
This is proprietary data only you have - competitors cannot replicate this play.Calculate the operator's net demurrage position (demurrage paid to charterers minus demurrage recovered from own claims) to reveal hidden cash flow drain.
When operators pay £520K but only recover £210K, the £310K gap signals documentation protocol weaknesses that can be fixed.
Most operators track demurrage as two separate line items and don't realize they're in a net-negative position. Surfacing the £310K gap number creates immediate urgency because it's money already lost.
Attributing the gap to "documentation protocols not optimized for UK customs clearance timing" gives them a specific, fixable root cause rather than vague "process improvements."
This play requires visibility into both demurrage paid and demurrage recovered by customer through port agency services, plus vessel tracking to identify operator ownership across claims.
Combined internal claims data with public vessel ownership creates synthesis unique to your business.Use 6 years of historical laytime data from Immingham port agency services to identify seasonal congestion patterns, then cross-reference with operator's scheduled call volume to calculate exposure.
November 15 - December 20 adds 2.8 days average laytime at Immingham grain terminal. Operators with 12 calls during this window face £340K exposure they can avoid through scheduling optimization.
The 2.8 days average and November 15 - December 20 window are specific, actionable intelligence. When you combine this with their exact call volume (12 calls) and quantify exposure (£340K), you're providing a forecast they can act on immediately.
This helps them optimize voyage scheduling to avoid demurrage costs - they can use this value whether they respond or not.
This play requires historical laytime data from port agency services at Immingham (minimum 6 years to identify seasonal patterns) and customer call records with vessel scheduling.
Combined with public vessel tracking to verify operator's call patterns. This synthesis is unique to your business.Track operator's recovery rate trend by port over time, cross-referenced with their call volume, to identify where increased activity is yielding worse financial outcomes.
When Southampton calls increased 22% but recovery rate dropped from 64% to 41%, the operator is leaving £180K on the table despite doing more business.
The paradox of "more activity, worse results" creates immediate cognitive dissonance. When you reveal they're doing 22% more business at Southampton but recovering 23 percentage points LESS, you're surfacing a problem they didn't know existed.
Attributing it to "laytime calculation disputes with specific terminal operators" gives them a diagnosis with a fixable root cause, not just a symptom.
This play requires customer port call volumes, demurrage claims filed, and settlement outcomes by port tracked over 18+ months to identify trend reversal.
Combined with public vessel tracking to verify call frequency. This synthesis is unique to your business.Use aggregated demurrage settlement data across similar operators to benchmark individual operator performance, then combine with seasonal exposure forecasting to create urgency.
When operator recovered 52% vs 68% fleet average in Q1, and harvest season (September-November) is approaching, they need to fix the gap before the highest-volume period.
Benchmarking creates competitive urgency - "you're at 52%, others like you are at 68%" immediately signals underperformance. The harvest season timing creates a deadline: fix this before your busiest exposure window.
Offering port-by-port breakdown of where claims are weakest gives them actionable next steps rather than vague "improve your processes."
This play requires aggregated demurrage claim tracking data from port agency services showing settlement rates by customer with peer benchmarking across 50+ operators.
This is proprietary data only you have - competitors cannot replicate this benchmarking.Use operator's scheduled call volume at UK grain terminals during harvest season (October-December) combined with historical seasonal delay patterns to calculate total exposure, then compare to their weak recovery rate from prior year.
28 scheduled calls × 3.4 days average delay × demurrage rates = £890K exposure. Last year's 48% recovery means £460K left uncollected.
The £890K exposure number gets immediate attention because it's predictable future pain, not past regrets. When you add that they only recovered 48% last year (leaving £460K uncollected), you're showing them both the problem AND their historical inability to solve it.
The claims strategy question is appropriate because the exposure is coming regardless - the only variable is their response.
This play requires customer scheduling data (or vessel tracking to infer scheduled calls), historical seasonal delay patterns at UK grain terminals, and customer's recovery rate data from prior year.
Combined public vessel tracking with proprietary seasonal delay patterns and customer recovery history.Cross-reference operator's Paris MOU inspection results with peer benchmark data from other chemical tanker operators in your port agency portfolio to reveal systematic underperformance.
When their vessels average 4.2 deficiencies per inspection versus 2.1 for comparable operators, they're facing higher detention risk and P&I premium increases.
The 4.2 vs 2.1 benchmark is damning - it's double the deficiency rate of comparable operators. Connecting this to P&I premium impact adds a cost dimension they may not have quantified.
Offering to show which deficiency categories they're repeatedly failing gives them actionable diagnosis rather than vague "improve compliance."
This play requires benchmarking customer Paris MOU inspection results against other chemical tanker operators in your port agency portfolio (minimum 10-15 comparable operators for valid benchmark).
Public Paris MOU data combined with proprietary portfolio benchmarking creates competitive intelligence.Cross-reference Paris MOU detention data with internal customer survey records to identify non-obvious patterns the operator hasn't connected.
When 3 detained vessels all used Lloyd's Register for pre-arrival surveys within 60 days, the pattern suggests surveyor interpretation gaps versus MCA standards - a fixable root cause.
You're connecting dots across detentions the operator didn't see. Identifying Lloyd's Register as the common thread gives them a specific action (change surveyors or adjust survey scope) rather than generic "improve compliance."
The deficiency overlap analysis offer provides immediate diagnostic value they can use whether they respond or not.
This play requires access to customer vessel survey records (surveyor company, survey dates, vessel names) to cross-reference with public Paris MOU detention data.
Public detention data combined with internal survey records creates root cause diagnosis.Use internal demurrage settlement timing data by UK port to reveal systematic cash flow impact from slow-settling ports, then quantify the working capital cost for the operator's specific call pattern.
When Teesport takes 86 days average versus Humber at 28 days, and the operator has £220K Q1 claims still outstanding, their cash is tied up 3x longer than necessary.
The 86 vs 28 days comparison creates immediate clarity about the magnitude of the problem - 3x longer cash tie-up hurts balance sheet and working capital ratios. Quantifying £220K Q1 outstanding makes it specific to their business.
Offering a diagnostic ("why Tees is systematically slower for your fleet") gives them a low-commitment next step with immediate actionable value.
This play requires customer demurrage settlement timing data by UK port from port agency services (minimum 12 months of settlement data to calculate reliable averages).
Combined with public vessel tracking to verify call frequency. This synthesis is unique to your business.Identify operators whose chemical tankers show multiple Paris MOU detentions across different UK ports within a 6-month window, revealing a pattern they may not be tracking at fleet level.
When 3 vessels from the same operator are detained at Southampton, Immingham, and Milford Haven with cargo system deficiencies, Paris MOU flags them for targeting priority (25-40% inspection probability on every UK call).
Fleet-level pattern recognition shows you did deeper analysis than just looking at individual detentions. The targeting priority consequence (25-40% inspection probability) is something they need to care about immediately because it affects future operations.
The question "Is someone tracking the pattern across your fleet?" addresses whether they're coordinating response or treating each detention as isolated incident.
Use internal claims tracking to identify operators with large volumes of open demurrage claims at specific ports past 90 days with no settlement progress, then provide port-specific dispute pattern context.
When 26 claims totaling £340K are stuck at Liverpool past 90 days, and Liverpool terminal operators dispute laytime calculation methodology on 73% of claims, the operator needs different documentation approach.
The 26 claims and £340K stuck money are specific to the operator's situation - that's THEIR cash tied up right now. The 90 days past due timing creates urgency because these claims should have settled already.
Revealing that 73% of Liverpool claims face laytime calculation disputes (not specific to them) gives them actionable context - it's a Liverpool pattern they need to address with different documentation.
This play requires customer claims tracking data and port-specific settlement pattern intelligence from port agency services showing terminal operator dispute behaviors.
Internal claims aging data combined with proprietary port dispute pattern intelligence.Identify operators whose hazmat vessels show the SAME deficiency category across multiple UK inspections within a quarter, suggesting fleet-wide equipment or maintenance protocol issues rather than isolated vessel problems.
When 4 vessels (MV Bristol, MV Cardiff, MV Dover, MV Edinburgh) all receive fire detection system deficiencies in Q3 2024, Paris MOU will escalate to systematic investigation.
Naming four specific vessels demonstrates impressive research depth and proves you're not sending generic alerts. The Q3 timeframe is recent and actionable.
Fleet-wide pattern identification is valuable insight they may not have connected across individual inspection reports. Paris MOU escalation threat is credible and creates urgency.
Identify chemical tanker operators whose vessels were detained by Paris MOU inspectors at UK ports within the last 30 days, creating immediate operational disruption and financial impact.
When MV Chemstar was detained at Southampton on November 8th with 14 deficiencies including cargo handling system failures, detention adds 3-5 days demurrage exposure per charter party - roughly £45K at current rates.
Extremely specific - they know their exact vessel and detention date from Paris MOU public records. The demurrage calculation (3-5 days at £45K) is immediately relevant to their P&L and demonstrates you understand the financial impact.
The routing question "Who's coordinating the reinspection with MCA?" is easy to answer and appropriate for the urgency level of a current detention.
Identify hazardous cargo vessels cited for the SAME deficiency category across 2+ MCA inspections within 18 months at different UK ports, signaling systemic compliance gaps that precede regulatory escalation.
When MV Northsea was cited for cargo hold ventilation deficiencies at Teesport in March AND Liverpool in September, recurring deficiencies trigger ISM audit requirements and potential charter party warranty breaches.
Specific vessel and recurring pattern shows real research, not template spam. ISM audit trigger is a compliance escalation they need to care about because it affects their Safety Management Certificate.
Charter party warranty mention hits commercial risk - charterers can reject vessels with ISM non-conformities. Root cause analysis question is appropriate because recurring deficiencies signal systemic issues.
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 MV Chemstar was detained at Southampton on November 8th with 14 deficiencies" instead of "I see you operate chemical tankers," 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 |
|---|---|---|
| Paris MOU Port State Control Detention Database | vessel_name, IMO_number, port_of_detention, detention_date, deficiency_code | Chemical tanker detentions, fleet-level detention patterns, targeting priority alerts |
| UK Maritime and Coastguard Agency (MCA) Survey and Inspection Database | vessel_name, IMO_number, inspection_date, deficiency_classification, compliance_status | Recurring deficiency patterns, systematic compliance gaps, ISM audit triggers |
| Vessel Tracking Platforms (MarineTraffic, VesselFinder) | vessel_name, IMO_number, port_visits, arrival_departure_dates, operator | Port call frequency, route patterns, seasonal scheduling, operator identification |
| Internal Demurrage Claims Database | settlement_amount, recovery_rate, port, customer, claim_date, settlement_timing | Recovery rate benchmarking, port-specific settlement intelligence, claims aging analysis |
| Internal Port Agency Records | laytime_duration, seasonal_delays, congestion_patterns, terminal_operations | Seasonal demurrage forecasting, port congestion patterns, optimal scheduling windows |
| Internal Customer Survey Records | surveyor_company, survey_date, vessel_name, survey_scope | Root cause analysis for detention patterns, surveyor performance correlation |