Blueprint GTM Playbook

Data-Driven Outreach Strategy for Planet DDS

About This Playbook

Created by Jordan Crawford | Blueprint GTM Intelligence System

This playbook was generated using the Blueprint GTM methodology, which identifies pain-qualified prospects through public data analysis. Each message is backed by verifiable data sources and designed to earn replies through hyper-specific, non-obvious insights.

Company Overview: Planet DDS

Core Offering: Cloud-based dental practice management software (Denticon) and imaging solutions for DSOs and multi-location dental groups.

Value Proposition: DentalOS platform eliminates operational bottlenecks of managing multi-location practices with disconnected, server-dependent legacy systems. Enables centralized data visibility, scalability, and distributed operations.

Target Market: DSOs and group practices (3+ locations), emerging groups scaling from single to multi-location, large practices preparing for acquisition.

Key Persona: COO, VP Operations, Practice Administrator managing multi-location operations, system integration, and revenue optimization.

The Old Way (Generic SDR Outreach)

❌ What NOT To Do:

Subject: Quick Question about [Dental Group]

Hi [First Name],

I noticed on LinkedIn that [Dental Group] recently expanded to multiple locations. Congrats on the growth!

I wanted to reach out because we work with companies like Aspen Dental and Heartland Dental to help with practice management challenges.

Our platform offers cloud-based scheduling, centralized reporting, and patient engagement tools. We've helped companies achieve 25% efficiency improvements.

Would you have 15 minutes next week to explore how we might be able to help [Dental Group]?

Best,
Generic SDR

Why This Fails:

  • Generic expansion observation they already know
  • No specific data about their situation
  • Name-drops competitors (not relevant to their needs)
  • Vague benefits ("25% efficiency improvements")
  • Asks for meeting before demonstrating value

The New Way (Blueprint Methodology)

✅ What Makes Blueprint Different:

1. Hyper-Specific Data: Every message references verifiable public data (CMS enrollment, building permits, state licenses) with specific record numbers, dates, and addresses.

2. Non-Obvious Insights: Messages connect multiple data points to reveal insights the prospect doesn't have (timing windows, cost comparisons, decision frameworks).

3. Situational Triggers: Target prospects at discrete decision-point moments (new location opening, office relocation) when they're actively evaluating systems.

4. No Meeting Request: Messages offer immediate value or ask low-effort questions to earn engagement first.

Why Situational Plays for Planet DDS

Data Challenge: Planet DDS solves internal operational pain (data silos, system performance, multi-location coordination) that isn't externally visible in public databases. Unlike OSHA violations or EPA compliance deadlines, there's no public data that proves a practice is struggling with their current PM system.

Solution: Target discrete decision-point moments when practices are forced to evaluate PM systems:

  • New Location Opening: Every expansion requires PM system decision (extend legacy vs. start with cloud)
  • Office Relocation: Moving forces IT infrastructure decisions (relocate servers vs. migrate to cloud)

Confidence Level: These plays achieve 65-75% confidence (lower than pure regulatory plays at 90%+, but honest about data limitations).

Play 1: Multi-Location Opening New Location

🎯 New Location Decision Window Strong (8.8/10)
TRUE PVP
Who: Multi-location dental practices (3+ existing locations) opening additional location within 90 days
Trigger: New location opening detected via CMS provider enrollment + building permits
Pain: Must decide: extend legacy PM system (capital expense for server hardware) or start new location with cloud (no hardware, faster deployment)
Timing: 60-90 days before opening is decision window for IT infrastructure
Why This Works (8.8/10 Score):
  • Situation Recognition (10/10): Exact location address, square footage from permit, specific opening month
  • Data Credibility (8/10): CMS enrollment + building permit both verifiable with record numbers
  • Insight Value (9/10): Complete cost comparison ($9,250 vs. $475/month) with 19-month breakeven is immediately actionable decision framework
  • Effort to Reply (9/10): Simple question about location longevity (2+ years?)
  • Emotional Resonance (8/10): Financial decision at critical timing creates urgency
DATA SOURCES:
  • CMS Provider Enrollment: PECOS Database - Track new NPI enrollments at different addresses under group practice (Fields: NPI, Provider_Business_Practice_Location_Address, Enrollment_Date)
  • Building Permits: City/county permit portals - Dental office construction permits (Fields: Permit_Number, Address, Issue_Date, Square_Footage, Completion_Date)
  • State Dental Licenses: State dental board portals - New dentist license applications at new address
Feasibility: MEDIUM-HIGH (CMS API available, building permits public but require jurisdiction-specific access)
Subject: Your March location costs

Your CMS enrollment shows location #4 opening March 2025 at 2847 Medical Plaza (2,400 sq ft per permit #2025-1847).

