← All articles Request a quote

Booking systems For trades

What a custom booking system costs to build and run in 2026

Three things people mean by "custom", the monthly running cost almost nobody publishes, and the arithmetic that decides whether owning beats renting.

Ivan Kriuchkov

The short answer

€1,500–3,000

Configured for your trade, live in days

€15,000+

Built from scratch around how you work, takes months

≈$5/month

To run on a paid plan, for a sole trader taking jobs online

A custom booking system costs between about €1,500 and €100,000. The range only means something once you know which of three different products you are pricing. A configured platform is €1,500 to €3,000 and takes days. A bespoke build starts around €15,000 and takes months. Renting software costs nothing up front and €10 to €60 a month forever. The running cost of a modern serverless build, which almost nobody publishes, is a few euros a month for a solo operator. Whether owning beats renting depends on what you pay today, and below a certain subscription it never does.

On this page
  1. 01Three things people mean by "custom"
  2. 02What each one costs to build
  3. 03What it costs to run
  4. 04Own or rent: the break-even maths
  5. 05What moves the build price
  6. 06Red flags in a quote
  7. 07When you should not build one
  8. 08Questions people ask

Three things people mean by "custom"

Most of the confusion in this market comes from one phrase covering three products at very different prices.

Three categories of booking system, with typical cost, ownership and delivery time

Rented software

Calendly, Acuity, Setmore, SimplyBook, Square, Fresha, Booksy

Build cost

None

Do you own it?

No, you rent it

Time to live

An afternoon

A configured platform

Real software, built once, set up for your business on your domain

Build cost

≈€1,500 to €3,000

Do you own it?

Yes

Time to live

Days to two weeks

Bespoke, written from scratch

A unique application designed around your workflow

Build cost

≈€15,000 to €100,000+

Do you own it?

Yes

Time to live

Two to six months

Only the bottom two rows are custom in any meaningful sense. The middle row is where most appointment businesses belong, and it is the row that gets described least clearly. Agencies selling the third thing have an interest in pretending the second does not exist. And a rebranded plugin gets called bespoke for the same reason.

What each one costs to build

UK agencies publishing their own numbers in 2026 broadly agree on the shape of the market, even where they disagree on where the boundaries sit.

Jabu Designs quotes three tiers: £2,000 to £5,000 for a single-resource system, £6,000 to £15,000 for the multi-resource builds they describe as most common, and £20,000 to £50,000 and up for multi-location operators with compliance requirements. Bee Viral splits it differently: rented apps from free to about £60 a month, a booking journey built into your own site from around £1,500 with an optional £250 a month care plan, and fully bespoke software from £15,000 into six figures.

The two agencies draw the line between "configured" and "bespoke" in different places, because the line is blurry. What matters for you is asking a supplier which side of it they are on, and what specifically is being written for you rather than configured.

Ours sits in that middle row: a configured booking platform at €1,500, live in a few days, with customisation quoted separately. That is the price of software which already exists being set up for one more business. Anyone quoting €1,500 for bespoke development is giving you something else under that name.

On currencies

Agency figures here are in the currency each one publishes, sterling in both cases. Provider rates are in dollars, because that is how Cloudflare, Google and Anthropic bill. Our own prices are in euro. Nothing is converted, because the rate moves and a converted figure goes stale faster than the underlying one.

The number nobody publishes: what it costs to run

Build cost gets argued about. Running cost gets a hand-wave, and where it is quantified the figures tend to assume a traditional server.

Jabu Designs, quoted above, budgets £75 a month for hosting a mid-tier custom build. That is a fair figure for a rented virtual server, and to their credit they budget separately for support and transactional email rather than pretending those are free. On serverless the hosting line is roughly 75 times smaller.

Here are the actual provider allowances, checked in September 2026.

Provider free allowances and rates for running a small booking system

ComponentFree allowanceRate beyond it
Hosting and application codeCloudflare Pages and Workers 100,000 requests/day. Static files unlimited and free. Workers Paid from $5/month, including 10 million requests
DatabaseCloudflare D1 5 million row reads/day, 100,000 row writes/day, 5 GB stored Included in the same $5 plan: 25 billion reads and 50 million writes a month
Address lookup and service areasGoogle Maps Platform 10,000 calls/month per Essentials SKU. Pro SKUs get 5,000, Enterprise 1,000. ≈$2.83 per 1,000 autocomplete calls
AI assistantClaude Haiku 4.5 API None $1 per million input tokens, $5 per million output
Owner notificationsTelegram bot Unlimited Free
Customer SMSTwilio or similar None Per message, varies by country

