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 Intergraph (Hexagon) 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.
Company URL: https://intergraph.com
Core Problem They Solve: Enterprise organizations lack integrated geospatial and infrastructure data management systems to plan, design, and operate critical infrastructure assets (utilities, transportation, government) efficiently and safely.
Product Type: Enterprise Software | Geospatial Intelligence Platform
Target ICP: Large enterprises (500+ employees) managing extensive asset networks including electric utilities, water utilities, gas utilities, telecommunications carriers, oil and gas operators, government agencies, and transportation infrastructure organizations. These companies require real-time operational visibility, regulatory compliance, emergency response capabilities, and capital asset planning across distributed geographic areas.
Primary Buyer Persona: Director of GIS Operations / Infrastructure Operations Manager / VP of Engineering Operations responsible for network design, asset lifecycle management, real-time operational visibility, regulatory compliance, and cross-departmental collaboration for capital projects.
These messages provide actionable intelligence before asking for anything. The prospect can use this value today whether they respond or not.
Benchmark major outage response performance across utilities in the same metro region using actual storm event data. Show prospects exactly how their restoration time compares to nearby peers during recent verifiable weather events.
Storm response is the #1 visible KPI for utility operations managers. Every minute of delay is public, embarrassing, and measured. When you tell them "you're 40% slower than the metro average during the November storm," you're hitting their most painful public performance metric with recent, verifiable data. The crew dispatch analysis offers immediate tactical value to improve their most scrutinized operational outcome.
This play requires aggregated storm response metrics (restoration times, crew dispatch patterns) across 22+ utilities in the same metro region during a recent major outage event.
This synthesis of actual performance data from comparable utilities is proprietary - only you have visibility into how peer utilities performed during the same weather event.Use internal benchmarking data from regional utility customers to show prospects exactly how their outage-to-crew-dispatch time compares to peer utilities. Quantify the specific time gap and offer detailed process analysis to identify where delays occur.
Outage response time is the single most visible KPI for infrastructure operations managers. When you tell them "you're 22 minutes slower than regional peers" with specific numbers (53 minutes vs. 31 minutes), you're exposing a performance gap they feel daily but may not have quantified. The offer of a benchmark showing dispatch process gaps provides immediate diagnostic value to improve their #1 operational metric.
This play requires aggregated outage response metrics (outage-to-crew-dispatch times, process steps) across 38+ regional utility customers with performance measurement capabilities.
This benchmarking data is proprietary to your customer base - competitors cannot provide regional peer comparisons without similar implementation scale.Use recent customer implementation data from the same state to show prospects realistic deployment timelines and ROI achievement. Provide concrete evidence that peer utilities completed full asset digitization and hit positive ROI within specific timeframes.
State-level specificity makes this immediately relevant - these are regulatory peers facing the same compliance environment. The recent timeline (Q4 2024) proves this isn't outdated case study material. The specific ROI timing (month 8) and tangible improvements (38% faster response, reduced truck rolls) help the prospect build an internal business case using data from utilities they likely know by name. The phasing approach offers practical implementation guidance they can use today.
This play requires tracked deployment timelines, ROI metrics, and operational improvement measurements from 5+ utility customers in the same state.
This state-specific implementation data with measured outcomes is proprietary to your customer base - competitors cannot provide this regional peer evidence.Benchmark capital project approval timelines across utility customers to identify prospects with abnormally long planning-to-approval cycles. Show exactly how much time they're losing compared to peer utilities and quantify the financial impact of delayed projects.
Capital project delivery timeline is a critical KPI for infrastructure directors. A 9-week delay in planning-to-approval directly impacts project delivery, budget utilization, and executive visibility. The $12M in accelerated projects quantifies the financial upside of process improvement. The offer of a process comparison showing "where your 9 weeks are lost" provides immediate diagnostic value to identify bureaucratic bottlenecks.
This play requires aggregated capital project approval timelines and process analysis across 29+ utility customers with project tracking capabilities.
This benchmarking data showing actual planning cycle bottlenecks is proprietary to your implementation base - competitors cannot provide this without similar project visibility.Analyze work order and data request patterns across utility customers to identify prospects with abnormally high internal data request volumes. Show exactly how much engineering overhead they're burning on manual data fulfillment compared to utilities with integrated platforms.
Engineering directors feel the pain of constant data requests from field crews but may not have quantified the volume. When you tell them "340+ internal data requests monthly," you're surfacing a metric they haven't measured but immediately recognize as a massive time sink. The 78% reduction and $180K annual savings tie directly to their budget concerns. The workflow analysis showing where requests originate provides immediate tactical value to justify platform investment or headcount decisions.
This play requires analysis of work order ticket volume, data request patterns, and engineering overhead across 41+ utility customers with work order system integration.
This benchmarking data showing internal request patterns and efficiency gains is proprietary to your customer base - competitors cannot quantify these operational savings without similar implementation data.Use geographic proximity (200 miles) to make recent customer implementations feel immediately relevant. Show prospects that nearby utilities completed full asset digitization and achieved measurable operational improvements.
Geographic specificity (200 miles, "your region") makes this feel like hyper-local intelligence rather than generic marketing. The recent timeline (past 9 months) proves this isn't outdated case study material. The 38% outage response improvement ties directly to the prospect's #1 KPI. The competitive angle ("puts you at disadvantage for storm response contracts") creates urgency by framing this as a competitive threat. The deployment timeline case study offers practical implementation guidance.
This play requires tracked deployment timelines and measured outage response improvements from 3+ utility customers within the same geographic region.
This regional peer data with specific operational outcomes is proprietary to your customer base - competitors cannot provide this hyperlocal implementation evidence.Use aggregated asset digitization completion rates from your customer base to show prospects exactly how they compare to peer utilities. Quantify the time lag and translate it into concrete operational costs and performance impacts.
The specificity of "47 utilities" and "18 months behind median" feels like genuine research, not marketing fluff. The quantified cost implications ($2.3M maintenance costs, 40 minutes extended outage response) help the prospect justify budget internally. The low-commitment ask (just send the anonymized benchmark report) makes it easy to engage. The data synthesis requiring internal benchmarking only you have passes the "how did they know that" test.
This play requires aggregated asset digitization completion rates (median % of assets digitized at 6/12/18-month milestones) across 47+ utility implementations.
This benchmarking data is proprietary to your customer base - only you have visibility into actual digitization timelines across comparable utilities.Old way: Spray generic messages at job titles. Hope someone replies.
New way: Use proprietary benchmarking data from your customer base to show prospects exactly how they compare to peer utilities in their region.
Why this works: When you lead with "Your outage response is 22 minutes slower than 38 regional peers" instead of "I see you're hiring for operations roles," you're not another sales email. You're the person with insider data they can't get anywhere else.
The messages above aren't templates. They're examples of what happens when you combine internal performance benchmarks with specific utility situations. Your team can replicate this using aggregated customer data from your implementation base.
Every play traces back to internal benchmarking data combined with public utility identification. Here are the sources used in this playbook:
| Source | Key Fields | Used For |
|---|---|---|
| Internal Customer Storm Response Data | restoration times, crew dispatch patterns, asset visibility capabilities | Benchmarking storm response performance across regional utilities |
| Internal Customer Performance Data | emergency response times, dispatch metrics, outage-to-crew-dispatch times | Comparing outage response performance across utilities |
| Internal Customer Deployment Data | implementation timelines, ROI measurements, operational improvements, phasing approaches | Showing realistic deployment timelines and ROI achievement |
| Internal Customer Project Data | capital project approval timelines, process steps, completion rates | Benchmarking capital planning cycle efficiency |
| Internal Customer Work Order Data | data request volume, request patterns, engineering overhead analysis | Quantifying internal data request overhead and efficiency opportunities |
| Internal Customer Digitization Data | asset discovery completion rates, digitization timelines, milestone tracking | Benchmarking asset digitization progress across utilities |
| EIA Form 861 - Annual Electric Power Industry Report | utility_name, service_territory_states_counties, distribution_circuits_count, customer_counts_by_sector | Utility identification, service territory verification, peer grouping by region and size |
| FERC Form 1 - Electric Utility Annual Report (PUDL) | plant_in_service_valuations, depreciation_by_function, transmission_lines_schedule_422 | Capital investment patterns, asset valuation context |