Blueprint Playbook for NationGraph

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

Subject: Government Procurement Opportunity Hi [Name], I noticed your company is selling to government agencies. We help vendors win more contracts by providing better visibility into opportunities. Would love to grab 15 minutes to chat about how we're helping similar companies like yours grow their government business. Best, [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.

NationGraph 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.8/10)

Play: GSA Schedule SIN Gap Analysis vs. Peer Competitors

What's the play?

This play compares the prospect's GSA Schedule 70 contract SINs against the top 5 peer contractors in their product category (identified via FPDS award analysis), identifies missing SINs that those peers added in Q3 2024, and cross-references live SAM.gov solicitations requiring those SINs. The prospect is in pain because they don't know they're locked out of a $220M DoD IDIQ vehicle due to a missing SIN—information that requires cross-referencing three data systems (their own GSA schedule, competitor FPDS records, and live SAM.gov postings) that no competitor can easily synthesize.

Why this works

This email triggers competitive anxiety. Being told 'Lockheed and Raytheon won $47M in awards under a SIN you don't have' creates immediate urgency tied to a discrete, fixable problem. The routing question 'Is someone on your contracts team already working the SIN modification?' is brilliant—it either routes to someone who needs to act immediately or exposes an internal gap. The specificity (GSA schedule number, exact SIN codes, named competitors, dollar amounts, and a specific $220M opportunity) signals sophisticated competitive intelligence that the prospect can't easily replicate.

Data Sources
  1. GSA eLibrary & GSA Schedules - contractor_name, schedule_number, contract_number, labor_category
  2. Federal Procurement Data System (FPDS-NG) - contractor_name, obligated_amount, contract_date_signed, agency, naics
  3. SAM.gov - System for Award Management - agency, contract_amount, solicitation_number, response_deadline

The message:

Subject: Lockheed and Raytheon winning awards your GSA schedule misses Your GSA Schedule 70 (GS-35F-0119Y) doesn't include SIN 518210C (cloud professional services) — Lockheed Martin and Raytheon both added that SIN in Q3 2024 and have combined $47M in DoD cloud awards under it since August. DOD CIO posted a $220M cloud migration IDIQ on SAM.gov on December 2nd that requires SIN 518210C eligibility for award consideration. Is someone on your contracts team already working the SIN modification?
PQS Public + Internal Strong (8.5/10)

Play: Competitive Engagement Velocity Analysis

What's the play?

This play analyzes the prospect's own FPDS award history to identify RFPs they responded to but lost, then cross-references SAM.gov pre-solicitation postings and sources-sought notices to calculate when the winning vendor first engaged the contracting officer. The prospect is in pain because they don't know they're losing deals due to late engagement—they engage after RFP posting while competitors engage 30-60 days before. NationGraph calculates the engagement gap (prospect engaged 34 days AFTER the winner's first documented contact) using the prospect's own award data, making the insight impossible to ignore or dismiss.

Why this works

This email is designed to trigger recognition and embarrassment. Being shown 'you lost 3 deals because you were late' with specific proof (contract numbers, timing data, calculation showing the winner engaged 34 days before you) creates cognitive dissonance that forces action. The question 'Are you tracking pre-solicitation activity, or are you relying on SAM.gov alerts?' perfectly diagnoses the operational gap—SAM.gov alerts miss the pre-solicitation window where deals are shaped. The emotional response is 'I've been doing this wrong and I didn't realize it.'

Data Sources
  1. Federal Procurement Data System (FPDS-NG) - contractor_name, obligated_amount, contract_date_signed, agency, piid
  2. SAM.gov - System for Award Management - agency, solicitation_number, presolicitation_notice_date, response_deadline
  3. Public Bid Tracker - state, solicitation_type, procurement_agency, deadline

The message:

Subject: Your team engaged 3 RFPs after competitors in Q4 Across 3 RFPs your firm responded to in Q4 2024 — NITAAC CIO-SP4 task order 75N98124R00041, GSA BPA GS-10F-0532P, and a DHS SEWP order — your first vendor engagement came an average of 34 days after the top-ranked awardee's first documented agency contact. Firms that engage 60+ days before RFP release win at 3x the rate of firms engaging after posting, based on FPDS award timing data across your 3 losses. Is your BD team tracking pre-solicitation activity, or are you relying on SAM.gov alerts?
EXISTING CUSTOMER PLAY

The prospect's own FPDS award history for the last 12 months, cross-referenced with SAM.gov presolicitation notice dates and sources-sought posting dates for each RFP they bid on