Two things about that Maps row are easy to miss. The cap is per SKU rather than per API, and a single address lookup in a booking form can bill two or three SKUs against separate buckets: autocomplete as the customer types, then geocoding, then place details. The caps are also tiered, so a feature that sounds similar to another can carry half or a tenth of the allowance.

Watch this one

Google pushed Maps Platform subscriptions hard through 2026, starting at $100 a month. The free caps above exist on the pay-as-you-go plan, not on a subscription. A small booking business has no reason to be on a subscription, and moving to one turns a €0 line into a €100 one.

A worked monthly bill

Take a solo repair business taking 120 bookings a month, with roughly 300 people starting the booking form and a handful of declined bookings that send an SMS. The platform in this example has an AI assistant built into the admin panel, which the owner uses about 100 times a month to check the schedule and change prices.

Worked monthly running cost for a solo operator at 120 bookings per month

Hosting and codeWell under 100,000 requests/day€0 on free tiers, or $5/month on Workers Paid
Database writes≈2,400/month against roughly 3 million€0
Database reads≈900,000/month against roughly 150 million. D1 bills rows scanned rather than queries, so an unindexed availability lookup is what moves this number.€0
Maps≈1,800 calls/month against 10,000 on the busiest SKU€0
AI assistant100 commands, ≈4,000 input and 400 output tokens each≈€0.55
Telegram alerts120 bookings€0
SMS5 declines at roughly €0.07≈€0.35
Total ≈€0.90 on free tiers or about $5.90 on Workers Paid

Add €10 to €15 a year for the domain. One line is missing from that table on purpose: transactional email. This platform notifies the owner through Telegram and the customer by SMS, so there is no email provider in the stack and no email bill. If you want branded confirmations and reminders by email, that is a real line item on any system, usually free up to a few thousand messages a month and a few dollars after that. A quote that omits it is incomplete.

SMS and AI usage are metered per use, so they grow in proportion to activity rather than arriving as a subscription increase. Maps behaves differently. It costs nothing until you cross the free cap, at roughly 660 bookings a month on these assumptions of fifteen lookups per booking, and then it bills per call. That is the line to watch as you grow.

Serverless platforms charge for requests and rows, and a business doing a few hundred bookings a month generates a rounding error of both. A system on a rented virtual server would cost €20 to €75 a month whether anyone booked anything or not.

The free-tier cliff

The free numbers above are mostly daily, and they reset at midnight UTC. The failure mode of exceeding one is not a surprise invoice. It is a failed query, which for a booking system means a customer who cannot book and does not come back.

That is why a working business belongs on the $5 plan rather than the free one, and why I would treat any quote leaning on free tiers as one that has not thought about a busy Saturday. Five dollars is not the interesting number. The interesting number is the headroom it buys: roughly a hundred times what a small operator uses.

Own or rent: the break-even maths

This is the calculation that should decide it, and it turns on what you pay today. Assume a €1,500 build and €1 a month to run, against a subscription you are paying now.

Break-even time for a €1,500 owned booking system against various subscription costs

What you pay now Break-even, build only With a €100/month care plan
€15/month
€180 a year
≈8.9 years
Never pays back
€30/month
€360 a year
≈4.3 years
Never pays back
€60/month
€720 a year
≈2.1 years
Never pays back
€120/month
€1,440 a year · multi-staff, single location
≈1.0 years
≈6.3 years

If your platform also takes a cut of each booking, the arithmetic changes in your favour, because commission scales with your success while a build fee does not. A marketplace charging a percentage of new-client bookings costs you more every year you grow. Check your own statement for the rate you are actually paying and multiply it out over three years before anyone shows you a build quote.

The right-hand column is the one an agency would normally leave out. A €100 a month care plan costs €1,200 a year, which is more than most booking subscriptions, so on cost alone ownership loses almost everywhere once you add it.

The care plan changes the maths

A care plan buys developer availability, updates and changes. That is a different product from software rental and it should be justified on its own terms rather than folded into a break-even table to improve the numbers.

Some owners run the platform themselves and pay nothing beyond provider fees. That means handling a payment-provider webhook change, a Google billing change, and a Saturday evening outage yourself. If that is not you, the care plan is not optional, and the left-hand column above is not the comparison that applies to you.

What moves the build price

Within the configured-platform tier, quotes vary mostly along these lines:

Resources and rules

One person with one calendar is simple. Several staff, rooms or pieces of equipment, with dependencies between them, is not.

Payments

Taking a deposit at booking means payment integration, refund logic on cancellation and VAT handling. Pay-on-arrival avoids all of it.

Design

Your logo, colours and content are usually included. A different interface layout or a bespoke visual design is real design work and is quoted as such.

