The Garba Arts Admin
An internal ops tool for a dance class business, replacing a shared Excel sheet with real lead tracking, fee handling, and role-based access, refined over 90+ rounds of feedback from the actual owner.
- Next.js
- Supabase (Postgres
- RLS)
- TypeScript
The Garba Arts is a real dance class business with two locations and six batches, and until this project, everything (leads, attendance, fees, split cash/UPI payments) lived in one Excel sheet shared across staff who shouldn't necessarily see each other's numbers.
I built a staff-only ops system for them, shaped by a lot of back-and-forth with the actual owner rather than a spec written up front. Leads move from inquiry to joined, but not on a rigid pipeline: someone can enter the system at any stage. Fees track split cash/UPI payments as one transaction instead of two disconnected numbers. There's a shared pool for leads who called in before anyone's decided which location they'll join. And the permission model started out flat and became location-scoped once real usage showed where that boundary actually needed to be.
Adding a phone-intake role that could claim a lead into either location surfaced a genuinely obscure Postgres behavior: a row-security policy's USING clause gets evaluated against the proposed new row, not just the existing one, even when there's a separate WITH CHECK clause too, which isn't how it's usually explained. My first fix looked right by every reasonable check and still failed silently on the real database. Getting to the actual cause took about a dozen raw-SQL tests, run directly against Postgres under different impersonated sessions, bypassing the app entirely, until I isolated the exact failing condition. The fix was a narrowly-scoped function with its own explicit check, instead of one broad policy, and that became the standing pattern, so the same shape of problem got avoided three more times later in the project without relearning it the hard way.
There's a second story from this one, too: users reported random sign-in failures on the live app, and it happened on two different browsers and on mobile data, looking exactly like a flaky network problem. It turned out to be a service-worker bug: a cache-first strategy that could return undefined on a cold cache miss, which the browser just reports as a generic connection failure. I found it and shipped the fix the same day it was reported.
This project has 91 logged decisions behind it, and real staff at both locations used it from August to October 2026, the pre-season before Navratri.
Outcome
Used August to October 2026, 91 logged decisions, 2 locations
More work
Solar Sahay
A free rooftop solar calculator for Indian homes. It uses your electricity bill and state to estimate system size, subsidy and payback, in English, Gujarati or Hindi.
Synergy
A shared points-and-recognition system for every student club in my MBA program, with QR check-in and live quizzes, and an access model that's actually hard to cheat, not just a leaderboard with a QR code taped to a poster.
Upasthiti
A mobile-first attendance PWA I built for an NGO, designed to survive patchy field signal and to stop depending on one person's personal spreadsheet.
Want to talk about work like this?
Get in touch →