Blueprint Playbook for OpenAsset

Who the Hell is Jordan Crawford?

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.

The Old Way (What Everyone Does)

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 OpenAsset SDR Email:

Subject: Transform your firm's digital asset management Hi Sarah, I noticed your firm just won the City Hall renovation project - congrats! OpenAsset helps architecture firms like yours organize project images and create winning proposals faster. We integrate with your existing tools and our AI-powered proposal writer can cut your RFP response time in half. Top firms like Gensler and Perkins&Will trust us to manage their asset libraries. Do you have 15 minutes next week to see how we can help your team work more efficiently? Best, Alex

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.

The New Way: Intelligence-Driven GTM

Blueprint flips the approach. Instead of interrupting prospects with pitches, you deliver insights so valuable they'd pay consulting fees to receive them.

1. Hard Data Over Soft Signals

Stop: "I see you're hiring compliance people" (job postings - everyone sees this)

Start: "Your 3 active Historic Tax Credit projects need IRS photo documentation packages" (NPS database with specific project names and certification dates)

2. Mirror Situations, Don't Pitch Solutions

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.

OpenAsset PVP Plays: Delivering Immediate Value

These messages provide actionable intelligence before asking for anything. The prospect can use this value today whether they respond or not.

PVP Internal Data Strong (9.1/10)

Multi-Office Asset Discovery Map

What's the play?

Alert multi-office AEC firms that their best project assets are scattered across offices where proposal teams can't find them. Provide a cross-office asset map showing exactly which waterfront/educational/healthcare images live in which office library.

Why this works

This exposes a blind spot proposal teams live with daily - not knowing what visual assets exist across distributed offices. The specificity of image counts and project types proves you analyzed their actual data. The map delivers immediate value by showing them assets they didn't know they had, making their next proposal more competitive whether they buy or not.

Data Sources
  1. Internal Customer Asset Libraries - project tags, office locations, image counts, project types

The message:

Subject: Mapped where your best waterfront images actually live Analyzed your 3 offices - your Portland office has 127 waterfront project images your Seattle proposal team has never accessed. You're probably submitting waterfront RFPs without knowing these exist. Want the cross-office map showing which waterfront assets are in which office library?
DATA REQUIREMENT

This play requires access to customer's asset libraries across all offices with metadata showing project type tags, office storage locations, and cross-office access patterns from usage logs.

This synthesis is unique to your business - competitors cannot replicate without your multi-office customer data.
PVP Internal Data Strong (8.8/10)

Duplicate Search Waste Report

What's the play?

Identify when proposal teams in different offices run identical asset searches (e.g., "educational facility exterior") without knowing the other office already found the results. Quantify the wasted hours from duplicated search effort across distributed teams.

Why this works

This surfaces operational waste the recipient didn't know existed. The specific search query count and 90-day timeframe proves you analyzed real usage data. The duplicate search report provides immediate value by identifying process inefficiency they can eliminate to improve team productivity, regardless of purchase decision.

Data Sources
  1. Internal Search Query Logs - search terms, timestamps, office location, user ID, results accessed

The message:

Subject: Your Seattle team recreates searches Portland already ran In the past 90 days, your Seattle and Portland proposal teams ran identical searches 23 times for "educational facility exterior" images. They're duplicating work because they don't know what the other office already found. Want the duplicate search report showing where teams are wasting hours?
DATA REQUIREMENT

This play requires search query logs across all customer offices with timestamps, search terms, and user/office attribution to detect duplicate search patterns.

This analysis is proprietary - only you have visibility into cross-office search duplication patterns.
PVP Public + Internal Strong (8.7/10)

Historic Project Cross-Office Asset Discovery

What's the play?

Cross-reference customer's active Historic Tax Credit projects (from NPS database) with their internal asset libraries across offices to surface relevant historic preservation images scattered in different locations that proposal teams don't know exist.

Why this works

The specific image count (847) and office locations prove you analyzed their actual data, not guessing. Multi-office fragmentation is a daily pain for AEC proposal teams. The cross-office asset map delivers immediate value by showing them where relevant work exists for their current projects, improving their next proposal whether they buy or not.

Data Sources
  1. NPS Historic Preservation Tax Credit Program Database - project names, addresses, certification dates
  2. Internal Customer Asset Libraries - project tags, image counts, office locations

The message:

