Blueprint Playbook for Verusen

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 Verusen SDR Email:

Subject: Quick question about your supply chain operations Hi [Name], I noticed you're managing a large manufacturing operation with multiple facilities. We work with companies like yours to optimize their inventory and reduce costs. Our platform helps streamline MRO operations and improve visibility across your systems. Would love to set up a brief call to discuss how we might help. Best regards, [Your 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 facility at 1234 Industrial Pkwy received EPA violation #2024-XYZ on March 15th" (government database with record number)

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.

◆

Verusen PQS Plays: Mirroring Exact Situations

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.

PQS Public Data Strong (8.3/10)

Play: Equipment-Failure Incidents on Low-Production Deepwater Platforms

What's the play?

BSEE incident records (equipment-related, trailing 24 months) normalized by production volume reveal within-fleet outlier platforms carrying a disproportionate share of equipment incidents on a small share of barrels. When 3 of 14 platforms account for 58% of equipment-related INCs but only 11% of barrels, and all three sit in 1,000+ feet of water where resupply requires a boat run, the signal points to spare parts availability and lead-time constraints specific to deepwater logistics. This targeting joins BSEE incident records (PINC/regulation codes), BOEM Platform Structures (water depth, structure type, operator status), and OGOR production data aggregated to platform.

Why this works

Offshore operators track incidents per platform but not normalized against their own production — so a within-fleet outlier (high incidents on low barrels) at deep water depths is a number their operations team has never seen. The water depth plus the boat-run logistics line lands exactly on their resupply headache: shallow platforms can swap parts on a supplier truck; deepwater platforms depend on supply boats and helicopter resupply, making the cost of a missing spare exponential. The data is public and traceable in under a minute, which signals credibility.

Data Sources
  1. BSEE Data Center - platform_id, platform_name, operator, location, water_depth, structure_type, compliance_incidents, incident_date, incident_cause, regulation_code, pinc_code
  2. BOEM Data Center - platform_id, operator_name, lease_number, location, platform_status, structure_type, production_data
  3. OGOR (Oil and Gas Operations Report) - lease_id, platform_id, production_volumes, well_count, well_status

The message:

Subject: 9 INCs on [Platform A] [Platform A] drew 9 of your 31 equipment-related BSEE INCs between March 2024 and February 2026 while producing 4% of your barrels. It sits in 1,850 feet of water, 95 miles out, and 5 of the 9 INCs cite production safety system components (P-series PINCs) that [Platform D] and [Platform E] also run. Want the 9 INCs matched to the sister platforms running the same equipment?
PQS Public Data Strong (8.2/10)

Play: Equipment-Defect Citations Across Sister Mines

What's the play?

MSHA citations for running equipment with uncorrected defects (30 CFR 56/57.14100) rolled up across a single operator's multiple active mines within 12 months signal a cross-site spare parts availability failure. When 6 of 9 sister mines are cited under the same standard, the common thread is the repair part that was not on any shelf, not 6 separate local safety lapses. This targeting uses MSHA Violations records, MSHA Mines controller/operator roll-up with active status and lat/long, and USGS Mineral Resources Database for operator footprint and production scale.

Why this works

Mining operators are accountable for equipment defect citations across their fleet and acutely aware when the same failure pattern repeats at multiple sites 140 miles apart. The data shows them a pattern they track by mine but not by standard across their controller ID — making the insight genuinely new. The specificity (named mines, distances, S&S flags) proves you did the work, which breaks through generic outreach. The inference from citations to parts unavailability is honest (60-75% confidence) and lets them verify it themselves in their storerooms.

Data Sources
  1. MSHA Mine Data Retrieval System - mine_id, mine_name, operator, current_controller_name, current_mine_status, latitude, longitude, active_status
  2. MSHA Violations - section_of_act (56.14100, 57.14100), violation_issue_date, significance_and_substantial_flag
  3. USGS Mineral Resources Database - mine_name, operator, location, commodity, production_volume, facility_type

The message:

