Edtech Advisor
Strategic frameworks for education-technology founders, operators, and product leaders.
Disclaimer: Frameworks and orientation only. Not legal advice. Edtech compliance (FERPA, COPPA, GDPR, state laws) requires specialist counsel. Use this skill to organize strategy.
Keywords
edtech, K-12, higher education, higher ed, university, college, FERPA, COPPA, GDPR-K, student data, LMS, SIS, learning management, school district, RFP, district sales, corporate learning, L&D, training, certification
Quick Start
- Run student-data compliance checker on a 1-paragraph product description
- Identify primary market (K-12 / Higher Ed / Corporate L&D / Direct-to-Learner)
- Read the corresponding section of
references/edtech_market_dynamics.md
Core Workflows
Workflow 1: Student Data Compliance Scoping
- Run:
python scripts/student_data_compliance_checker.py description.txt
- Cross-reference with
references/student_data_privacy.md
- Hand findings to counsel — FERPA / COPPA / GDPR-K + state laws
- Document scope and BAA / Student Data Privacy Agreement (SDPA) inventory
Time Estimate: 4-6 weeks for first scope.
Workflow 2: Market Selection (K-12 vs HiEd vs Corp)
- Read
references/edtech_market_dynamics.md
- Score product fit against each market: buyer, contract length, sales cycle, pricing benchmarks, churn dynamics
- Pick one primary market for first $1M-$5M ARR
- Build content, sales motion, and pricing aligned to that market
Time Estimate: 4-8 weeks.
Workflow 3: District Sales Strategy
- Map district decision-makers: superintendent, assistant superintendent, CTO, curriculum director, principal, teacher
- Plan procurement path: RFP, sole source, statewide cooperative
- Plan implementation: PD (professional development), rostering (Clever, ClassLink), SIS integration
- Validate with reference districts before broader investment
Time Estimate: 6-12 months for first major district win.
Tools
student_data_compliance_checker.py
Scans a product description for indicators of student-data handling and likely compliance regime exposure (FERPA, COPPA, GDPR-K, state laws).
python scripts/student_data_compliance_checker.py description.txt
python scripts/student_data_compliance_checker.py description.txt --json
Reference Guides
references/student_data_privacy.md — FERPA, COPPA, GDPR-K, state laws (SOPIPA, NY Ed Law 2-d, etc.)references/edtech_market_dynamics.md — K-12, Higher Ed, Corporate L&D, D2C — buyer, sales cycle, pricing
Templates
assets/sdpa_inventory_template.md — Student Data Privacy Agreement and compliance posture template
Integration Points
- Pairs with
legal/ for SDPA / DPA contract review
- Pairs with
marketing/launch-strategy for back-to-school launch timing
- Pairs with
c-level-advisor/cs-fundraising-advisor for edtech-specific fundraising
Best Practices
- Plan for the academic calendar. District purchase cycles peak in spring (for fall) and again at end-of-year. Selling in October to start in November is a non-starter.
- Sign SDPAs before piloting. Many states require districts to have a Student Data Privacy Agreement before a tool can touch student data — even a free pilot.
- Don't conflate K-12 and Higher Ed. Different buyers, different sales cycles, different compliance regimes (FERPA applies to both but how it's interpreted differs).
- Corporate L&D is not edtech. It's HR-tech with edtech roots. Different buyer (CHRO / L&D leader), different metrics (completion, retention), different sales motion.
1---2name: edtech-advisor3description: Strategic advisory for edtech founders on FERPA/COPPA compliance, K-12 vs higher-ed vs L&D dynamics, district sales, and pricing. Use when scoping an edtech product or navigating procurement, or mentioning edtech, K-12, FERPA, COPPA, or LMS.4license: MIT + Commons Clause5---6
7# Edtech Advisor
8
9Strategic frameworks for education-technology founders, operators, and product leaders.
10
11> **Disclaimer:** Frameworks and orientation only. Not legal advice. Edtech compliance (FERPA, COPPA, GDPR, state laws) requires specialist counsel. Use this skill to organize strategy.
12
13---
14
15## Keywords
16
17edtech, K-12, higher education, higher ed, university, college, FERPA, COPPA, GDPR-K, student data, LMS, SIS, learning management, school district, RFP, district sales, corporate learning, L&D, training, certification
18
19---
20
21## Quick Start
22
231. Run student-data compliance checker on a 1-paragraph product description
242. Identify primary market (K-12 / Higher Ed / Corporate L&D / Direct-to-Learner)
253. Read the corresponding section of `references/edtech_market_dynamics.md`
26
27---
28
29## Core Workflows
30
31### Workflow 1: Student Data Compliance Scoping
321. Run: `python scripts/student_data_compliance_checker.py description.txt`
332. Cross-reference with `references/student_data_privacy.md`
343. Hand findings to counsel — FERPA / COPPA / GDPR-K + state laws
354. Document scope and BAA / Student Data Privacy Agreement (SDPA) inventory
36
37**Time Estimate:** 4-6 weeks for first scope.
38
39### Workflow 2: Market Selection (K-12 vs HiEd vs Corp)
401. Read `references/edtech_market_dynamics.md`
412. Score product fit against each market: buyer, contract length, sales cycle, pricing benchmarks, churn dynamics
423. Pick one primary market for first $1M-$5M ARR
434. Build content, sales motion, and pricing aligned to that market
44
45**Time Estimate:** 4-8 weeks.
46
47### Workflow 3: District Sales Strategy
481. Map district decision-makers: superintendent, assistant superintendent, CTO, curriculum director, principal, teacher
492. Plan procurement path: RFP, sole source, statewide cooperative
503. Plan implementation: PD (professional development), rostering (Clever, ClassLink), SIS integration
514. Validate with reference districts before broader investment
52
53**Time Estimate:** 6-12 months for first major district win.
54
55---
56
57## Tools
58
59### student_data_compliance_checker.py
60
61Scans a product description for indicators of student-data handling and likely compliance regime exposure (FERPA, COPPA, GDPR-K, state laws).
62
63```bash
64python scripts/student_data_compliance_checker.py description.txt
65python scripts/student_data_compliance_checker.py description.txt --json
66```
67
68---
69
70## Reference Guides
71
72- **`references/student_data_privacy.md`** — FERPA, COPPA, GDPR-K, state laws (SOPIPA, NY Ed Law 2-d, etc.)
73- **`references/edtech_market_dynamics.md`** — K-12, Higher Ed, Corporate L&D, D2C — buyer, sales cycle, pricing
74
75---
76
77## Templates
78
79- **`assets/sdpa_inventory_template.md`** — Student Data Privacy Agreement and compliance posture template
80
81---
82
83## Integration Points
84
85- Pairs with `legal/` for SDPA / DPA contract review
86- Pairs with `marketing/launch-strategy` for back-to-school launch timing
87- Pairs with `c-level-advisor/cs-fundraising-advisor` for edtech-specific fundraising
88
89## Best Practices
90
91- **Plan for the academic calendar.** District purchase cycles peak in spring (for fall) and again at end-of-year. Selling in October to start in November is a non-starter.
92- **Sign SDPAs before piloting.** Many states require districts to have a Student Data Privacy Agreement before a tool can touch student data — even a free pilot.
93- **Don't conflate K-12 and Higher Ed.** Different buyers, different sales cycles, different compliance regimes (FERPA applies to both but how it's interpreted differs).
94- **Corporate L&D is not edtech.** It's HR-tech with edtech roots. Different buyer (CHRO / L&D leader), different metrics (completion, retention), different sales motion.
borghei