why my student startup failed

most people write about the thing that worked. this is about the one that didn't, because i learned more from it and because the internet has enough launch posts.

the idea

i was doing my BE in electronics in surat. a friend and i noticed something that still bothers me: college students build genuinely interesting projects, and then those projects die.

they get demoed once to an examiner, graded, and dropped into a folder that nobody opens again. years of work, gone. meanwhile the same students would go into interviews with nothing to show.

so we built projugaadu. a place where students could publish their own projects under their own name. effectively a blogging platform for one niche: student work. you'd get a page, your project would exist on the internet, and you'd have something to point at.

i still think the observation was right.

what actually happened

it didn't take off. not in a dramatic way. it just quietly didn't.

the honest version is that we solved the part we knew how to solve. we could design a platform and we could build it, so we did. what we never solved, and never really had a plan for, was getting anyone to actually show up.

we had no answer for distribution. that's the whole failure, stated plainly. building the site was the part that felt like progress: something to open, something to show a friend, something that proved we could ship. getting a hundred students to create an account and upload their work was a completely different skill, and neither of us had it or had thought hard about how to get it.

so we did what founders with no distribution plan usually do. we finished the product and quietly hoped that being good would be enough to travel. it wasn't. nobody arrives at an empty platform and decides to be the first person to fill it.

what i'd tell myself

not "validate the idea first". that advice is everywhere and it's too vague to act on.

what i'd actually say is: building was never the hard part, and we spent almost all our effort on it anyway, because it was the part we knew how to do and it produced something we could look at. distribution felt uncomfortable and unfamiliar, so it stayed an afterthought right up until it was the reason the thing didn't work.

if i did it again, the first month would have no code in it at all. it would be me, personally, going and finding real students with real projects and getting them onto the platform one at a time, before it was polished, before it was finished. if that was hard or nobody wanted to bother, i'd have learned the actual lesson in weeks instead of months, and without burning the build effort first.

the name outlived the idea

here's the part i didn't expect.

projugaadu still exists, pointed somewhere else. the student publishing idea didn't find its audience, but the name and the habit of shipping our own things survived, and it became the hardware and software prototyping side of my work: esp32, ble, sensors, 3d design, from a prd through to a working prototype.

that's a slightly odd inheritance, a name from a failed college platform now attached to hardware. but the through line is the same one i had at nineteen: ideas are cheap, and the interesting part is the distance to something real. i was right about that. i was just wrong about which idea, and badly wrong about how much of the work is getting anyone to care.

the actual lesson

failing at projugaadu is the reason i now build things end to end and take distribution seriously as part of the job rather than as somebody else's problem.

it's also why, when i build my own products now, i ship them properly and watch what happens instead of assuming. the habit app i built later has real users, and the difference isn't that the idea was better. it's that i understood the second half of the work existed.

one failed platform bought me that. cheap, in the end.