B
Integrated School Administrative Calendar for Parents in Their 40s
3.05
Derivation Chain
Step 1
Public administration education data opening
→
Step 2
School administrative management for children of dual-income couples in their 40s
→
Step 3
Problem of missing schedules due to scattered school, academy, and local government education calendars
Problem
Dual-income couples in their 40s-50s with two middle or high school children must check school events (performance assessments, parent-teacher conferences, after-school class registration, meal fee payments, etc.), cram school test schedules, and local government education program registration deadlines across different apps (e-Learning Center, school website, academy apps, local government apps). Missing registration deadlines leads to losing popular after-school classes or not being able to take leave for parent-teacher conferences, occurring 3-4 times per semester.
Solution
On the web, users register their children's school and cram school, and the service automatically collects school events, tests, payments, and conference schedules into a family-shared calendar. Key features: (1) automatic parsing of school website notices to extract schedules, (2) simultaneous alerts to both parents 3 days before registration deadlines, (3) monthly view with filtering by child and type.
NUMR-V Scores
NUMR-V Scoring System
| N Novelty | 1-5 | How uncommon the service is in market context. |
| U Urgency | 1-5 | How urgently users need this problem solved now. |
| M Market | 1-5 | Market size and growth potential from proxy indicators. |
| R Realizability | 1-5 | Buildability for a small team with realistic constraints. |
| V Validation | 1-5 | Validation signal quality from competition and demand data. |
N=.15 U=.20 M=.15 R=.30 V=.20
Feasibility (65%)
Data Availability
20.8/25
Feasibility Breakdown
| Tech Complexity | / 40 | Difficulty of core implementation stack. |
| Data Availability | / 25 | Practical availability and cost of required data. |
| MVP Timeline | / 20 | Expected time to ship a usable MVP. |
| API Bonus | / 15 | Bonus for viable public API leverage. |
Market Validation (54/100)
Validation Breakdown
| Competition | / 20 | Signal quality from competitor landscape. |
| Market Demand | / 20 | Demand proxies from search and mention patterns. |
| Timing | / 20 | Fit with current shifts in tech, behavior, and regulation. |
| Revenue Signals | / 15 | Reference evidence for monetization viability. |
| Pick-Axe Fit | / 15 | How well the concept serves participants in a trend. |
| Solo Buildability | / 10 | Practicality for lean-team implementation. |
Technical Requirements
Backend [medium]
Frontend [medium]
Data Pipeline [medium]