Blueprint GTM Playbook

Zywave
Data-Driven Outreach Plays for Insurance Technology

About This Methodology

This playbook was created by Jordan Crawford, founder of Blueprint GTM. Jordan specializes in permissionless value proposition (PVP) development—outreach messages that deliver immediate, actionable value using publicly available data synthesis.

The Blueprint methodology replaces generic "spray and pray" outreach with hyper-specific, data-grounded messages that prospects can verify and act on immediately. Every play in this playbook is built on real government databases, competitive intelligence, and velocity signals—not assumptions or soft signals.

The Old Way: Generic Outreach

Most sales teams send messages like this to insurance agencies:

❌ Generic SDR Email Example

Subject: Quick Question about Zywave Hi [First Name], I noticed on LinkedIn that Zywave recently expanded its product offerings and has been growing significantly. Congrats on the momentum! I wanted to reach out because we work with companies like Applied Systems and Vertafore to help with agency management and client engagement. Our platform provides integrated workflows, compliance tracking, and data analytics. We've helped agencies achieve 30% faster onboarding and 25% improvement in client retention. Would you have 15 minutes next week to explore how we might be able to help Zywave continue its growth trajectory? Best, Generic SDR
Why This Fails: No specific data about the prospect's situation. Uses soft signals ("growing," "momentum") and generic pain points. Requires a meeting before providing any value. The prospect deletes this immediately because it could be sent to any company.

The New Way: Hard Data + Non-Obvious Synthesis

✅ The Blueprint Difference

Hard Data: Every claim in these messages traces to a specific government database field, competitive intelligence source, or velocity signal. No assumptions, no soft signals like "I noticed you're growing" or "congrats on the funding."

Non-Obvious Synthesis: These messages combine 2-3 data sources to reveal insights the prospect doesn't have. They know their licenses are expiring—they don't know how their multi-state complexity + hiring pace creates documented compliance pinch points vs single-state agencies.

Two Message Types:

  • PQS (Pain-Qualified Segment): Mirrors exact painful situation with verifiable data to spark conversation
  • PVP (Permissionless Value Proposition): Delivers immediately actionable analysis the prospect can use without replying

Target Market Analysis

Zywave's Core Offering

Zywave provides integrated insurance technology solutions—agency management systems (AMS), client engagement platforms (Client Cloud), compliance tracking, and data analytics. The company serves 15,000+ insurance organizations including all top 100 US insurance firms, with recognition in the Forrester Wave for Insurance Agency Management Systems.

Ideal Customer Profile (ICP)

Industries: Independent insurance agencies, insurance brokerages, carriers, and MGAs (managing general agents)

Company Scale: Mid-market to enterprise agencies (20-500+ employees, multi-state operations)

Operational Context: Agencies struggling with fragmented systems (separate AMS, CRM, compliance tools), multi-state licensing complexity, compliance tracking gaps, and inability to leverage data for competitive advantage

Target Persona

Title: Operations Manager, Chief Operating Officer, Chief Information Officer, Agency Principal

Responsibilities: Managing technology stack, ensuring compliance across jurisdictions, coordinating license renewals, overseeing producer onboarding, maintaining E&O insurance requirements, scaling operations during growth

KPIs: License renewal compliance rate, E&O claim frequency, operational cost per producer, system uptime, onboarding time-to-productivity, client retention rate

Blind Spots: Don't realize how their multi-state complexity compounds compliance risk vs single-state agencies. Don't benchmark their tech stack fragmentation costs vs integrated platforms. Don't see how hiring velocity creates system strain that competitors avoid.

Strong PQS Plays

These messages mirror exact painful situations with verifiable data to spark high-quality conversations.

Play #1: Multi-State License Renewal Pressure Good (7.6/10)
STRONG PQS
Who This Targets: Independent insurance agencies operating in 5+ states with 40+ producers and active hiring (3+ job postings in 60 days).

The Trigger Event: High volume of producer license expirations (15%+ of total licenses expiring within 90 days) coinciding with rapid hiring creates compliance coordination chaos. Multi-state agencies must manage different CE requirements, renewal windows, and carrier appointment protocols across jurisdictions while onboarding new producers who need immediate licensing.

Why This Hurts: License lapses suspend producers from writing business, creating revenue loss and client service disruptions. E&O insurance claims spike when agencies fail to track renewal requirements properly. Hiring surges compound the problem because compliance teams are simultaneously coordinating renewals AND processing new producer appointments.

Why This Message Works (Buyer Critique: 7.6/10)

Situation Recognition (8/10): Hyper-specific with exact license counts (47), date ranges, and state-by-state breakdown. If accurate, this perfectly mirrors the operations manager's current situation.

Data Credibility (7/10): NIPR license data is authoritative and verifiable. Job posting counts are observable. Slight concern about data freshness since NIPR requires paid subscription.

Insight Value (7/10): The state-by-state expiration calendar is genuinely useful—most ops managers don't have this consolidated view. The connection between hiring surge and renewal coordination is logical but somewhat obvious.