Subject: 140 miles, same defect [Mine A] and [Mine B] both drew S&S citations in the 12 months ending February 2026 for running equipment with uncorrected defects (57.14100), and so did 4 more of your 9 active mines. Those two sites run the same underground haulage class and sit 140 miles apart, which puts the same repair parts on two separate storeroom lists. Want the 6 citations with the equipment named in each?

Verusen PVP Plays: Delivering Immediate Value

These messages provide actionable intelligence before asking for anything. The prospect can use this value today whether they respond or not.

PVP Public + Internal Strong (9.3/10)

Play: Open Defect Citation Resolved via Idled-Site Spares

What's the play?

An open S&S equipment defect citation at an active mine, matched to an idled sister mine that ran the same equipment and shut down within 24 months, creates a 'missing piece found in your own storeroom' moment. MSHA Violations narrative text names the equipment (e.g., CAT 785 haul truck), MSHA Mines status dates confirm the idled mine's shutdown, and Verusen's aggregated redeployment data shows that mobile-equipment brake and hydraulic parts are the most frequently matched component classes across multi-site redeployment engagements. This combines public pain-proving data (open defect, idled sister fleet) with proprietary redeployment outcome data to make an irrefutable business case.

Why this works

A VP of Supply Chain seeing an open S&S brake defect at their mine can call the idled sister mine's storeroom today and order brake parts they already own — without replying to your email. The fact that you matched the two sites, the equipment class, and the defect to the idled storeroom proves you did the work. The brake-and-hydraulics ranking comes from Verusen's redeployment outcomes, which is proprietary and competitive. This is the most powerful play because it hands the operator a way to abate a live regulatory finding using inventory they already own.

Data Sources
  1. MSHA Violations - citation_number, violation_date, violation_narrative, equipment_name, regulation_code, significance_and_substantial_flag
  2. MSHA Mine Data Retrieval System - mine_id, mine_name, operator, current_controller_name, current_mine_status, current_status_date, latitude, longitude
  3. BOEM Data Center - platform_id, operator_name, lease_number, location, platform_status, structure_type, removed_structures_history, removal_date

The message:

Subject: [Mine B]'s brake defect, [Idled Mine]'s storeroom MSHA cited [Mine B] on September 9, 2025 ([citation number]) for keeping a CAT 785 haul truck with a defective service brake in service, and [Idled Mine] - 90 miles away and Intermittent since April 14, 2025 - ran the same CAT 785 fleet until it idled. Across the 11 multi-site fleets where we have run idled-site redeployment, 31% of idled storeroom value matched a live sister-site requisition within 12 months, and mobile-equipment brake and hydraulic parts were the most frequent match. Want the full idled-to-active pair list for your 7 active mines?
DATA REQUIREMENT

Aggregated redeployment outcomes from 10+ multi-site mining and offshore customers: redeployable share of idled storeroom value (31% illustrative), transfer value realized, and ranking of most-frequently matched component classes (mobile-equipment brake and hydraulic illustrative).

Public side requires MSHA Violations narrative text naming the equipment at both the cited active mine and the idled mine, plus MSHA Mines status dates and lat/long for distance. The brake-and-hydraulics ranking and redeployable-share percentage are drawn from Verusen's own multi-site redeployment engagements (e.g., 17-rig fleet) and are aggregated across 10+ entities. Replace illustrative numbers with Verusen's actual aggregate before send.
PVP Public + Internal Strong (8.7/10)

Play: Stranded Spares at Idled Sister Sites

What's the play?

MSHA Mines status change (Intermittent / Temporarily Idled / NonProducing in trailing 24 months) paired to active sister mines of the same operator running the same equipment class within geographic proximity creates a high-confidence signal of stranded storeroom inventory. Idled mines retain their spare parts inventory, which is rarely fully liquidated at closure. When an idled mine and three active sister mines all run gold-ore crushing and haul-truck equipment within 90-210 miles, the operator is sitting on critical spares they already own that can supply active production, freeing working capital and accelerating emergency repairs. This targeting uses MSHA Mines status history with lat/long, USGS Mineral Resources Database for commodity/facility type matching, BOEM removed-structures history for offshore, and Verusen's aggregated redeployable-share outcome data (31% of idled storeroom value matched to active-site requisitions within 12 months across 11 multi-site mining and offshore fleets).

