An EdTech company’s buyer spends 17 minutes reading your district case study, downloads a sample lesson plan, forwards the link to three colleagues, and never fills out a form. Your analytics shows a session. Your CRM shows nothing. Six weeks later a different vendor wins the district.
Form-gated pipeline in EdTech is brutal. Teachers and district administrators are some of the most form-averse buyers in B2B, partly because they receive more outbound than almost any other segment and partly because district procurement cycles make individual “leads” feel pointless from the champion’s point of view. At Leadpipe, we work with EdTech vendors across K-12, higher ed, corporate L&D, and workforce training. This is the playbook we hand them.
Who is actually buying EdTech
EdTech buying committees change dramatically by sub-vertical.
- K-12 district sales. Superintendent, Director of Curriculum, Director of Technology, Director of Assessment, Director of Special Education, Finance / Business Manager, occasionally a school board. Principals and teachers are champions, not buyers.
- Higher ed. Provost, Dean of a specific school, CIO, VP Enrollment, Director of Student Success, Director of Institutional Research, procurement office.
- Corporate L&D. CHRO, VP L&D, Director of Talent Development, IT for integrations, finance for budget.
- Workforce / career training. VP Workforce, Director of Training, State workforce agency leads, union officials.
Teachers, professors, and L&D practitioners are the functional champions, but they almost never complete a demo form. The district or institution does the evaluation as a committee, and the committee-level touches happen in email, on Slack, and on your website in anonymous tabs.
The answer up front
Install a JavaScript pixel. Leadpipe deterministically identifies 30-40%+ of your US B2B visitors with name, business email, title, institution, and firmographics. You alert when a director of curriculum at a target district views your case study, or a provost views your pricing, or a director of L&D at a Fortune 1000 views your integrations page. You reach the committee early, not after the formal RFP.
For the primer, see what is identity resolution and person-level intent data, how it works.
Where EdTech buyers research
EdTech evaluation leaves a distinctive trail that is nothing like SaaS evaluation.
| Page | Who visits | Signal strength |
|---|---|---|
| Case study by district size / institution type | Champion plus committee | Very high |
| Sample lesson plan / curriculum preview | Teacher champion, curriculum director | High |
| Pricing / district licensing | Finance, procurement | Very high |
| Research / efficacy / ESSA Tier evidence | Curriculum director, superintendent | Very high |
| Integrations (Clever, ClassLink, Canvas, Schoology, Workday) | Director of Tech, CIO | High |
| Accessibility / WCAG / Section 508 | IT plus compliance | High |
| Free trial / pilot sign-up page | Teacher champion | High |
| Careers | Not a buyer | None |
For higher ed and corporate L&D, substitute LMS integration content (Canvas, Blackboard, D2L, Cornerstone) and compliance content (FERPA for higher ed, SCORM / xAPI for L&D).
Comparison: intent signals EdTech teams should build around
Build these into your Orbit audiences and CRM automations. The Orbit audiences every SaaS company should build framework translates well to EdTech with role swaps.
| Signal | Audience or alert | Why |
|---|---|---|
| Director of Curriculum on efficacy / research page | Immediate rep alert | Rigorous-evidence check, late-stage signal |
| Superintendent on district case study | District-committee watchlist | Executive interest, likely committee forming |
| IT director on integrations page | Technical-qualification watchlist | Landability review |
| Repeat visits from same institution in 21 days | Score boost | Multi-stakeholder eval |
| Pricing page from finance / business manager | Finance-led procurement signal | Budget sizing |
| Customer institution on new product line | CSM alert | Expansion |
| Teacher champion on sample content | PLG nurture | Bottoms-up champion-building |
| Orbit: Director Curriculum researching competitor | Pre-site watchlist | Shortlist before RFP |
Four buyer motions, worked out
1. A Director of Curriculum at a 40,000-student district on your efficacy page
Leadpipe identifies them. They view your ESSA Tier evidence, two case studies for districts of similar size, and your pricing.
- Immediate alert to the territory rep. This is a late-funnel evaluation signal, not a top-of-funnel tire-kick.
- First touch is educational, not a demo push. Reference the ESSA evidence directly and offer a 30-minute curriculum-fit call with an educator on your team, not a general demo.
- Add the district to an Orbit watchlist. Expect the superintendent, director of tech, and business manager to show up within 14-30 days. When they do, you know the committee is activating.
2. A superintendent on a district case study
Executive-level engagement. Rare, valuable, and fragile. A misfire here costs you the district.
- Rep alert plus head of sales or VP Education.
- First touch is never sales. A short note from a former superintendent on your team (most EdTech vendors hire former district leaders; use them) referencing a specific challenge the case study addresses.
- No calendar links. Offer a phone call window.
3. A Director of Institutional Research at a regional university on your analytics module
Higher ed signal. The institutional research team is the quiet power-center in most universities and rarely appears in vendor databases.
- Alert the higher-ed rep.
- Proactively send anonymized peer-institution benchmarks. IR leaders are hungry for comparison data.
4. A VP of L&D at a 2,500-person company on your integrations and pricing pages
Corporate L&D evaluation. Similar to HR-tech evaluation but with a learning-specific lens.
- Alert the AE. Send integration-specific content for the corporate LMS they use.
- Offer a 20-minute technical call, not a product demo.
For cadence specifics, see the SDR playbook for identified website visitors and website visitor identification for sales teams.
Why EdTech match rates behave differently
EdTech traffic mixes a large volume of teacher / professor browsing (often from school-network devices that resolve at the institution level but not the individual level) with a smaller, higher-value volume of administrator and procurement browsing. Expect match rates at the 30-40%+ range, with a meaningful split between “institution identified, individual not identified” (common for teachers on school WiFi) and “full person-level match” (common for admins on district-issued laptops over corporate networks).
That split is fine and matches the reality of the buying process. Teachers are champions. Admins are buyers. You get person-level data on the buyers, which is what you need.
For the underlying accuracy story, the visitor identification accuracy independent test showed Leadpipe at 8.7/10 versus RB2B at 5.2/10 and Warmly at 4.0/10 on 75,000 visitors over 120 days.
Deterministic match accuracy (independent test):
Leadpipe ████████████████████ 8.7/10
RB2B ███████████ 5.2/10
Warmly ████████ 4.0/10EdTech buyers have long memories for vendors who get personalization wrong. Deterministic matching matters specifically to avoid false-positive “Hi [wrong name]” emails that get forwarded to the entire admin team. See deterministic vs probabilistic matching.
Using Orbit for pre-site EdTech intent
Orbit monitors person-level research across 5M websites and 20,810 topics, refreshed daily. For EdTech, useful audiences:
- Directors of Curriculum at mid- to large-district K-12 researching your category, adjacent categories, or competitor names.
- Provosts and Deans at four-year institutions researching “student success platform,” “adaptive learning,” or competitor names.
- VPs of L&D at 1,000+ employee companies researching “LXP,” “learning experience platform,” or “upskilling platform.”
- Directors of Special Education researching IEP software, accessibility tools, or adaptive instruction.
- Existing customers researching competitor names (renewal-risk watchlist).
See orbit person-level intent audiences and orbit competitive intelligence for mechanics.
Stack: connecting EdTech intent to your go-to-market
- Pixel on the marketing site, blog, and any resource / curriculum sample portals.
- CRM sync. EdTech vendors typically run HubSpot or Salesforce. Use the Leadpipe Salesforce integration or Leadpipe + Clay + HubSpot recipe.
- Slack routing by role. Curriculum director alerts go to the territory rep. IT director alerts go to the SE. Superintendent alerts go to the regional VP. Teacher champion alerts go to a separate low-pressure nurture, not to a sales queue. See Leadpipe Slack visitor alerts.
- Orbit for pre-RFP signal.
- Suppression. Competitor domains, staff domains, and any university athletics / event sites that generate unrelated traffic to your marketing surfaces.
For role-specific playbooks, see visitor identification guide for CMOs and visitor identification guide for demand gen.
Compliance notes specific to EdTech
- FERPA. Visitor identification operates on commercial B2B contact data, not student data, so FERPA does not directly apply. However, do not mix Leadpipe data with student-facing systems. Keep the staff buyer data in the CRM and the student data in the SIS.
- COPPA. Applies to children under 13 on the product side. Not a visitor-ID issue, because visitor identification targets B2B adults doing institutional purchasing.
- CCPA. Covered. Honor opt-outs via suppression lists.
- GDPR, company-level default for EU / UK. If you sell into UK / EU institutions, EU traffic resolves at the company level by default. Person-level requires consent.
- SOC 2. Leadpipe is pre-cert, readiness in progress. EdTech buyers (especially K-12 districts and universities) will ask. Send the DPA and subprocessor list. Do not claim certification.
For the EU specifics, see GDPR-compliant visitor identification.
The teacher-champion problem, solved
EdTech has a unique bottoms-up dynamic. The teacher champions the tool. The district buys it. Teacher forms are high-volume but low-quality because most districts will not adopt a tool just because one teacher loves it.
Visitor identification solves this by surfacing the admin layer, not just the teacher layer. When five teachers at the same district browse your sample content in a month, plus a director of curriculum views your efficacy page, plus the director of technology views your integrations page, you have a real signal. The cost of anonymous website traffic post explores this gap between high-volume form fills and real committee evidence.
Getting started
- Pixel on the marketing site and resources / sample-content portals.
- Build three Orbit audiences: directors of curriculum researching competitor, provosts / deans at higher ed, VPs of L&D at 1,000+ employee companies.
- Slack alerts on efficacy page, integrations page, pricing page, and competitor comparison page.
- Run it for 45 days. Then review by institution, not by individual. Any institution with three identified individuals across champion, admin, and IT in 21 days is a late-stage shortlist candidate.
In EdTech, the form is the smallest surface of the real evaluation. Visitor identification is how you see the rest.
If you want the short version: $147/mo gets you person-level identification on 500 visitors with full contact data. See full pricing →
