July 2026
Seven booking systems later
I have built booking for limousines, cleaners, a clinic, a party bus, a coworking space and a trade association. The feature was never the hard part. Here is what actually goes wrong, and when I tell clients to skip booking entirely.
Across the studio's projects I have shipped at least seven things a client would call a booking system. A limousine service taking reservations and quote requests. A premium transport company that needed payments built in. A cleaning company whose customers customise the service before scheduling it. A party bus with point-to-point transfers and hourly rentals priced differently. A beauty clinic booking appointments. A coworking space reserving rooms and desks. A trade association hiring out meeting rooms. One word, seven different machines. But after building all of them, the surprises were never where I expected.
Clients know what they want. That is not the risk.
There is a consulting cliche that clients do not know what they are asking for. That has not been my experience. My clients usually arrive with their requirements already in hand: they know their business, they know how their customers book today, and they know what they want the website to take over. The real work sits one step later, and it is explanation, not extraction. Before anything gets built, I walk them through in depth how the thing will actually behave: what happens on payment, what happens on cancellation, what the customer sees, what they will have to manage themselves. I credit that habit with a specific result: not one client has regretted the payments decision we made together, in either direction. Informed decisions age well. Assumed ones do not.
The change that forces a rebuild
The messiest booking projects I have run all broke the same way: the scope changed in the middle of the build, and the build could not bend to it. A booking flow is not like a headline or a colour, where changing your mind costs a conversation. The flow is structural. Pricing rules, schedule logic, what gets collected when, whether money moves: all of it is baked in early, and a mid-build change to any of it can mean rebuilding rather than adjusting. I have eaten that rebuild before, and it taught me to treat the booking flow the way a builder treats foundations: agreed on paper before construction, and any change after that priced and planned as the structural work it really is, not slipped in as a tweak.
Plugins are cheap the way renting is cheap
Early on, the studio used off-the-shelf booking plugins, and for that stage it was the right call: easier, cheaper, faster to a working product. The cost showed up later, and it is the hidden cost I now warn every client about. Booking plugins run on subscriptions, and subscriptions are a dependency you do not control. The plugin stops working, or the vendor changes terms, or the licence lapses, and suddenly a core function of the business is down until someone renews or replaces it. Nowadays, with more experience behind us, we build custom booking solutions and plugins instead. The day-one price is higher and I say so openly. What the client buys for it is ownership: a booking system that fits exactly, with no third party who can switch it off.
Sometimes the answer is a WhatsApp button
The most useful thing I have learned about booking systems is when not to build one. It depends entirely on the industry, and for a lot of the businesses I work with, a contact form and a WhatsApp button do the job better than any booking engine. Singapore runs on WhatsApp. If your customers already message you to arrange everything, a booking system is friction dressed up as a feature, and it will sit unused next to the chat thread where the real bookings happen. I would rather tell a client that plainly and lose the line item than sell a system their customers will route around.
So the lesson from seven booking systems is not really about booking. Explain the machine before you build it. Lock the structure before you pour it. Own the tools your business stands on. And when the honest answer is that you do not need the feature at all, say that too. It costs you a line item and buys you trust, and trust is what a repeat-client business actually runs on.
Working on something like this?
I take projects from brief to delivery. If this note resonated, the case studies show the same thinking applied.