Blueprint Playbook for CONET

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

Subject: Accelerate Your Digital Transformation Hi [First Name], I noticed your company is growing rapidly and investing in digital transformation initiatives. At CONET, we help enterprises like yours modernize IT infrastructure and implement SAP solutions that drive operational efficiency. We've worked with leading companies in manufacturing and financial services to deliver 40+ years of consulting expertise. Our clients see improved system uptime, faster project delivery, and reduced IT costs. Would you be open to a quick 15-minute call next week to discuss how we can support your digital transformation goals? Best regards, [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 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.

CONET 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 (9.3/10)

FDA Pharma Facilities with GMP Violations + Facility Expansion Permits

What's the play?

Target pharmaceutical manufacturers who received recent FDA Form 483 GMP violations and simultaneously filed facility expansion permits. These companies face a critical timeline conflict: new capacity cannot be validated until violations are closed.

Why this works

You're surfacing a timeline risk they may not have connected yet. The specificity of knowing exact violation dates, permit filings, and facility addresses proves you understand their regulatory environment. This isn't generic compliance talk - it's their actual operational bottleneck.

Data Sources
  1. FDA Drug Establishment Database (eDRLS) - facility_name, facility_address, gmp_compliance_status, inspection_history, regulatory_citations
  2. EPA ECHO - permit_status, facility_expansions

The message:

Subject: Your Edison facility has 3 GMP violations + expansion permit Your Edison, NJ facility received 3 Form 483 GMP violations on November 12th, 2024. You filed a 45,000 sq ft expansion permit on December 3rd - new space can't be validated until violations are closed. Is someone coordinating the remediation timeline with the expansion schedule?
PQS Public + Internal Strong (9.2/10)

EPA Chemical Plants with Violations + Compliance Remediation Budget Sizing

What's the play?

Target chemical manufacturing facilities with recent EPA Clean Air Act violations and cross-reference their publicly filed compliance budgets against CONET's benchmarked remediation cost data. Identify facilities where budgeted amounts fall significantly short of typical remediation requirements.

Why this works

You're providing financial intelligence they need but may not have calculated yet. The budget gap insight creates immediate urgency - they either need to find more funding or reprioritize remediation activities. This shifts the conversation from "do we need help?" to "how do we close this gap?"

Data Sources
  1. EPA ECHO - facility_name, compliance_status, violation_history, enforcement_actions, facility_type
  2. Internal CONET Data - aggregated_remediation_budgets, typical_project_timelines

The message:

Subject: Your Baton Rouge facility has 4 CAA violations EPA cited your Baton Rouge plant with 4 Clean Air Act violations on September 18th, 2024. Your FY2025 budget filed November 2024 allocated $340,000 for environmental compliance - that's 60% below the typical remediation cost for 4+ violations. Who's managing the compliance budget and remediation timeline?
DATA REQUIREMENT

This play requires aggregated project budgets and timelines from 15+ EPA compliance remediation projects at chemical manufacturing facilities, correlated by violation type, facility size, and enforcement action severity.

Combined with public EPA violation data to identify budget shortfalls. This synthesis is unique to CONET's 40-year track record.
PQS Public + Internal Strong (9.1/10)

Defense Contractors with Expiring Security Clearances + Active Contract Renewals

What's the play?

Target defense contractors with facility security clearances expiring 6-9 months before scheduled contract renewal boards. Cross-reference FPDS contract data with DCSA clearance timelines to identify contractors at risk of missing renewal deadlines due to lapsed clearances.

Why this works

You're flagging an operational risk that could cost them millions in contract revenue. The specificity of knowing their exact clearance ID, expiration date, and contract renewal schedule proves this isn't generic outreach. This is a time-sensitive operational gap they need to address immediately.

Data Sources
  1. Federal Procurement Data System (FPDS) - contractor_name, cage_code, contract_end_date, facility_security_clearance, contract_value
  2. Internal CONET Data - aggregated_clearance_renewal_timelines

The message:

Subject: Your facility clearance expires before contract renewal Your Top Secret Facility Clearance (FSO-2347) expires March 15th, 2025. Your DoD contract 47-ALPHA-2024 renewal decision is scheduled for April 2025 - 3 weeks after clearance lapse. Is someone already handling the FSO recertification timeline?
DATA REQUIREMENT

This play requires aggregated facility security clearance renewal timelines and process duration data from 20+ defense contractor transformation projects, correlated with contract types and clearance levels.

Combined with FPDS contract data to identify timing conflicts. This correlation is proprietary to CONET.
PQS Public + Internal Strong (8.9/10)

FDIC Banks Post-Merger with Legacy System Integration Timelines

