A booking system that only offers times you can actually keep.

What the team sees is built around how you actually work — by day, by person, by location or by what still needs doing. It is a working list, shaped for whoever is doing the job.

Reporting across bookings, revenue and other systems is a dashboard project rather than a booking one.

Illustrative interface · sample data

Channels are connected to suit the project — email, SMS or WhatsApp, each through a provider account with its own setup and running cost. We work out which ones your case actually needs before anything is built.

Where payment is part of the booking we connect a provider you already hold or choose to open, and the money moves through that provider directly to you. Deposits, refunds and any cancellation charge follow the rules your business sets.

Cancellation, rescheduling and any charge on a change follow the policy your business chooses. We build that policy in, make it behave the same way on every channel, and keep a record of who changed what.

What moves across depends on what your current tool can export. We check that at the very start, so you know exactly what comes with you before the build begins.

Access is designed per project and enforced in the system rather than by convention. Security and compliance requirements are scoped per project. No certification or compliance standard is implied unless expressly included in the agreed scope.

No two of these move together, which is why a booking project is scoped before it is priced rather than the other way round.

What is a custom booking system?

It is booking software built around how one business actually works, rather than a subscription tool you adapt to. It holds your services, your people, your rooms and equipment, your hours and your rules, and it decides what a customer can book from those. Branditify builds it, you own it, and it does what your operation needs rather than what a product roadmap allows.

When is a booking form enough, and when is it not?

A form is fine when any time you are open will do, one person handles everything, and the volume is low enough that replying by hand is not a burden. It stops being enough the moment availability depends on more than one thing — a specific person, a room, a piece of equipment, a limit on numbers — or the moment somebody is spending real time confirming bookings by hand.

How does the system decide a time is available?

It tests that time against the rules the service requires: how long it takes, whether someone who can do it is free, whether the room or equipment is free, whether there is space left, whether the gap you need before and after has cleared, whether you are open, and whether it is far enough ahead. A time is offered only when every one of those passes.

What does the customer actually do?

They pick a service, they are shown only times that genuinely work, they choose one, they give you the details you need, and they get a confirmation. The slot is held while they finish so nobody else takes it mid-form. On a phone this is usually four screens, and it is designed to be finished in one sitting.

What does our team see once a booking is made?

A working list rather than an inbox: what is due today, in what order, with who it is assigned to and anything that still needs attention. Bookings can be moved, reassigned and closed from there, and each one ends as completed, cancelled or a no-show — which is what makes it possible to count anything later.

What happens when a booking has to change?

The same booking moves rather than a second one appearing. The new time is checked against exactly the same rules as the original, the slot that was given up goes back into availability, and whoever you have decided should be told is told. Whether the customer can do that themselves, and up to what point, is your rule and the system holds it.

Can the booking system be part of a larger business platform?

Yes. Booking covers availability, reservations and the journey around a scheduled service. Where your operation also needs customer records, service workflows, internal tools or reporting, those sit alongside the booking layer inside a wider custom system — scoped around how the business actually runs rather than forced into the booking layer. Branditify builds both, and the first conversation works out which parts you need.

What does starting a booking project involve?

A conversation about how you take bookings now, what your availability really depends on, and which of your rules are firm. From that we can tell you what the build actually is, what it needs to connect to, what is realistic to move across, and what it will cost. We scope the availability rules first, because that is the part that decides the size of the work, and the quote follows from it.

If you are still deciding which system you need, or how a custom build works in general, these are the better places to start.

How is a custom booking system different from a booking form on our website?

A form collects a request and emails it to somebody, who then checks a calendar and replies. A booking system checks availability itself, offers only times that work, holds the slot while the customer finishes, and confirms it to both sides at once. The difference is whether a person has to be involved for every single booking.

Can availability depend on staff, rooms, equipment or capacity?

Yes, and that is usually the reason to build one. A service can require a specific qualified person, a particular room, a piece of equipment, or several of these at once, and a time is only offered when everything it needs is genuinely free. Capacity is handled too, so a class or a table can hold several bookings until it is full.

Can different services have different durations and booking rules?

Yes. Each service can carry its own length, its own resource requirements, its own buffer before and after, its own notice period and its own limits on who can book it. That is a normal part of the scope rather than an extra, because almost no real business has services that all behave the same way.

Can customers reschedule or cancel their own bookings?

They can if you decide they should. Whether self-service changes are allowed, up to what point before the appointment, and what happens to the slot afterwards are all your rules — and the system applies them consistently. Cancellation and rescheduling rules follow the policy your business chooses, and we build that policy in.

Can we take payments or deposits when someone books?

Yes. Payments can be part of the booking flow where taking money at reservation time fits how your business works, and equally a booking can simply hold the time with payment handled later or in person. Where payment is included we connect a provider you hold or choose, and the money moves through that provider directly to you. Deposits, refunds and any charge on cancellation follow the rules you set.

What reminders can the system send?

Confirmations, reminders and updates can go out by email, SMS or WhatsApp, and staff can be notified inside the system itself. None of these is automatic or included: email needs a sending service on your domain, SMS needs a provider account and is charged per message, and WhatsApp needs an approved business sender and message templates. We work out which ones you actually need before anything is built.

Can it connect to our CRM, calendar or accounting software?

It can connect to anything that exposes an API, a documented integration or a usable export, which covers most mainstream calendars, CRMs and accounting tools. We check what your specific tools allow at the start, so the connections in the plan are the ones your stack can genuinely support.

Can we move our existing bookings and customer list into it?

Usually yes. Upcoming bookings, customers, services and history can be brought across from a spreadsheet, a calendar or an export from the tool you are leaving. We read what you actually have, map it with you, flag clashes and impossible dates for you to confirm, and keep the original file alongside. What moves across depends on what your current tool can export, and we check that at the start.

Does it work on mobile, and do we need a separate app?

It is built mobile-first, because most bookings are made on a phone, and the staff side works on a tablet or a desk browser. It runs in the browser, so it works on every device with nothing to install and updates for everyone at once. An app is worth adding when there is a real reason for one, and that is scoped as its own project.

Who owns the booking system and the booking data?

You do. The system is built for your business, the source code and the data belong to you, and your bookings and customers are yours to export at any time. This is a custom build, not a licence to a Branditify product, so there is no subscription that holds your data hostage if you stop working with us.

See selected Branditify work Companies Branditify has worked with