Effort to Reply (9/10): Dead simple yes/no question: "Want the full expiration calendar?"

Emotional Resonance (7/10): Triggers concern if the recipient doesn't have renewals well-organized. Creates curiosity about how the sender obtained this specific data.

DATA SOURCES: NIPR (National Insurance Producer Registry) - Producer license records including expiration dates, states, license types, disciplinary actions (requires commercial subscription ~$1000+/year for bulk access)

Indeed + LinkedIn Jobs - Job posting velocity by company (free search, or $500-2000/mo for API access)

Confidence Level: 70% (hybrid approach - requires paid NIPR subscription, but data is authoritative once accessed)
Subject: 47 licenses expire in 73 days
Your agency has 47 producer licenses expiring between March 15 and April 30 across six states (FL: 18, TX: 12, GA: 9, NC: 5, SC: 2, VA: 1). You're hiring three new producers right now per your job postings—renewal coordination across six states while onboarding is a documented compliance pinch point. Want the state-by-state expiration calendar?

📊 Calculation Worksheet

CLAIM: "47 producer licenses expiring between March 15 and April 30"
Data Source: NIPR (National Insurance Producer Registry)
Fields: LICENSE_NUMBER, EXPIRATION_DATE, STATE, PRODUCER_NAME, AGENCY_NPN
Calculation: Query all licenses for agency NPN → Filter WHERE EXPIRATION_DATE BETWEEN '2026-03-15' AND '2026-04-30' → COUNT = 47
Verification: "Log into NIPR PDB, search agency NPN, export license report, filter by expiration date range"
CLAIM: "across six states (FL: 18, TX: 12, GA: 9, NC: 5, SC: 2, VA: 1)"
Data Source: NIPR (same query)
Fields: STATE, LICENSE_NUMBER
Calculation: From same 47 licenses → GROUP BY STATE → COUNT per state
Verification: "Same NIPR report, group by state column"
CLAIM: "hiring three new producers right now per your job postings"
Data Source: Indeed + LinkedIn job search
Fields: job_title, company_name, posted_date
Calculation: Search "insurance producer [agency name]" posted within 60 days → Manual count or API query = 3 postings
Verification: "Search '[agency name] insurance producer' on Indeed/LinkedIn, filter to last 60 days"
Note: Job boards may not capture all hiring; postings may be expired/filled (65% confidence)
Play #2: Rapid Growth + System Fragmentation Good (7.6/10)
STRONG PQS
Who This Targets: Insurance agencies experiencing measurable growth (30%+ review velocity increase year-over-year) while hiring rapidly (5+ positions in 90 days).

The Trigger Event: Sharp increase in Google review velocity (observable proxy for client growth) combined with active producer hiring signals operational scale pressure. When agencies run separate platforms for core functions (AMS, CRM, compliance), growth amplifies system fragmentation costs exponentially.

Why This Hurts: Every new hire must learn 3+ different systems before becoming productive, extending time-to-first-commission from 30 days to 60-90 days. Client data lives in silos, preventing cross-sell opportunities and creating service gaps. Compliance tracking failures increase as volume overwhelms manual processes.

Why This Message Works (Buyer Critique: 7.6/10)

Situation Recognition (8/10): Specific and verifiable—47% review growth with exact counts (83 vs 56) that the recipient can immediately check in their Google Business Profile.

Data Credibility (8/10): Google Maps review data is directly verifiable and authoritative. The YoY comparison is compelling evidence of growth.

Insight Value (7/10): The connection between client growth signals (reviews) and operational system strain is logical and relevant. Not revolutionary, but useful for ops managers focused on scaling infrastructure.

Effort to Reply (8/10): Simple question about onboarding process—easy to answer with 1-2 sentences.

Emotional Resonance (7/10): Resonates strongly if the agency is actually feeling growth pains. Creates validation that their operational struggles are visible in external data.

DATA SOURCES: Google Maps Places API - Review data including timestamps, ratings, text (generous free tier, $5 per 1000 requests after)

Indeed + LinkedIn Jobs - Job posting velocity

BuiltWith - Technology stack detection ($295/mo for API, manual inspection free but time-consuming)

Confidence Level: 70-75% (hybrid - review data is reliable, tech stack detection is less certain and may not reflect internal systems)
Subject: 47% review growth
Your Google reviews jumped 47% year-over-year (83 in 2025 vs 56 in 2024)—strong growth signal. You're hiring five producers in 90 days to support this expansion, but your current tech stack uses separate systems for core operations based on platform detection—onboarding complexity scales faster than headcount. How are new hires getting up to speed?

📊 Calculation Worksheet