What's the play?

Target FDIC-insured banks that have completed mergers with FDIC-mandated system integration deadlines. Cross-reference merger completion dates with typical integration timelines from CONET's banking projects to identify institutions with compressed timelines.

Why this works

You're providing a reality check on their integration timeline based on real-world data from similar projects. The specificity of knowing branch counts, deposit amounts, and regulatory deadlines proves you understand banking M&A complexity. This creates urgency around a regulatory mandate they cannot miss.

Data Sources
  1. FDIC BankFind Suite API - institution_name, total_assets, merger_date, branch_count
  2. Internal CONET Data - aggregated_integration_timelines, system_consolidation_budgets

The message:

Subject: Your core banking migration deadline is Q2 2025 Your merger with Cornerstone Bank closed October 2024 with FDIC-mandated system integration by June 30th, 2025. That's 6 months to migrate 47 branches and $2.1B in deposits onto a single core platform. Who's managing the integration timeline?
DATA REQUIREMENT

This play requires aggregated system integration project timelines, budgets, and success metrics from 15+ FDIC-insured bank merger/acquisition IT consolidation projects, segmented by combined asset size.

Combined with FDIC merger data to benchmark realistic timelines. This benchmarking data is proprietary to CONET.
PQS Public Data Strong (8.8/10)

Electric Utilities with Aging SCADA Systems + NERC Violation History

What's the play?

Target electric power generation facilities with SCADA systems commissioned pre-2005 that have received NERC CIP-007 cybersecurity violations in the past 24 months. These facilities face escalating enforcement risk from aging infrastructure combined with documented compliance failures.

Why this works

You're connecting two public data points - system age and violations - to surface a pattern they may not have explicitly acknowledged. The specificity of knowing substation names, installation years, and violation types proves you understand critical infrastructure operations. NERC violations carry serious penalties, creating urgency.

Data Sources
  1. EIA Form 860 (Generator Data) - plant_name, operator_name, commissioning_year, nameplate_capacity, nerc_region
  2. EPA ECHO - violation_history, enforcement_actions

The message:

Subject: Your SCADA system is 17 years old with 2 NERC violations Your Allen Substation SCADA infrastructure (installed 2008) is 17 years old. NERC cited you twice in 2024 for CIP-007 compliance failures - aging systems are the primary cause. Who's managing the SCADA modernization timeline?
PQS Public Data Strong (8.7/10)

FDA Pharma Facilities - Expansion Blockage Variant

What's the play?

Alternative message for the same segment - pharmaceutical manufacturers with GMP violations blocking facility expansion plans. This variant leads with the construction permit to catch executives focused on growth initiatives.

Why this works

Leading with the expansion permit appeals to growth-minded executives who may not be directly involved in compliance remediation. It reframes violations as a blocker to revenue-generating capacity expansion rather than just a compliance issue.

Data Sources
  1. FDA Drug Establishment Database (eDRLS) - facility_name, gmp_compliance_status, regulatory_citations
  2. EPA ECHO - permit_status, facility_expansions

The message:

Subject: 3 Form 483s blocking your facility expansion FDA cited your Edison plant with 3 GMP violations on November 12th. Your December 3rd permit for 45,000 sq ft expansion can't proceed to validation until citations close. Who's leading the remediation effort?
PQS Public + Internal Strong (8.7/10)

EPA Chemical Plants - Budget Gap Focus

What's the play?

Alternative message for chemical plants with EPA violations - this variant emphasizes the financial gap between budgeted compliance spend and typical remediation costs.

Why this works

CFOs and finance leaders respond to budget variance data. By leading with the $510K gap, you're speaking their language and creating a financial planning urgency separate from compliance pressure.

Data Sources
  1. EPA ECHO - facility_name, violation_history, enforcement_actions
  2. Internal CONET Data - aggregated_remediation_budgets, typical_project_timelines

The message:

Subject: $340K budgeted for 4 EPA violations Your Baton Rouge plant received 4 CAA violations on September 18th. Your compliance budget shows $340,000 allocated, but typical 4-violation remediation runs $850,000-$1.2M. Is someone already working on the budget gap?
DATA REQUIREMENT

This play requires benchmarking data on typical remediation costs for similar violation profiles from CONET's past projects.

Combined with public budget filings to identify shortfalls. This cost intelligence is proprietary.
PQS Public + Internal Strong (8.6/10)

FDIC Banks - Migration Complexity Focus

What's the play?

Alternative message for post-merger banks - this variant emphasizes the operational complexity of migrating 47 branches on incompatible core systems.

Why this works

IT directors and operations leaders respond to technical complexity warnings. Leading with incompatible systems and deposit risk appeals to their operational concerns.