Subject: Found 847 historic project images across your offices I mapped your 3 HTC projects to past work - found 847 relevant historic preservation images scattered across your Boston and Providence offices. Your proposal team is probably recreating searches manually for each RFP response. Want the cross-office asset map showing which images live where?
DATA REQUIREMENT

This play requires access to customer's asset library metadata including project tags (historic preservation keywords), office storage locations, and total image counts by project type.

Combined with public NPS data to identify active HTC projects. This synthesis is unique to your customer data access.
PVP Public + Internal Strong (8.2/10)

HTC Project Pipeline Match

What's the play?

Match customer's completed historic preservation projects against current NPS Historic Tax Credit pipeline to identify 4-5 active RFP opportunities that match their past work (similar scale, building type, and region). Provide RFP list with submission deadlines and project contacts.

Why this works

This generates qualified bid opportunities the recipient's business development team doesn't know about yet. The specific project match (Pawtucket Mill to industrial conversions) shows you understand their portfolio. The actionable RFP list with deadlines provides immediate value for lead generation whether they buy or not.

Data Sources
  1. Internal Customer Project Portfolio - completed projects, building types, locations, project scale
  2. NPS Historic Tax Credit Program Database - active Part 1 applications, project scope, locations

The message:

Subject: Your Pawtucket Mill project matches 4 active HTC RFPs Your Pawtucket Mill adaptive reuse project matches 4 current HTC RFPs in the NPS pipeline - similar scale, industrial conversion, New England location. Your proposal team probably doesn't know these opportunities exist yet. Want the RFP list with submission deadlines and project contacts?
DATA REQUIREMENT

This play requires knowing customer's completed project portfolio including building types, locations, and project characteristics to match against NPS pipeline data.

Combined with public NPS Part 1 application data showing active tax credit projects. This lead generation synthesis is unique to your customer knowledge.

OpenAsset PQS Plays: Mirroring Exact Situations

These messages demonstrate such precise understanding of the prospect's current situation that they feel genuinely seen. Every claim traces to a specific data source with verifiable details.

PQS Internal Data Strong (8.6/10)

Proposal Teams Missing Best Work Across Offices

What's the play?

Target multi-office AEC firms where proposal teams in one office don't have visibility into best project examples stored in other offices. Show them they're submitting waterfront/educational/healthcare RFPs without their strongest visual examples because those images live in a different office's library.

Why this works

The specific scenario (Seattle proposal team missing Portland waterfront projects from 2022-2023) mirrors exactly what happens in distributed firms. The question "how many bids have you submitted in the past 6 months for waterfront projects?" forces them to realize they don't know the answer - and that blind spot directly impacts their win rate KPI.

Data Sources
  1. Internal Customer Asset Libraries - asset distribution by office, project type tags, search patterns by user/office

The message:

Subject: Your proposal team can't find your best project photos Your firm has 34,000+ images across 3 offices, but your proposal team in Seattle doesn't know about the Portland waterfront projects from 2022-2023. That means you're submitting waterfront RFPs without your strongest visual examples. How many bids have you submitted in the past 6 months for waterfront projects?
DATA REQUIREMENT

This play requires analyzing customer's asset distribution across offices and identifying gaps in typical search patterns where proposal teams miss relevant work stored in other locations.

This insight is proprietary - only you can see internal search patterns and cross-office access gaps.
PQS Public + Internal Strong (8.4/10)

HTC Projects at Risk of IRS Photo Documentation Failure

What's the play?

Target historic preservation architecture firms with active Historic Tax Credit projects (verified via NPS Part 2/Part 3 certifications) and alert them about IRS photo documentation compliance requirements. Calculate tax credit value at risk from incomplete photo records that could trigger certification review and credit recapture.

Why this works

The specific dollar amount ($2.8M in tax credit certification) makes the compliance risk tangible and urgent. IRS recapture risk is a serious pain point for HTC projects. The question about locating required before/during/after photos exposes a common blind spot about distributed photo records across project teams and timelines.

Data Sources
  1. NPS Historic Preservation Tax Credit Program Database - project names, certification approval dates, project scope
  2. Internal Customer Project Libraries - HTC project assets, photo documentation completeness (if available)

The message:

Subject: 3 HTC projects need IRS photo documentation packages The IRS requires comprehensive photo documentation for your 3 active Historic Tax Credit projects to maintain $2.8M in tax credit certification. Missing or incomplete photo records can trigger certification review and credit recapture. Is your team able to locate all required before/during/after photos across these projects?
DATA REQUIREMENT

