Scholaro
Scholaro had grown into five products wearing one logo. Students, teachers, parents, school admins and district IT each had their own portal, and each portal had its own AI roadmap. We turned it into one product that knows who you are.
- Industry
- Education SaaS, K-12
- Scope
- Strategy, audit, vibe-prototype
- Duration
- 14 weeks
- Handoff
- Coded prototype to 2 dev squads
What we walked into
Five portals, 140 live features and 31 new ideas on the table. A parent with two kids needed two logins. Teachers graded in one place and messaged families in another. Each portal had its own AI assistant, and none of them shared context.
What we did
We stopped designing portals and started designing the school day. Five portals became five roles in one app, and 140 features became 38. One AI now knows the whole day.
We stopped designing portals and started designing the school day.
What testing showed
A coded prototype went in front of 10 real users before any production code. Nine of ten found their first task without help, and teachers asked to keep the shared inbox, unprompted.
7 stakeholders, 4 teams, one shared picture.
Every stakeholder got a place on the same map, so trade-offs became visible instead of political.
- Students
- Teachers
- Parents
- School admins
- District IT
- Support
- Product
- Product
- Engineering
- Data & AI
- Customer success