Shipping side projects that survive demo day

Why most student projects die the day after they are shown, and the handful of habits that keep one alive: a real user, a deploy that stays up, a changelog, monthly maintenance, and knowing when to archive well.

A career session for students
A career session for students

Demo day is where most student projects go to die. The demo works, the applause happens, and the deploy quietly expires three weeks later when the free tier does. Of everything I have built, the projects that mattered — Annapurna after BYTEBATTLE, SCULT Studio, the AI apps — were the ones that survived the day after. Here is what kept them alive.

One real user before demo day

A project with a user has a reason to exist on Monday. Find one person — a classmate, a club, a shopkeeper — who will use it and complain. Their complaints are your roadmap; see after the hackathon.

A deploy that stays up

  • A host you will still be able to afford next semester, with the memory budget written down.
  • Health checks and an uptime ping that emails you when it is down.
  • Environment variables and secrets in the platform, not in a laptop that might be reinstalled.
  • A database with backups, even a daily export.

A changelog and a monthly hour

One hour a month: update dependencies, read the logs, fix one thing a user mentioned, write a line in the changelog. Projects die of neglect, not of bugs. A changelog with twelve monthly entries is also one of the strongest signals a recruiter can find in a repository.

Make it findable

A README that leads with the problem, a link that works, a post when something meaningful changes. A living project that nobody can find is indistinguishable from a dead one.

Or archive well

Not every project should live. When one is done, say so: a final README with what it did, what you learned, and a recording of it working. Archived honestly, it remains a portfolio piece. Abandoned silently, it becomes a broken link.

The habit that underlies all of this is treating a side project as a product with one user rather than a demo with an audience. It is the habit I try to hand students in every session, because it is the one that turns projects into careers.

Side projectsShippingStudentsMaintenance
Pranjul Rathour
Pranjul Rathour
GenAI Engineer · Kanpur, Uttar Pradesh, India

GenAI engineer and AI product builder with 2+ years shipping production-grade AI systems: RAG pipelines, fine-tuned LLMs, hybrid retrieval and multi-modal apps across vision, speech and OCR, architected end to end from ingestion to deployment. Leads engineering for SCULT INDIA's 14-member team, founded the 500+ member TechVerse Enclave community and has mentored 200+ students. Three hackathon first prizes: Changethon 2025 (IIT Roorkee), Product Genesis at Vividhotsava 2025 (CSJMU Kanpur) and BYTEBATTLE (MeetKats).

Open to GenAI roles, hackathon judging, mentorship sessions and guest talks at colleges. Email pranjulrathour41@gmail.com.

Keep reading

More on Shipping AI

All Shipping AI posts →
Campus talks · hackathon judging · mentoring

Want this as a live session at your college?

Open to GenAI roles, hackathon judging, mentorship sessions and guest talks at colleges.

Pranjul Rathour, GenAI engineer in Kanpur