Data Sources
  1. FDIC BankFind Suite API - institution_name, branch_count, total_assets
  2. Internal CONET Data - system_consolidation_timelines

The message:

Subject: 47 branches, 6 months to integrate FDIC requires your Cornerstone merger integration complete by June 30th, 2025. 47 branches running on incompatible core systems with $2.1B deposits at risk if you miss the deadline. Is someone already managing the migration plan?
DATA REQUIREMENT

This play requires understanding of typical bank integration timelines and risk factors from CONET's banking projects.

Combined with FDIC merger data to assess deadline feasibility.
PQS Public Data Strong (8.5/10)

Electric Utilities - CIP Violations Emphasis

What's the play?

Alternative message for utilities with SCADA violations - this variant leads with the NERC violations to appeal to compliance-focused leaders.

Why this works

Compliance officers and regulatory affairs teams track NERC violations closely. Leading with CIP-007 violations creates immediate recognition and urgency around penalty escalation risk.

Data Sources
  1. EIA Form 860 (Generator Data) - plant_name, commissioning_year
  2. EPA ECHO - violation_history, enforcement_actions

The message:

Subject: 2 NERC CIP violations at Allen Substation Allen Substation received 2 NERC CIP-007 violations in 2024 for cybersecurity controls. Your SCADA system there has been in service since 2008 - 17 years without major upgrades. Is someone already handling the remediation plan?
PQS Public + Internal Strong (8.4/10)

Defense Contractors - Revenue Risk Focus

What's the play?

Alternative message for defense contractors - this variant emphasizes the financial risk of contract disqualification due to lapsed clearances.

Why this works

CFOs and business development leaders respond to revenue risk warnings. The $4.2M contract value makes the clearance lapse a business continuity issue, not just an administrative task.

Data Sources
  1. Federal Procurement Data System (FPDS) - contractor_name, contract_value, contract_end_date
  2. Internal CONET Data - clearance_renewal_timelines

The message:

Subject: 3-week gap between clearance and contract decision Your FSO-2347 clearance lapses March 15th, but your $4.2M contract renewal board meets April 8th. A lapsed clearance automatically disqualifies you from the renewal evaluation. Who's managing the clearance renewal timeline?
DATA REQUIREMENT

This play requires understanding of DCSA clearance renewal timelines and disqualification rules from CONET's defense contractor experience.

Combined with FPDS contract data to identify revenue at risk.

CONET 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.1/10)

Budget Model for CAA Violations

What's the play?

Deliver a pre-built remediation cost model that shows the exact budget gap and categorizes which violations can be resolved with operational changes vs. capital investment. This gives CFOs and compliance leaders immediate financial planning intelligence.

Why this works

You're solving their immediate problem - budget justification - before asking for anything. The categorization of operational vs. capital solutions helps them prioritize and make faster decisions. This positions CONET as a strategic advisor, not a vendor.

Data Sources
  1. EPA ECHO - facility_name, violation_history
  2. Internal CONET Data - remediation_cost_benchmarks, solution_categorization

The message:

Subject: Budget model for your 4 CAA violations I built a remediation cost model for your Baton Rouge plant's 4 Clean Air Act violations. It shows the $510,000 budget gap and identifies which violations can be resolved with operational changes vs. capital investment. Want the cost model?
DATA REQUIREMENT

This play requires remediation cost benchmarking data from past EPA violation projects, with categorization by solution type (operational vs. capital).

This cost intelligence combined with public violation data creates unique financial planning value.
PVP Public Data Strong (9.1/10)

Parallel-Path Remediation Timeline

What's the play?

Deliver a pre-built timeline that shows how to remediate GMP violations while keeping the facility expansion on schedule. The timeline includes FDA response deadlines, validation windows, and the earliest construction start date.

Why this works

You're solving their biggest fear - expansion delays - with a concrete timeline they can use today. The parallel-path approach shows expertise in managing competing priorities, which is exactly what they need. This demonstrates capability without requiring a commitment.

Data Sources
  1. FDA Drug Establishment Database (eDRLS) - facility_name, gmp_compliance_status, regulatory_citations
  2. EPA ECHO - permit_status, facility_expansions

The message:

Subject: Remediation timeline for your Edison expansion I built a parallel-path timeline that closes your 3 Form 483 violations while keeping your 45,000 sq ft expansion on schedule. It includes FDA response deadlines, validation windows, and the earliest date you can proceed with construction. Want the timeline?
PVP Public + Internal Strong (9.0/10)

Integration Roadmap for 47-Branch Migration

What's the play?

