Schools, parents, and students were stuck with fragmented, offline communication — circulars on paper, scattered WhatsApp groups, no single source of truth for attendance, announcements, fees, and academics. Coordination was slow and information got lost.
Idea Validation
Instead of assuming, I went to the source. I spoke directly with school administrators and teachers to confirm the pain was real, urgent, and worth paying for — validating demand before writing serious code.
Product Design
I designed a mobile-first platform connecting schools, teachers, parents, and students — real-time announcements, academic updates, and media sharing — shaped around the workflows administrators described, not what was easiest to build.
Engineering
I built the entire stack solo: a React Native mobile app and React web dashboard, a Node.js + Express + GraphQL backend, Firebase for auth and notifications, Cloudinary for media, and Socket.IO for real-time messaging.
Launch
I shipped it to the real world — published the app on the Google Play Store and got it into the hands of actual schools, not just a demo on my laptop.
Sales
I personally presented the product to 100+ school administrators — running live demos, handling objections, and translating technical capability into business value for non-technical buyers.
Customer Discovery
I visited schools in person, watched how staff actually worked, and collected feedback directly from users — then folded those insights back into the product to make it fit how schools really operate.
Lessons Learned
Building is the easy part — distribution, trust, and understanding the buyer are what make a product real. I learned to validate before building, to sell what I build, and that proximity to the customer is an unfair advantage for an engineer.