Blueprint Playbook for Project Canary

Who the Hell is Jordan Crawford?

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.

The Old Way (What Everyone Does)

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 Project Canary SDR Email:

Subject: Transform your emissions monitoring Hi [First Name], I noticed your company is focused on ESG and sustainability initiatives. At Project Canary, we help energy companies accurately measure and certify their emissions using our TrustWell platform. Our AI-powered continuous monitoring gives you real-time insights into your methane emissions, helping you meet regulatory requirements and achieve premium pricing for responsibly sourced gas. We've helped companies like yours reduce their carbon footprint while improving their ESG scores. I'd love to show you how we can do the same for your operations. Are you available for a 15-minute call next week? Best, SDR Name

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.

The New Way: Intelligence-Driven GTM

Blueprint flips the approach. Instead of interrupting prospects with pitches, you deliver insights so valuable they'd pay consulting fees to receive them.

1. Hard Data Over Soft Signals

Stop: "I see you're hiring compliance people" (job postings - everyone sees this)

Start: "Your Lea County facility received a methane super-emitter detection on November 14th with no response filed in EPA systems" (EPA ECHO data with specific date and location)

2. Mirror Situations, Don't Pitch Solutions

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.

Project Canary Plays: Data-Driven Intelligence

These messages are ordered by quality score. The best plays come first, whether they use public data, proprietary internal data, or a hybrid approach.

PVP Public + Internal Strong (9.5/10)

RSG Premium You're Missing: $127K/Month

What's the play?

Target Midland Basin oil and gas operators whose methane intensity significantly exceeds certified peer averages, quantifying the exact monthly revenue they're losing by not accessing Responsibly Sourced Gas (RSG) premium markets. Identify specific wells contributing to excess methane.

Why this works

You're showing them money they're leaving on the table every single month with surgical precision. The combination of basin-specific peer benchmarks, their actual production volume, and well-level granularity (11 wells = 82% of excess) proves you've done deep analysis specific to their operations. This isn't generic - it's their exact revenue opportunity.

Data Sources
  1. Internal: Aggregated methane intensity data from certified operations across basins
  2. EPA GHGRP Oil and Gas Dashboard - basin-level emissions trends and benchmarks
  3. State oil & gas commission production data - facility-level production volumes

The message:

Subject: RSG premium you're missing: $127K/month Your Midland Basin production averages 0.19% methane intensity vs. certified peer average of 0.08% - that gap costs you RSG premium access. At your 85 MMcf/day production and $0.18/Mcf RSG premium, that's $127,000/month in lost revenue. Want to see which 11 wells account for 82% of your excess methane?
DATA REQUIREMENT

This play requires aggregated methane intensity metrics from your certified customer base, segmented by basin and facility type, with percentile ranges across 10+ facilities per segment. You also need well-level monitoring data to isolate specific contributors.

This synthesis of your proprietary monitoring network with public production data is unique to Project Canary - competitors cannot replicate this granular revenue impact analysis.
PVP Public Data Strong (9.4/10)

We Caught 3 Methane Events at Your Facilities

What's the play?

Target oil and gas operators with multiple methane super-emitter events detected via satellite monitoring in EPA's system, where no detection responses have been filed. Quantify the penalty risk and offer to provide the specific event details their compliance team needs.

Why this works

You're providing immediate compliance intelligence they don't have. Three specific events at their facilities with a concrete penalty amount ($50,814 each) creates urgent, quantified risk. The offer to provide dates, locations, and emission rates gives them everything needed to act immediately - this is actionable value whether they buy or not.

Data Sources
  1. EPA ECHO Methane Super Emitter Program Data Explorer - event_location_coordinates, facility_name, owner_operator_name, event_date, event_status, methane_confirmation_status
  2. EPA GHGRP FLIGHT - facility_id, facility_name, location_state to cross-reference operators

The message:

Subject: We caught 3 methane events at your facilities Satellite monitoring detected 3 super-emitter events at your Permian facilities between October 15-November 30th - none show detection responses in EPA systems. Each unreported event is a potential $50,814 penalty under the new methane rule. Want the event dates, locations, and emission rates for your compliance team?
PVP Public + Internal Strong (9.3/10)