Deliver a pre-built 6-month integration roadmap that prioritizes the highest-deposit branches first and includes fallback options for technical delays. This gives IT directors and project managers immediate planning value.

Why this works

You're providing a concrete roadmap with risk mitigation built in. The prioritization approach (highest-deposit branches first) shows you understand banking operations and regulatory priorities. This demonstrates CONET's methodology without requiring a sales conversation.

Data Sources
  1. FDIC BankFind Suite API - institution_name, branch_count, total_assets
  2. Internal CONET Data - integration_roadmap_templates, risk_mitigation_strategies

The message:

Subject: Integration roadmap for 47-branch migration I built a 6-month integration roadmap for migrating your 47 Cornerstone branches by the June 30th FDIC deadline. It prioritizes the 12 highest-deposit branches first and includes fallback options if you hit technical delays. Want the roadmap?
DATA REQUIREMENT

This play requires integration roadmap templates and risk mitigation strategies from CONET's banking merger projects.

Combined with FDIC branch data to create customized prioritization. This methodology is proprietary.
PVP Public + Internal Strong (8.9/10)

Clearance Renewal Timeline for Contract Sync

What's the play?

Deliver a pre-built clearance renewal timeline that includes all DCSA submission deadlines, inspection windows, and contingency buffers to avoid the March-April gap between clearance expiration and contract renewal.

Why this works

You're providing operational risk mitigation with specific deadlines they can act on today. The timeline prevents revenue loss from contract disqualification. This demonstrates CONET's understanding of defense contractor operations and DCSA processes.

Data Sources
  1. Federal Procurement Data System (FPDS) - contractor_name, contract_end_date, facility_security_clearance
  2. Internal CONET Data - dcsa_submission_timelines, clearance_renewal_process

The message:

Subject: Clearance renewal checklist for contract 47-ALPHA I built a clearance renewal timeline for FSO-2347 that syncs with your April 8th contract board. It includes all DCSA submission deadlines, inspection windows, and contingency buffers to avoid the March-April gap. Want me to send the timeline?
DATA REQUIREMENT

This play requires understanding of DCSA clearance renewal process timelines and critical deadlines from CONET's defense contractor projects.

Combined with FPDS contract data to build customized timelines. This process knowledge is proprietary.
PVP Public Data Strong (8.9/10)

SCADA Modernization Plan for 24/7 Uptime

What's the play?

Deliver a pre-built phased SCADA upgrade plan that closes both CIP-007 violations while maintaining 24/7 uptime. The plan includes vendor selection criteria, cutover windows, and a 90-day compliance timeline.

Why this works

You're solving their biggest operational constraint - zero downtime requirements - with a concrete upgrade plan. The phased approach and cutover windows show you understand critical infrastructure operations. This demonstrates CONET's capability without requiring a commitment.

Data Sources
  1. EIA Form 860 (Generator Data) - plant_name, commissioning_year
  2. EPA ECHO - violation_history

The message:

Subject: SCADA modernization plan for Allen Substation I built a phased SCADA upgrade plan for Allen Substation that closes both CIP-007 violations while maintaining 24/7 uptime. The plan includes vendor selection criteria, cutover windows, and a 90-day compliance timeline. Want the upgrade plan?
PVP Public + Internal Strong (8.8/10)

Risk Register for Integration Delays

What's the play?

Deliver a pre-built risk register that identifies the 8 highest-probability delay scenarios for the Cornerstone integration, with contingency actions mapped to keep the bank compliant with the FDIC deadline.

Why this works

You're providing proactive risk management before they've asked for it. The specificity of 8 scenarios with contingencies shows deep understanding of banking integration complexity. This positions CONET as a strategic partner who anticipates problems.

Data Sources
  1. FDIC BankFind Suite API - institution_name, merger_date
  2. Internal CONET Data - integration_risk_patterns, contingency_strategies

The message:

Subject: Risk mitigation plan for June 30th deadline I created a risk register for your Cornerstone integration that identifies the 8 highest-probability delay scenarios. For each scenario, I mapped contingency actions to keep you compliant with the FDIC deadline. Should I send the register?
DATA REQUIREMENT

This play requires knowledge of typical bank integration risk patterns and proven contingency strategies from CONET's merger projects.

This risk intelligence is proprietary to CONET's 40-year banking experience.
PVP Public + Internal Strong (8.8/10)

Remediation Timeline for Budget Constraints

What's the play?

Deliver a pre-built 12-month remediation plan that aligns with the $340K budget constraint by prioritizing the 2 violations with highest penalty risk and deferring lower-risk items to FY2026.

Why this works

