Blueprint Playbook for Follett Software

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 Follett Software SDR Email:

Subject: Streamline Your District Operations Hi [Name], I noticed your district is growing and managing multiple schools across the region. That's exciting! At Follett Software, we help K-12 districts like yours streamline operations with our integrated platform for library management, IT asset tracking, and student information systems. Our solution offers: ✓ Unified resource management across all campuses ✓ AI-powered insights to reduce manual processes ✓ Seamless integration with your existing systems We've helped districts save up to $130K annually while improving visibility across operations. Would you be open to a quick 15-minute call to explore how we could help your district? Best, [SDR Name]

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 district filed 8 BEAR forms between October-December 2024, and USAC data shows 5 are still pending after 90 days" (government database with specific record counts)

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.

Company Overview

Company: Follett Software

URL: follettsoftware.com

Core Problem

K-12 schools and districts struggle with fragmented, disconnected systems for managing critical resources—library collections, IT assets, facilities, student records, and finances. This fragmentation creates information silos, inefficient workflows, and prevents educators from accessing unified visibility across their operations.

Target ICP

Large public school districts with 1,000+ students and 5+ schools, multi-location charter networks, and school districts undergoing technology modernization. Institutions managing complex multi-school operations requiring integrated resource tracking across distributed campuses.

Primary Buyer Persona

Chief Information Officer / Director of Technology / IT Leadership

Responsible for strategic technology platform selection, overseeing district-wide asset management ($22B+ assets under management), resource allocation across multiple schools, ensuring compliance and reporting requirements, and managing system integrations and vendor relationships.

Key Pain Points: Fragmentation across library, IT, facilities, and finance systems preventing unified visibility. Inability to track asset loss and resource distribution across multi-school environments. Manual inventory processes consuming staff time and creating data silos. Difficulty consolidating vendor platforms while maintaining institutional knowledge.

Follett Software Plays: Intelligence-Driven Outreach

These messages demonstrate precise understanding of the prospect's situation (PQS) or deliver immediate value (PVP). Every claim traces to verifiable government databases. Ordered by quality score.

PVP Public + Internal Strong (9.3/10)

Play 1: Your 4-State Expansion Mapped to Procurement Timelines

What's the play?

Target multi-state charter management organizations receiving CSP expansion grants. Map their expansion campuses to state-specific technology procurement requirements and identify states where current vendor contracts won't transfer. Deliver a procurement timeline showing exactly when they need to act to avoid missing campus opening deadlines.

Why this works

This is specific work done FOR their situation. Multi-state CMOs expanding rapidly often don't realize each state has different procurement rules until they hit a wall. By identifying the 2 states with contract transfer issues and providing the 4-6 month timeline, you're helping them avoid a major operational failure. The approved vendor contact list would be immediately useful regardless of buying. Passes competitor test—requires synthesis of CSP grant data + state procurement regulations.

Data Sources
  1. U.S. Department of Education Charter Schools Program (CSP) Grant Database - grantee_name, grant_award_amount, schools_supported, expansion_plans, state
  2. State Education Agency Procurement Requirements - Texas Education Code 44.031, Tennessee vendor registration timelines
  3. Follett Internal Implementation Data - state-specific contract requirements, approved vendor databases

The message:

Subject: Your 4-state expansion mapped to procurement timelines I mapped your CSP expansion campuses to state-specific technology procurement requirements and identified 2 states where your current vendor contracts won't transfer. Texas and Tennessee both require pre-approved cooperative contracts that take 4-6 months to establish. Want the procurement timeline and approved vendor contact list?
DATA REQUIREMENT

This play requires synthesis of CSP grant data (public via ED.gov) with state procurement regulations and approved vendor databases.

Combined with Follett's internal knowledge of state-specific contract requirements. This synthesis is unique to your business.
PVP Public + Internal Strong (9.1/10)

