Blueprint Playbook for WeAreProject

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

Subject: Quick question about your IT infrastructure Hi [First Name], I noticed your company is growing and wanted to reach out. WeAreProject has helped over 380 companies modernize their IT infrastructure with our comprehensive managed services. We offer 24/7 SOC monitoring, cloud migration expertise, and digital workplace solutions. I'd love to show you how we've helped similar companies in your industry reduce costs and improve security. Are you free for a quick 15-minute call next week? Best, Sales Rep

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.

WeAreProject 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.9/10)

Hazmat Carriers with Accident Clustering and Poor Safety Ratings

What's the play?

Target hazmat motor carriers whose FMCSA safety ratings dropped from Satisfactory to Conditional after experiencing 3+ accidents in 24 months, combined with OSHA citations for vehicle/equipment violations. This pattern reveals systemic fleet management failures.

Why this works

You're identifying a specific failure pattern (brake-related incidents on a specific route) that proves you understand their operational problem at a forensic level. The safety rating downgrade triggers immediate business consequences (quarterly audits, contract losses), creating urgency. Most vendors talk generically about "fleet management" - you're showing them the exact data trail that matters to DOT auditors.

Data Sources
  1. FMCSA SAFER System - carrier_name, USDOT_number, safety_rating, accident_record, inspection_frequency
  2. OSHA Establishment Search Database - violation_type, citation_history, penalty_amount

The message:

Subject: 3 hazmat incidents in 6 months on Route 95 Your trucks had 3 DOT-reportable hazmat incidents on Route 95 between June and November - all involving brake failures. FMCSA shows your safety rating dropped from Satisfactory to Conditional on December 1st. Is someone investigating the brake maintenance pattern?
PQS Public Data Strong (8.7/10)

Non-Compliant UWWTD Treatment Plants with Capacity Overload

What's the play?

Target municipal water utilities operating at 120%+ design capacity while showing non-compliance status in EU Waterbase UWWTD data. This dual pressure (regulatory penalties + operational failure risk) indicates urgent SCADA/operational technology modernization needs.

Why this works

You're citing the exact capacity metric (142%) from public EU compliance data, showing you understand both their operational constraint and regulatory deadline. Water utility managers know their capacity issues but rarely see someone connect that to the specific UWWTD 120% threshold. The December 2026 deadline creates a concrete timeline for action.

Data Sources
  1. Waterbase - UWWTD (Urban Waste Water Treatment Directive Data) - treatment_plant_name, compliance_status, capacity_vs_load, population_equivalent, country

The message:

Subject: Your Napoli plant at 142% capacity Your Napoli wastewater treatment plant is operating at 142% of design capacity according to December EU compliance data. UWWTD requires capacity upgrades within 24 months when exceeding 120% - your deadline is December 2026. Is someone already scoping the expansion project?
PQS Public Data Strong (8.6/10)

FDA Warning Letter Recipients Approaching QMSR Deadline

What's the play?

Target medical device manufacturers who received FDA Warning Letters in 2023-2024 and face the QMSR (Quality Management System Regulation) effective date in February 2026. The combination of existing compliance debt plus new regulatory requirements creates urgent QMS/IT modernization pressure.

Why this works

You're demonstrating knowledge of the exact FDA process timeline (15 business days for CAP response) and connecting their specific Warning Letter date to the broader QMSR deadline. Quality directors live in fear of FDA enforcement - showing you understand both their past violations and upcoming regulatory changes positions you as someone who understands their compliance world.

Data Sources
  1. FDA Inspection Classification Database - facility_name, warning_letter_issued, inspection_date, 483_observations, product_type

The message:

Subject: Your October FDA letter and March QMSR deadline Your facility received an FDA Warning Letter on October 22nd for medical device quality system violations. The QMSR requires corrective action plan submission within 15 business days - your deadline is March 15th. Is someone already drafting the CAP response?
PQS Public Data Strong (8.4/10)

SEVESO Facilities with Recent Major Accidents Facing Compliance Deadlines

What's the play?

Target chemical and pharmaceutical facilities classified under SEVESO III that experienced major accidents in the past 24 months. These facilities face immediate regulatory scrutiny and mandatory infrastructure modernization to prevent recurrence - accident history triggers compliance audits requiring IT/safety system upgrades.

Why this works

You're citing the exact facility location, incident date, and regulatory deadline from EU accident reporting systems. The 46-day timeline to complete incident investigation and safety report creates legitimate urgency. Most safety consultants talk generically about "compliance" - you're showing them you tracked their specific incident in eMARS and know their exact filing deadline.

Data Sources
  1. eSPIRS (Seveso Plants Information Retrieval System) - operator_name, establishment_address, facility_classification
  2. eMARS (Major Accidents Reporting System) - accident_date, accident_type, substance_involved, injuries_fatalities

The message:

Subject: Your Bari plant's March incident and April deadline Your Bari facility had a major accident on March 14th requiring a SEVESO safety report update by April 30th. That's 46 days to complete incident investigation, root cause analysis, and regulatory submission. Is someone already coordinating the safety report revision?

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
FMCSA SAFER System carrier_name, USDOT_number, safety_rating, accident_record, hazmat_operations Hazmat carriers with accident clustering and safety rating downgrades
OSHA Establishment Search employer_name, violation_type, citation_history, penalty_amount, inspection_date Manufacturing facilities with safety violations requiring infrastructure upgrades
Waterbase - UWWTD treatment_plant_name, compliance_status, capacity_vs_load, population_equivalent Water utilities with capacity overload and compliance violations
FDA Inspection Database facility_name, warning_letter_issued, 483_observations, inspection_date Medical device/pharma manufacturers with quality system violations
eSPIRS (Seveso Plants) operator_name, establishment_address, facility_classification, activity_type Chemical/pharma facilities under major accident regulations
eMARS (Accident Reports) accident_date, facility_name, substance_involved, environmental_impact Facilities with recent major accident history requiring system upgrades