Why this works

Operators know which of their sites are idled but do not systematically cross-check idled storerooms against active demand — it is invisible until someone thinks to call the idled site. The three named active mines paired to the idled site with distances and shared equipment class turns that invisible inventory into actionable intelligence. The 31% redeployable figure is Verusen's own engagement data drawn from 11 customer redeployment engagements, which a competitor cannot cite and no Google search can surface. This positions Verusen as the expert in cross-facility parts reuse, and hands the operator a storeroom sweep they can start today.

Data Sources
  1. MSHA Mine Data Retrieval System - mine_id, mine_name, operator, current_controller_name, current_mine_status, current_status_date, latitude, longitude, primary_sic, mine_type
  2. USGS Mineral Resources Database - mine_name, operator, location, commodity, mine_status, production_volume, facility_type
  3. BOEM Data Center - platform_id, operator_name, lease_number, location, platform_status, structure_type, removed_structures_history, removal_date

The message:

Subject: 3 active sites for [Idled Mine]'s spares [Idled Mine] has been Intermittent with MSHA since April 14, 2025 while [Mine B] (90 miles), [Mine C] (140 miles), and [Mine D] (210 miles) stayed Active and run the same gold-ore crushing and haul-truck class. Across the 11 multi-site mining and offshore fleets where we have run idled-site redeployment, 31% of idled storeroom value matched a live sister-site requisition within 12 months. Want the 3-pair match sheet by equipment class?
DATA REQUIREMENT

Aggregated redeployable-share outcome data from 10+ multi-site mining and offshore redeployment engagements: the share of idled-site storeroom value matched to active-site requisitions within 12 months (31% is illustrative), transfer value realized, and avoided purchase spend by equipment class.

This aggregate is drawn from Verusen's cross-facility parts-sharing engagements (e.g., 17-rig fleet case study) and is aggregated across 10+ entities. It is not identifiable to any single customer and would not embarrass customers if shared. Replace the 31% and fleet count with Verusen's actual aggregate before send.
◆

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 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.

Data Sources Reference

Every play traces back to verifiable public data. Here are the sources used in this playbook:

Source Key Fields Used For
MSHA Mine Data Retrieval System mine_id, mine_name, operator, current_controller_name, current_operator_name, current_mine_status, current_status_date, latitude, longitude, primary_sic, mine_type, commodities, employment_data, inspection_date, citation_count, violation_severity, accident_date, injury_type, production_data Identifying mining operators with repeat equipment-defect citations across sister mines, status changes to Intermittent/Idled/NonProducing, and pairing active mines to idled sites by commodity and geography
MSHA Violations section_of_act, violation_issue_date, violation_narrative, equipment_name, citation_number, regulation_code, significance_and_substantial_flag, mine_id Filtering equipment-defect citations (30 CFR 56/57.14100), extracting named equipment from narrative text, and identifying open S&S defects at active mines
BSEE Data Center platform_id, platform_name, operator, location, water_depth, structure_type, production_volumes, well_count, well_status, pipeline_data, compliance_incidents, facility_measurement_points, incident_date, incident_cause, regulation_code, pinc_code Identifying offshore platforms with equipment-related incidents, normalizing incident frequency against production volume, and mapping incident PINC codes to shared equipment across sister platforms
BOEM Data Center platform_id, operator_name, lease_number, location, platform_status, structure_type, production_data, inspection_system, removed_structures_history, removal_date Retrieving platform operator registry, production volumes aggregated by platform, platform structure type, and removed/decommissioned structures within 24 months
USGS Mineral Resources Database mine_name, operator, location, commodity, mine_status, production_volume, facility_type, geological_features Matching commodity and facility type (e.g., gold-ore crushing, haul-truck class) between idled and active sister mines, identifying high-volume producers, and confirming operator footprint
OGOR (Oil and Gas Operations Report) lease_id, platform_id, production_volumes, well_count, well_status, facility_type, operator_id Aggregating production volumes to platform level to normalize BSEE incident frequency by production share