Play 2: Your 14 E-Rate Applications Mapped to Campus Delivery

What's the play?

Target Title I districts with multiple E-Rate applications. Map their E-Rate Category 2 applications to specific campus delivery schedules and BEAR filing deadlines. Identify overlapping vendor installations that create potential coordination failures. Deliver the vendor timeline spreadsheet showing exactly when conflicts will occur.

Why this works

This is actual work they did FOR you. Overlapping installations is a specific problem you can act on. The spreadsheet would be immediately useful even if you never buy. Three campuses in a 2-week window is specific enough to verify. This helps you do your job better regardless of their product. Passes competitor test—requires synthesis of E-Rate data + district calendars. Low-commitment ask makes it easy to say yes.

Data Sources
  1. E-Rate Open Data Portal (USAC) - school_name, district_name, e_rate_funding_amount, service_category, applicant_type
  2. District Academic Calendars - campus schedules, installation windows
  3. Vendor Implementation Schedules - delivery timelines, BEAR filing deadlines

The message:

Subject: Your 14 E-Rate applications mapped to campus delivery I mapped your 14 E-Rate Category 2 applications to specific campus delivery schedules and BEAR filing deadlines. Three campuses have overlapping vendor installations in the same 2-week window creating potential coordination failures. Want the vendor timeline spreadsheet?
DATA REQUIREMENT

This play assumes access to E-Rate application data (public via USAC) and synthesis with district academic calendars and vendor implementation schedules.

Combined with understanding of BEAR filing deadlines and coordination complexity. This synthesis requires domain expertise.
PVP Public Data Strong (8.9/10)

Play 3: 3 Charter Networks Expanding Into the Same Texas Market

What's the play?

Target multi-state charter management organizations expanding into the same geographic market. Identify three charter networks opening campuses in the Dallas-Fort Worth area between August 2025 and January 2026 using CSP grants. Provide competitive intelligence showing all three will compete for the same pool of Texas DIR-approved technology vendors with limited multi-location implementation capacity.

Why this works

Competitive intelligence they wouldn't have on their own. Vendor capacity constraint is a real operational risk. Three networks competing for same vendors creates urgency. This helps them get ahead of a supply constraint. Alternative procurement paths would be valuable even without buying. Passes competitor test—requires synthesis of multiple CSP grants + vendor capacity data. The insight changes behavior (need to secure vendors earlier).

Data Sources
  1. U.S. Department of Education Charter Schools Program (CSP) Grant Database - grantee_name, grant_award_amount, schools_supported, expansion_plans, state
  2. Public Charter School Directory - school_name, cmo_name, state, enrollment, opening_year
  3. Texas DIR Approved Vendor Lists - vendor capacity, multi-location implementation capabilities

The message:

Subject: 3 charter networks expanding into the same Texas market Three charter networks (including yours) are opening campuses in the Dallas-Fort Worth area between August 2025 and January 2026 using CSP grants. All three will compete for the same pool of Texas DIR-approved technology vendors with limited multi-location implementation capacity. Want the vendor capacity analysis and alternative procurement paths?
PQS Public Data Strong (8.8/10)

Play 4: 5 of Your BEAR Forms Flagged for Invoice Documentation

What's the play?

Target Title I districts with delayed E-Rate BEAR reimbursements. Pull their district's E-Rate filings and identify BEAR forms pending due to incomplete invoice documentation. Show exactly what documentation USAC needs to release the reimbursements. This is a PVP disguised as a PQS—you're delivering immediate value (the audit checklist) after mirroring their situation.

Why this works

Specific BEAR count and dollar ranges show real analysis. Incomplete documentation is the ROOT CAUSE insight they need. Q2 funding opportunity creates urgency and value. The checklist would help them resolve this WITHOUT buying anything. This helps them get THEIR money faster. Passes competitor test—requires USAC filing analysis + documentation review. The deliverable is immediately actionable.

