Right now bookings probably arrive like this: a WhatsApp message asking if tomorrow afternoon is free, you check a notebook or a Google Calendar, reply that three o'clock works, and two hours later they confirm — by which time somebody else has taken it.
Kokiyo Studio builds online booking systems for Malaysian businesses: customers see real availability and book it themselves, the system handles slots and capacity, sends confirmations and reminders automatically, and supports multiple staff and branches behind an admin calendar that is actually usable. We look at how you schedule today first — and if an off-the-shelf booking product already covers it, we say so rather than building one.
The cost is not the minutes spent replying. It is three things happening at once: double bookings resolved by apology, no-shows with nothing to absorb them, and a schedule that exists only in one person's head — so when that person takes leave, the business stalls. Open a second branch or hire a second pair of hands and the arrangement simply stops scaling.
The root cause is not the absence of software. It is that availability has no single source of truth: the calendar, the notebook, the WhatsApp thread and a colleague's memory each hold a version, any of which may be right and all of which may be stale. What a booking system actually does is make “is that slot still free” a question with exactly one answer.
What gets built
Slots and capacity rules
Different durations per service, buffer time between bookings, how many people fit one slot, how late a booking can be made, and how far ahead.
Staff, resources and branches
Scheduling by person, by room or by equipment; each with their own hours and time off; branches run independently while the owner sees all of them.
Automatic confirmations and reminders
A confirmation on booking and a reminder before the appointment. This is the most direct lever on no-shows, and the one that needs no one to keep it running.
Cancellations, reschedules and deposits
Your rules encoded rather than negotiated case by case: how late a free change is allowed, whether a deposit or full payment is taken up front, how refunds work. A payment gateway can be connected where it fits.
An admin calendar and the day's list
What your team opens in the morning: who is coming when, who has paid, who moved. Whether this one screen is good decides whether the system gets used at all.
Connecting to your site and systems
Booking lives inside your own site on your own domain rather than handing customers to a third-party page. It can connect to accounting, contact or messaging tools where that is worth doing.
Reporting
Which slots fill, which sit empty, how often people do not turn up, whose schedule is tightest. Used to plan rosters, not to produce attractive charts.
Where this usually fits
Salons, beauty and nails
Clinics, dental and physiotherapy
Fitness, yoga and class-based studios
On-site services and repair scheduling
Events and workshop registration
Education and tuition centres
Consultation scheduling for professional services
When you should not build this with us
If you take bookings yourself, a handful a day, for one kind of service, with no deposits and no second branch — use an off-the-shelf booking product. It costs a monthly fee, you can start today, and somebody else maintains it. Building custom at that stage does not pay for itself, and we are not going to pretend otherwise.
Custom usually starts making sense when: an off-the-shelf tool blocks how you actually work (unusual slot rules, scheduling by room or equipment, branches that must be both separate and visible together); booking has to connect to systems you already run; you need to hold the data and the customer list yourself; or the booking is only the first step of a longer process with quoting, work and follow-up after it. That is the point to have this conversation.
What is not included
Marketing. Building the booking page does not bring people to it; traffic is separate work.
Content and photography. Service descriptions, prices and images are provided by you unless quoted otherwise.
A point-of-sale or full accounting system. We can connect to one; we do not rebuild it.
Third-party costs. Payment gateways, SMS and messaging services bill you directly.
Long-term maintenance after launch. That is an ongoing partnership, quoted separately rather than quietly folded in.
What this usually looks like
Illustrative examples — not a client’s account
A salon with a handful of stylists
Customers ask on WhatsApp whether tomorrow is free, and the front desk checks a book and replies. The problem is not reply speed: two people can ask about the same slot at once, and the book is only updated minutes later. A customer who wants a specific stylist is harder still — someone has to check whether that person is even in. Once booking is online, the customer sees real availability broken out by stylist and takes it themselves, and the front desk moves from looking things up to handling exceptions.
An event with a fixed number of places
Sign-ups come through a Google Form, payment is a bank transfer with a screenshot, and the organiser reconciles the two in a spreadsheet. Registrations arrive in a rush in the last two days, manual checking falls behind, and a few places get oversold and then apologised for. The hard part is the day itself: confirming on the spot whether someone registered and paid means scrolling a phone. With registration, payment and the list as one system, overselling stops being possible rather than being caught, and checking a name at the door stops depending on memory.
Related work
These say what was built and nothing more. No result figures appear here, because we do not publish numbers a client has not agreed to and we cannot verify.
A salon's brand site, with the booking and sales experience built into the same site.
A salon schedules along two axes at once: by person and by service length. A cut and a colour do not occupy the same amount of chair time, and no two stylists keep the same hours — which is why “is tomorrow afternoon free” is a question nobody outside the shop can answer. That is the thing booking exists to fix.
An event registration site with an admin system behind it — public sign-up at the front, the organiser's management screens at the back.
Event registration is the same problem in another shape: the demand is compressed against one deadline, places are finite, and what the organiser needs on the day is not the sign-up page but a list they can search, export and check people in against. The work starts when registration closes.
Why this page carries no starting price
Website packages publish a floor because their scope is bounded. Booking systems do not, because a one-person booking form and a multi-branch system scheduling by equipment with payments and reporting are an order of magnitude apart. A figure in the middle would be dishonest to both.
There is no starting figure, and that is deliberate. A one-person, one-service booking form and a multi-branch system scheduling by equipment with deposits and reporting are an order of magnitude apart. A rough number would deter the small project and be a promise we could not keep on the large one. A free diagnostic settles the rules, the staff, the branches and the integrations first; the quotation follows that.
Can it work with my existing website?
Usually yes, and it depends on what your current site is built with. WordPress, Wix and Shopify can normally be embedded into or connected to. If the existing site is itself the constraint, we will say plainly whether replacing it first is the cheaper order of work — rather than selling you both.
Will customers actually use it, or keep asking on WhatsApp?
Some will keep messaging, and that is normal rather than a failure. The approach is to make booking online obviously less effort — one link, real availability, done in a moment, confirmation immediately — while keeping WhatsApp open with your team booking on the customer's behalf. The goal is not to force customers to change; it is to stop your team retyping the same thing.
Is the data mine, and what if we stop working together?
The customer list and the booking records are yours and can be exported at any time. The system runs on your domain and your hosting, and what we hand over is maintainable, documented code — another developer can pick it up, by design. A system only its author can change costs far more over its life than it did to build.
See it clearly before deciding to build
Six questions about how your business actually runs, about three minutes. You get back where you are, what a sensible next step is, and what is not worth spending on yet — including the answer “you do not need a booking system”.
