Bespoke booking systems, built in 14 days

Bespoke booking systems for clinics, studios, venues and schools, built around your rules in 14 days at a fixed price. What it costs, what's included, what isn't.

The App14 teamUpdated 16 November 20266 min read

We build bespoke booking systems in fourteen days for a fixed price: a booking app for your customers on iPhone and Android, and an admin dashboard for your team, built around the rules your current tool cannot handle. For comparison, published UK pricing for a custom booking system usually starts around £10,000 and takes two to four months.

What a bespoke booking system costs

RouteTypical costTypical timelineFits when
Off-the-shelf booking software£50 to £300 a monthDays to set upYour rules fit its fields
Custom booking system, UK agencyFrom about £10,000, commonly £20,000 to £50,0006 to 16 weeks, plus testingYour rules are specific and the scope is still forming
Multi-site or heavily integrated platform£50,000 to £75,000+Several monthsMany locations, many systems, procurement
Published UK agency and vendor pricing, 2026.

Compare over three years, not one month. A subscription at £50 to £300 a month costs £1,800 to £10,800 over three years. If it does the job, that is the cheaper answer. A custom build starts to pay when staff spend hours a week working around the tool, or when the rules it cannot express are costing you bookings.

We are not one of those rows. We build one fixed scope in fourteen days for £999 or £1,999, with a full refund any time before we start. Straightforward booking with reminders and deposits fits the Starter App. Multi-resource slots, conditional pricing or approval steps usually need the Advanced App, which covers complex logic. The full breakdown of UK pricing is in our guide to app development costs.

What bespoke actually means here

The word gets used loosely, so it is worth being precise. Most booking tools are configurable: you set your opening hours, your services and your prices, and the product does the rest. That is genuinely enough for a lot of businesses.

A bespoke booking system is what you need when your rules do not fit the fields on offer. Not because the tool is bad, but because it was built for the average of ten thousand businesses and you are not the average. The test is simple. If you are filling in the fields, configure. If you are working around them, build.

When a plugin stops being enough

Your situationPluginBespoke
Fixed 30-minute slots, one personFineOverkill
Variable appointment lengths by serviceAwkwardStraightforward
Rooms or equipment that cannot double-bookUsually not supportedCore requirement
Different deposit rules by serviceRarely supportedStraightforward
Staff with individual availability and skillsSometimes, badlyStraightforward
One booking consuming two resources at onceNoStraightforward
Your own app with notificationsNoYes

The rules that break off-the-shelf tools

In practice the same handful of requirements come up, and they are the ones that turn a configuration job into a build.

A booking that consumes more than one thing. A treatment that needs a therapist and a room. A van and a driver. A tutor and a classroom. Most tools model one calendar per person and cannot express a slot that is only available when two separate resources are both free.

Rules that depend on what came before. No bookings within four hours of the last one for that member of staff. A deep clean after certain treatments. A minimum gap for travel between sites. These are invisible to a tool that treats every slot as independent.

Prices and deposits that vary by more than the service. By customer type, by time of day, by whether it is a first visit. Once pricing has conditions, most booking products run out of room quickly.

Approval before a booking is confirmed. Common in schools, clinics and the public sector, where a request is a request until somebody with authority accepts it. Off-the-shelf tools generally treat booking and confirmation as the same event.

Somebody else's system holding the truth. If your practice management software, your CRM or your finance system already owns the customer record, the booking system has to fit around it rather than become a second version of it.

Booking systems by type

The rules differ more by how you sell time than by sector. These are the shapes we see most.

Appointment booking

Clinics, therapists, salons and consultants. One customer, one slot, but the slot depends on who is free, how long the service takes and which room it needs. Deposits and reminders do most of the work against no-shows; the arithmetic of no-shows shows why.

Class and studio booking

Fitness, dance, yoga and music studios. Many customers in one slot, so the rules are about capacity: a class that fills, a waiting list that promotes the next person when someone cancels, class packs or memberships that count down, and instructors who cover each other.

Event booking

Workshops, courses, tours and ticketed sessions. Fixed dates, limited places, sometimes several ticket types, and a way to check people in on the day. The hard part is usually what happens when an event is moved or cancelled, and who gets refunded what.

Room, venue and equipment hire

Meeting rooms, sports facilities, studios, vans and tools. One booking blocks an asset for a period rather than a slot, often with turnaround time either side and a deposit that depends on the length of hire. Stopping double bookings starts here.

Booking with approval

Schools, colleges, councils and membership organisations. Parents, staff or members request; somebody with authority confirms. The system has to show who asked, who approved and when. More on this in our pages for education and the public sector.

What's included

  • A booking app for your customers on iPhone and AndroidSelf-service booking, rebooking and cancelling, so reception is not the bottleneck.
  • An admin dashboard for your teamThe diary, customers, staff and resources, for the people who run it day to day.
  • Automated remindersThe cheapest intervention against no-shows.
  • Deposits and paymentThe second cheapest, and usually the more effective one.
  • Your availability rulesRooms, equipment, and people with their own rules, including slots that need two things free at once.
  • Cancellation and waiting listsSo a cancelled slot refills itself.
  • Approval steps where you need themA request stays a request until somebody accepts it.
  • Store submission, accounts in your name, and 30 days of supportAs with every build.

