About This Playbook:
This playbook was built using the Blueprint GTM methodology by Jordan Crawford. Blueprint identifies pain-qualified segments using hard data from government databases, competitive intelligence, and velocity signals—not generic pain points or soft proxies like funding or hiring.
Jordan Crawford is the architect of the Blueprint GTM system, which has generated millions in pipeline for B2B companies by replacing spray-and-pray outreach with hyper-specific, data-driven messages that buyers actually respond to.
Company Overview
Feeld.ai is an AI-powered field service management platform that helps companies with mobile workforces optimize scheduling, tracking, and technician productivity. The platform offers smart scheduling/dispatching, real-time GPS tracking, skills-based technician matching, and an AI assistant (AURA) that provides instant access to technical documentation and setup procedures.
Proven Results: Customers achieve 23% improvement in first-time fix rate (FTFR), 11% reduction in response time, and 14% reduction in mean time to repair (MTTR).
Target Market: Utilities, HVAC contractors, telecom infrastructure providers, and equipment maintenance companies with 10+ field technicians managing SLA obligations and compliance requirements.
The Old Way: Generic Outreach
❌ What NOT to Do
Subject: Quick Question about [Company Name]
Hi [First Name],
I noticed on LinkedIn that [Company Name] recently expanded operations. Congrats on the growth!
I wanted to reach out because we work with companies like [Competitor 1] and [Competitor 2] to help with field service efficiency and technician productivity.
Our platform offers smart scheduling, real-time tracking, and AI-powered assistance. We've helped companies improve their first-time fix rates by up to 25%.
Would you have 15 minutes next week to explore how we might be able to help [Company Name] optimize your field operations?
Why This Fails: Generic growth signal (expansion), no company-specific data, industry benchmarks instead of prospect's actual pain, asks for meeting without providing value, sounds like every other vendor email.
The New Way: Hard Data, Non-Obvious Insights
Blueprint GTM replaces soft signals with verifiable government data and competitive intelligence that proves the prospect is in a painful situation RIGHT NOW. Every claim is traceable to a specific database field or API endpoint.
The Texada Test (Quality Framework):
Every Blueprint message must pass three criteria:
- Hyper-specific: Exact dates, record numbers, percentages—not "recent" or "many"
- Factually grounded: Every claim traces to a documented data source the prospect can verify
- Non-obvious synthesis: Insight the persona doesn't already have (connecting dots they can't see)
Pain-Qualified Segment (PQS) Plays
PQS messages mirror an exact painful situation using government data. Goal: Earn a reply by proving you understand their specific problem.
Play #1: Utilities with High PSC Response Time Complaints
Strong (9.2/10)
TRIGGER EVENT:
Utility company has high volume of state Public Service Commission (PSC) customer complaints specifically citing "delayed response" or "missed service window," indicating systematic scheduling/routing inefficiency and regulatory compliance risk.
WHY IT WORKS:
Field Service Managers at utilities are measured on SLA compliance and customer satisfaction. PSC complaints = regulatory risk (fines, rate case impact, mandatory reporting). Quantifying what percentage of complaints are response-time related (vs billing, quality, etc.) is a NON-OBVIOUS insight they don't extract themselves. Connects operational gap (routing inefficiency) to regulatory consequence.
DATA SOURCES:
Primary: State Public Utilities Commission Complaint Databases (varies by state - California CPUC example linked)
Fields: Company name, complaint ID, filing date, complaint description/category
Detection Method: Search PSC database by company name → extract complaints from last 12 months → keyword search complaint text for "delayed," "late," "missed appointment," "no-show," "slow response" → calculate percentage
Confidence: 80% (government data, but complaint categorization varies by state)
CALCULATION WORKSHEET:
Claim: "37 customer complaints filed with California Public Utilities Commission in past 12 months—23 of these (62%) cite 'delayed arrival' or 'missed service window'"
Data Source: California CPUC Consumer Complaints database
Raw Data: Search company name → extract all complaints with filing_date in last 12 months → total count = 37
Calculation: Extract complaint description text for all 37 → keyword search for response time indicators → 23 matches → 23/37 = 62%
Verification: Prospect can access CPUC complaint search and filter by their company name
Subject: 37 PSC complaints, 12 months
Your company has 37 customer complaints filed with the California Public Utilities Commission in the past 12 months—23 of these (62%) cite "delayed arrival" or "missed service window."
State mandate requires 24-hour emergency response, but complaint volume suggests systematic routing inefficiency.
Is dispatch meeting SLA requirements?
Play #2: Utilities with Repeat OSHA Safety Violations
Strong (9.0/10)
TRIGGER EVENT:
Utility receives multiple OSHA "Serious" or "Repeat" violations within 18-24 months, with violation descriptions explicitly citing "unqualified employee," "inadequate training," or similar language—proving dispatch is sending wrong-skilled technicians to hazardous jobs.
WHY IT WORKS:
Operations Directors know they have OSHA violations, but they don't always connect the root cause to their dispatch system's inability to match technician certifications (confined space, electrical, elevated work) to job requirements. This synthesis reveals a SKILLS-MATCHING gap, not just a "safety culture" issue. Creates urgency (repeat violations = escalating fines, willful classification risk) and directly connects to Feeld.ai's skills-based dispatch feature.
DATA SOURCES:
Primary: OSHA Establishment Search
Fields: ESTAB_NAME (company name), INSP_NR (inspection number), OPEN_DATE (inspection date), VIOL_TYPE (Serious/Willful/Repeat), STANDARD (violation code), VIOL_DESC (violation description text)
Detection Method: Search company name → filter inspections to last 18-24 months → extract violations with VIOL_TYPE = "Serious" or "Repeat" → keyword search VIOL_DESC for "unqualified," "inadequate training," "untrained"
Confidence: 95% (pure government data, exact records)
CALCULATION WORKSHEET:
Claim: "OSHA citation #987654321 on March 15, 2025 for violation 1926.451(g)(1)—unqualified employee performing elevated work" + "second 'unqualified personnel' citation in 18 months"
Data Source: OSHA Establishment Search database
Raw Data: Search company name → extract all inspections in 18-month window → filter for violations mentioning "unqualified" in VIOL_DESC
Calculation: Count matches = 2 violations (March 2025, October 2023) → extract INSP_NR, OPEN_DATE, STANDARD for each
Verification: Go to OSHA website, search company name, view inspection records
Subject: OSHA inspection #987654321
Your substation crew received OSHA citation #987654321 on March 15, 2025 for violation 1926.451(g)(1)—unqualified employee performing elevated work on energized equipment.
This is your second "unqualified personnel" citation in 18 months, following inspection #923456789 in October 2023.
Is dispatch sending wrong-skilled techs to hazardous jobs?
Play #3: Utilities with PSC Complaints (Regulatory Risk Angle)
Strong (8.6/10)
TRIGGER EVENT:
Same data source as Play #1, but framed to emphasize the REGULATORY RISK and downstream consequences (fines, rate case impact, mandatory corrective action plans) rather than just operational inefficiency.
WHY IT WORKS:
Some buyers respond more to regulatory/compliance framing than operational efficiency framing. By explicitly mentioning "regulatory risk" and connecting response time failures to PSC oversight, this variant appeals to risk-averse executives who prioritize compliance. The question "Tracking actual vs promised arrival times?" is more operational/tactical than Play #1's question, making it easier to reply with a specific system/process answer.
DATA SOURCES:
Same as Play #1 (State PSC Complaint Databases)
Confidence: 80%
CALCULATION WORKSHEET:
Same methodology as Play #1—complaint count, keyword categorization, percentage calculation.
Subject: 62% response time complaints
California CPUC data shows 23 of your 37 customer complaints in 2024-2025 specifically mention "late technician arrival" or "missed appointment window."
Your emergency response SLA is 24 hours, but complaint frequency suggests dispatch routing delays are creating regulatory risk.
Tracking actual vs promised arrival times?
Play #4: HVAC Contractors with FTFR-Driven Low Google Ratings
Strong (8.2/10)
TRIGGER EVENT:
Licensed HVAC contractor has Google Business Profile rating below 3.5 stars with 50+ reviews, and a significant percentage of recent reviews explicitly mention "multiple visits needed," "had to come back," or similar first-time fix rate failure language.
WHY IT WORKS:
HVAC service managers know their Google rating is poor, but they don't usually quantify HOW MUCH of the damage is attributable to FTFR failures vs other issues (pricing disputes, scheduling, technician attitude). This message performs competitive intelligence (review sentiment analysis) to isolate the FTFR-specific reputation damage. For HVAC contractors, online reputation directly impacts lead generation—low ratings = fewer quote requests. Offering "the full list of FTFR-related reviews" provides immediate value.
DATA SOURCES:
Primary: Google Maps Places API
Fields: rating (overall stars), user_ratings_total (total reviews), reviews[].text (review content), reviews[].time (timestamp)
Detection Method: API call with place_id → extract last 50 reviews sorted by time → keyword search reviews[].text for FTFR indicators ("came back," "multiple visits," "still not fixed," "had to return," "second trip") → count matches
Confidence: 85% (review sentiment analysis, keyword matching may miss paraphrased mentions but direct quotes are verifiable)
CALCULATION WORKSHEET:
Claim: "2.8 stars across 87 reviews" + "17 of your last 50 reviews (34%) explicitly mention 'had to come back' or 'needed multiple visits'"
Data Source: Google Maps Places API
Raw Data: API response for company's place_id → rating=2.8, user_ratings_total=87 → extract reviews[].text for last 50 reviews
Calculation: Keyword search 50 review texts for FTFR language → 17 matches → 17/50 = 34%
Verification: Prospect can read their Google Business Profile reviews and manually count FTFR mentions
Subject: Your Google review breakdown
I analyzed your Google Business reviews—2.8 stars across 87 reviews.
17 of your last 50 reviews (34%) explicitly mention "had to come back" or "needed multiple visits," suggesting first-time fix rate issues are damaging your online reputation.
Want the full list of FTFR-related reviews?
The Transformation
Blueprint GTM doesn't sell features or benefits. It sells non-obvious insights derived from data the prospect can't easily access themselves. By mirroring their exact situation with verifiable data, you earn the right to a conversation.
Results to expect:
- 8-15% reply rates (vs 1-3% for generic outreach)
- Qualified conversations with decision-makers who have budget and urgency
- Shorter sales cycles (pain is already proven, no discovery needed)
- Higher close rates (you led with their problem, not your product)