Websites & Ecommerce
How much does a direct booking system cost to build?
The short answer
A bespoke direct booking system in the UK typically costs £8,000 to £40,000 to build, with most single-site operators landing between £15,000 and £25,000. Running costs are usually £60 to £400 a month plus card processing at roughly 1.5%. Against OTA commission of 15–20% per booking, operators taking more than about £150,000 a year through third-party platforms usually recover the build inside the first season.
Indicative price ranges
Single-site availability and payment
£8,000 – £15,000
Live availability calendar, rules-based pricing, deposit or full payment, confirmation emails and a simple admin view.
Full booking platform
£15,000 – £25,000
Multiple unit types, seasonal and length-of-stay pricing, extras, amendments and cancellations, housekeeping and arrivals views, reporting.
Multi-site or channel-managed
£25,000 – £40,000+
Several locations, channel manager sync, dynamic pricing, memberships or subscriptions, EPOS or accounting integration.
These are indicative UK ranges based on projects we have actually delivered. Scope drives the number, not the sales conversation — we quote a fixed price after a scoping session, and we will tell you if an off-the-shelf tool is the cheaper answer.
Typical timescales
- 1–2 weeks
Rules and inventory mapping
Every pricing rule, minimum stay, changeover day and exception written down. This is where booking projects succeed or fail.
- 2–3 weeks
Design and booking flow
A mobile-first flow tested against real customers, because most bookings now start on a phone.
- 5–10 weeks
Build
Availability engine, payments, admin, notifications and the edge cases — double bookings, part refunds, date changes.
- 2 weeks
Parallel running and launch
Run alongside the existing method until a full week passes with no discrepancy.
Who this suits
- Operators paying 15–20% commission on a meaningful share of revenue.
- Businesses whose pricing or inventory rules do not fit an off-the-shelf booking tool.
- Anyone rekeying bookings from a platform into a spreadsheet or diary.
- Operators who want the customer relationship, and the email address, to be theirs.
Who it does not suit
- Very low booking volumes where a £40-a-month tool is plainly sufficient.
- Businesses relying on OTAs purely for discovery with no direct demand to convert.
- Operators without someone to own availability accuracy day to day.
- Anyone who needs it live before the season starts in three weeks.
What actually drives the cost
Pricing complexity
Flat nightly rates are simple. Seasonal bands, length-of-stay discounts, changeover rules and dynamic pricing each multiply the test cases.
Inventory model
Ten identical units is straightforward. Mixed types with individual attributes and allocation rules is a real engineering problem.
Channel sync
Keeping availability accurate across your own site and third-party platforms is the single most failure-prone area, and it must be built defensively.
Payments
Deposits, balances, part refunds, chargebacks and reconciliation add far more work than a single checkout.
Admin depth
A booking list is cheap. Arrivals boards, housekeeping schedules and occupancy reporting are a second product.
The commission maths
This is the only calculation that matters:
- Annual revenue booked through third-party platforms.
- Multiply by your blended commission rate — typically 15–20%.
- That is your annual cost of not owning the booking path.
An operator putting £300,000 a year through OTAs at 17% is paying around £51,000 annually. A £20,000 platform with £3,000 of running costs does not need to convert all of that to be an obviously good decision — shifting a third of bookings direct covers it in the first year.
The lever most operators underuse is a visible direct-booking price advantage. Hartswood Holiday Park undercuts the OTA channel by 10% on its own site: the guest saves, the operator still keeps more per booking than the platform route, and the relationship stays first-party.
What to insist on in the build
- No double bookings, ever. Availability locking under concurrent load is a specific engineering requirement — ask how it is handled.
- Mobile-first. Most enquiries and an increasing share of bookings happen on a phone, often out of hours.
- Your data, your list. Guest details, booking history and marketing consent should sit in your system.
- A usable admin. If the team cannot amend a booking on a phone from the yard, they will keep a paper diary as well and the data will drift.
Do not forget the demand side
A booking engine converts demand; it does not create it. Budget for the pages and search visibility that bring people to your site in the first place — see what a UK business website costs — and connect the bookings to your customer records rather than leaving them stranded, as covered in running your website, CRM and automation as one system.
Proof
Where we have done this
How we worked these numbers out
The price bands and timescales on this page are first-party figures taken from projects The Digital Hub has quoted and delivered for UK clients since 2020, not from third-party survey data. Ranges are rounded and exclude VAT. They are reviewed at least every six months and updated when our own delivered costs move. Where a figure depends on a third-party licence or hosting cost, that cost is named in the text so you can check it yourself.
Written by
Tom Beachell
Founder & Technical Director, The Digital Hub
Tom leads scoping and delivery at The Digital Hub, quoting and shipping bespoke websites, CRM platforms and private AI systems for UK businesses. The price bands and timescales on this page come from projects he has personally scoped.
Published 2026-08-26 · Last reviewed August 2026 · About The Digital Hub
Common questions
Should we drop the OTAs entirely?
Rarely. Most operators keep them for discovery and reach, then work hard to convert repeat guests to direct. The goal is shifting the mix, not going cold turkey.
Can a bespoke system sync with Booking.com or Airbnb?
Yes, usually through a channel manager. It adds cost and it must be built defensively, because sync failures cause double bookings.
What are the ongoing costs?
Hosting and monitoring from around £60 to £400 a month depending on scale, card processing at roughly 1.5%, plus support and improvements. No per-booking commission.
How long until we take a booking on it?
Most single-site operators are live in ten to fourteen weeks, and we always run it in parallel with the existing method before switching off.
Who owns the guest data?
You do. That is much of the point — the codebase, the database and the customer list are yours.
Next step
Get a fixed price for your own version of this
A 30-minute scoping call, then a written fixed price and delivery date. If an off-the-shelf tool is the cheaper answer for you, we will say so on the call.
- 1You tell us the process and the tools you pay for today.
- 2We map the scope and flag anything that will move the number.
- 3You get a fixed price, a schedule and an honest recommendation in writing.
Reply within 24 hours · No obligation · Full code ownership on every build