CLAIM: "Google reviews jumped 47% year-over-year (83 in 2025 vs 56 in 2024)"
Data Source: Google Maps Places API
Fields: reviews[].time (UNIX timestamp)
URL: maps.googleapis.com/maps/api/place/details/json?place_id=[ID]
Calculation: All reviews with timestamps → COUNT where year=2025 vs year=2024 → (83-56)/56 = 48.2% ≈ 47%
Confidence: 85% (API data reliable, assumes reviews correlate with growth)
Verification: "Check your Google Business Profile > Reviews, filter by year"
CLAIM: "hiring five producers in 90 days"
Data Source: Indeed/LinkedIn job search
Fields: job_title, posted_date, company_name
Calculation: Search "[agency name] insurance producer" posted within 90 days → Count = 5 postings
Confidence: 65% (may not capture all hiring activity)
Verification: "Search your company name + 'insurance producer' on job boards"
CLAIM: "separate systems for core operations based on platform detection"
Data Source: BuiltWith API or manual website inspection
Fields: Detected technologies, platform categories
Calculation: Website technology scan → Identify distinct platforms in AMS, CRM, compliance categories
Confidence: 60% (tech detection not 100% accurate, may miss internal systems)
Verification: "Ask agency directly what systems they use" (tech stack detection has limitations)

Additional Strong PQS Plays

Play #3: Multi-State Compliance Complexity Good (7.2/10)
STRONG PQS
Who This Targets: Agencies with 50+ producers operating in 6+ states.

The Trigger Event: Large volume of licenses (40+) expiring within 90 days across multiple jurisdictions, each with different continuing education (CE) requirements, renewal windows, and carrier appointment protocols.

Why This Hurts: Compliance teams at multi-state agencies spend 15-20 hours per month manually coordinating renewals—tracking CE completion across different state portals, managing staggered renewal deadlines, and ensuring carrier appointments remain active. During hiring surges, this coordination load compounds as new producers need expedited appointments.

Why This Message Works (Buyer Critique: 7.2/10)

Situation Recognition (8/10): Specific license counts, state count, and time window are verifiable and concrete.

Data Credibility (8/10): CE requirements are publicly documented state regulations. License data from NIPR is authoritative.

Insight Value (6/10): The recipient likely already knows CE requirements vary by state—this is their daily reality. The connection between jurisdictional complexity and tracking burden is somewhat obvious to operations managers.

Effort to Reply (8/10): Simple question about current tracking methods.

Emotional Resonance (6/10): Mildly relatable but not particularly urgent or novel.

DATA SOURCES: NIPR - Producer license data

State DOI websites - CE requirements by state (publicly documented regulations)

Confidence Level: 70% (NIPR data requires subscription, CE requirements are public knowledge)
Subject: 6 states, 47 renewals
Your agency has 47 producer licenses expiring in the next 90 days across six states—Florida requires 24 CE hours, Texas requires 30, Georgia requires 12, each with different renewal windows. Coordinating 47 renewals across six different regulatory frameworks while your compliance team onboards three new hires creates documented tracking gaps. How are you managing this right now?
Play #4: Onboarding Delays from System Fragmentation Good (7.0/10)
STRONG PQS
Who This Targets: Growing agencies posting 5+ producer positions in 90 days while running 3+ separate systems for core functions.

The Trigger Event: Rapid hiring pace combined with fragmented technology stack (separate AMS, CRM, compliance platforms) creates onboarding complexity that extends time-to-productivity.

Why This Hurts: Each new producer needs 15-20 hours of system training spread across 3+ platforms before they can effectively manage client relationships and write business. Agencies with integrated platforms onboard producers in half the time, creating competitive disadvantage. During high-velocity hiring periods, training bandwidth becomes a bottleneck.

Why This Message Works (Buyer Critique: 7.0/10)

Situation Recognition (7/10): Specific hire count (5 in 90 days) and system count (3) if detection is accurate. Some uncertainty around tech stack detection accuracy.

Data Credibility (6/10): Job postings are verifiable. Tech stack detection is less certain—may not capture internal systems, and detection tools aren't 100% accurate.

Insight Value (7/10): The connection between system count and onboarding complexity is logical. The 15-20 hours training estimate provides useful context for quantifying the problem.

Effort to Reply (8/10): Easy question about current onboarding process.

Emotional Resonance (7/10): Resonates if the agency is actually struggling with onboarding during rapid hiring. Less impactful if they've already addressed this pain point.

DATA SOURCES: Indeed + LinkedIn - Job posting velocity

BuiltWith - Tech stack detection ($295/mo API or manual inspection)

Confidence Level: 60-65% (job posts verifiable, tech stack detection has limitations)
Subject: 5 hires, 3 systems
You've posted five producer roles in 90 days while running separate platforms for agency management, CRM, and compliance based on your tech stack. Each new hire needs training across three different systems before writing business—that's 15-20 hours of system training per producer vs integrated platforms. How are you handling onboarding right now?

The Transformation

These four plays represent a fundamentally different approach to B2B outreach for insurance technology. Instead of interrupting with generic value propositions and meeting requests, you're leading with hyper-specific, verifiable data about situations they're experiencing right now.

The operations manager reading "47 licenses expire in 73 days across six states" doesn't need to take a meeting to understand the value—they immediately see you understand their world at a granular level. That's what earns replies.

This is Blueprint GTM: transforming publicly available data into non-obvious insights that insurance agencies can't ignore.