Web architecture
Autonomous Booking Systems
We build booking engines where customers book, reschedule and cancel on their own, with capacity per location, online payments and a per-practitioner calendar your team no longer has to hold together by hand.
Per branchOne diary per location, one system · GIGI Nails
Sound familiar?
- Bookings arrive over WhatsApp and someone copies them into a calendar by hand.
- You run several locations and none of them sees the real availability of the others.
- No-shows cost you money because nobody leaves a deposit when booking.
- The booking software you tried charges per seat and has no concept of your capacity.
Why a manual calendar breaks as you grow
With one location and one practitioner, WhatsApp works. The problem is not the tool: it is that availability lives in the head of whoever answers. The moment there are two locations, three rooms or five practitioners, that person becomes the bottleneck and the single point where the business can fail.
The symptoms are always the same: double bookings, gaps nobody filled because nobody could see them, and no-shows that cost the person who did not turn up precisely nothing.
What real self-service changes
Self-service is not a contact form with time slots. It means the customer sees true availability - the result of crossing capacity, room, practitioner and personal blocks - books, pays where applicable, and can then change their mind without messaging anyone.
For your team the change shows up in two places: the hours no longer spent moving appointments, and the share of slots filled, which rises because availability stops being a secret.
And capacity?
This is the part off-the-shelf tools usually get wrong. A nine-place class, a room that takes two overlapping appointments, a machine that can only be used once per slot: these are different rules and they live in the same calendar. They get modelled up front, not patched afterwards.
What you get
- Booking engine with full self-service - book, reschedule and cancel without messaging anyone.
- Capacity and availability per location, per room and per practitioner, with your own rules.
- Integrated online payments, deposit or full payment depending on the appointment type.
- Automated reminders by email and messaging, with customer confirmation.
- Operations panel for your team, with day, location and practitioner views.
- Deployed in Docker containers on your infrastructure or ours, with no per-seat fee.
How we work
- 01
Calendar modelling
1 weekAppointment types, durations, capacity, permitted overlaps and cancellation policy. Whoever holds the calendar together today takes part.
- 02
Build
4 to 6 weeksAvailability engine, booking flow, payments and operations panel, tested against real cases from your own calendar.
- 03
Rollout by location
1 to 2 weeksStaged launch: one location first, tuned against real usage, then the rest. Team training included.
Investment
Scoped quote
A costed proposal within 3–5 business days
Scope drives price. Send us the project: within one business day we tell you whether it fits, and the proposal — what is in, what is out and what it costs — arrives within three to five business days.
The range depends on how many locations, how complex the capacity rules are, and whether payments and loyalty are in scope. The number comes out of the scoping call.
Proof of work
Frequently asked questions
Why custom instead of Calendly or Booksy?
Because off-the-shelf tools charge per practitioner and assume a calendar model that is rarely yours. They work well for one person and a fixed duration. As soon as you have several locations, shared rooms, class capacity, prices per appointment type or loyalty, you start bending the tool until it breaks. Past a certain headcount the monthly fee also overtakes the cost of owning the system.
Can customers cancel and reschedule without calling us?
That is exactly the point. Full self-service is what removes the manual work - if your team still has to touch every change, the system has not solved anything.
How do no-shows actually go down?
Two levers, enabled independently: a deposit at booking time, and reminders that require confirmation. Which one fits depends on your sector, and it is decided from your own calendar data rather than by default.
Does it integrate with the calendar we already use?
Yes. We sync both ways with Google Calendar or Outlook so a practitioner personal block shows up in public availability.
Where does the system live?
Wherever you prefer. It ships in Docker containers, so it can run on your infrastructure or ours, and move later without rewriting anything.