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.
Website: granicus.com
What they do: Granicus provides a Government Experience Cloud platform that helps government agencies deliver citizen services efficiently. They solve the problem of disconnected systems, low digital adoption, and staff resource constraints across municipal, state, and federal agencies.
Core problem: Government agencies struggle to deliver citizen services efficiently across disconnected systems, resulting in staff resource constraints, low digital adoption, and inability to engage constituents through modern channels. Citizens must navigate fragmented processes for permits, records requests, and service delivery.
Industries: Local government (cities, counties), state government agencies, federal agencies, K-12 and higher education, special districts (water, fire, utilities, transit)
Company size: Mid-sized to large government organizations serving 50,000+ constituents
Operational context: Agencies with high permit/licensing volume, FOIA compliance requirements, citizen service delivery needs, meeting management requirements, short-term rental oversight mandates, public records management, and technology modernization initiatives
Title: Director of Digital Services / Chief Information Officer (Government) / City/County Manager / Chief Administrative Officer
Key KPIs: Citizen satisfaction scores, permit processing time reduction, compliance violation count, digital service adoption rates, operational cost savings, staff productivity improvements
Blind spots: Cannot see fragmented citizen data across disconnected systems, lack visibility into service bottlenecks, unclear which digital services citizens actually need/use, unable to optimize workflows without unified data
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 Granicus 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. The job posting signal is generic - everyone sees it. The stats are meaningless without context. 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 permit office processed 4,200 applications last year with 8 staff - that's 525 per person vs 300 peer average" (Census Bureau data + municipal budget records)
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.
These messages are ordered by quality score (highest first). Each demonstrates either precise situational understanding (PQS) or delivers immediate actionable value (PVP). Every claim traces to specific government databases.
Target municipal permitting departments processing 500+ permits monthly with below-median staffing. Use public permit volume data combined with internal workflow benchmarks to show exactly where automation reclaims staff time - task by task.
Directors can't argue with their own permit volume data. Breaking down time savings by specific task (notifications, routing, inquiries) makes the ROI tangible and credible. Showing where reclaimed time goes (complex reviews, constituent support) addresses the "what would we do with extra capacity?" objection before it's raised.
This play requires workflow time-study data from government clients showing task-level time allocation for permit processing operations.
Combined with public permit volume and staffing data to create peer comparisons. This synthesis is unique to companies serving multiple government agencies.Analyze FOIA tracking data to identify which departments are causing compliance bottlenecks. Show public records officers exactly where delays concentrate and diagnose root causes (email retrieval vs legal complexity).
Department-level breakdown is operationally useful and immediately actionable. The insight that IT delays are about email retrieval (not legal review) helps the recipient prioritize technology investments over legal staffing. This shows synthesis beyond just counting overdue requests.
This play requires FOIA request tracking data showing department ownership, request complexity classification, submission dates, and response status.
Analysis identifies which departments need process support or technology upgrades. Only possible with system-level tracking data across requests.Use internal permit workflow data to break down exactly where processing delays occur compared to peer jurisdictions. Show stage-by-stage comparison (plan review, routing, inspections) and diagnose root causes.
The stage-by-stage breakdown is operationally diagnostic - it tells the director exactly where to focus improvement efforts. Identifying that plan review adds 8 extra days (42% of total gap) and suggesting root causes (understaffing vs tools) provides an implementation roadmap.
This play requires detailed permit workflow data showing time spent at each approval stage (submission, plan review, routing, inspection, approval) across multiple jurisdictions.
Helps recipients identify exact process improvements needed to speed constituent permit processing. Only possible with stage-level tracking across peer agencies.Analyze license database to identify which renewals during peak season could shift to automated online processing. Show licensing boards exactly how many hours they'd reclaim and which license types are automation candidates vs manual-required.
Identifying 892 contractor licenses (48% of Q2-Q3 volume) as automation-ready creates an immediate quick win. Quantifying 60-70 hours reclaimed during peak season shows tangible ROI. The breakdown by license type enables prioritization and implementation planning.
This play requires license database access with renewal dates, license types, disciplinary history, and inspection records to identify automation-safe renewals.
Helps constituents renew licenses faster while reducing government processing burden during peak season. Requires clean license data with history tracking.Combine public permit volume and staffing data with internal workflow benchmarks to show permitting directors where automation reclaims staff time. Break down by specific process areas (plan review routing, inspection scheduling, notifications).
The 75% higher workload comparison to peers is compelling. Identifying specific process areas (not generic "automation") makes it credible. Quantifying time savings per employee (8-12 hours weekly) provides clear ROI. The diagnostic breakdown offer is immediately useful for decision-making.
This play requires workflow analysis combining public permit volume data with process time benchmarks from government clients showing typical time allocation by task.
Helps staff reclaim time to focus on constituent service instead of manual routing. Requires workflow data across multiple agencies for credible benchmarks.Analyze FOIA request data by department to identify where delays concentrate. Show public records officers that IT's overdue requests average 52 days (double other departments) and all involve email searches - proving the bottleneck is manual archive searching, not legal complexity.
The department-specific problem identification helps the recipient prioritize technology investments. The 52-day average quantifies severity. Diagnosing that manual email search (not legal review) is the bottleneck changes the solution from "hire more lawyers" to "upgrade search tools." The request-level detail offer enables immediate action.
This play requires FOIA system data with department ownership, request type classification (email search vs document retrieval), and timeline tracking showing submission and response dates.
Helps recipients prioritize technology investments to reduce constituent wait times for records. Requires request-level tracking across departments.Use internal permit processing data across peer jurisdictions to show directors exactly where their timelines exceed benchmarks. Quantify business impact to constituents (project delays, costs) and competitive risk (permit shopping to neighboring counties).
The specific benchmark comparison to true peers (population and commercial activity matched) is credible. Quantifying constituent impact ($15K-$30K in delayed project starts) addresses political pressure. Identifying competitive risk (permit shopping) hits the director's accountability to elected officials. The diagnostic breakdown offer provides an implementation roadmap.
This play requires permit processing time data across multiple jurisdictions, segmented by population size and commercial activity levels, with stage-by-stage timeline breakdowns.
Helps recipients identify process bottlenecks that slow down their constituents' projects. Only possible with multi-agency permit timeline data.Analyze license renewal clustering during Q2-Q3 to show licensing boards their daily operational impact during peak season. Identify which license types could shift to automated online renewal to reclaim staff capacity.
Quantifying the daily operational impact (20 renewals per business day) makes the bottleneck tangible. Identifying specific automation opportunities by license type (contractor licenses, food permits) shows you've done the analysis. The 60-70% time savings is a compelling ROI signal. The breakdown offer is immediately actionable for prioritization decisions.
This play requires license database access with renewal dates and license type classifications, plus automation feasibility analysis based on renewal complexity and verification requirements.
Helps recipients identify quick wins for reducing manual workload during peak season. Requires license data with type-level process analysis.Target municipal permitting departments with high permit volume but below-median staffing. Use Census Bureau permit data combined with municipal budget records to calculate per-person workload and compare against peer jurisdictions.
The 133% comparison to peers is quantified and verifiable. The message addresses a likely political pressure point (constituent complaints about backlogs). The director can quickly verify this with internal data, building trust. The question about backlogs is easy to answer and opens the conversation.
Analyze FOIA request tracking data by department to show public records officers where delays concentrate. Diagnose that IT's bottleneck is manual email archive searching, not legal complexity.
Identifying the specific department bottleneck (IT with 38% of overdue requests) shows focused research. The diagnosis that manual email search (not legal review) is the root cause helps the recipient prioritize technology investments. The question confirms a suspected process gap and opens dialogue.
This play requires FOIA tracking data with department ownership and request type classification to identify department-level bottlenecks.
Combined with state compliance deadline data to calculate risk exposure. Helps recipients diagnose process gaps.Use FOIA tracking data to identify jurisdictions with overdue public records requests. Quantify legal and financial risk exposure per request to make compliance gaps tangible.
The specific count of overdue requests (37) shows you researched their situation. Quantifying legal/financial risk ($18K-$37K cumulative exposure) is compelling and addresses audit-level accountability. The question about centralized tracking is practical and easy to answer, opening the conversation about process gaps.
This play requires ability to track FOIA request submission dates, statutory deadlines, and response status across departments to identify overdue requests.
Combined with state penalty data to quantify risk exposure. Demonstrates audit-level research into compliance gaps.Use internal permit processing data to show municipal permitting directors how their timelines compare to peer jurisdictions with similar population and commercial activity. Identify political pain points (complaints, competitive loss to neighboring counties).
The specific benchmark comparison with peer definition (population, commercial activity) is credible and verifiable. Identifying political pain points (constituent complaints, competitive loss to neighboring counties) addresses elected official pressure. The council meeting question hits a likely accountability trigger and opens dialogue.
This play requires permit processing time data across peer jurisdictions with similar population and commercial activity profiles.
Helps recipients understand where they stand relative to peers and identify political pressure points. Requires multi-agency timeline data.Target municipal permitting departments with high permit volume but below-median staffing. Use Census Bureau permit data and municipal budget records to show the exact workload disparity vs peer jurisdictions.
Specific numbers about the recipient's staffing vs workload demonstrate research. Peer comparison (12 staff average vs their 8) gives useful context without being generic. The easy yes/no question about capacity clearly identifies an operational pain point the director likely feels daily.
Analyze occupational license expiration dates to identify licensing boards facing seasonal renewal bottlenecks. Show the exact concentration of renewals during peak processing windows (Q2-Q3).
The specific license count and date range (May 1 - July 31) shows research. The 64% concentration metric clearly illustrates the bottleneck. The question about manual vs automated processing addresses the automation gap directly. The director can immediately verify this against their license database, building credibility.
Analyze occupational license renewal clustering to quantify daily operational impact during peak season. Show licensing boards exactly how many renewals per business day they process and calculate the staff time requirement.
Quantifying daily workload impact (20 renewals per business day) makes the bottleneck tangible. The time calculation (10-15 hours daily just for renewals) makes operational impact concrete. Identifying the crowding-out effect on new applications addresses business impact. The yes/no question about backlogs is easy and opens the conversation.
Analyze occupational license expiration clustering to show licensing boards the operational impacts of peak season processing. Identify whether manual paper-based processes are contributing to delays.
The 64% concentration metric is striking and immediately illustrates the problem. Lists concrete operational impacts (delays, overtime costs, error rates) that directors recognize. The question about in-person visits or paper submissions gets at the modernization gap and opens dialogue about digital transformation.
Use FOIA tracking data to identify high-complexity multi-department requests that are causing compliance delays. Show public records officers that cross-department coordination is the bottleneck, not individual department capacity.
Identifies a specific high-risk request pattern (multi-department coordination) that public records officers recognize as a nightmare. The 4x higher litigation risk stat adds urgency. The routing question gets directly to the process gap causing delays.
This play requires FOIA tracking system data showing department involvement per request and request complexity classification to identify multi-department coordination gaps.
Helps recipients identify which requests need process support or centralized coordination. Requires request-level department tracking.Target municipal permitting departments with below-median staffing handling high permit volume. Show the exact workload disparity (133% of peer average) and identify multiple operational impacts (processing times, error rates, burnout).
Clear workload comparison to peers (8 staff vs 12 peer average) is verifiable. Identifying multiple operational impacts (time, errors, burnout) shows understanding of cascading consequences. The turnover question hits an HR/budget pain point that's likely top-of-mind for directors.
Use internal permit workflow data to isolate which specific process stage is causing delays. Show municipal permitting directors exactly where their bottleneck occurs (plan review) and what percentage of total delay it represents.
Isolating the specific process stage (plan review) responsible for delay provides actionable intelligence. The 42% attribution shows where to focus improvement efforts. Offering two diagnostic hypotheses (capacity vs tools) demonstrates analysis. The question probes the likely root cause and opens dialogue.
This play requires permit timeline data broken down by approval stage (submission, plan review, routing, inspection, approval) across peer jurisdictions for comparison.
Helps recipients identify where to focus process improvements. Requires stage-level workflow tracking across multiple agencies.Use internal permit processing data to benchmark the recipient's timelines against peer jurisdictions. Offer a diagnostic breakdown showing which approval stages account for delays.
Concrete comparison to relevant peer group (population, commercial base) is credible. Addresses political pain (constituent complaints and competitive loss to neighboring counties). The diagnostic offer showing which stages cause delay is immediately useful and actionable.
This play requires aggregated permit timeline data across peer jurisdictions with process stage breakdowns showing where delays concentrate.
Helps recipients diagnose bottlenecks and prioritize process improvements. Only possible with multi-agency workflow data.Old way: Spray generic messages at job titles. Hope someone replies.
New way: Use public data to find agencies in specific painful situations. Then mirror that situation back to them with evidence.
Why this works: When you lead with "Your permit office processed 4,200 applications with 8 staff - 133% higher workload than peer counties" instead of "I see you're hiring for a Permitting Manager," 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.
Every play traces back to verifiable data. Here are the sources used in this playbook:
| Source | Key Fields | Used For |
|---|---|---|
| Census Bureau Building Permits Survey | location, permit_type, count, value, date_issued | Municipal permit volume tracking and peer benchmarking |
| Data.gov State/Local Finance Database | jurisdiction, expenditure_type, budget_amount, staffing_count, department | Government agency staffing and budget analysis |
| State Occupational Licensing Databases | license_number, licensee_name, profession, status, expiration_date | License renewal clustering and processing volume |
| EPA ECHO - ICIS-NPDES Database | facility_name, permit_status, violation_type, inspection_date | Environmental permit compliance and enforcement tracking |
| Data.gov Permitting Datasets | permit_number, applicant, location, type, status, date_issued | Municipal permitting data across multiple cities/counties |
| City Open Data Portals | permit_number, applicant, location, status, completion_date | Building permits, licenses, and processing timelines |
| Internal Customer Data (Granicus) | processing_times, workflow_stages, staffing_ratios, automation_benchmarks | Peer benchmarking and workflow optimization analysis |
| Internal FOIA Tracking System (Granicus) | request_id, department_owner, submission_date, response_date, complexity_tier | FOIA compliance analysis and bottleneck identification |