This play requires access to the prospect's award history (loss data) from FPDS and the ability to cross-reference pre-solicitation activity timelines. NationGraph must maintain historical SAM.gov presolicitation records and sources-sought archive to calculate the engagement gap. This is a private data play because it requires the customer's specific transaction history.
PQS Public + Internal Strong (8.3/10)

Play: Win Probability Scoring for RFP Portfolio Management

What's the play?

This play monitors K-12 district RFP portals to track vendor registration counts on active Student Information System procurements, then cross-references the prospect's own RFP responses against LAUSD's historical SIS award data (last 6 awards) to surface probability signals. The vendor is in pain because they allocate proposal budgets to RFPs without understanding competitive saturation—at 14 registered bidders, their win probability falls below 8% based on LAUSD's own award history. NationGraph provides the specific RFP number, due date, named competitors, and the historical probability metric tied to LAUSD's actual award patterns.

Why this works

This email triggers resource-allocation guilt. Most sales leaders allocate proposal budgets based on deal size or relationship, not win probability. Being told 'you're spending $50K in proposal effort to win an 8% probability deal' forces an immediate re-prioritization conversation. The mention of named incumbents (PowerSchool, Infinite Campus) signals that research has been done and the competition is real. The question 'Is your team still allocating proposal budget to this one?' is perfectly designed to make the recipient pause and audit their proposal pipeline.

Data Sources
  1. K-12 School District Procurement (RFPSchoolWatch) - school_district, rfp_type, deadline, vendor_registration_count
  2. Public Bid Tracker - solicitation_type, procurement_agency, deadline

The message:

Subject: Los Angeles USD RFP has 14 registered vendors LAUSD's Student Information System RFP (RFP-24-0892, due February 3, 2025) already has 14 registered bidders — including PowerSchool and Infinite Campus — as of today's vendor registration list. At 14 competitors, average award probability on LAUSD procurements historically drops below 8% based on their last 6 SIS awards. Is your team still allocating proposal budget to this one?
DATA REQUIREMENT

NationGraph's historical analysis of LAUSD SIS award patterns across the last 6 procurements to calculate win probability by competitor count

This assumes NationGraph tracks vendor registration counts on active RFP portals and maintains a proprietary database of district-level historical award patterns that allows win probability scoring by competitor count and category.
PQS Public Data Strong (8.1/10)

Play: Contract Expiration Warning with Live RFP Match

What's the play?

This play targets cybersecurity vendors with DHS IDIQ contracts expiring in 2025 by cross-referencing SAM.gov procurement postings against known contract databases. The prospect is in acute pain because their largest government revenue stream (IDIQ base period) ends in 90 days, and they lack visibility into replacement opportunities posted to SAM.gov. NationGraph identifies the specific contract number, expiration date, and a directly matching RFP posted days earlier—something a vendor can't easily discover across fragmented government portals.

Why this works

This email makes the recipient feel exposed and behind. The specificity (contract number, expiration date, exact RFP posting date) signals that someone is monitoring their business in real-time. The mention of '2x higher win rates for 90+ day engagement' contextualizes urgency without sounding manufactured. The CTA (send the contracting officer's contact) is frictionless—one word 'Yes' removes all research burden and signals respect for their time.

Data Sources
  1. SAM.gov - System for Award Management - agency, contract_amount, solicitation_number, response_deadline, contract_type
  2. Federal Procurement Data System (FPDS-NG) - contractor_name, obligated_amount, contract_date_signed, agency, piid

The message:

Subject: Your DHS IDIQ contract expires March 2025 Your DHS Continuous Diagnostics and Mitigation IDIQ (HSHQDC-21-D-00123) has a base period ending March 31, 2025 — DHS posted a $340M IT modernization RFP on SAM.gov on November 14th covering the same CDM scope. Vendors who engage the contracting officer 90+ days before award typically see 2x higher win rates on follow-on work. Should I send the full SAM.gov posting with the contracting officer's contact at DHS?

NationGraph 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.2/10)

Play: Pre-Solicitation Window Sourcing

What's the play?

This play monitors sources-sought notices posted across the prospect's top 3 agency targets (HHS, DHS, VA) over the last 21 days, identifies those with no vendor responses yet recorded, cross-references against estimated award values, and surface all still-open pre-solicitation windows. The prospect is in pain because they lack visibility into the pre-RFP shaping window—they only learn about opportunities after formal RFP posting, by which time requirements are locked and competitors have already shaped them. NationGraph identifies a $85M VA sources-sought notice still in the response phase, with a January 10 deadline, and no competitor responses on record yet.

Why this works