8 Wells Dragging Your Methane Intensity Down

What's the play?

Target Delaware Basin operators whose methane intensity exceeds certified peer averages, offering to identify the specific wells contributing the majority of excess emissions. Quantify the RSG premium opportunity they're missing.

Why this works

You've isolated the problem to 8 specific wells contributing 67% of the issue - that's surgical precision. The prospect can immediately act on well IDs to improve performance. The RSG premium range ($0.15-0.40/Mcf) is verifiable market data they recognize. This provides value even before they respond - they now know exactly where their problem is.

Data Sources
  1. Internal: Well-level methane intensity data from certified operations, with basin-specific peer benchmarks
  2. EPA GHGRP FLIGHT - facility-level emissions by basin
  3. State oil & gas commission well data - production volumes by well

The message:

Subject: 8 wells dragging your methane intensity down Your Delaware Basin operations average 0.18% methane intensity - we've isolated 8 wells contributing 67% of that. Certified peers in your basin average 0.09% and access RSG premiums of $0.15-0.40/Mcf. Want the well IDs and their specific intensity calculations?
DATA REQUIREMENT

This play requires well-level monitoring data from your certified customer base, with the ability to calculate methane intensity at individual well granularity and aggregate basin-level peer benchmarks.

Only Project Canary has this level of well-specific continuous monitoring data across certified operations - competitors have satellite or spot-check data, not operational granularity.
PVP Public + Internal Strong (9.2/10)

Your Permian Methane Intensity: 0.21% vs 0.11%

What's the play?

Target Permian Basin operators whose methane intensity significantly exceeds certified peer averages, explicitly naming the RSG buyers (Pacific Gas & Electric, Southern California Gas) they're disqualified from. Offer facility-level intelligence showing which assets drive the excess.

Why this works

You're naming real RSG buyers they recognize (PG&E, SoCal Gas) - these aren't hypothetical markets. The 0.10% gap is quantified and specific to their basin. Identifying 6 facilities contributing 73% of excess emissions provides surgical, actionable intelligence. This identifies revenue they're leaving on the table right now with named buyers.

Data Sources
  1. Internal: Aggregated methane intensity from 280 certified Permian operators
  2. EPA GHGRP Oil and Gas Dashboard - Permian Basin emissions trends
  3. Public utility RSG procurement standards - PG&E and SoCal Gas methane intensity thresholds

The message:

Subject: Your Permian methane intensity: 0.21% vs 0.11% We certify 280 Permian operators - your basin average is 0.21% methane intensity vs. certified peer average of 0.11%. That 0.10% gap disqualifies you from RSG contracts with Pacific Gas & Electric and Southern California Gas. Want to see which 6 facilities are driving 73% of your excess emissions?
DATA REQUIREMENT

This play requires aggregated methane intensity metrics across 50+ certified Permian operations, with facility-level granularity to isolate contributors to overall intensity.

Your certified monitoring network across 280 Permian operators is proprietary - competitors cannot benchmark against this peer group.
PVP Public + Internal Strong (9.1/10)

Your Delaware Basin Wells vs. Certified Peers

What's the play?

Target Delaware Basin production facilities with methane intensity double the certified peer average across Project Canary's 340 monitored operations. Offer to identify the specific wells pulling their basin average down.

Why this works

The 340 certified operations provides massive peer sample size - this is a credible benchmark. Doubling the peer average (0.18% vs 0.09%) is significant underperformance. Offering to identify which 8 specific wells are the problem provides immediate actionable intelligence. The RSG market access and institutional capital references connect to business outcomes they care about.

Data Sources
  1. Internal: Methane intensity data from 340 certified Delaware Basin operations
  2. EPA GHGRP FLIGHT - facility-level emissions for Delaware Basin
  3. State oil & gas commission well production data

The message:

Subject: Your Delaware Basin wells vs. certified peers We monitor 340 certified operations in the Delaware Basin - your methane intensity is 0.18% vs. the certified average of 0.09%. That gap costs you access to premium RSG markets and institutional capital. Want to see which 8 of your wells are pulling your basin average down?
DATA REQUIREMENT

