Moments Galaxy

The problem

Bookings, customer details, pricing, and follow-ups were spread across phone calls, spreadsheets, and WhatsApp. Staff had no single view of availability, and customers had no reliable way to book without calling.

The platform replaced that with one system for both sides: a public booking flow and an internal operations console backed by the same data.

What it does

• Public booking wizard with branch, date, slot, and add-on selection.
• PhonePe payments with server-side verification and webhook handling.
• Admin console for bookings, customers, inventory, catalog, pricing, and staff roles.
• CRM with lead pipeline, activity history, and automation rules.
• WhatsApp bridge for confirmations, reminders, and inbound messages.
• ESP32 relay integration for on-site hardware alongside the web platform.

How it runs

A Next.js application backed by MongoDB, with Firebase Auth for identity and MongoDB as the source of truth for roles and permissions. Payments run through PhonePe; the WhatsApp bridge is self-hosted and paired to the venue's number.

It runs on a single VPS behind nginx with PM2, TLS via Let's Encrypt, and daily backups. One process tree, one database, no managed-platform bill surprises.

What I would change

The original build grew vertically: too much logic in route handlers and too many responsibilities in a single deployment. The next step is a layered module structure with generated API types and clearer boundaries between booking, CRM, and operations.