Skip to main content
Back to Work
Aditya Gangwani
0 → 1 Product Build

RallyVerse

A sports event registration and management platform built for sports event organizers to streamline player acquisition, UPI payment screenshot verification, event-day check-in, and sports event operations.

Role

Product & Technical Owner

Timeline

3 Weeks (Concept to Deploy)

Focus

Product Logic & System Arch

Stack

Next.js · Node.js · Postmark

Overview

RallyVerse was conceived to solve the fragmentation experienced by grassroots sports event organizers and badminton tournament coordinators. Organizers currently jump between three to four tools: one for user sign-ups, another for manual WhatsApp UPI payment verification, a third for event-day check-in, and a fourth for transactional emails. RallyVerse unites these modules into a single, cohesive interface, dramatically lowering friction and optimizing registration conversion rates.

The Problem

In grassroots sports event operations, momentum is easily lost. Traditional flows force users through disconnected links, resulting in high drop-off rates:

  • Form Friction: Filling out external forms that don't save registration state or lack payment screenshot verification triggers.
  • Manual WhatsApp Verification: Organizing teams spend hours manually verifying transaction reference screenshots sent via chat apps.
  • Chaotic Check-In: Lack of automated, real-time check-in dashboards leads to long queues on event morning.

Product Thinking & UX

The guiding philosophy of RallyVerse was **radical operational simplification**. I designed player registration journeys that take fewer than three clicks on mobile browsers. For organizers, we shifted focus from manual spreadsheet logs to action-oriented workflows: instant payment status approvals, quick participant search, and live check-in counters. This turned offline event friction into a professional, scalable sports event registration and operations workflow.

Key Features

Dedicated Event Registration Pages

Allows instant category selection and mobile-first registration workflows for competitive players.

UPI Payment Verification Workflow

Uploads transaction reference screenshots during registration, processed via a dedicated organizer review queue.

Sports Event Operations Dashboard

Live event-day player check-in dashboard with attendance tracking and CSV reporting.

Targeted Email Notification Loops

Automated event alerts, payment status updates, confirmation receipts, and custom broadcast runs.

Participant Record Management

Easily review entries, assign slots, update categories, and sync registration sheets.

Event Performance Analytics

Provides aggregate insights on ticket conversions, daily attendance, and marketing campaign outcomes.

High-Level Architecture

RallyVerse was architected for low latency and high availability. It separates concerns across three logical layers: the frontend client, the API gateway server, and the database/messaging state layers.

Next.js ClientTailwindCSS & ReactNode.js API ServicePlayer Registration EngineUPI Verification HandlerCheck-In State ManagerDatabasePrisma / PostgreSQLEmail ProviderPostmark API

RallyVerse runtime data flow and dependency boundary overview.

Challenges & Tradeoffs

Building the platform in 3 weeks necessitated precise scope management and conscious tradeoffs:

Concurrent Slot Booking Row Locks

To prevent race conditions during sudden registration rushes (e.g., 20 category slots remaining with 80 concurrent player checkout sessions), we implemented database row-level locking. While this increases peak request processing latency slightly, it prevents the severe operational failure of overselling category capacity.

Synchronous Verification API vs. Async Workers

For transactional verification emails and registration confirmations, we chose direct, synchronous API requests to Postmark rather than managing a complex background worker cluster. This reduced server resource overhead while keeping average client page loading times under 150ms.

What I Learned

Execution Speed is a Feature: Shipping a working system and gathering real-world user metrics beats over-architecting in isolation.

The Value of Transaction Error Handling: Transactional registration failures (like failed payment logs or invalid screenshots) must have built-in client rollback behaviors. Designing clean visual error states prevented player support requests during peak registration hours.

The Outcome

RallyVerse proved that 0→1 engineering is as much about **product alignment** as it is about database performance. By designing custom UPI screenshot verification loops and check-in workflows matching typical tournament organizer habits, we created a deployment-ready system that turns manual operational headaches into a smooth user flow.