This play requires aggregated methane intensity data from 100+ certified operations in the Delaware Basin, with well-level monitoring capability to identify specific contributors.

Your 340-operation monitoring network in the Delaware Basin is proprietary - competitors cannot benchmark against this peer group at well-level granularity.
PVP Public + Internal Strong (9.0/10)

Your March ESG Report Needs February Certification

What's the play?

Target operators whose annual ESG reporting deadlines precede their projected certification completion dates, creating a gap where they'll report unvalidated emissions to investors. Offer the expedited certification solution used by peer operators.

Why this works

You've identified a specific 13-day gap (March 28th vs March 15th) between their cert and reporting deadline - that precision shows you know their timeline. The 8-operator pushback precedent makes the investor credibility risk concrete and real. Offering the proven solution from 8 real operators eliminates the "is this possible?" question - it's already been done.

Data Sources
  1. Internal: Customer certification timelines and completion dates by operator
  2. Public company ESG reporting schedules and investor disclosure deadlines
  3. Internal: Case studies from operators who accelerated certification timelines

The message:

Subject: Your March ESG report needs February certification Your annual ESG report is due March 15th to investors but your TrustWell certification doesn't complete until March 28th. That means you'll report Scope 1 emissions without third-party validation - 8 operators got investor pushback on unvalidated claims in 2024. Want the expedited certification option that 8 operators used to close this gap?
DATA REQUIREMENT

This play requires tracking of customer certification project timelines and completion dates, cross-referenced with their public ESG reporting schedules. Also requires case study data from operators who used expedited certification paths.

Your certification journey data and timeline benchmarks are proprietary - competitors don't have visibility into how long certification actually takes across different facility types.
PVP Public Data Strong (9.0/10)

Subpart W Prep Checklist for Freeport LNG

What's the play?

Target LNG export terminals crossing the 25,000 MT CO2e GHGRP reporting threshold within months, facing Subpart W natural gas supply chain reporting obligations. Offer the data collection checklist from peer terminals who already filed.

Why this works

You've calculated their exact threshold trigger date (August 2024) from throughput trends - that near-term urgency is real. Subpart W supply chain data requirements are genuinely complex and unfamiliar. Offering the proven checklist from 4 terminals who've already navigated this provides immediate, implementable value - they can use it whether they buy or not.

Data Sources
  1. FERC LNG Export Terminals Database - terminal_name, operator_name, capacity_mtpa, operational_status
  2. EPA GHGRP FLIGHT - facility emissions history and subpart categorization
  3. EPA GHGRP Subpart W requirements documentation

The message:

Subject: Subpart W prep checklist for Freeport LNG Your Freeport terminal crosses the 25,000 MT threshold in August 2024 based on current throughput - that triggers Subpart W in 90 days. Subpart W requires upstream supplier data, leakage rates, and transmission emissions you likely don't track today. Want the Subpart W data collection checklist from 4 terminals who filed in 2023?
PQS Public Data Strong (8.9/10)

November Methane Event at Reeves County

What's the play?

Target oil and gas operators with specific methane super-emitter events detected at named facilities, where satellite monitoring captured the plume but no detection response was filed with EPA within the required 15-day window.

Why this works

You've named their specific facility (Reeves County compression station), specific date (November 14th), and specific emission rate (1,847 kg/hr) - this is their exact situation mirrored back. The GHGRP Flight system reference shows deep regulatory knowledge. The 15-day requirement is factual and verifiable. The clear ownership question makes this easy to route.

Data Sources
  1. EPA ECHO Methane Super Emitter Program Data Explorer - event_location_coordinates, facility_name, event_date, notifier_organization, methane_confirmation_status
  2. EPA GHGRP FLIGHT - facility_name, facility_id, owner_operator_name to verify operator

The message:

Subject: November methane event at Reeves County Satellite monitoring caught a methane plume at your Reeves County compression station on November 14th at 1,847 kg/hr. EPA's methane rule requires you to investigate and respond within 15 days - no detection response appears in GHGRP Flight system. Who owns super-emitter event documentation for your Permian assets?
PQS Public Data Strong (8.9/10)

Your Sabine Pass Subpart W Gap

