Skip to content

Our story

Built inside the problem. Not around it.

HallHop started with students looking at a normal school day and asking a useful question: why does movement between classrooms still depend on paper and guesswork?

The beginning

Texas · 2025

A few lines of code became a different way to see the school day.

The first HallHop work focused on a Chrome extension that could understand a student’s schedule and make checking out and returning straightforward.

That led to a larger idea: connect the student moment, the teacher decision, and the school-wide view without turning movement into surveillance.

What has stayed true

Technology should make a school feel more understandable—not more watched.

01

Student perspective

Build with the reality of the people moving through the system.

02

Teacher attention

Measure success partly by how little the workflow interrupts instruction.

03

Responsible context

Give authorized people useful information with clear boundaries around it.

The founding team

Students building for schools.

Portrait of Varun Bhadurgatte Nagaraj

Founder · Lead developer

Varun Bhadurgatte Nagaraj

Started HallHop after noticing how much hallway movement depended on paper, memory, and guesswork. Leads the product and technical direction.

Portrait of Rithul Bhat

Co-founder · Developer

Rithul Bhat

Helped shape the teacher-side experience, with an emphasis on reliable pass decisions and practical classroom workflows.

Portrait of Maanya Shekar

Co-founder · Outreach

Maanya Shekar

Contributed to the project’s early structure, documentation, and outreach to the school community.

Still building

The work now.

Teacher command

Refining the fastest daily decisions

Pattern review

Keeping signals explainable and human-reviewed

Schedule intelligence

Strengthening Home Access Center context

Browser experience

Making the student flow feel nearly invisible

Start a conversation.

Tell us what movement looks like at your campus.

Contact sales