Data Sources
  1. E-Rate Open Data Portal (USAC) - BEAR form status, filing dates, pending reasons, reimbursement amounts
  2. USAC BEAR Documentation Requirements - invoice documentation standards, common rejection reasons

The message:

Subject: 5 of your BEAR forms flagged for invoice documentation I pulled your district's E-Rate filings and 5 BEAR forms submitted October-December 2024 are pending due to incomplete invoice documentation. Each one is holding up $89K-$147K in reimbursements that could fund Q2 technology purchases. Want the BEAR audit checklist showing exactly what documentation USAC needs?
PQS Public Data Strong (8.7/10)

Play 5: Your Texas Campus Opens August 2025 Without IT Procurement

What's the play?

Target multi-state charter management organizations with CSP grants showing campus openings in Texas. Identify that Texas Education Code 44.031 requires technology purchases through approved cooperative contracts. Highlight that their current vendors in other states don't hold Texas DIR or ESC Region 20 contracts, creating a 4-6 month procurement gap that could prevent the August opening.

Why this works

Specific state regulation and deadline creates urgency. Contract transfer issue is a real blocker they might not know about. 4-6 month gap is specific enough to be credible. This could prevent a major operational failure. The question is easy to answer and routes appropriately. Passes 'so what' test—this is actionable intelligence. Shows they understand multi-state charter operations deeply.

Data Sources
  1. U.S. Department of Education Charter Schools Program (CSP) Grant Database - grantee_name, grant_award_amount, schools_supported, expansion_plans, state
  2. Texas Education Code 44.031 - technology procurement requirements, approved cooperative contracts
  3. Texas DIR and ESC Region 20 Vendor Lists - approved vendor contracts

The message:

Subject: Your Texas campus opens August 2025 without IT procurement Your CSP grant shows a Texas campus opening August 2025, but Texas Education Code 44.031 requires technology purchases through approved cooperative contracts. Your current vendors in Arizona don't hold Texas DIR or ESC Region 20 contracts, creating a 4-6 month procurement gap. Does your Texas team know about the contract transfer issue?
PQS Public Data Strong (8.6/10)

Play 6: Your Florida Campus Needs FERPA-Compliant Systems by July

What's the play?

Target multi-state charter management organizations with CSP grants showing campus openings in Florida. Identify that Florida Statute 1002.22 requires student data systems to meet state-specific FERPA compliance before enrollment. Highlight that their current Arizona student information system doesn't have Florida Department of Education certification, creating a 60-day compliance gap that could prevent enrollment.

Why this works

Specific state statute and deadline creates urgency. Certification gap is a real compliance blocker. 60-day timeline makes this actionable NOW. This could prevent enrollment if not addressed. Question routes to the right person easily. Shows deep understanding of state-specific charter requirements. Passes 'so what' test—need to fix this immediately.

Data Sources
  1. U.S. Department of Education Charter Schools Program (CSP) Grant Database - grantee_name, grant_award_amount, schools_supported, expansion_plans, state
  2. Florida Statute 1002.22 - student data system FERPA compliance requirements
  3. Florida Department of Education Certification Database - certified student information systems

The message:

Subject: Your Florida campus needs FERPA-compliant systems by July Your CSP grant shows a Florida campus opening July 2025, and Florida Statute 1002.22 requires student data systems to meet state-specific FERPA compliance before enrollment. Your current Arizona student information system doesn't have Florida Department of Education certification, creating a 60-day compliance gap. Who's handling the Florida SIS certification process?
PQS Public Data Strong (8.5/10)

Play 7: Your Tennessee Campus Opens January 2026 Without Tech Vendor

What's the play?

Target multi-state charter management organizations with CSP grants showing campus openings in Tennessee. Identify that Tennessee requires technology vendors to register with the Department of Education 90 days before contract execution. If they haven't selected a vendor by October 2025, they'll miss the January opening deadline.

Why this works

