Bhaada — Cargo Logistics Platform

Bhaada set out to bring on-demand cargo delivery to Tier-2 cities in Uttar Pradesh — but a logistics marketplace isn't one product, it's four: a way for customers to book, a way for drivers to accept and deliver, a way for the business to run operations, and a way for both sides to discover the service in the first place. Building any one of these in isolation would have meant reconciling four different data models later. Bhaada needed a single platform designed as one system from day one.

Customer bookings, driver assignment, live tracking, payouts, and admin oversight all have to agree on the same order state in real time — a customer cancelling mid-delivery, a driver going offline mid-route, or a coupon applying differently on two sides of the same order can't be solved by four surfaces each guessing at the truth. Every surface needed to read and write through the same real-time core, and the marketing site had to launch first, pre-app, without anything to actually book yet.

• Shared order and driver-assignment state across customer app, driver app, and admin portal
• Uber H3 grid-based dispatch used identically by both apps
• One coupon, referral, and pricing engine instead of divergent logic per surface
• Marketing site pre-launch, apps in development — sequenced without blocking each other

We built Bhaada around a single Node.js, Express, TypeScript, MongoDB, and Redis backend — with Socket.IO pushing real-time state to every surface and an Uber H3 grid indexing drivers and coverage zones. Two Flutter apps, customer and driver, share that backend directly. An internal admin portal gives the Bhaada team city-wise operational control — approving drivers, tracking revenue, and managing coverage and pricing — without any of that tooling being public. A Next.js marketing site launched first, ahead of the apps, to build the driver-partner network and customer waitlist.

Every surface talks to the same backend, so state never drifts — a booking, a driver, and a payout are the same order everywhere you look. Customers and drivers each get a focused app that only shows a fraction of the whole system's complexity, while the admin portal is the one place that ever needs to see the full picture.