All work
Travel & HospitalityTaxi Jee

Two sides of a booking, in one application

Most taxi websites take an enquiry and email somebody. This one had to work for the traveller booking the car and the operator driving it — which makes it an application, not a page with a form on it.

Visit the website
2
portals
6
public sections
0.4s
page response
The Taxi Jee homepage, showing a Darjeeling hero with a Book Now call to action and a call-centre number.
About the client

A booking is a promise made to two people at once

Taxi Jee run cars out of Siliguri into the hills — Darjeeling, Kalimpong, Gangtok, the routes visitors arrive for. A traveller books a car; a local operator drives it. Both need to know the same thing at the same time, and neither is sitting at a desk.

A contact form would have been simpler and would have failed the operator entirely. Once a booking has two parties who each need to see and act on it, the site stops being a brochure and starts being an application.

How we built it

Built as software, not as pages

01

Two portals, because there are two jobs

Customers sign in to place and follow a booking. Operators sign in to see what has come in and take it. One account type pretending to serve both would have meant every screen hedging about who was reading it.

02

Packages and destinations, not a fare calculator

Someone booking a hill trip is choosing a journey, not pricing a distance. The public side is organised around destinations and packages, so a visitor picks the trip they came for and the pricing follows from that rather than the other way round.

03

Laravel, so the rules live in one place

Availability, pricing and who may see which booking are decisions that have to hold no matter which screen asks. Keeping them in the application rather than spread across pages is what lets a second portal be added without the first one quietly disagreeing.

04

Quick, on connections that are not

Pages respond in well under half a second. Much of this is booked from phones on hill-road signal, and an application that assumes a good connection is an application that fails exactly where its customers are.

Does your booking have two sides to satisfy?

A form can take a request. It cannot tell the person fulfilling it what to do next. That distinction decides what you need to build.

Book a discovery call