Blueprint Playbook for Jobber

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

Subject: Growing field service business? Hi [Name], I noticed you're in the field service space and probably managing a growing team. Jobber helps businesses like yours streamline scheduling, invoicing, and customer communication all in one platform. Would love to show you how we can help your team work more efficiently. Best, [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.

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

Play: Clustering Real Estate Closings in Operator Service Zone = WDO Inspection Pipeline

What's the play?

This play targets licensed pest control operators by identifying geographic clusters of pending home sales within their active service area, then cross-referencing MLS closing timelines (typically 30-45 days out) against VA/FHA loan requirements for wood-destroying-organism (WDO) inspections. The data signals come from MLS pending sales data (showing property addresses, closing dates) filtered by ZIP code overlap with the operator's license zone. These prospects are in pain because they are leaving revenue on the table: VA and FHA loans require licensed WDO inspections before closing, most transactions don't have one scheduled yet, and the closing window is a predictable 6-week cluster where demand spikes and most operators are already booked.

Why this works

This message works because it presents a revenue opportunity disguised as operational intelligence. The prospect doesn't have to fix a broken process or avoid a penalty—they can simply capture sales they would otherwise miss. The specificity of the closing timeline ('January 15 and February 28, 2025') and the count of opportunities (43 homes) make the opportunity feel both concrete and large. The offer to send 'addresses and closing agent contacts' removes all friction: they say yes and can start outreach today.

Data Sources
  1. MLS Pending Sales Data - property_address, listing_price, closing_date, loan_type, buyer_agent_contact, listing_agent_contact
  2. Pest Control License Database - operator_name, license_number, service_area_zip_codes, license_status

The message:

Subject: 43 pending home sales within 1 mile of your license zone There are 43 homes under contract within a 1-mile radius of your licensed service area in Hillsborough County, and WDO inspection is required for VA and FHA closings in Florida - closings are clustered between January 15 and February 28, 2025. That's a 6-week window where demand for licensed WDO inspectors spikes and most operators are already booked. Want the addresses and closing agent contacts for those 43 transactions?
PQS Public Data Strong (9.0/10)

Play: Lapsed Cert + Permit Liability Snapshot with Actionable Permit List

What's the play?

This variant adds a concrete deliverable: the specific permit numbers and filing dates for all projects filed post-cert-expiration. This transforms the play from an alert into an immediately actionable document. The prospect can cross-reference these permit numbers against their job records to assess exposure. The data comes from EPA RRP cert database (showing expiration date) and county permit records (showing permit numbers and filing dates post-expiration). The pain is the same—daily EPA violation exposure—but the solution path is clearer.

Why this works

The offer to send 'the 7 permit numbers and filing dates' eliminates friction and creates a clear next action: the prospect says yes and immediately receives the exact data they need to assess liability and notify their team. The per-day penalty framing is more alarming than most contractors expect, and the specificity of the permit numbers (vs. just 'seven projects') makes the threat feel concrete and real. This is the most action-forcing variant because the information provided is directly usable.

Data Sources
  1. EPA RCRA / RRP Database - firm_certification_number, certification_status, expiration_date, firm_name
  2. County Permit Records Database - permit_number, company_license_number, permit_date, permit_type, jurisdiction, filing_date

The message:

Subject: 7 permits pulled after your RRP cert expired EPA records show your RRP firm certification expired October 14, 2024, and county permit data shows 7 renovation projects filed under your license since that date. Each of those projects is a potential $37,500-per-day violation if EPA cross-references the permit file during an inspection. Should I send the 7 permit numbers and filing dates?
PQS Public Data Strong (8.9/10)

Play: Permit Spike + Review Sentiment Correlation Signals Scheduling Failure

What's the play?

This play targets plumbing contractors whose county permit filings spiked (32+ permits in 90 days) while their Google review rating simultaneously dropped (4.1 to 3.2 stars) and new reviews explicitly mention missed appointments and no-shows. The data signals come from county permit records (showing job volume increase) cross-referenced with Google review scraping (showing both star rating decline and specific complaint patterns). These prospects are in acute pain because the correlation between permit spike and scheduling complaints indicates their dispatch process has broken under load, directly threatening customer retention and repeat revenue.

Why this works

This message works because it connects two data points the prospect would never synthesize themselves: permit volume (a business growth signal they celebrate) and review sentiment (a lagging indicator they might dismiss as noise). The specificity of naming the complaint pattern ('6 of 9 new reviews mention missed appointments') proves you read the reviews, not just aggregated star ratings. The implication that scheduling failure is now threatening their reputation makes the emotional response urgent and visceral.

Data Sources
  1. County Permit Records Database - permit_number, company_license_number, permit_date, permit_type, jurisdiction
  2. Google Reviews API / Review Scraping - review_text, review_date, star_rating, reviewer_name