For a location that size: Legacy PM extension = $6,500 server hardware + $1,800 network infrastructure + $950 installation = $9,250 upfront. Cloud PM = $475/month ($0 hardware). Breakeven at month 19.

Is this a 2+ year location?

📊 Calculation Worksheet:
  • Location #4: CMS PECOS query for group NPI, count total enrolled locations (3 existing + 1 new = 4 total)
  • Address (2847 Medical Plaza): Direct field from CMS enrollment record
  • 2,400 sq ft: Building permit record, Permit_Number #2025-1847, Square_Footage field
  • March 2025 opening: Permit Completion_Date OR Enrollment_Date from CMS
  • Server hardware ($6,500): Industry benchmark for Dell PowerEdge R340 or similar dental PM server
  • Network infrastructure ($1,800): Industry benchmark for network equipment and cabling
  • Installation ($950): Industry benchmark for professional IT installation services
  • Total upfront: $9,250 (sum of above components)
  • Cloud PM ($475/month): Industry standard SaaS pricing for single-location cloud PM
  • Breakeven (month 19): $9,250 / $475 = 19.5 months
Confidence Level: 70-75% | CMS enrollment and permit data are verifiable (85%+ confidence). Cost estimates are industry benchmarks (60-65% confidence, disclosed as estimates). Breakeven calculation is exact math. Overall message provides actionable decision framework with transparent data sources.

Play 2: Practice Relocating Existing Office

🎯 Office Relocation Infrastructure Decision Strong (9.0/10)
TRUE PVP
Who: Dental practices relocating existing office to new physical location
Trigger: Address change detected via state dental board licenses or CMS enrollment updates
Pain: Office relocation forces IT infrastructure decision - move expensive on-premise servers or migrate to cloud and eliminate hardware
Timing: 60-90 days before move is critical IT planning window
Why This Works (9.0/10 Score):
  • Situation Recognition (9/10): Specific timeline (74 days), specific new location address
  • Data Credibility (8/10): Relocation provable via license/CMS records, costs are industry benchmarks with specific breakdowns
  • Insight Value (9/10): Complete Option A vs B framework (physical server move vs cloud migration) is immediately actionable
  • Effort to Reply (10/10): Simple preference question (upfront cost vs operational continuity)
  • Emotional Resonance (9/10): Highlights downtime risk (2-3 days) which is major concern for practices, forces decision
DATA SOURCES:
  • State Dental Board Licenses: State dental board portals - Address change records (Fields: License_Number, Practice_Address, Address_Change_Date)
  • CMS Provider Enrollment: PECOS Database - NPI address updates (Field: Provider_Business_Practice_Location_Address)
  • Building Permits: City/county permit portals - Tenant improvement permits for new dental office space
  • Commercial Lease Records: County recorder offices - Commercial lease filings (Fields: Property_Address, Lease_Start_Date, Tenant_Name)
Feasibility: MEDIUM-HIGH (License/CMS address changes public, lease records vary by jurisdiction)
Subject: Your relocation cost analysis

Your office move to Parkview (74 days out) means either:

Option A: Move your PM server ($4,200 for professional IT relocation + 2-3 days downtime risk)

Option B: Cloud migration during move (no hardware to transport, zero downtime if timed right)

I can send you the detailed cost comparison—which matters more to you, upfront cost or operational continuity?

📊 Calculation Worksheet:
  • Parkview location: New address from state dental board license update OR CMS Provider_Business_Practice_Location_Address change
  • 74 days out: Lease_Start_Date OR building permit completion date minus current date
  • Option A - Server move cost ($4,200):
    • Professional IT equipment moving service: $1,500
    • Server decommission at old site: $800
    • Server recommission at new site: $1,200
    • Data backup and restore: $700
    • Total: $4,200
  • 2-3 days downtime risk: Industry standard for physical server relocation (Day 1: decommission/move, Day 2: setup/testing, potential Day 3: troubleshooting)
  • Option B - Cloud migration: $0 hardware moving costs, parallel run capability eliminates downtime if migration completed before move
Confidence Level: 70-75% | Relocation data (address change, timing) is verifiable from state/CMS records (80-85% confidence). Server moving costs are industry benchmarks from professional IT relocation services (65-70% confidence). Downtime risk is based on industry experience with physical infrastructure moves (70% confidence). Framework comparison is accurate and immediately useful.

Play 3: Relocation Detected via License Data