What's the play?

Target LNG export terminals that reported emissions just below the 25,000 MT CO2e Subpart W threshold in their most recent GHGRP filing, while operational throughput data shows growth that will trigger the threshold in coming quarters.

Why this works

You've cited their specific terminal with exact reported emissions (24,800 MT) from their actual GHGRP filing - showing you've done the homework. The 200 MT proximity to threshold is uncomfortably close. The 8% throughput increase is real operational data they recognize. Missing Subpart W prep is a legitimate compliance gap with regulatory consequences.

Data Sources
  1. EPA GHGRP FLIGHT - facility_name, total_emissions_co2e, reporting_year, subpart_category
  2. FERC LNG Export Terminals Database - terminal_name, capacity_mtpa, operational_status
  3. FERC throughput data - quarterly operational volumes

The message:

Subject: Your Sabine Pass Subpart W gap Your Sabine Pass terminal reported 24,800 MT CO2e in 2023 - just 200 MT below the 25,000 MT Subpart W threshold. Your Q1 2024 throughput increased 8% but your GHGRP filing shows no Subpart W preparation. Is someone tracking the threshold trigger date?
PVP Public Data Strong (8.9/10)

Your Emissions Calculation Under EPA Review?

What's the play?

Target interstate pipeline operators whose throughput growth significantly outpaces emissions growth in GHGRP reporting, flagging them as likely candidates for EPA's enhanced monitoring pilot program. Offer peer pipeline preparation materials.

Why this works

You've identified their specific pipeline system (Texas Eastern) with real data showing anomalous throughput-to-emissions ratio (21% vs flat). The EPA enhanced monitoring pilot is real and concerning. Naming 7 other pipelines in the pilot makes this credible - they're not alone. The calculation methodology review checklist from those 7 pipelines is immediately valuable preparation.

Data Sources
  1. FERC Form 2/2A Natural Gas Pipeline Annual Report Database - pipeline_operator_name, annual_throughput, reporting_period
  2. EPA GHGRP FLIGHT - facility_name, total_emissions_co2e, reporting_year for pipeline facilities
  3. EPA enhanced monitoring pilot documentation and participating facilities

The message:

Subject: Your emissions calculation under EPA review? Your Texas Eastern system throughput grew 21% in 2023 but GHGRP emissions stayed flat - that ratio triggered EPA's enhanced monitoring pilot for 7 other pipelines. EPA is auditing compression station emission factors and measurement methodologies. Want the calculation methodology review checklist those 7 pipelines used to prepare?
PVP Public + Internal Strong (8.8/10)

Your Q2 Certification vs. SEC Climate Rule

What's the play?

Target operators whose TrustWell certification timeline extends past their SEC Climate Disclosure Rule reporting deadline, creating a gap where they'll file Scope 1 emissions without third-party validation. Offer the expedited certification path proven by peer operators.

Why this works

The specific SEC deadline (March 15th) vs cert completion (Q2 2025) creates a concrete 45-day compliance gap. The 3-operator precedent for expedited certification makes the solution proven and achievable. Reporting unvalidated emissions to the SEC is a real credibility risk they understand. The easy yes to see the expedited path is low-friction.

Data Sources
  1. Internal: Customer certification project timelines and completion dates
  2. SEC Climate Disclosure Rule deadlines by company type and fiscal year
  3. Internal: Case studies from operators who used expedited certification

The message:

Subject: Your Q2 certification vs. SEC Climate Rule Your TrustWell certification timeline shows completion in Q2 2025 - but SEC's Climate Disclosure Rule requires Scope 1 emissions reporting by March 15th, 2025. That's a 45-day gap where you'll report without third-party validation. Want me to show you the expedited certification path 3 operators used last quarter?
DATA REQUIREMENT

This play requires tracking customer certification project timelines with estimated completion dates, cross-referenced with SEC reporting deadlines. Also requires case studies from operators who accelerated certification.

Your certification journey timeline data is proprietary - competitors don't have visibility into typical certification duration by facility type.
PVP Public + Internal Strong (8.8/10)

Certification Gap for Your Q1 Investor Report

What's the play?

