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 Quorum Software 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 Eugene Island Block 198 federal lease expires November 2025 with production down 34% year-over-year" (ONRR database with specific lease number and production data)
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.
Company: Quorum Software
Core Problem: Energy companies operate with fragmented data and disconnected workflows across planning, operations, accounting, and land management. Quorum consolidates siloed information into unified systems with real-time visibility, enabling faster decision-making and operational efficiency across upstream and midstream energy businesses.
Ideal Customer Profile: Mid-market to enterprise energy companies with $100M+ revenue managing multiple operational domains (exploration, drilling, production, reserves, accounting, land, measurement) requiring centralized data, regulatory compliance, production forecasting, and capital/resource planning across geographies.
Primary Buyer Persona: VP of Operations / Operations Manager responsible for overseeing multi-asset production operations, production forecasting, regulatory compliance, and coordinating across well drilling, operations, and land functions.
These messages are ordered by quality score (highest first). Each play demonstrates either precise situation mirroring (PQS) or immediate value delivery (PVP) using verifiable government data.
Provide comprehensive incident pattern analysis across the prospect's entire pipeline network, quantifying cumulative downtime impact and lost throughput with segment-specific risk scores. This synthesis of PHMSA incident data with internal operational metrics delivers portfolio-level intelligence the prospect can't easily assemble themselves.
Pipeline operators see individual incidents but rarely synthesize the portfolio view. When you present 8 incidents across 3 segments resulting in 299,000 barrels lost, you're showing them the forest they couldn't see through the trees. The magnitude of the cumulative impact (61 days, nearly 300K barrels) demands executive attention and positions you as someone who understands their entire operation, not just one incident.
This play requires internal throughput and downtime data across the recipient's pipeline network to calculate cumulative impact metrics.
Combined with public PHMSA incident reports to create comprehensive portfolio risk analysis unique to your platform.Deliver platform-by-platform risk assessment showing the production-to-maintenance imbalance across aging offshore assets. By combining BSEE incident data with internal production and maintenance tracking, you reveal that 41% of production comes from platforms accounting for 78% of maintenance events - a pattern the prospect may not have quantified.
The 41% vs 78% ratio is the killer insight. It shows you analyzed their entire portfolio to identify the specific platforms dragging down operational efficiency. Four named platforms with exact ages and incident counts demonstrate deep research. The prospect immediately recognizes this as actionable intelligence worth reviewing, whether they buy from you or not.
This play requires internal production data showing each platform's contribution to total output and maintenance event tracking by platform.
Combined with public BSEE incident and platform commissioning data to identify production-maintenance imbalance patterns.Map the prospect's entire federal lease portfolio to identify upcoming expirations and flag which leases are tracking toward minimum production thresholds. Five specific lease blocks with exact expiration windows (November 2025 to May 2026) and the insight that three of five are at risk creates comprehensive portfolio-level urgency.
Federal lease operators track individual leases but rarely synthesize the portfolio timeline. When you show five leases expiring in 18 months with three at risk, you're delivering strategic planning intelligence they need but haven't assembled. The comprehensive view demonstrates you understand their entire federal footprint, positioning you as a strategic partner rather than a vendor.
This play requires production tracking data across the recipient's federal lease portfolio to identify which leases are approaching minimum production thresholds.
Combined with public BLM lease expiration records to create comprehensive lease compliance timeline.Analyze the prospect's entire pipeline network to identify the three highest-risk segments based on incident-to-throughput ratios. Quantify that these three segments account for 68% of unplanned downtime across the last 18 months, then offer the detailed segment-by-segment breakdown.
Pipeline operators know which segments have incidents, but incident-to-throughput ratio analysis requires synthesizing multiple data sources. The 68% statistic is the hook - over two-thirds of their downtime concentrated in three segments. They clearly analyzed the entire network to find this pattern, which positions the follow-up offer (segment breakdown) as genuinely valuable intelligence.
This play requires internal operational data showing throughput and downtime across the recipient's pipeline network.
Combined with public PHMSA incident data to calculate incident-to-throughput ratios and identify highest-risk segments.Alert federal lands operators to reserve replacement risk across their portfolio by identifying three specific lease blocks tracking toward minimum production thresholds in the next 8 months. Include BLM review timeline context (4-6 months) to create urgency and offer the full production trajectory analysis.
Three named lease blocks shows you analyzed their entire federal portfolio. The 8-month threshold window combined with 4-6 month BLM review timeline creates immediate urgency - they're in the action window right now. Offering the prepared trajectory analysis demonstrates you've already done the work, making it easy for them to say yes to seeing the full picture.
This play requires production decline data across the recipient's federal lease portfolio to identify which specific blocks are approaching minimum production thresholds.
Combined with public BLM lease expiration data and regulatory review timelines to create actionable compliance alerts.Alert the prospect to a structural integrity incident on a specific platform (Vermilion Block 331) with exact commissioning date, incident date from BSEE, and daily production volume. Frame the risk in production impact terms (2,400 bbl/day downtime cost) and offer the BSEE inspection schedule combined with production impact analysis.
Knowing the platform produces 2,400 bbl/day shows you understand their operations beyond just the public incident data. Framing the BSEE inspection in production impact terms speaks their language - they care about barrels and dollars, not just compliance. The combination of specific platform details (39 years old, May 2024 incident, exact production volume) demonstrates research depth that earns the right to offer further analysis.
This play requires internal production data showing daily production volume (2,400 bbl/day) for the specific platform.
Combined with public BSEE incident reports and platform commissioning dates to frame compliance risk in production impact terms.Provide detailed incident timeline analysis for a specific pipeline segment (Port Arthur Junction) showing three incidents with duration ranges, throughput data, and cumulative lost barrels (110,000). Offer root cause pattern analysis to help identify systemic issues rather than treating each incident as isolated.
The 110,000 barrel total is a big number that gets executive attention. More importantly, offering root cause pattern analysis (rather than just incident statistics) shows you're thinking about solving the underlying problem. Pipeline operators see individual incidents; you're offering to connect the dots across three events to identify systemic causes they can actually address.
This play requires internal throughput data for the Port Arthur Junction segment and downtime duration tracking for each incident.
Combined with public PHMSA incident reports to calculate cumulative throughput loss and identify root cause patterns.Alert the prospect that a specific federal lease (West Cameron Block 143) is tracking toward BLM minimum production threshold in Q2 2025 based on 38% YoY decline and January 2026 expiration. Offer a production trajectory model with timeline milestones showing exactly when they'll hit the threshold and need to act.
The Q2 2025 threshold trigger gives them time to act but creates urgency - it's close enough to matter. Offering the production trajectory model with timeline milestones is genuinely valuable - they get a visual roadmap of when decisions need to be made (drilling, M&A, or accepting lease forfiture). This is consulting-grade analysis delivered before asking for anything.
This play requires production decline data for West Cameron 143 showing 38% YoY decline and the ability to model future production trajectory.
Combined with public BLM lease expiration data to identify when the lease will hit minimum production thresholds requiring BLM review.Target federal lands operators with a specific lease block (Eugene Island Block 198) that's expiring in 11 months and showing 34% YoY production decline. Mirror the exact situation back to them with verifiable numbers and ask a simple routing question about who handles reserve replacement filings.
Knowing their exact lease block, expiration date, and production decline percentage demonstrates deep research. The BLM review threat is real and expensive - losing a federal lease means forfeiting $50M-$500M+ in asset value. The simple routing question makes it easy to respond while the specificity earns attention. This isn't a sales email; it's a compliance alert.
This play requires internal production data showing 34% YoY decline for this specific lease block.
Combined with public BLM lease expiration records to calculate when the lease will hit minimum production thresholds.Target federal lands operators with a specific lease (Ship Shoal Block 207) showing dramatic quarterly decline (41% Q3 to Q4 2024) and approaching BLM minimum production review trigger with 15 months until lease expiration. Ask if reserves engineering is already modeling the situation.
The 41% quarterly decline is alarming - that's not normal well decline, that's something broken or shut in. Specific lease block with exact quarterly percentage and March 2026 expiration date shows precise research. The yes/no question about reserves engineering makes it easy to route while the BLM minimum production trigger adds urgency. They need to know if their internal team is on top of this.
This play requires quarterly production data for Ship Shoal Block 207 showing the 41% Q3-Q4 decline.
Combined with public BLM lease expiration records to identify compliance risk timeline.Target pipeline operators with a specific incident (Katy pipeline, October 12th) where you've calculated the exact lost throughput (47,000 barrels) based on 9 days downtime at 5,200 bbl/day throughput. Tie to Q4 pricing to emphasize the financial pain and ask who's leading incident prevention review.
The 47,000 barrel number is the hook - that's real money. Specific date (October 12th), exact duration (9 days), and throughput calculation (5,200 bbl/day) shows you did the math they haven't done yet. Mentioning Q4 pricing makes it even more painful - they lost those barrels during peak pricing season. The simple routing question makes response easy while demonstrating you understand their business.
This play requires internal throughput data to calculate the 5,200 bbl/day baseline for the Katy pipeline.
Combined with public PHMSA incident reports showing the October 12th incident and 9-day duration to calculate total lost throughput.Target Gulf of Mexico operators with a specific platform (West Cameron Block 588) that's had three structural incidents since 2022 and is over 35 years old. Frame the three-incidents-in-36-months pattern as triggering enhanced inspection frequency and potential production curtailment, then ask who's leading BSEE coordination.
Three incidents in 36 months for a platform over 35 years old is a clear pattern that BSEE will flag. The exact platform (West Cameron Block 588), exact age (36 years, commissioned 1989), and exact incident timeline (since 2022) demonstrate thorough research. Mentioning production curtailment hits their real concern - dollars lost. The routing question is simple but the message establishes you as someone who tracks their compliance obligations.
Target pipeline operators with a specific platform (South Timbalier 295) that's had two structural incidents in 26 months - just over BSEE's 24-month pattern-of-concern threshold. Frame it as hitting the regulatory threshold for aging platforms and ask if they're already coordinating with BSEE.
The 24-month vs 26-month comparison is the hook - they're just over the threshold that triggers BSEE scrutiny. Two specific dates (April 2023 and June 2024) with BSEE source citation proves you're not guessing. The yes/no question makes it easy to respond while establishing you as someone who tracks regulatory thresholds they need to care about.
Target pipeline operators with a specific segment (Sabine Pass) that's had two incidents in eight months (March and November 2024), both causing 7+ day outages. Frame the two-incidents-within-12-months pattern as triggering enhanced monitoring requirements and ask if operations is already working on the integrity management plan.
Two incidents in eight months is a tight timeline that suggests a systemic issue, not random bad luck. Specific months (March and November 2024), specific segment (Sabine Pass), and specific duration (7+ days per PHMSA) demonstrate research depth. The 12-month enhanced monitoring trigger is a real compliance issue that costs money. The yes/no question about the integrity management plan makes it easy to route while showing you understand their regulatory obligations.
Target pipeline operators with a specific pipeline segment (Katy to Beaumont) that's had three incidents in 14 months (September 2023 to November 2024). Frame it as being on enhanced inspection protocol where the next incident triggers mandatory integrity management review, then ask if someone is tracking the follow-up inspection schedule.
Three incidents in 14 months is a clear pattern. Specific pipeline segment (Katy to Beaumont), exact timeline (September 2023 to November 2024), and PHMSA citation demonstrate verifiable research. The enhanced inspection protocol threat is real - mandatory integrity management review is expensive and time-consuming. The simple routing question makes it easy to respond while establishing you as someone who tracks their compliance obligations.
Target Gulf of Mexico operators with a specific platform (Eugene Island Block 330) that's 44 years old and had a structural integrity event flagged in the September 2024 BSEE inspection. Frame the 40-year threshold with any structural incident as typically triggering annual integrity assessments, then ask who's coordinating the assessment schedule with BSEE.
Exact platform (Eugene Island Block 330), exact age (44 years, commissioned 1981), and specific incident month (September 2024) demonstrate thorough research. The 40-year threshold with structural incident triggering annual assessments is a credible regulatory pattern. The routing question is simple but the specificity earns attention - this is actionable compliance information they need to be on top of.
Target Gulf of Mexico operators with a specific platform (South Timbalier 295) that's 38 years old and just had its second structural incident in 26 months. Frame the 35-year threshold with multiple structural events as typically facing enhanced inspection frequency, then ask who's managing the BSEE compliance calendar.
Exact platform (South Timbalier 295), exact age (38 years, commissioned 1987), and exact incident count with timeline (second incident in 26 months) demonstrate verifiable research. The 35-year threshold and enhanced inspection risk are both credible regulatory triggers. The straightforward routing question makes it easy to respond while the specificity shows you track compliance obligations that matter to them.
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 Eugene Island Block 198 federal lease expires November 2025 with production down 34% year-over-year" instead of "I see you're hiring for operations 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 |
|---|---|---|
| ONRR/BLM Federal Oil and Gas Leases and Production | operator_name, lease_number, location, monthly_production, acreage, federal_lands_type, lease_expiration_date | Federal lease reserve replacement risk, lease expiration timelines |
| PHMSA Incident and Accident Data | operator_name, incident_date, pipeline_type, cause, damage_amount, property_impact | Pipeline safety incidents, operational downtime patterns, enhanced inspection triggers |
| BOEMRE Offshore Oil and Gas Production and Lease Data | operator_name, lease_block, production_volume, water_depth, platform_type, status | Offshore platform aging analysis, structural incident patterns, GoM operations |
| EIA - Natural Gas Processing Plants and Capacity | facility_name, operator_name, location, input_capacity, state, company_id | Processing plant capacity and utilization analysis |
| EIA - Liquefied Natural Gas (LNG) Import and Export Terminals | terminal_name, operator_name, location, capacity_mtpa, status, state | LNG terminal operator identification and capacity tracking |
| FERC - Form 2/2A Major Natural Gas Pipeline Annual Report | company_name, pipeline_code, transmission_miles, annual_revenue, system_id, operational_metrics | Interstate pipeline operator identification and regulatory compliance |
| Texas Railroad Commission (RRC) - Production Data Query | operator_name, API_number, lease_id, monthly_production, well_type, district, county | State-regulated producer identification and production tracking |
| EIA - Natural Gas Storage Facility Data (Form EIA-191) | operator_name, storage_facility, location, capacity_bcf, deliverability_bcf, field_type | Storage facility operator identification and capacity analysis |