Teachers have no quick, structured way to document behavioral redirections and incidents across all students. When a student or parent claims targeting, teachers lack data to defend themselves.
A mobile-first app where teachers tap to log redirections, disruptions, and conversations per student in real-time. Generates reports showing frequency distribution across all students, timestamped incident logs, and exportable summaries for admin or parent meetings.
Freemium — free for individual teachers (limited students), $8/mo pro for unlimited students and export. $3/student/year for school-wide licenses with admin dashboards.
This is a career-survival problem. Teachers face real risk of disciplinary action, reassignment, or termination from unsubstantiated targeting claims. The Reddit post shows visceral anxiety. This pain is acute, recurring, and has no current structured solution — teachers use notebooks and memory. The emotional weight (fear, helplessness, professional vulnerability) makes this a top-tier pain point.
~3.7M K-12 teachers in the U.S. alone. Secondary teachers (the core audience with 100+ students) represent ~1.7M. If 10% adopt at $8/month = ~$163M TAM for individual subscriptions. School-wide licensing at $3/student across 50M U.S. students = $150M TAM. Total addressable ~$300M+. Not massive by VC standards, but excellent for a bootstrapped or small-team SaaS. International expansion (UK, Australia, Canada) adds significant upside.
Teachers notoriously have low personal spending budgets for tools (~$500/year out of pocket). BUT this is a professional protection tool, not a teaching aid — it is closer to malpractice insurance than a classroom supply. Teachers pay for union dues ($500-1000/year) for protection. $8/month ($96/year) positioned as career insurance is compelling. The school-wide licensing path ($3/student) is where real revenue lives, as schools have budgets for this. Evidence: teachers already spend on tools like Planbook, TeacherPay, etc.
Core MVP is straightforward: mobile app (React Native or Flutter), simple data model (teachers, students, incidents with timestamps/categories/notes), basic reporting/charting, PDF export. No ML, no complex integrations needed for v1. A competent solo dev can build a functional MVP in 4-6 weeks. Auth, CRUD, charts, PDF generation — all well-solved problems. Could even start as a polished PWA to skip app store friction.
This is the killer insight: ZERO competitors address the teacher self-defense documentation use case. Every existing tool is either gamification (ClassDojo) or institutional PBIS compliance. No product lets an individual teacher independently build a timestamped, narrative-rich evidence trail that proves equitable treatment across all students. The gap is not incremental — it is a completely unserved need hiding inside a crowded-looking market.
Strong recurring dynamics: teachers need continuous documentation throughout the school year (Aug-Jun). Data accumulates and becomes more valuable over time — switching costs increase. Annual school calendars create natural renewal cycles. School-wide licenses are inherently annual contracts. Risk: summer churn (3 months of non-use), but this is predictable and manageable with annual billing.
- +Genuinely unserved niche — zero competitors address teacher self-defense documentation despite massive emotional need
- +Bottom-up adoption model — individual teachers can start using it today without school IT approval, creating organic word-of-mouth
- +High emotional urgency drives fast adoption — this is career protection, not a nice-to-have
- +Simple MVP — core functionality is CRUD + timestamps + charts + PDF export, achievable by a solo dev in weeks
- +Clear upsell path from individual teacher (free/paid) to school-wide licensing with admin dashboards
- +Pain signal is searchable and visible — Reddit, teacher forums, and union conversations are full of this exact anxiety
- !FERPA/COPPA compliance is non-negotiable and adds legal complexity — student behavioral data is sensitive, and a breach or compliance failure could be catastrophic
- !Teacher out-of-pocket spend is limited — conversion from free to $8/month may be slow without school-level purchasing
- !ClassDojo could add a 'documentation mode' feature and crush this with their existing install base overnight
- !Summer churn: 10-week gap where teachers are not actively using the product, complicating retention metrics
- !School IT departments may block or discourage unauthorized tools that store student data, limiting grassroots adoption
- !Union and legal dynamics vary wildly by state/district — what constitutes acceptable documentation differs
Dominant classroom behavior tracking platform. Teachers award positive/negative behavior points, share updates with parents via social feed, and build classroom community. Used in ~95% of U.S. K-8 schools.
Digital implementation of the PBIS framework. Teachers award points tied to school-wide behavioral expectations with tiered behavioral support data and a student reward economy.
Behavior tracking and school culture platform. Teachers award/deduct points for behavior tied to school values, with student reward store, parent notifications, and admin dashboards.
Behavior management and culture platform popular in charter networks. Provides classroom behavior tracking, PBIS alignment, SEL tracking, and admin dashboards with ties to academic outcomes.
Behavior management platform focused on tracking referrals, incidents, and interventions. More incident-focused than point-based systems. Admin workflow for processing disciplinary referrals.
PWA (Progressive Web App) to avoid app store reviews initially. Core features: (1) Quick-tap incident logging — teacher selects student, taps category (redirection, disruption, conversation, positive), adds optional 1-sentence note, auto-timestamps. (2) Student roster with bulk import via CSV. (3) Dashboard showing incident frequency distribution across ALL students in a class — the key visual that proves 'I am not targeting anyone.' (4) PDF export of incident logs filtered by student, date range, or class for admin/parent meetings. (5) Simple bar chart: 'Redirections per student this month' — the single most powerful defense artifact. Skip: parent communication, school admin features, integrations. Ship in 4-5 weeks.
Free tier (up to 30 students, 1 class, basic logging) → Pro at $8/month (unlimited students/classes, PDF exports, pattern reports, data backup) → School license at $3/student/year (admin dashboard, cross-teacher visibility, aggregate reporting, PBIS framework alignment, SIS integration). First revenue from individual Pro subscriptions within 2-3 months of launch. School licenses pursued after proving product-market fit with 500+ individual teacher users who can champion internally.
4-6 weeks to MVP launch. First paying users within 2-3 months. Target: $1K MRR by month 4-5 via individual Pro subscriptions. School licenses (higher ACV) realistically start converting in month 6-9 after building case studies. Best launch timing: July-August (back-to-school season) when teachers are setting up their systems for the year.
- “She claimed that I am targeting her and her friends”
- “This claim is false, as there are other students in the class who I need to monitor closely”
- “I've had to redirect her frequently”
- “While I have redirected other students more than her in general”