01
Homeschool Home Leader
Parent and daily teacher
A parent at home running curriculum across one or two grade levels. Found Math-U-See because it is tactile, sequential, and works for kids who froze on traditional math. Wants the digital toolbox to support that rhythm, not replace it.
Needs
- · Lesson clarity
- · Progress at a glance
- · Light-weight admin
Avoids
- · Heavy onboarding
- · School-style dashboards
- · Anything that feels like surveillance
02
Homeschool Community Leader
Co-op and pod organizer
Runs a co-op or learning pod. Teaches multiple families' children at once, often across grade levels. Cares about scaling the same Math-U-See experience across students without becoming an LMS administrator.
Needs
- · Multi-student views
- · Shared lesson notes
- · Lightweight reporting
Avoids
- · Per-seat pricing friction
- · Permissions that block a parent
- · Mandatory school taxonomy
03
Education Administrator
School, charter, or district decision-maker
Evaluates curriculum at the institutional level. Needs SSO, FERPA-aligned data handling, classroom-shaped reporting, and a path to roll Math-U-See into existing K-8 math sequencing without a full vendor procurement cycle.
Needs
- · SSO and roster sync
- · Compliance-ready reporting
- · Pilot-then-scale pricing
Avoids
- · Homeschool-only positioning
- · Anything that reads as consumer software
- · Surprise per-student fees
04
Young Learner
Student, K-8
The student. Touches the Digital Toolbox surface most often. Cares about whether the lesson feels doable and whether progress feels real. The dashboard had to read warm, not corporate, without being childish.
Needs
- · Clear next step
- · Visible progress
- · A reason to come back tomorrow
Avoids
- · Grades-as-judgment UI
- · Cluttered nav
- · Any moment that feels like a test