A student with an idea should have a structure, a mentor and a team behind them within a week, not a semester. Everything below exists to make that true.
InnoSphere exists so that a student with an idea has a structure, a mentor and a team behind them within a week, not a semester.
To become the campus's innovation engine: a place where student-led solutions ship, get used, and follow their builders into their careers.
Theory is half the equation. The industry wants graduates who can apply it, then build something that survives contact with real users.
InnoSphere exists to close that gap.
Your domain is where you start, the craft you go deep in. A Sphere is what you build with it: a team you assemble yourself, around a problem that refuses to sit inside one subject. The Medici effect, run as club architecture.
Sensors read the building, models decide what to do about it. Energy that turns itself down, queues that predict themselves, labs that flag a fault before anyone files a complaint.
Every Sphere here is started by a student. Name it, pull in whoever you need from anywhere on campus, and go. Or invent a Sphere that isn't on this ring at all.
Spot a problem, name the Sphere, pull in whoever you need. No approval queue, no waiting for someone senior to bless the idea.
Spheres are open to every student on campus. The people who make an idea work are rarely the ones sitting next to you.
The four domains are a starting grid, not a ceiling. If the Sphere you want doesn't exist yet, that's the best possible reason to create it.
We run as an internal innovation consultancy: SRM sets the problems, students do the work, and the result has to hold up in front of the people who asked for it.
SRM is the playground and the priority. We operate as an internal innovation consultancy, so members get real client experience without leaving campus.
First brief: an immersive virtual campus tour for the Admissions Office.
Students and faculty submit structured proposals for real, validated problems. The strongest ones get resourced, mentored and staffed with a team built for the job.
Accountability by design: outcomes, not attendance.
Four domains give you depth and two mentors each. Spheres are what you build with that: teams you assemble yourself, from anywhere on campus, around problems that don't fit inside one subject.
Start in a domain. Build a Sphere. Or invent one that doesn't exist yet.
Any student or faculty member submits a structured proposal for a specific, validated problem.
Shortlisted proposals get funding, expert mentorship and a team assembled for complementary skills.
Every project runs to a measurable outcome and a demo. Participation isn't the finish line.
Three standing programmes that push our directors to design things students actually want to attend, and that leave members with something to show for it.
Curated conversations built to start arguments about ideas. Good ones get recorded and published.
Out of the university bubble and into startups, government innovation programmes and alumni-run labs.
A verified digital record of everything you shipped, tagged by skill and stamped by your project lead.
Salon themes on deck
Both routes are open to every department, and both end with a short 1-on-1.
Aptitude plus foundational technical questions. The standard entry route, with no prior domain experience assumed.
Aptitude plus an advanced technical evaluation, for people ready to contribute at depth from day one.