EduLens
How a personal student problem became a Student Operating System.
EduLens began with my own confusion about education decisions.
It evolved through repeated research, product experiments, and more than 500 stakeholder conversations.
- Problem
- Students don’t struggle because they lack information. They struggle because they lack navigation.
- Evolution
- Mentorship → Information → Summaries → Tools → AI → Student Operating System.
- Evidence
- 500+ conversations over roughly two and a half years with students, guardians, counselors and experts.
- Today
- Working MVP. Pilot preparation. Product refinement. Pre-seed conversations open.
What problem were you trying to solve?
Students don’t struggle becausethey lack information.They struggle becausethey lack navigation.
Students were confused because they didn’t have enough information about studying abroad.
In 2023, researching my own options, two agencies gave me dramatically different guidance about the same destination. One mainly specialized in another country, even though I had asked about the United States.
The problem was not information access. It was that no system knew where a student stood, what was missing, what had changed, or what should happen next.
Every product decision after that had to serve navigation, not content.
Why did your first ideas fail?
What did students teach you?
Students, guardians, international students, counselors, education stakeholders and study-abroad experts.
Students did not just need answers. They needed navigation.
Why did EduLens become a Student Operating System?
Nothing yet.
The whole student journey mapped into tools: profile, roadmaps, documents, opportunity tracking, university comparison, expert guidance, AI agents, requirement monitoring, application workflows, versioning, status tracking.
An exciting vision that could not ship.
What exists today?
Working MVP
- Who it’s for
- Students preparing for high-stakes education journeys, starting with study-abroad readiness.
- Current focus
- Activation, trust, repeat usage and distribution, not more features.
- Next milestone
- Pilot preparation, product refinement, and university and education partnerships in conversation.
Who the student is, what they’ve done, what evidence supports it.
Where they stand relative to a goal.
A dynamic path from reality to desired outcome.
Programs, universities and opportunities being monitored.
Application materials connected to real evidence.
Deadlines, changes, and conversations that don’t disappear.
How do you decide what to build?
What did you choose not to build?
Supply could never match demand. Mentors did not have consistent time; students needing help vastly outnumbered them.
Students were already overwhelmed by sources. Adding a cleaner source would have added another fragment.
Shorter answers do not help someone deciding about money, deadlines, eligibility and years of preparation.
Tools assume the student already knows what to look for. Most did not.
Useful today, gone tomorrow. Without a persistent student profile, the progress disappeared with the conversation.
Five deliberate deletions · each one paid for by user evidence
Where is it going next?
The goal is not to help someone submit one application. It is to build a system that stays useful as the student grows, identity gets richer, readiness updates, evidence stays connected, and the next step stays clear.
Students should not have to rebuild their context every time they make an important decision.
The mission stayed. The model got clearer.