Languages

Every additional language multiplies the content, and machine translation still needs a human pass.

Integrations

Accounting, calendar sync, CRM. Each is a small project of its own.

Data handling

A booking system holds names, phone numbers, addresses and appointment history. Where that sits, who processes it, and whether a data processing agreement comes with the build are scope questions, and they cost time when the answer is not the default.

Migration

Moving existing bookings and customer records off your current platform is the most tedious part of the job, and it is often left out of quotes.

If a quote does not say which of these are in and which are out, it is not a quote yet.

Red flags in a quote

  1. 01

    Per-booking or per-customer fees on a build you are paying for. Escaping those is the reason to own the system. A build fee plus a per-transaction cut is rental with a deposit.

  2. 02

    Payment processing marked up. Stripe publishes its card rates for every market. If a developer is adding a margin on top of the processor's own fee, ask why.

  3. 03

    Hourly billing for the initial build. Fine for changes later. For an agreed scope you want a fixed price, because the risk of a bad estimate should sit with the person doing the estimating.

  4. 04

    No discovery or written specification. If nobody has documented what is being built, the quote is a guess and the overrun is yours.

  5. 05

    No answer on where customer data is stored. Which provider, which region, who the processor is, and whether a data processing agreement comes with the build. A supplier who has not thought about it has not thought about your customers' phone numbers either.

  6. 06

    No written handover of the accounts. Code ownership is the question people ask; the accounts are where they get stuck. The domain, the hosting, the payment provider. Our own builds run in the client's own Cloudflare, Google and payment accounts from the first day, so there is nothing to transfer at the end.

  7. 07

    "Custom" that is a configured plugin, sold as bespoke. Configured software is a legitimate and often correct choice. The problem is pricing and describing it as something else.

When you should not build one

Four situations where the answer is no.

You have not proved people will book online.

Find out whether your customers will book through a screen before you pay to own the screen. Start free on Calendly or Square; those tiers are good enough to answer the question.

Your subscription is small.

See the table above. Under about €20 a month, the payback period is longer than the useful life of most small businesses' systems.

Booking is not your real problem.

If what you need is a till, stock control, staff rotas and payroll, an all-in-one salon or clinic suite will serve you better even with its monthly fee.

You are on a marketplace for the customers, not the software.

Booksy and Fresha charge commission partly because they introduce people who would never have found you. Owning your booking page does not replace that discovery. It sits alongside it, and the sensible move is often to run both and shift repeat customers to your own page over time.

Questions people ask

How much does a custom booking system cost?

The question that decides the price is which of three products you are buying. A configured platform, built once and set up for your business, runs about €1,500 to €3,000. A bespoke build, written from scratch around your workflow, starts around €15,000 and can reach six figures. Rented software has no build fee and costs roughly €10 to €60 a month. Work out which one you need and the price mostly answers itself.

What does a custom booking system cost to run each month?

On serverless infrastructure, a solo operator doing around 120 bookings a month pays under a euro in usage on free tiers, or about $5 a month on Cloudflare's paid plan, which is the one a working business should be on. Add roughly €10 to €15 a year for the domain. SMS and AI features are billed per use. Map lookups are free up to a monthly cap and then start charging, which at fifteen lookups per booking lands at roughly 660 bookings a month.

Is it cheaper to own a booking system or subscribe to one?

It depends on what you pay now. Against a €15 a month subscription, a €1,500 build takes roughly nine years to pay back, so you should not do it. Against €30 a month it takes about 4.3 years. Against €60 a month, a little over two years. Add a managed care plan and ownership stops winning on cost almost everywhere, because the plan costs more per year than most subscriptions. If your platform takes a commission on bookings, the payback depends on your volume rather than a subscription price, and it is usually much faster.

Is a €1,500 custom booking system a red flag?

Only if it is sold as bespoke development. At that price nobody is writing a booking system from scratch for you, and an agency claiming otherwise is selling you something else under that name. It is a reasonable price for a productized platform: real software, built once, configured and deployed for your business. Ask which of the two you are being quoted for, and ask which parts are being written and which are being configured.

What should I never pay for in a booking system quote?

Per-booking, per-customer or per-transaction fees on something described as a custom build, because escaping those is the point of owning it. Payment processing marked up above the processor's own published rate. Hourly billing for the initial build rather than a fixed price against an agreed scope. Any arrangement that does not hand you the code, the hosting account, the payment account and the domain on final payment.

Work out your own number

Tell us what you book and roughly how many a month, and we will tell you whether owning one makes sense for you. If your subscription is small enough that it does not, we will say so.

Book a call Request a quote