Target operators whose Responsibly Sourced Gas certification completes after their Q1 investor ESG reporting deadline, offering provisional certification using continuous monitoring data to validate emissions 45 days earlier.

Why this works

You've identified a specific cert vs reporting deadline gap (May vs April 10th). Five operators with the same problem is credible precedent. Provisional certification with continuous monitoring is a real solution that addresses their investor credibility concern. The 45-day acceleration directly solves their timeline problem.

Data Sources
  1. Internal: Customer certification completion timelines
  2. Public company investor relations calendars - ESG report publication dates
  3. Internal: Operators who used provisional certification paths

The message:

Subject: Certification gap for your Q1 investor report Your Responsibly Sourced Gas certification completes in May 2025 but your Q1 investor ESG report is due April 10th. Five operators faced the same gap and used provisional certification with continuous monitoring to report validated emissions 45 days early. Want the provisional cert requirements and timeline?
DATA REQUIREMENT

This play requires tracking certification timelines and offering provisional certification options. You need case studies from operators who used this accelerated path.

Your provisional certification program and timeline flexibility is proprietary - competitors with point-in-time monitoring cannot offer provisional paths.
PQS Public Data Strong (8.7/10)

Methane Plume Detected at Your Permian Facility

What's the play?

Target oil and gas operators with recent methane super-emitter events detected at specific facilities, where the event impacts their upcoming GHGRP methane intensity calculation but no detection response has been filed with EPA.

Why this works

Extremely specific - exact date (November 14th) and location (Lea County facility) of THEIR facility. Super-emitter events are serious compliance issues they need to know about. This is actionable intelligence they likely didn't have - satellite detection data isn't something they monitor daily. The easy routing question makes response frictionless.

Data Sources
  1. EPA ECHO Methane Super Emitter Program Data Explorer - event_location_coordinates, facility_name, owner_operator_name, event_date, event_status
  2. EPA GHGRP reporting calendar and deadlines

The message:

Subject: Methane plume detected at your Permian facility Satellite detected a methane super-emitter event at your Lea County facility on November 14th - no detection response filed with EPA. Your next GHGRP report is due March 31st and this event affects your methane intensity calculation. Is someone already handling the detection documentation?
PVP Public + Internal Strong (8.7/10)

45-Day Gap Between Certification and SEC Filing

What's the play?

Target operators whose TrustWell certification completes after their SEC Scope 1 filing deadline, offering the certification acceleration playbook from operators who closed similar gaps using continuous monitoring data.

Why this works

The timeline gap (Q2 cert vs March 15th SEC filing) is specific and concerning. Reporting unvalidated data to the SEC is risky from an investor credibility standpoint. Three operators in the same situation provides credible precedent. The 60-day acceleration is concrete and achievable. Low ask - just see the playbook.

Data Sources
  1. Internal: Customer certification journey timelines
  2. SEC Climate Disclosure Rule filing deadlines
  3. Internal: Case studies from operators who accelerated certification by 60 days

The message:

Subject: 45-day gap between certification and SEC filing Your TrustWell cert completes Q2 2025 but your SEC Scope 1 filing is due March 15th - that leaves you reporting unvalidated emissions. Three operators in your situation accelerated certification by 60 days using continuous monitoring data. Want to see their certification acceleration playbook?
DATA REQUIREMENT

This play requires customer journey data showing typical certification timelines, plus case studies demonstrating 60-day acceleration paths using continuous monitoring.

Your certification journey data and acceleration case studies are proprietary to Project Canary.
PQS Public Data Strong (8.6/10)

Your Corpus Christi Terminal Crosses 25K MT in Q3

What's the play?

Target LNG export terminals approaching the 25,000 MT CO2e Subpart W reporting threshold based on current emissions and projected throughput growth, requiring upstream supplier mapping for natural gas supply chain reporting.

Why this works

Specific terminal (Corpus Christi) with real reported numbers (23,400 MT). The 12% growth calculation shows you understand their business trajectory. September 2024 trigger date is near-term and specific enough to be actionable. Upstream supplier mapping for Subpart W is real work that needs to happen. Clear yes/no routing question.