This email reframes opportunity timing from 'RFPs are opening' to 'you have time to shape requirements.' The fact that 'no vendor responses are yet recorded' signals first-mover advantage—a powerful motivator. The specific deadline (January 10) creates urgency tied to a concrete action (submit capability statement). Offering contracting officer names and emails means 'Yes' enables action today. The $85M estimated value makes clear this isn't a small opportunity. This directly addresses the engagement velocity problem from the previous play with a concrete solution.

Data Sources
  1. SAM.gov - System for Award Management - agency, solicitation_number, presolicitation_notice_date, response_deadline, estimated_award_value, contracting_officer_contact
  2. Public Bid Tracker - state, solicitation_type, procurement_agency, deadline
  3. Federal Procurement Data System (FPDS-NG) - agency, obligated_amount, contract_date_signed

The message:

Subject: 5 pre-solicitation windows open in your agency targets I found 5 sources-sought notices posted in the last 21 days across your top 3 agency targets (HHS, DHS, and VA) where no vendor responses are yet recorded — the largest is a VA enterprise IT modernization notice (VA-24-00318, capability statements due January 10, 2025) with an estimated $85M award. All 5 are still in the pre-solicitation window, meaning you can influence requirements before the formal RFP drops and get your name on the contracting officer's radar. Want me to send the full list with contracting officer names and direct email addresses?
DATA REQUIREMENT

NationGraph's real-time monitoring of sources-sought notices across HHS, DHS, and VA, with tracking of vendor response counts and estimated award values

This play assumes NationGraph maintains a proprietary database of sources-sought notices tracked by agency and response count, enabling identification of pre-solicitation windows still open with no competitor responses. This requires continuous monitoring of SAM.gov sources-sought postings and real-time response tracking that represents a material competitive advantage.
PVP Public + Internal Strong (9.1/10)

Play: Low-Competition RFP Discovery and Early Engagement

What's the play?

This play scans 14,000+ K-12 district procurement portals for Student Information System RFPs posted in the last 45 days, filters for those with fewer than 3 registered bidders, and cross-references historical incumbent data to identify greenfield opportunities. The vendor is in pain because they lack visibility into district procurement timelines and spend effort on saturated opportunities while missing greenfield buys. NationGraph surfaces specific RFPs (Fresno USD with $2.1M value, 2 vendors, January 28 deadline), incumbent status, and procurement contact names—enabling resource-efficient targeting.

Why this works

This email reframes from 'you're losing deals' to 'here are the deals nobody's fighting for.' Greenfield RFPs (no incumbent vendor) trigger psychological relief—the prospect perceives lower risk of losing to an entrenched competitor. The specificity (Fresno USD, 2 vendors, $2.1M, January 28 deadline) signals that research has been done at the district level, not through generic alerts. Offering the full list with award histories means 'Yes' gives the prospect everything needed to prioritize and act without another touchpoint.

Data Sources
  1. K-12 School District Procurement (RFPSchoolWatch) - school_district, rfp_type, category, deadline, estimated_value, vendor_registration_count
  2. Public Bid Tracker - state, solicitation_type, procurement_agency, bid_amount, deadline

The message:

Subject: 4 low-competition SIS RFPs your team hasn't touched I found 4 Student Information System RFPs posted in the last 45 days with fewer than 3 registered bidders each — the largest is Fresno USD (RFP-FY25-114, $2.1M, due January 28, 2025) with only 2 vendors registered so far. All 4 districts have fewer than 15,000 students, no incumbent vendor on record, and procurement contacts listed in the posting. Want me to send the full list with district contact names, emails, and award histories?
DATA REQUIREMENT

NationGraph's proprietary tracking of vendor registration counts across district RFP portals and historical incumbent vendor data by district and procurement category

This assumes NationGraph monitors 14,000+ K-12 district procurement portals in real-time, tracks vendor registration counts on active RFPs, and maintains a proprietary database of incumbent vendor records by district and solicitation category. This represents core product differentiation over competitors monitoring only national aggregators.
PVP Public Data Strong (9.0/10)

Play: Competitive SIN Gap Analysis with Live Solicitation Matching

What's the play?

This play builds a side-by-side comparison of the prospect's GSA Schedule 70 SINs versus the 5 peer contractors who won the most DoD awards in their product category in 2024, identifies 2+ missing SINs that those peers hold, calculates the dollar value of awards those peers won under those SINs ($47M), and flags 2+ live DoD solicitations (with numbers and deadlines) that require both SINs for award consideration. The prospect is in acute pain because they're locked out of two active opportunities with near-term deadlines—a fixable problem that requires cross-referencing GSA schedules, FPDS award records, and live SAM.gov solicitations.

Why this works

