School maintenance requests take months to resolve for trivial tasks, with no visibility or accountability. Teachers can't even change clocks because of jurisdictional rules, yet maintenance staff never get to it.
Simple work order submission app for teachers/staff with automatic escalation timers, photo documentation, SLA tracking, and admin dashboards showing average resolution times. Flags overdue items to building principals.
Subscription per-building ($50-150/mo) or per-district licensing. Free tier for single buildings to drive adoption.
The Reddit thread is visceral — 430 upvotes and 125 comments of teachers describing months-long waits for trivial fixes. This isn't a mild inconvenience; it directly impacts instruction, morale, and safety. Teachers doing maintenance themselves despite jurisdictional rules signals a completely broken process. This is a hair-on-fire problem for building principals who get blamed for facility conditions they can't control.
~130,000 K-12 school buildings in the US across ~13,000 districts. At $100/building/month = $156M TAM for US alone. Realistic SAM targeting districts with 5+ buildings = ~$50-80M. Not a unicorn market, but very solid for a bootstrapped/small-team SaaS. International expansion (UK, Canada, Australia have similar structures) adds upside.
Schools DO pay for this category — SchoolDude/FMX prove the budget line item exists. However, school purchasing is bureaucratic and slow. $50-150/building/month is well within facilities budgets (cheaper than incumbents). The risk: individual schools may resist paying, and district-level procurement takes 3-9 months. Free tier for single buildings is the right move to bypass procurement initially, but converting to paid requires selling to administrators, not teachers.
This is a CRUD app with timers and notifications — well within solo dev MVP territory in 4-6 weeks. Core features: work order form with photo upload, timer/escalation engine (cron jobs), dashboard with basic analytics, email/push notifications. No AI required, no complex integrations needed for MVP. Standard web stack (Next.js + Postgres or similar). The accountability timer and escalation logic is straightforward to implement.
This is the strongest signal. The incumbent (SchoolDude/Brightly) is a bloated Siemens-owned legacy product with terrible UX. FMX is better but still lacks the core differentiator: accountability timers and escalation. NO existing product makes overdue work orders visible to principals automatically or tracks SLA compliance as a first-class feature. The transparency/accountability angle is genuinely unserved. You're not competing on features — you're competing on a philosophy (visibility) that incumbents structurally resist because their customers (maintenance departments) don't WANT to be tracked.
Textbook SaaS subscription. Schools need this every single day of the school year. Work orders are continuous. Once embedded in a building's workflow, switching costs are high (historical data, trained staff, established processes). District-level contracts are typically annual with auto-renewal. Expansion revenue is natural: single building → full district → neighboring districts.
- +Visceral, validated pain point with strong emotional engagement (430 upvotes, teachers describing years of frustration)
- +Clear competitive gap — NO incumbent offers accountability timers or automatic escalation to principals
- +Technically simple MVP — CRUD + timers + notifications, buildable in 4-6 weeks by a solo dev
- +Proven budget category — SchoolDude/FMX prove districts already allocate money for this exact software
- +Natural viral loop — teachers tell teachers at other schools, principals talk at conferences
- +Incumbent vulnerability — SchoolDude is a legacy Siemens product with terrible UX and slow innovation, ripe for disruption
- +Per-building pricing is dramatically cheaper than per-user incumbents, making the sales pitch easy
- !School procurement cycles are painfully slow (3-9 months), which delays revenue and tests founder patience
- !Maintenance departments may resist adoption because the accountability feature threatens them — you need admin/principal buy-in to override this
- !SchoolDude/Brightly has massive incumbent advantage in district procurement (existing contracts, vendor lists, relationships)
- !Free tier users in single buildings may never convert if the building principal doesn't champion paid adoption
- !Seasonality — school budgets are decided in spring for the following year, creating a narrow sales window
- !Risk of building a great product that teachers love but can't get past district IT/procurement gatekeepers
Dominant incumbent in K-12 maintenance management. Offers MaintenanceDirect for work orders, plus separate modules for capital planning, utilities, and inventory. Used by thousands of districts.
Cloud-based facility management platform popular with K-12 and higher ed. Covers maintenance requests, room scheduling, calendar management, and inventory.
Mobile-first CMMS aimed at maintenance teams. Work orders, asset management, preventive maintenance, parts inventory. Has a free requester portal.
Cloud-based CMMS targeting mid-market including schools, healthcare, and property management. Work orders, preventive maintenance, asset tracking.
Enterprise-grade CMMS used across industries including education. Deep work order management, preventive maintenance, asset tracking, and inventory.
Web app with three views: (1) Teacher/Staff portal — submit work order with photo, room number, category, urgency; track status in real-time. (2) Maintenance portal — receive/claim/complete work orders, log time and notes. (3) Admin dashboard — see all open orders, average resolution time, overdue items flagged in red, auto-escalation emails to principals when items exceed configurable SLA thresholds (e.g., 48 hours for urgent, 2 weeks for routine). Skip asset management, preventive maintenance, and inventory for MVP. The accountability timer IS the product — make it prominent and impossible to ignore.
Free for single buildings (up to 1 admin, 1 maintenance user, unlimited requesters) to drive bottom-up adoption → $50/building/month for multi-building with full dashboards and escalation configuration → $150/building/month for district tier with cross-building analytics, API access, and SIS/ERP integration → Annual district contracts ($5K-$30K/year) sold to facilities directors. Upsell path: compliance reporting, board presentation exports, predictive maintenance add-on.
8-14 weeks. 4-6 weeks to build MVP, 2-4 weeks to get 5-10 free pilot buildings (target frustrated teachers from that Reddit thread and similar communities), 2-4 weeks to convert first paid building or small district. First meaningful revenue ($1K+ MRR) likely 4-6 months. The free-to-paid conversion will be the hardest part — plan to personally onboard and hand-hold early customers through procurement.
- “It takes them like a year to do their job”
- “It took them 3 months to change the panels which I could have done in three minutes”
- “We are not even allowed to change the clocks... That's their job yet we end up doing it anyway”