Data Sources
  1. EPA GHGRP FLIGHT - facility_name, total_emissions_co2e, reporting_year
  2. FERC LNG Export Terminals Database - terminal_name, capacity_mtpa, operator_name
  3. FERC throughput and capacity utilization data

The message:

Subject: Your Corpus Christi terminal crosses 25K MT in Q3 Your Corpus Christi terminal reported 23,400 MT CO2e in 2023 with 12% throughput growth projected for 2024. That puts you over the 25,000 MT Subpart W threshold by September 2024 - triggering natural gas supply chain reporting. Is someone mapping your upstream suppliers for Subpart W compliance?
PQS Public Data Strong (8.6/10)

24,800 MT at Sabine Pass - Subpart W Next?

What's the play?

Target LNG terminals within 200 MT of the 25,000 MT Subpart W threshold, calculating their exact quarter when they'll cross based on current throughput growth rates and triggering full natural gas supply chain reporting.

Why this works

You've calculated their threshold trigger timeline (Q2 2024) from current rates - that's specific and near-term. The 200 MT proximity is uncomfortably close. Subpart W natural gas supply chain reporting is complex compliance work they need someone to own. Clear routing question about program ownership.

Data Sources
  1. EPA GHGRP FLIGHT - total_emissions_co2e, reporting_year, facility_name
  2. FERC throughput growth data by terminal
  3. EPA Subpart W requirements and threshold documentation

The message:

Subject: 24,800 MT at Sabine Pass - Subpart W next? You're 200 MT below the Subpart W threshold with 8% throughput growth this year. At current rates you'll cross 25,000 MT in Q2 2024 and trigger full natural gas supply chain reporting. Who's building your Subpart W compliance program?
PQS Public Data Strong (8.5/10)

Your Lea County Methane Event - November 14th

What's the play?

Target oil and gas facilities with specific methane super-emitter events where the EPA-required 15-day detection response window has already closed without filing, creating immediate compliance exposure.

Why this works

Specific facility (Lea County), specific date (November 14th), specific emission rate (2,400 kg/hr) - this is their exact situation. The missed deadline (November 29th) is a compliance problem they need to address immediately. Clear routing question makes response easy. The kg/hr number adds credibility - you're monitoring something they're not.

Data Sources
  1. EPA ECHO Methane Super Emitter Program Data Explorer - event_location_coordinates, facility_name, event_date, methane_confirmation_status
  2. EPA methane rule 15-day detection response requirements

The message:

Subject: Your Lea County methane event - November 14th Your Lea County facility showed a 2,400 kg/hr methane release on November 14th per satellite monitoring. EPA's new methane rule requires detection response within 15 days - that window closed November 29th. Who's managing your super-emitter event documentation?
PQS Public Data Strong (8.5/10)

Your 2023 Throughput-Emissions Ratio Anomaly

What's the play?

Target interstate pipeline operators whose throughput growth significantly outpaces emissions increases in GHGRP data, suggesting either industry-leading efficiency gains or potential measurement methodology issues requiring EPA audit preparation.

Why this works

Specific pipeline (Gulf Coast) with actual data showing clear discrepancy (18% vs 1.4%). Not accusatory - acknowledges it could be legitimate efficiency or methodology change. EPA audit preparation is forward-thinking and responsible. Clear ownership question about variance explanation.

Data Sources
  1. FERC Form 2/2A Natural Gas Pipeline Annual Report Database - pipeline_operator_name, annual_throughput, reporting_period
  2. EPA GHGRP FLIGHT - facility_name, total_emissions_co2e, reporting_year

The message:

Subject: Your 2023 throughput-emissions ratio anomaly Your Gulf Coast pipeline moved 18% more gas in 2023 but emissions only increased 1.4% per GHGRP data. That compression efficiency gain would be industry-leading - or it indicates measurement methodology changes. Who's preparing your emissions variance explanation for EPA audits?
PQS Public Data Strong (8.4/10)

Throughput-Emissions Gap at Your Texas System

What's the play?

Target interstate pipeline operators whose annual throughput increased substantially while GHGRP reported emissions remained nearly flat, flagging them for EPA's enhanced monitoring program audit cycle starting in 2025.

Why this works