This play assumes you can calculate tax credit values from NPS project scope data and potentially assess photo documentation completeness if the customer stores HTC assets in your system.

Combined with public NPS certification data showing active HTC projects. Tax credit value calculation requires project budget data from NPS Part 3 applications.
PQS Internal Data Strong (8.1/10)

Multi-Office Search Friction Waste

What's the play?

Target multi-office AEC firms with 30,000+ distributed project images where proposal teams manually search 3+ separate office libraries for the same content. Quantify the annual time waste (40+ hours) from duplicate search effort and ask who decides search priority across offices.

Why this works

The specific office locations (Seattle, Portland, San Francisco) and total image count (34,000+) proves you researched their actual structure. The 40-hour annual waste is specific and believable. The question "who decides which office's library to search first?" exposes the coordination chaos they live with but rarely quantify.

Data Sources
  1. Internal Customer Asset Libraries - multi-office structure, total asset counts by location, search patterns from usage logs

The message:

Subject: Your team searches 3 offices for the same images Your Seattle, Portland, and San Francisco offices each maintain separate asset libraries totaling 34,000+ project images. When your proposal team needs waterfront project photos, they're searching 3 systems manually - that's 40+ hours annually on duplicate searches. Who decides which office's library to search first?
DATA REQUIREMENT

This play requires analyzing customer's multi-office asset library structure and calculating search friction from usage logs showing cross-office search patterns and time-to-find metrics.

This operational waste insight is proprietary - only you can quantify their internal coordination inefficiency.
PQS Public + Internal Okay (7.8/10)

HTC Project Photo Documentation Compliance Gap

What's the play?

Target architecture firms with active Historic Tax Credit projects (verified via NPS database) and ask who manages the before/during/after photo documentation workflow required for IRS certification compliance. Surface the pain of distributed photo records across project timelines.

Why this works

The specific project count (3 active HTC projects) shows you researched NPS database records about their firm. HTC documentation requirements are a real compliance pain they manage constantly. The routing question is easy to answer but exposes who owns this workflow, making it feel like genuine discovery not a pitch.

Data Sources
  1. NPS Historic Preservation Tax Credit Program Database - Part 1/Part 2 certifications, project names, approval dates
  2. Internal Customer Project Libraries - HTC project identification (if projects are tagged)

The message:

Subject: Your firm has 3 federal tax credit projects active Your firm has 3 active Historic Tax Credit projects listed in the National Park Service database. These projects require extensive before/during/after photo documentation to maintain IRS certification compliance. Who's managing the photo documentation workflow for these?
DATA REQUIREMENT

This play assumes you can identify HTC projects through NPS Part 1/Part 2 certifications and potentially cross-reference with customer database if they tag projects as HTC work.

Combined with public NPS certification data. The insight strength depends on whether you can verify which projects are actively using your system.

What Changes

Old way: Spray generic messages at job titles. Hope someone replies.

New way: Use public data to find companies in specific painful situations. Then mirror that situation back to them with evidence.

Why this works: When you lead with "Your Portland office has 127 waterfront project images your Seattle proposal team has never accessed" instead of "I see you're hiring for marketing roles," 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.

Data Sources Reference

Every play traces back to verifiable data. Here are the sources used in this playbook:

Source Key Fields Used For
NPS Historic Preservation Tax Credit Database project_name, property_address, certification_approval_date, project_budget, architect_firm Identifying HTC projects with photo documentation requirements and compliance deadlines
OpenAsset Internal Customer Asset Libraries project_tags, office_location, image_count, asset_type_distribution, search_query_logs Analyzing multi-office asset fragmentation, cross-office search patterns, duplicate search waste
OpenAsset Internal Search Query Logs search_terms, timestamps, office_location, user_id, results_accessed Detecting duplicate search patterns across offices and quantifying wasted search time
OpenAsset Customer Project Portfolio completed_projects, building_types, locations, project_scale, project_characteristics Matching completed work against active RFP opportunities in NPS pipeline
SAM.gov Contract Awards API entity_name, NAICS_code, contract_history, contract_value, place_of_performance Identifying federal architecture and construction contractors with active GSA work
State PE License Board Rosters licensee_name, PE_license_number, state, firm_affiliation, license_expiration_date Verifying professional engineering firm credentials and renewal compliance