You're providing smart prioritization that respects their budget reality. The penalty risk scoring shows you understand EPA enforcement patterns. This gives CFOs a defensible compliance strategy they can use immediately.

Data Sources
  1. EPA ECHO - facility_name, violation_history, enforcement_actions
  2. Internal CONET Data - epa_penalty_risk_scoring, remediation_sequencing

The message:

Subject: Remediation timeline for September violations I mapped a 12-month remediation plan for your 4 CAA violations that aligns with your $340K budget. The plan prioritizes the 2 violations with highest penalty risk and defers lower-risk items to FY2026. Should I send the plan?
DATA REQUIREMENT

This play requires understanding of EPA penalty risk scoring and optimal remediation sequencing from CONET's compliance projects.

This prioritization methodology is proprietary to CONET.
PVP Public Data Strong (8.7/10)

Fast-Track Plan for Facility Validation

What's the play?

Deliver a pre-built remediation plan that identifies which expansion activities can proceed in parallel with violation remediation, without waiting for full FDA approval.

Why this works

You're providing acceleration tactics that reduce time-to-revenue. The parallel-path approach shows deep understanding of FDA validation processes and what activities can legally proceed during remediation.

Data Sources
  1. FDA Drug Establishment Database (eDRLS) - facility_name, regulatory_citations
  2. EPA ECHO - permit_status

The message:

Subject: Fast-track plan for Edison facility validation I created a remediation plan that lets you start pre-validation work while closing your November 12th violations. The plan identifies which expansion activities can proceed in parallel without FDA approval delays. Should I send the plan?
PVP Public + Internal Strong (8.6/10)

DCSA Submission Calendar for Renewal

What's the play?

Deliver a pre-built calendar that maps every DCSA submission deadline between now and the April 8th contract renewal board, flagging the 3 critical dates where delays would push past the March 15th clearance expiration.

Why this works

You're providing operational certainty with specific dates they can track. The critical date flagging shows you understand DCSA process dependencies and timeline risks.

Data Sources
  1. Federal Procurement Data System (FPDS) - contractor_name, contract_end_date
  2. Internal CONET Data - dcsa_process_timelines, critical_deadline_mapping

The message:

Subject: DCSA submission calendar for your renewal I mapped out every DCSA submission deadline between now and your April 8th contract renewal board. The calendar flags the 3 critical dates where delays would push you past your March 15th clearance expiration. Should I send the calendar?
DATA REQUIREMENT

This play requires detailed understanding of DCSA submission process timelines and critical path analysis from CONET's defense projects.

This process expertise is proprietary.
PVP Public Data Strong (8.6/10)

CIP-007 Remediation Roadmap

What's the play?

Deliver a pre-built remediation roadmap that addresses both NERC CIP-007 violations and includes SCADA modernization options, showing which fixes can be done with patching vs. which require hardware replacement.

Why this works

You're providing practical cost/benefit analysis that helps them prioritize spending. The patching vs. hardware categorization shows you understand both compliance requirements and operational budget constraints.

Data Sources
  1. EIA Form 860 (Generator Data) - plant_name
  2. EPA ECHO - violation_history

The message:

Subject: CIP-007 remediation roadmap for 2025 I created a remediation roadmap that addresses your 2 NERC CIP-007 violations and includes SCADA modernization options. The roadmap shows which fixes can be done with patching vs. which require hardware replacement. Should I send the roadmap?

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
EPA ECHO facility_name, facility_address, compliance_status, inspection_records, violation_history, enforcement_actions, permit_status EPA-Regulated Chemical Plants, Electric Power Facilities, Public Water Systems
FDA Drug Establishment Database (eDRLS) facility_name, facility_address, establishment_registration_number, gmp_compliance_status, inspection_history, regulatory_citations FDA-Regulated Pharmaceutical Manufacturing Facilities
FDIC BankFind Suite API institution_name, headquarters_address, total_assets, employee_count, certificate_number, regulatory_history, branch_count, deposit_base FDIC-Insured Banking Institutions
Federal Procurement Data System (FPDS) contractor_name, cage_code, contract_value, contract_type, ordering_agency, contract_start_date, contract_end_date, facility_security_clearance Defense Contractors, Federal Law Enforcement, Federal Civilian Agencies
EIA Form 860 (Generator Data) plant_name, plant_state, operator_name, nameplate_capacity, fuel_type, commissioning_year, ownership_type, nerc_region Electric Power Generation Facilities, Natural Gas Pipeline Operators
CONET Internal Data aggregated_clearance_renewal_timelines, aggregated_integration_timelines, system_consolidation_budgets, aggregated_remediation_budgets, typical_project_timelines All HYBRID plays - provides benchmarking and cost intelligence