What's not included

The complete list for every build is on what's included.

Connecting to what you already use

Most booking systems need to talk to at least one other thing. The common ones are card payments for deposits, Google or Outlook calendars for staff, email and SMS for reminders, and an export to your accounting or CRM tool.

Each live connection takes real time. One or two fit comfortably in fourteen days. If your practice management or finance system has no way in other than a nightly export, the honest design is usually a scheduled sync rather than a live one. Integrating with existing systems covers the trade-offs.

How the fourteen days work

  1. Day 1

    Kick-off and scope

    We go through your goals, your users, and the one job the app has to do. Everything that is not that job goes on a version-two list.

  2. Days 2 to 3

    Design

    Screens, flows, and the look of the thing. You review and revise until you sign off. Nothing gets coded until you have.

  3. Days 4 to 10

    Build

    Front end, backend, accounts, notifications, admin dashboard. You see working builds as they land rather than a reveal at the end.

  4. Days 11 to 12

    Test and fix

    Real devices, real data, edge cases. This is where most of the unglamorous work happens.

  5. Days 13 to 14

    Submit and launch

    Store listings, screenshots, privacy details, and submission to the App Store and Play Store. Then 30 days of support while your first users arrive.

Day one is about your rules: every exception your staff handle by hand gets written down, and anything that is not essential goes on a version-two list. The full process is on how we work.

Moving off what you have now

Most businesses asking for a bespoke booking system already have something, and the question is not whether to build but what happens to the bookings currently in the old tool.

Bookings themselves migrate cleanly, because a booking is a date, a customer, a service and a resource, and every tool exports that. What migrates badly is history that only makes sense inside the old system: internal identifiers, audit trails, soft-deleted records. Decide before the build which of that you actually need, because pulling all of it across is usually more work than the booking system itself.

What you own at the end

The code, the database and the accounts are yours, transferred when the build completes. You can host it where you like and take it to another developer. That matters more with booking systems than most software, because the diary is the business, and renting it from whoever built it is how businesses end up unable to leave. There is more on this in who owns the code.

Who this suits, and who it doesn't

It suits clinics and therapy practices where the constraint is rooms and equipment, salons and studios where it is staff skills and class capacity, venues and hire businesses where one booking blocks an asset, and schools where somebody has to approve a request. The common thread is not the sector. It is that the diary has rules a calendar cannot express.

It does not suit a business with one person and fixed slots (a plugin is better and cheaper), a booking marketplace for many businesses, or an organisation that needs a long procurement process before anyone can start.

We have not published a booking-system case study yet. The closest example of how a build runs is Fast Flyer Transport, which went live on day ten of the fourteen.

Common questions

How much does a bespoke booking system cost in the UK?

Published UK pricing for a custom booking system usually starts around £10,000 and commonly runs from £20,000 to £50,000, with larger multi-site platforms above that. We build one fixed scope in fourteen days for £999 or £1,999.

How long does it take to build a booking system?

UK agencies typically quote six to sixteen weeks, plus testing. We build and submit to both app stores in fourteen days, because the scope is fixed before we start.

What makes a booking system bespoke rather than configured?

A configured system is an existing product with your logo and your opening hours in it. A bespoke booking system encodes rules the product does not have a field for: a treatment that needs two staff and a room, a deposit that changes by service, a slot that cannot be booked within four hours of the last one. If your rules fit the fields, configure. If you are working around the fields, build.

Why not use a booking plugin?

Use one if it fits. Plugins fail when your rules are specific: variable appointment lengths, resources that cannot be double-booked, staff with different availability, deposits that differ by service. That is when bespoke starts being cheaper than working around the tool.

Can it take deposits?

Yes, and for most businesses this is the single most effective thing against no-shows, more so than reminders.

Does it handle staff and resource availability?

Yes. Rooms, equipment, and people can each have their own rules, which is usually the exact thing off-the-shelf tools get wrong.

Can we move our existing bookings across?

Usually. Most tools export to CSV, and the bookings themselves migrate cleanly. What rarely migrates is history tied to the old system's internal ids. We agree before the build what has to come across and what can stay behind in a read-only export.

Do we own the system at the end?

Yes. The code, the database and the accounts are yours, transferred on completion. You are not renting it from us and you can take it to another developer.

Want to talk it through?

Tell us what you're trying to build and we'll tell you honestly whether a 14-day sprint is the right way to do it.

Full refund any time before we start work.

About the author

The App14 team · Design and engineering, Appetite Studio

App14 is the 14-day app sprint run by Appetite Studio, a London-registered design and engineering studio. We design, build, and ship production iOS and Android apps in two weeks, at a published fixed price. Everything we write here comes out of work we have actually delivered: the prices are our real prices, the timelines are our real timelines, and the limits are the ones we genuinely hold to.

Our articles are drafted with AI assistance and reviewed by the App14 team before publication. The prices, timelines, delivery record, and client outcomes described are our own.

Read next