Case Study · Events

EventEye

College events, from discovery to door, in one platform.

Year
2024
Timeline
3 months
Role
Full product design & engineering
Status
Live in production
Visit live site
EventEye - product screenshot
Overview

A dual-sided college event platform with cross-institution discovery, sub-30-second ticket checkout, and a real-time organizer dashboard - replacing the WhatsApp-and-Google-Forms scramble.

The Challenge

College events ran on a duct-taped stack of WhatsApp broadcasts, Google Forms, and manual attendance at the door. Students had no way to discover what was happening beyond their own campus, organizers had zero real-time visibility into who was coming, and there was no data to learn from afterward. Every event was a logistical scramble with no infrastructure underneath it and no discovery layer on top of it.

What We Built

We built EventEye as a dual-sided platform that serves attendees and organizers as two distinct, purpose-built experiences. Attendees get a cross-institution discovery feed and a ticket checkout that takes under 30 seconds from intent to confirmed pass, paid through Razorpay. Organizers get a dashboard with real-time attendance, analytics, community tools, and role-based team access so a whole committee can run an event together. One codebase powers two products, each tuned for exactly what its audience needs.

How We Built It
01 · Discovery

Following one attendee end to end

We traced a single student from seeing a poster to walking through the door, and found the drop-offs were all at handoffs: discovery to registration, registration to payment, payment to entry. Closing those seams became the brief.

02 · Architecture

One record from discovery to door

A ticket is the same object whether it is being browsed, paid for or scanned at entry. Modelling it that way removed the reconciliation work that normally sits between a registration list and a door list.

03 · Delivery

Tested against a real event

We launched against an actual campus event rather than a staging dataset. Door scanning under patchy venue wifi is the kind of problem that only shows up when several hundred people arrive in ten minutes, and it is why offline-tolerant check-in exists in the product.

Key Capabilities

Cross-institution discovery

A unified feed surfaces events across colleges and institutions, so students can finally find what is happening beyond their own campus walls.

Sub-30-second checkout

An optimized, Razorpay-backed flow takes an attendee from intent to a confirmed ticket in under 30 seconds, removing the friction that killed conversions on forms.

Real-time organizer dashboard

Organizers see live attendance and event health as it happens, replacing the door-clipboard and the after-the-fact spreadsheet.

Event analytics

Post-event analytics turn every event into data organizers can learn from, so the next one is run on evidence rather than guesswork.

Community tools

Built-in community features let organizers build an audience around their events instead of starting from a cold broadcast each time.

Role-based team access

A whole organizing committee can collaborate with scoped, role-based permissions, so running an event is a team sport rather than one person's burden.

Outcomes
< 30s
Ticket checkout
2
Purpose-built experiences
Multi
Institution discovery
3 mo
Concept to launch
Tech Stack
React
Node.js
PostgreSQL
Razorpay
Tailwind

Project FAQ

About this
build

Common questions about how we approached and shipped EventEye.

A form takes registrations; EventEye runs the whole event. It adds cross-campus discovery so students find the event, a sub-30-second paid checkout, and a real-time organizer dashboard - none of which a form can do.

Like what you see?

Let's ship something like this.

EventEye went from concept to production in 3 months. Tell us what you're building and we'll scope exactly how we'd ship it.