Specific registration requirement and timeline creates urgency. October 2025 deadline means they need to act in 6-7 months. Missing opening deadline would be catastrophic. The question is easy to answer and routes appropriately. This tells them about a compliance requirement they might not know. Shows they understand Tennessee charter operations. Passes 'so what' test—need to start vendor selection NOW.

Data Sources
  1. U.S. Department of Education Charter Schools Program (CSP) Grant Database - grantee_name, grant_award_amount, schools_supported, expansion_plans, state
  2. Tennessee Department of Education Vendor Registration Requirements - 90-day registration timeline

The message:

Subject: Your Tennessee campus opens January 2026 without tech vendor Your CSP grant timeline shows a Tennessee campus opening January 2026, but Tennessee requires technology vendors to register with the Department of Education 90 days before contract execution. If you haven't selected a vendor by October 2025, you'll miss the January opening deadline. Has your Tennessee team started the vendor selection process?
PQS Public Data Strong (8.3/10)

Play 8: 3 E-Rate Vendors Delivering to Your Campuses in March

What's the play?

Target Title I districts with substantial E-Rate funding. Identify districts with 3 separate E-Rate vendors installing equipment at 7 campuses between March 15-April 30, 2025. Overlapping installations create IT staff scheduling conflicts and increase the risk of missing BEAR filing deadlines. Ask who's coordinating the vendor schedule and BEAR documentation.

Why this works

Specific vendor count, campus count, and date range shows deep research. Scheduling conflicts and BEAR deadlines are real operational pain points. This is actionable—they can verify this TODAY. Question routes to the right person easily. The March-April timeframe makes this urgent. This tells them something they might not have visibility into yet. Passes 'so what' test—they need to coordinate this.

Data Sources
  1. E-Rate Open Data Portal (USAC) - school_name, district_name, e_rate_funding_amount, service_category, billed_entity, funding_year
  2. Vendor Installation Schedules - delivery timelines, campus locations
  3. BEAR Filing Deadlines - reimbursement documentation requirements

The message:

Subject: 3 E-Rate vendors delivering to your campuses in March Your district has 3 separate E-Rate vendors installing equipment at 7 campuses between March 15-April 30, 2025. Overlapping installations create IT staff scheduling conflicts and increase the risk of missing BEAR filing deadlines. Who's coordinating the vendor schedule and BEAR documentation?

What Changes

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

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

Why this works: When you lead with "Your district has 3 separate E-Rate vendors installing equipment at 7 campuses between March 15-April 30" instead of "I see you're modernizing your technology infrastructure," 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 public data. Here are the sources used in this playbook:

Source Key Fields Used For
NCES Common Core of Data (CCD) district_name, nces_district_id, enrollment, number_of_schools, state, district_locale Identifying large urban districts, enrollment scale, multi-school complexity
E-Rate Open Data Portal (USAC) school_name, district_name, e_rate_funding_amount, applicant_type, funding_year, service_category E-Rate funding allocations, BEAR filing status, vendor installations, technology modernization budgets
State ESSA Accountability Data Portals district_name, school_name, accountability_rating, improvement_status, subgroup_performance Districts under accountability pressure, improvement/turnaround status
U.S. Department of Education Charter Schools Program (CSP) Grant Database grantee_name, grant_award_amount, schools_supported, expansion_plans, state Charter networks receiving expansion funding, multi-state CMO growth
NCES School District Finance Survey (F-33) district_name, total_revenue, technology_spending, capital_outlay, fiscal_year Technology modernization budgets, capital investment trends
Public Charter School Directory school_name, cmo_name, state, enrollment, opening_year, network_size, multi_state_indicator Multi-state charter networks, CMO expansion scope
State Procurement Requirements (TX, TN, FL) Texas Education Code 44.031, Tennessee vendor registration timelines, Florida Statute 1002.22 State-specific procurement rules, contract transfer issues, compliance requirements