Case study · Buswing

Peak season, without the double-bookings.

Hourly rentals, outstation trips and airport transfers on one platform — live fleet availability, a pricing engine, online payment and instant confirmation, with an operations dashboard behind it.

Client
Buswing
Sector
Travel & transport
Where
Mumbai
Built
2024 · 4-month build, then run by us
100+Bookings a dayProcessed without adding headcount
50+Vehicles managedLive availability across the fleet
0Double-bookingsSince launch
3 minAverage booking timeFrom service choice to confirmation

01 Before

The situation.

  • Every booking was a call

    Availability tracked by hand; at peak the team couldn't keep up.

  • Double-bookings

    No live fleet view, so the same vehicle could be promised twice.

  • Prices varied by who answered

    Fares quoted manually, with no consistency for customers.

  • No operational view

    No dashboard, no fleet overview — it lived in people's heads.

02 Built

What we built.

  • Next.js
  • React Query
  • Node.js
  • Redis
  • Google Maps
  • AWS
01

Three booking flows

Hourly, outstation and airport — each with its own pricing and availability rules.

02

Live fleet availability

Vehicle status updates automatically; nothing is tracked by hand.

03

Pricing engine

Fares from distance, duration, vehicle and time of day — the same answer every time.

04

Automatic confirmations

Confirmation, driver details and receipt sent the moment payment clears.

05

Operations dashboard

Fleet, bookings, revenue and utilisation at a glance.

06

Payments

Integrated gateway with instant receipts and clean reconciliation.

03 On screen

The system, as its users see it.

Buswing home page with a one-way, round-trip, local and airport booking form
buswing.com · BookingChoose a service, enter the trip, pick a vehicle at a live price, pay — confirmation is instant.

04 Timeline

Built, then run.

Launch was the halfway mark. We have run the system every month since.

  1. Discovery 2 weeks

    Booking operations, fleet workflows and the pricing model, validated with the team.

  2. Design 3 weeks

    Flows for customers, drivers and admins; booking prototype tested with users.

  3. Build 12 weeks

    Booking engine for three services, Maps and pricing, payments, confirmations and the dashboard.

  4. Run Ongoing

    Beta with part of the fleet, full rollout, then performance work and steady improvement.

Next case studyChaitanya's Academy — One system for a two-campus residential academy.

Next step

What’s one job you’d hand to an agent tomorrow?

Bring it to a free 30-minute audit. We’ll tell you whether an agent should do it, what it would take and what it would cost — or that it shouldn’t.

Book a free AI auditWhatsApp us

30 minutes · free · no pitch deck

WhatsApp