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.
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 Procore SDR Email:
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.
Blueprint flips the approach. Instead of interrupting prospects with pitches, you deliver insights so valuable they'd pay consulting fees to receive them.
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)
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.
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.
This play targets GCs with active permitted projects (from Building Permits Database: permit_number, project_address, contractor_name, issue_date) who have subcontractors with open OSHA violations (from OSHA Establishment Search: establishment_name, citation_id, violation_type, case_status). We cross-reference the GC's active subcontractor roster (from Procore or permit filings) against OSHA's public inspection data to surface unabated violations tied to named subs. The prospect is in acute pain: under Illinois OSHA multi-employer worksite doctrine, the GC of record carries joint liability for subcontractor safety performance—an exposure they're not actively monitoring.
The named project address, named subcontractors, and specific violation status make this feel like someone actually pulled their permit file and cross-referenced OSHA. The multi-employer worksite doctrine is a real legal concept that surfaces a blind spot. The offer to send violation numbers is immediately useful—the recipient can act on this TODAY without a meeting. The underlying psychology is protective and actionable: you have liability exposure, here's what to do about it.
Access to the GC's subcontractor roster from Procore's subcontractor management module or permit filing records, cross-referenced against OSHA's public inspection database
For Procore users, the subcontractor roster is already available in the platform. This play synthesizes that data with public OSHA records to surface liability exposure the GC may not be actively tracking. The recipient can immediately identify and address sub-level OSHA violations before they create joint liability risk.This play targets federal contractors with specific dollar-amount SAM.gov awards who have unresolved OSHA citations still marked open in public inspection logs. We cross-reference the SAM.gov Contract Awards Database (contractor_name, contract_value, contract_award_date) against OSHA Establishment Search (citation_id, case_status, inspection_date) to identify active award holders at compliance risk. The prospect is in acute pain because contracting officers can pull award eligibility under FAR 9.104-5 without formal debarment—a faster, less visible process they don't see coming.
The specific award dollar amount ($4.2M) makes this feel like reconnaissance, not a generic template. The precise FAR reference (9.104-5) is immediately verifiable and signals competence. The offer to send citation numbers removes friction—the prospect feels helped, not pitched. The psychology is protective (you could lose your contract) rather than prescriptive (you need our tool).
This play targets federal GCs with active projects in Procore's system who are experiencing documented labor hour deviations vs. baseline plan (from progress billings data: labor_hours_logged vs. labor_hours_planned by cost code). We surface the 18% deviation magnitude and connect it to the historical pattern (6-8 week lag before cost overruns appear in financial reports). The prospect is in acute pain: cost overruns on federal contracts are contractually significant, and this 6-8 week early warning window represents their last chance to course-correct before the overrun becomes visible to contracting officers and impacts profitability.
The specific deviation percentage (18%) tied to their actual progress billings feels like internal reconnaissance. The 6-8 week early warning framing identifies a blind spot—this is exactly what their traditional financial reporting misses. The cost code breakdown offer is low-commitment and immediately actionable. The psychology is protective and time-sensitive: you can fix this now, but you only have weeks.
Access to the prospect's project financial data within Procore: labor hours logged vs. plan by cost code, progress billing schedules, and contract baseline
This play leverages real-time project data available only to Procore's active users. The recipient's project manager can see the exact cost codes where labor is running hot and intervene before FHWA oversight or invoice reconciliation surfaces the overrun. Competitive advantage: no other platform has live access to this same cost-of-work visibility across federal contractors' active projects.This play targets highway and bridge contractors with FHWA Major Project Awards (from FHWA Major Projects Database) who have OSHA Total Recordable Incident Rates (TRIR) above sector median (from OSHA Establishment Search). We cross-reference contractor_name and project_location to connect active federal awards with elevated safety metrics. The prospect is in acute pain: FHWA major project oversight includes mandatory safety performance reviews under 23 CFR Part 635, and a TRIR above 3.5 is a documented trigger for contractor performance flags—creating federal oversight exposure they haven't connected to their current award.
The message ties the prospect's actual TRIR (4.2) to a sector benchmark (2.8 median) without making the benchmark the hook—the federal oversight risk is. The precise regulatory reference (23 CFR Part 635) is verifiable and signals competence. The question ("Is your safety team already tracking incident documentation?") routes to the right owner and feels collaborative, not adversarial. The underlying emotion is protective: you could get flagged by FHWA.
This play targets general contractors with active building permits in prevailing wage jurisdictions (pulled from Building Permits Database filtered by jurisdiction + permit_type) who lack a GSA Schedule listing (verified via GSA eLibrary). We're using Davis-Bacon Wage Determinations data to confirm the contractor is subject to prevailing wage requirements. The prospect is in acute pain: without certified payroll documentation tied to a compliant schedule, a DOL audit on these active permits could trigger back-wage assessments and disqualify them from future federal work.
The specificity (3 permits in Cook County, a named Davis-Bacon jurisdiction) makes this feel like someone actually pulled their permit file, not a list. The WH-347 form reference shows domain knowledge. The DOL audit risk is credible and real—it's a liability threat, not a feature pitch. The question routes to the right owner (whoever manages payroll compliance) and is immediately actionable.
This play targets general contractors with active SAM.gov federal contract awards who simultaneously have unabated OSHA serious violations on file. We're using the SAM.gov Contract Awards Database to identify active federal work and cross-referencing against the OSHA Establishment Search (IMIS) database to surface open violations. These prospects are in acute pain: FAR 9.406-2 allows contracting officers to initiate debarment proceedings when OSHA violations remain unresolved during active contract performance—a real compliance threat they haven't synthesized yet.
The message connects two data points the prospect hasn't linked themselves (their federal award + their OSHA violations), creating an uncomfortable but credible urgency signal. The specific FAR reference makes it verifiable and removes the sense of generic compliance noise. The one-word answerable question ("Is someone already managing the abatement documentation?") makes it feel like a real colleague asking, not a sales probe.
This play targets highway contractors with specific FHWA Major Project Awards (from FHWA Major Projects Database: project_name, project_cost, project_status) combined with above-median OSHA TRIR records (from OSHA Establishment Search: establishment_name, inspection_date, violation_type). The prospect is in acute pain: FHWA project representatives can request incident documentation with 48 hours notice under federal major project oversight rules, and contractors with elevated incident rates are high-probability audit targets—creating urgent documentation readiness pressure.
The named project corridor (I-94) adds a layer of specificity that makes this feel like targeted research. The 48-hour documentation request window is genuinely alarming and creates urgency without being hyperbolic. The routing to the incident log owner is immediate and clear. The underlying psychology is preparation: you need to be ready before they show up.
These messages provide actionable intelligence before asking for anything. The prospect can use this value today whether they respond or not.
This play targets GCs with active projects who have subcontractors with open, unabated OSHA violations. We surface specific OSHA case numbers (from OSHA Establishment Search: citation_id, violation_type, case_status, violation_date) tied to named subs on their active permitted projects (Building Permits Database + Procore subcontractor data). The prospect is in acute pain: as GC of record, they need documented evidence that they notified subs of unabated violations—this documentation is their protection against multi-employer liability if OSHA conducts a follow-up inspection.
The OSHA case numbers (OSHA Case #1625834, OSHA Case #1598271) are specific enough to verify in 30 seconds—maximum credibility. The named subs, named project, specific violation types, and specific dates remove all vagueness. The 'formal notice' framing tells the recipient exactly what action to take. The psychology is liability protection: this documentation protects you if OSHA shows up. The offer to send full violation detail enables immediate action.
Access to the GC's subcontractor roster from Procore or permit filings, linked to OSHA public inspection data with specific case numbers and violation details for named subs
This is a PVP for GCs who need to create documented sub notification letters TODAY. The recipient's safety manager gets the exact OSHA case numbers and violation details needed to issue formal sub notification letters, creating documented protection against multi-employer liability. The case numbers are verifiable and give maximum credibility. Competitive advantage: synthesizing real-time subcontractor roster data with OSHA public records to create actionable liability documentation.This play targets active Procore users managing federal projects with mid-project labor productivity deviations. We pull cost code-level data (from Procore: labor_hours_logged vs. labor_hours_planned by cost_code, project_phase, financial_data) and surface the 4 cost codes with the widest variance. Concrete forming at 34% over baseline is the critical flag that will trigger contracting officer attention at Q2 billing. The prospect is in acute pain: they have ~3 weeks before the variance becomes visible to the customer, creating urgent course-correction pressure.
The four specific cost codes with specific percentages (sitework 7%, concrete forming 34%, MEP rough-in 12%, steel 9%) is exactly what the PM needs to act. The 34% concrete forming callout is alarming without needing to be exaggerated. The 3-week window before Q2 billing is genuinely urgent and creates decision pressure. The offer to send the full cost code report is low-friction and high-value—the prospect will say yes just to see the data.
Access to the prospect's live project cost code data within Procore: labor hours logged vs. baseline plan, cost code names, project phase status, and progress billing schedule
This is a PVP for existing Procore customers only. The recipient's PM gets actionable cost code data to course-correct before the overrun becomes visible to FHWA or in formal project financials. The 3-week window and specific cost code percentages create genuine urgency. Competitive advantage: only Procore has real-time access to this cost-of-work detail across active federal projects.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.
Every play traces back to verifiable public data. Here are the sources used in this playbook:
| Source | Key Fields | Used For |
|---|---|---|
| SAM.gov Contract Awards Database | contractor_name, unique_entity_identifier, naics_code, place_of_performance_state_code, place_of_performance_city, contract_award_date, contract_value, principal_naics_code, agency_name, socio_economic_status, set_aside_type | Identifying federal contractors with active awards and understanding their federal project pipeline and contracting patterns |
| OSHA Establishment Search (IMIS Database) | establishment_name, state, zip_code, inspection_activity_number, inspection_date, citation_id, violation_type, penalty_amount, case_status, violation_description | Surfacing open OSHA violations tied to contractors and subcontractors, identifying safety compliance risks and debarment exposure |
| Davis-Bacon Wage Determinations (SAM.gov) | wd_number, state, county, labor_category, prevailing_wage_rate, fringe_benefits, work_rules, effective_date, modification_date | Identifying prevailing wage jurisdictions and confirming Davis-Bacon compliance requirements for contractors with permits in covered areas |
| Building Permits Database (Shovels.ai) | permit_number, project_address, permit_type, building_type, contractor_name, project_value, issue_date, completion_date, jurisdiction, zipcode, contractor_specialty, decision_data | Identifying active construction projects, contractor names and project locations, and connecting GCs to their subcontractor rosters on specific permitted projects |
| FHWA Major Projects Database | project_name, state, project_cost, funding_source, project_status, completion_timeline, project_scope, major_construction_phases | Identifying contractors with active federal highway and bridge awards and understanding federal oversight requirements tied to major projects |
| GSA eLibrary (Federal Supply Schedule Contractors) | contractor_name, gsa_schedule_number, naics_code, products_services, pricing, business_size, location, contract_start_date | Verifying whether contractors have GSA Schedule listings and identifying gaps in federal vendor registration |
| Procore Project Management Data | labor_hours_logged, labor_hours_planned, cost_code, project_phase, progress_billing_date, cost_code_name, subcontractor_name, project_id, contract_date, project_address | Surfacing labor productivity deviations against baseline for existing Procore customers and identifying cost overrun early warning signals; also tracking subcontractor rosters on active projects |