when the principal gave us the quiz idea, my brain went straight to building. screens, scoring, timers, sync. ship it, done.
i was thinking of it as a feature. Jagan sir was thinking of it as a company.
he was thinking like zoho. one organization, many products sitting under it.
maahita.com → the organization
school.maahita.com → the school ERP
vinodam.maahita.com → the quiz product
one tree, many branches.
so the quiz did not stay "the quiz thing we built for that school". it got a name, vinodam. it got a home, its own subdomain under the org. and for the branding we did not even need a new logo. we already had the māhita banyan tree, so kids playing around that same tree became vinodam.
the māhita tree → vinodam: kids playing around the same tree
a separate product, but clearly part of the same family. you see it once and you know it is ours.
then came the part i really did not expect. the marketing.
we did not pitch it to the principal as a quiz tool. we pitched it as an app for children engagement in summer holidays, where kids learn by attending quizzes for fun. learning, packaged as play.
same software, completely different story. and that story is what the principal bought.
that is the gap, and i could only see it once it was in front of me. i was thinking like a developer, build what was asked. he was thinking like a company, name it, brand it, position it, sell it.
the code was maybe 70% of the work. the thinking around it is what made it a product instead of a feature.
the app → Vinodam
the build story → Building Vinodam: the product that taught me what shipping really means
#buildinpublic #startup #productthinking #branding #maahitatechnologies