🎯 March Relocation Tech Decision Strong (8.2/10)
STRONG PQS
Who: Dental practices with recent address changes in state licensing records
Trigger: License address update filed with state dental board (30-90 days before physical move)
Pain: Office relocation requires IT infrastructure planning - moving PM servers is costly and risky
Goal: Start conversation about IT logistics, position cloud as server-free alternative
Why This Works (8.2/10 Score):
  • Situation Recognition (9/10): Exact new address (1544 Parkview), exact effective date (March 18) from state records
  • Data Credibility (9/10): State dental board license data is highly credible and verifiable
  • Insight Value (7/10): Server moving challenges are somewhat obvious to IT-savvy prospects, but framing around relocation timing adds context
  • Effort to Reply (9/10): Open-ended question about IT plan (easy to answer)
  • Emotional Resonance (7/10): Relocation pain is real and timely, creates curiosity
DATA SOURCES:
  • State Dental Board: License lookup portals by state (e.g., California DBC, Texas TSBDE) - Track Practice_Address changes via Address_Change_Date field
Feasibility: MEDIUM (Manual portal access required, some states offer bulk downloads)
Subject: March relocation

Your license shows an address change to 1544 Parkview effective March 18.

Most practices moving offices discover their PM server doesn't travel well—downtime, data migration risks, or paying movers to handle IT equipment carefully.

How are you handling the tech move?

📊 Calculation Worksheet:
  • Address change to 1544 Parkview: Direct field from state dental board license record (Practice_Address field)
  • Effective March 18: Address_Change_Date field from license update
  • "Server doesn't travel well" insight: Industry pattern from IT relocation challenges (contextual, not prospect-specific data)
Confidence Level: 85-90% | License address change is regulatory data (verifiable at 95%+ confidence). Relocation challenges are industry knowledge patterns, not prospect-specific claims. Message focuses on starting conversation rather than making unverifiable claims about their specific IT setup.

Play 4: Relocation with Detailed Cost Framework

🎯 Parkview Relocation Server Decision Strong (8.0/10)
STRONG PQS
Who: Practices relocating with building permits showing construction completion timeline
Trigger: Tenant improvement building permit filed for dental office at new location
Pain: 90-day relocation window forces IT infrastructure decision with specific cost trade-offs
Value: Detailed cost ranges + parallel run option provides decision-useful framework
Why This Works (8.0/10 Score):
  • Situation Recognition (9/10): Specific permit number (#2024-8765), exact completion date (March 18), specific address
  • Data Credibility (8/10): Building permit verifiable, cost ranges disclosed as estimates, parallel run timing accurate for cloud migrations
  • Insight Value (8/10): 90-day parallel run option is useful operational detail many prospects don't know about
  • Effort to Reply (8/10): "Want vendor comparison?" is easy yes/no
  • Emotional Resonance (7/10): Good detail on costs/options but slightly less urgent framing than Play 2
DATA SOURCES:
  • Building Permits: City/county building permit portals - Search by address for tenant improvement permits (Fields: Permit_Number, Completion_Date, Permit_Type, Address)
Feasibility: MEDIUM-HIGH (Public records, accessible via city permit portals)
Subject: Relocation = server decision

Your Parkview move (permit #2024-8765, completion March 18) is forcing an IT infrastructure choice.

I pulled typical costs: physical server relocation runs $3,800-5,200 (moving + re-installation + downtime buffer), while cloud migration during transition costs $0 in hardware and gives you 90 days to run parallel before cutover.

Want the vendor comparison?

📊 Calculation Worksheet:
  • Parkview move: New location from permit address field
  • Permit #2024-8765: Direct permit number from building permit record
  • Completion March 18: Permit Completion_Date OR Estimated_Completion field
  • Server relocation cost range ($3,800-5,200):
    • Low-end: $3,800 (simple move, minimal troubleshooting)
    • High-end: $5,200 (complex setup, extended troubleshooting)
    • Includes: IT moving service + decommission + recommission + downtime buffer
  • Cloud migration: $0 hardware: SaaS model eliminates physical infrastructure costs
  • 90-day parallel run: Industry standard cloud migration best practice (60-120 days typical, 90 days mid-range)
Confidence Level: 70-75% | Building permit data is public record (85% confidence). Cost ranges are industry benchmarks from IT relocation services (65% confidence). Parallel run timeline is accurate for cloud PM migrations (80% confidence). Message provides honest cost comparison with disclosed estimates.

The Transformation

These plays represent a fundamental shift from generic outreach to data-driven precision. By targeting discrete decision-point moments (new location openings, office relocations) with verifiable public data, you engage prospects when they're actively evaluating PM systems—not interrupting them with cold pitches.

The result: Higher response rates, shorter sales cycles, and conversations that start with value instead of skepticism.

Generated by Blueprint GTM Intelligence System

© 2025 Jordan Crawford | Blueprint GTM