This email escalates competitive anxiety into action. The side-by-side comparison forces the prospect to see themselves losing to named competitors on specific awards. The offer includes peer contractor names and contracting officer emails—meaning 'Yes' gives them everything needed to fix the gap AND engage the opportunities today. The two hard deadlines (January 31 and February 14) create real urgency tied to specific solicitation numbers the prospect can verify on SAM.gov immediately. This is the kind of intelligence that triggers immediate CRO/CFO-level conversations.

Data Sources
  1. GSA eLibrary & GSA Schedules - contractor_name, schedule_number, contract_number, labor_category
  2. Federal Procurement Data System (FPDS-NG) - contractor_name, obligated_amount, contract_date_signed, agency, naics_code
  3. SAM.gov - System for Award Management - agency, contract_amount, solicitation_number, response_deadline, contracting_officer_contact

The message:

Subject: Your GSA schedule missing SIN that won $47M in DoD awards I built a side-by-side of your GSA Schedule 70 SINs versus the 5 peer contractors who won the most DoD awards in your product category in 2024 — you're missing SIN 518210C and SIN 54151S, which together account for $47M of those awards. I've also flagged 2 active DoD solicitations (SAM-DOD-24-0981 due January 31 and SAM-DOD-24-1104 due February 14) that require both SINs for award eligibility. Want me to send the full comparison with the 5 peer contractors listed and both solicitation POC emails?
PVP Public Data Strong (8.7/10)

Play: Pre-RFP Shaping Window Discovery

What's the play?

This play identifies multiple CDM-scope RFPs posted to SAM.gov within 30 days that overlap with the prospect's current DHS IDIQ contract scope. The vendor is in pain because they don't know which recompetes are coming, when pre-solicitation windows close, and how much time they have to influence requirements before formal RFP release. NationGraph synthesizes SAM.gov postings, solicitation numbers, and pre-solicitation closing dates to surface which windows are still open—information that typically requires manual monitoring across dozens of agency RFP portals.

Why this works

This email reframes the problem from 'I'm losing a contract' to 'I'm leaving money on the table by not shaping requirements.' Pre-solicitation engagement is non-obvious to most sales teams—they focus on RFPs, not the shaping window before them. Offering names and emails means the prospect can act immediately without meetings. The specific dollar amount ($180M) and deadline (January 17) create real urgency tied to an actionable step, not manufactured pressure.

Data Sources
  1. SAM.gov - System for Award Management - solicitation_number, agency, estimated_award_value, presolicitation_closing_date, contracting_officer_contact
  2. Federal Procurement Data System (FPDS-NG) - contractor_name, obligated_amount, agency, naics_code

The message:

Subject: 3 CDM recompetes posted while your IDIQ expires I pulled 3 CDM-scope RFPs posted to SAM.gov in the last 30 days that overlap with your current DHS IDIQ scope — the largest is a $180M CISA endpoint security recompete (solicitation CISA-24-00441, response due January 17, 2025). All 3 have pre-solicitation windows closing before your March contract end date, meaning you can still shape requirements if you engage the POC now. Want me to send the full list with contracting officer names and emails?

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
SAM.gov - System for Award Management agency, contract_amount, solicitation_number, response_deadline, contract_type, presolicitation_notice_date, estimated_award_value, contracting_officer_contact Identifying active federal procurement opportunities, RFP posting dates, pre-solicitation windows, and contracting officer contact information
Federal Procurement Data System (FPDS-NG) contractor_name, obligated_amount, contract_date_signed, agency, naics_code, piid, contract_action_type Analyzing federal contract awards, identifying incumbent contractors, calculating engagement timing gaps, and cross-referencing peer competitor win history
USAspending.gov - Government Spending Open Data award_recipient, agency, award_amount, award_date, transaction_type, geographic_data Tracking federal spending patterns, identifying agency IT budgets, and analyzing procurement trends by agency and contract type
IT Dashboard (itdashboard.gov) agency_it_spending, major_investments, modernization_dollars, cloud_spending, agency_name Identifying federal agencies with active IT modernization budgets and prioritizing targets by funding levels
GSA eLibrary & GSA Schedules contractor_name, schedule_number, contract_number, labor_category, cage_code Analyzing GSA Schedule contract coverage, identifying SIN gaps relative to competitors, and tracking contractor eligibility for federal vehicles
Public Bid Tracker state, solicitation_type, procurement_agency, bid_amount, deadline, category Aggregating state and local RFP postings, tracking procurement cycles by state, and identifying high-competition vs. low-competition opportunities
K-12 School District Procurement (RFPSchoolWatch) school_district, state, rfp_type, category, deadline, budget_range, vendor_registration_count Monitoring K-12 district RFPs, tracking vendor registration counts, identifying greenfield opportunities with no incumbents, and analyzing historical award patterns by district