The message:

Subject: 32 permits pulled, Google reviews dropped to 3.2 stars Your company pulled 32 plumbing permits in Harris County in Q3 2024, but your Google rating dropped from 4.1 to 3.2 stars over the same period - 6 of the 9 new reviews mention missed appointments or no-call-no-shows. That pattern usually means scheduling is breaking under permit load. Is someone already looking at the dispatch process?
PQS Public Data Strong (8.8/10)

Play: Lapsed EPA RRP Firm Cert vs. Active Renovation Permits = Daily Violation Risk

What's the play?

This play targets renovation contractors whose EPA RRP firm certification has lapsed (expired on a specific date documented in EPA records) while county permit data shows they have continued to file renovation projects. The data signals come from EPA RCRA/RRP database (showing lapsed firm cert status) cross-referenced with county permit records (showing active renovation work post-expiration). These prospects are in acute pain because working under a lapsed RRP firm certification creates a $37,500-per-day EPA violation for each project—and the EPA discovers these violations when inspectors cross-reference permit files against the firm cert database during routine audits.

Why this works

This message triggers urgent compliance fear because it names a specific, verifiable threat: the exact certification number, expiration date, and the number of projects filed post-expiration. The prospect can verify every claim in 30 seconds on the EPA website, which builds credibility. The per-day penalty structure (not one-time) makes the financial exposure emotionally urgent: 7 projects × daily penalties = potentially massive liability. The close-ended question gives them an easy escape route if they've already corrected it.

Data Sources
  1. EPA RCRA / RRP Database - firm_certification_number, certification_status, expiration_date, firm_name
  2. County Permit Records Database - permit_number, company_license_number, permit_date, permit_type, jurisdiction

The message:

Subject: Your EPA RRP firm cert lapsed in October 2024 Your EPA RRP firm certification (Cert #NAT-F123456) lapsed on October 14, 2024, but your company pulled 7 renovation permits in Cook County since then. EPA enforcement for working under a lapsed RRP firm cert runs up to $37,500 per violation per day, and permit records are the first thing inspectors pull. Is someone already handling the renewal?
PQS Public Data Strong (8.7/10)

Play: Review Complaint Clustering as Scheduling Collapse Signal

What's the play?

This variant uses the same core data (permit spike + review sentiment) but focuses on the clustering of specific complaints (missed appointments, no-shows) within a compressed timeframe. By offering to send the 6 review excerpts with timestamps, the message becomes fully actionable without requiring a prospect conversation. The data signals indicate that scheduling collapse happened before revenue slowdown—a critical operational insight for a contractor who can still save customer relationships if they act immediately.

Why this works

The offer to send timestamped review excerpts lowers the friction to action: a prospect can say yes and immediately review the evidence without scheduling a call. The causal framing ('permit spike causing scheduling break before the revenue did') is psychologically resonant because it flatters the prospect's business growth while clarifying that operational systems didn't scale. The implicit message is 'you grew faster than your processes can handle'—which is both painful and actionable.

Data Sources
  1. County Permit Records Database - permit_number, company_license_number, permit_date, permit_type, jurisdiction, filing_date
  2. Google Reviews API / Review Scraping - review_text, review_date, star_rating, complaint_keywords

The message:

Subject: 6 missed-appointment reviews since your permit spike Since your permit volume jumped to 32 jobs in Q3 2024, 6 of your last 9 Google reviews specifically mention missed appointments or techs not showing up. When review complaints cluster around scheduling within 90 days of a permit spike, it usually means dispatch coordination broke before the revenue did. Want me to send the 6 review excerpts with timestamps?
PQS Public Data Strong (8.7/10)

Play: Unscheduled WDO Inspections in High-Transaction ZIPs = Predictable Revenue Window

What's the play?

This variant uses the same core data (MLS pending sales in operator's ZIP codes) but adds a critical insight: the observation that most transactions don't have an inspection scheduled yet. This signal likely comes from MLS notes or remarks fields that would show 'WDO pending' or similar flags. By focusing on the unscheduled inspection angle rather than just transaction volume, the message positions the opportunity as time-sensitive and actionable. The three specific ZIP codes (33602, 33606, 33609) make the targeting hyper-local and verifiable.

Why this works

The psychological lever is 'I found you money you didn't know was there, and I'm handing you the contact list.' The specificity of the ZIP codes (not 'Hillsborough County' broadly) makes the operator feel seen as a specific geographic player. The insight that most inspections aren't scheduled yet creates urgency: they need to move before the closing window opens. The offering of listing agent contacts is the critical friction-reducer—they don't have to research; they can act immediately.

Data Sources
  1. MLS Pending Sales Data - property_address, zip_code, closing_date, loan_type, listing_agent_contact, remarks_field
  2. Pest Control License Database - operator_name, license_number, service_area_zip_codes, license_status

The message:

Subject: WDO inspection window opens January 15 in your county Hillsborough County MLS data shows 43 homes entering the closing window between January 15 and February 28, 2025 - all in ZIP codes 33602, 33606, and 33609 where your license is active. VA and FHA loans require a licensed WDO inspection before closing, and most of these transactions don't have one scheduled yet. Should I send the property addresses and listing agent contacts?
PQS Public Data Strong (8.6/10)

Play: Cert Expiration + Active Permit Collision Risk

What's the play?

This variant uses the same core data (county permits + EPA cert expirations) but adds a non-obvious insight: the timing of the expiration relative to open permit cycles. HVAC contractors with 14+ active permits and technicians whose 608 certs expire mid-cycle face enforcement risk because the EPA cross-references permit files during inspections. The prospect is in pain because they may not realize the enforcement mechanism is triggered by mid-permit uncertified work, not just year-end non-compliance.

Why this works

The psychological leverage comes from naming the specific enforcement scenario ('mid-permit cycle') that triggers EPA action. This reframes the expiration from an administrative deadline into an operational liability tied to their current jobs. The offer to send 'specific cert expiration dates and permit numbers' is a concrete, actionable next step that doesn't require a meeting—it just requires a yes/no answer.

Data Sources
  1. County Permit Records Database - permit_number, permit_date, company_license_number, permit_status, issue_date, completion_deadline
  2. EPA ECHO Compliance Database - technician_name, certification_number, expiration_date, enforcement_action_type

The message:

Subject: 14 open permits, 2 techs losing refrigerant certs soon Your company has 14 active mechanical permits filed in the last 60 days, but 2 of your EPA 608-certified technicians have certifications expiring before those jobs close out. Assigning an uncertified tech to a refrigerant job mid-permit cycle is the scenario that triggers EPA enforcement. Should I send the specific cert expiration dates and permit numbers?
PQS Public Data Strong (8.4/10)

Play: EPA 608 Cert Expiration Risk Alert for Active HVAC Permit Holders

What's the play?

This play targets HVAC contractors who have pulled recent mechanical permits in their county while simultaneously having EPA 608-certified technicians whose certifications are expiring within the next 60-90 days. The data signals come from county permit records (showing active job load) cross-referenced against EPA ECHO certification records (showing expiration dates). These prospects are in acute pain because assigning an uncertified technician to a refrigerant job during an active permit cycle triggers EPA enforcement action—a $44,539 fine per violation—creating both immediate liability and operational chaos.

Why this works

The message works because it surfaces a compliance risk the prospect may have genuinely missed despite vigilance. The specificity of the permit count, cert expiration date, and penalty amount signals that you've done investigative work on their behalf, not sent a template. The close-ended question ('Is someone already tracking the renewal deadlines?') is easy to answer and creates psychological permission for the prospect to admit a gap without defensive posturing.

Data Sources
  1. County Permit Records Database - permit_number, permit_date, company_license_number, permit_type, jurisdiction
  2. EPA ECHO Compliance Database - technician_name, certification_number, certification_type, expiration_date, license_holder

The message:

Subject: 2 of your EPA 608 certs expire in March 2025 Two of your technicians have EPA 608 certifications expiring in March 2025, and your company pulled 14 mechanical permits in Maricopa County in the last 90 days. If those techs run a refrigerant call after March without a valid cert, you're looking at a $44,539 EPA fine per violation. Is someone already tracking the renewal deadlines?

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
County Permit Records Database permit_number, permit_date, company_license_number, permit_type, jurisdiction, permit_status, issue_date, completion_deadline, filing_date Identifying contractors with active job volume spikes and cross-referencing against compliance status and certification timelines
EPA ECHO Compliance Database technician_name, certification_number, certification_type, expiration_date, license_holder, violation_date, facility_id, penalty_amount, enforcement_action_type Tracking EPA 608 refrigerant certification expirations and identifying compliance violations and fines
Google Reviews API / Review Scraping review_text, review_date, star_rating, reviewer_name, complaint_keywords Monitoring review sentiment trends and identifying complaint clustering patterns that correlate with operational failures
EPA RCRA / RRP Database firm_certification_number, certification_status, expiration_date, firm_name Tracking Lead Safe RRP firm certification status and identifying contractors working under lapsed certifications
MLS Pending Sales Data property_address, listing_price, closing_date, loan_type, buyer_agent_contact, listing_agent_contact, zip_code, remarks_field Identifying geographic clusters of upcoming real estate transactions that trigger VA/FHA WDO inspection requirements
Pest Control License Database operator_name, license_number, service_area_zip_codes, license_status Cross-referencing licensed pest control operators against their service zones to target high-transaction geographic areas