Booking looks like a solved problem until you try to buy it. There are dozens of tools that take a name and a time slot, and almost none of them handle the thing that makes your business different — the deposit rule, the two-staff-per-slot constraint, the booking that blocks a room and a person at once.
This is what actually drives the number.
Start with the free option, honestly
If your booking is one person, one slot, one price, and you are happy sending customers to a page that is not yours, an off-the-shelf tool is the right answer and you should stop reading. Nobody should pay for custom software to do what a $15/month tool does.
Custom starts making sense when one of these is true.
The five things that move the price
Does it take money? Taking a deposit means a payment provider, a tested path for declined cards, refunds, and a record that survives a dispute. That is a category of work, not a feature.
How many things does one booking hold? A haircut books a person. A dive trip books a boat, an instructor, two tanks and a slot in the tide table. Every additional resource multiplies the rules.
Who else needs to see it? Customer, staff, and manager are three different views with three different permission sets. Most of the cost of a booking system is not the booking — it is everything that happens after.
What are the rules that only you have? Minimum notice. Blackout dates. Different prices for different days. Group bookings that need a deposit but individuals that do not. These are cheap individually and expensive collectively.
Does it need to talk to anything else? Your accounting, your calendar, your messaging. Each integration is real work and real ongoing maintenance.
What we quote, and why the range is wide
A booking system sits in our business systems tier — typically two to four weeks. The spread inside that comes almost entirely from the five questions above, which is why we will not give a number before answering them.
Anyone who quotes a booking system without asking what a booking contains is quoting a different project from the one you need.
The question worth asking yourself first
What happens today when a booking goes wrong?
If the answer is "someone phones the customer and sorts it out", you may not need software — you need the phone number to be easier to find. If the answer is "we don't find out until they arrive", that is the actual problem, and it is worth building for.
What good looks like
- A customer can book without an account
- Staff can override anything, because reality does not follow rules
- Double-booking is impossible by design, not by discipline
- Cancellations free the slot automatically
- You can see tomorrow at a glance without exporting anything
If a quote covers those five and names a delivery window, it is a real quote. If it is a single number with no breakdown, ask for the breakdown before you compare it to anything.