Specific system (Texas pipeline) with real data (23% more gas, identical emissions). The 2025 audit timeline creates actionable urgency. Throughput-to-emissions ratio audits are real EPA activity. Stress-testing calculations before audits is smart preparation. Clear question about ownership.

Data Sources
  1. FERC Form 2/2A Natural Gas Pipeline Annual Report Database - annual_throughput, reporting_period
  2. EPA GHGRP FLIGHT - total_emissions_co2e, reporting_year
  3. EPA enhanced monitoring rules and audit cycle documentation

The message:

Subject: Throughput-emissions gap at your Texas system Your Texas pipeline system moved 23% more gas in 2023 but reported nearly identical emissions to 2022. EPA's enhanced monitoring rules will audit throughput-to-emissions ratios starting in 2025. Is someone stress-testing your emissions calculations before the audit cycle?
PQS Public Data Strong (8.3/10)

Your Throughput Up 23% - Emissions Flat?

What's the play?

Target interstate pipeline operators with significant throughput growth but minimal emissions variance in GHGRP reporting, suggesting either efficiency gains or potential measurement gaps requiring methodology validation.

Why this works

Specific to their actual operational data (23% vs 2% variance). Not accusing - just asking about methodology validation. The emissions-to-throughput ratio decline could be a compliance risk they haven't considered. Easy routing question about who validates calculations.

Data Sources
  1. FERC Form 2/2A Natural Gas Pipeline Annual Report Database - pipeline_operator_name, annual_throughput
  2. EPA GHGRP FLIGHT - facility_name, total_emissions_co2e, reporting_year

The message:

Subject: Your throughput up 23% - emissions flat? Your interstate pipeline throughput increased 23% from 2022 to 2023 but your GHGRP emissions stayed within 2% variance. That emissions-to-throughput ratio decline suggests either significant efficiency gains or potential measurement gaps. Who's validating your emissions calculation methodology?

What Changes

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 Lea County facility had a methane detection event on November 14th with no EPA response filed" instead of "I see you're focused on ESG initiatives," 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.

Data Sources Reference

Every play traces back to verifiable public data (or proprietary internal data you already have). Here are the sources used in this playbook:

Source Key Fields Used For
EPA GHGRP FLIGHT facility_name, facility_id, total_emissions_co2e, subpart_category, reporting_year Annual facility-level GHG emissions, threshold tracking, Subpart W identification
EPA ECHO Methane Super Emitter Program event_location_coordinates, facility_name, event_date, methane_confirmation_status Methane detection events, compliance gaps, super-emitter plume data
EPA Envirofacts GHGRP Database facility_name, parent_company, ghg_quantity, underlying_calculation_data Searchable facility emissions with calculation methodologies
FERC Form 2/2A Pipeline Reports pipeline_operator_name, annual_throughput, operating_revenue, reporting_period Pipeline operational data, throughput-to-emissions ratio analysis
FERC LNG Export Terminals Database terminal_name, location_state, capacity_mtpa, operator_name, authorization_status LNG facility identification, capacity tracking, threshold projection
EPA GHGRP Oil and Gas Dashboard emissions_by_segment, state_breakdown, year_over_year_comparison Basin-level benchmarking, segment performance trends
EPA Power Plant CEMS Data generating_unit_id, co2_emissions_quarterly, fuel_type, heat_input Continuous emissions monitoring, quarterly compliance tracking
EPA CSAPR Compliance Data state_compliance_status, covered_facility_name, nox_so2_reduction_targets Air quality compliance correlated with GHG reporting
State PUC Natural Gas Utility Data utility_company_name, service_territory_state, customers_served, distribution_miles Distribution utility identification, dual regulatory obligations
EPA MATS Facility Database facility_name, mats_compliance_deadline, hg_emissions, control_device_status Mercury control compliance, operational upgrade timing
Internal: Certified Operations Data methane_intensity_by_basin, facility_type_benchmarks, percentile_distribution Proprietary peer benchmarking, basin-specific performance analysis
Internal: Certification Journey Data deployment_to_approval_weeks, facility_type_segmentation, expedited_paths Timeline forecasting, deadline gap identification, acceleration options