Custom Booking System Cost: $12k–$80k (2026 AU)

The question we get asked most often by service businesses past about 500 bookings a month: "How much would it cost to just build our own?" Followed by the polite assumption that the answer will be horrifying.

It's usually less horrifying than people expect. A properly built custom booking system in Australia, fixed-price, runs AU$12,000 at the bottom and AU$60,000-80,000 at the top. The bottom number gets you something genuinely good. The top number gets you something a SaaS company would charge AU$2,000 a month for indefinitely.

The interesting question isn't whether you can afford a custom build. It's whether you're already paying more for SaaS than a custom build would cost over three years. For most clients past 1,500 bookings a month, the answer is yes.

This is the breakdown.

The case for staying on SaaS

Before the numbers, the honest acknowledgement: most service businesses should stay on SaaS. Acuity, Cliniko, Setmore, and the others exist because they're cheaper than custom for the vast majority of use cases. The economics are clear:

• Under 200 bookings a month: SaaS wins by a wide margin
• 200-1,500 bookings a month: SaaS still usually wins
• 1,500-3,000 bookings a month: depends on staff count, complexity, and integration needs
• 3,000+ bookings a month: custom usually wins
• Industry-specific compliance needs: custom may be the only option

If you're a solo physio doing 80 sessions a month on Cliniko at AU$45/month, please don't email us asking for a quote. Stay on Cliniko. It's the right tool.

What "custom booking system" actually means

A lot of confusion comes from people meaning different things by "custom."

Custom UI on top of SaaS backend. The booking front-end is custom-built and lives on your domain, but it talks to Acuity or Cliniko via API. Calendar, payments, reminders all stay with the SaaS. AU$8,000-18,000.

Full custom front-end and back-end. Your own database, your own calendar logic, your own payment integration, your own SMS provider. Nothing depends on a SaaS subscription. AU$25,000-60,000.

Custom platform with multiple locations and complex routing. Multi-staff, multi-location, multi-service, with pricing variation, package management, recurring bookings, integration with accounting and CRM. AU$50,000-120,000.

These are different products with different price tags. When you ask "what does a custom booking system cost," the first question back should be "which of these three?"

The AU$12,000-18,000 tier: custom UI on SaaS backend

This is the most common tier and the one we recommend for most businesses considering custom for the first time.

What you get:

• A native booking flow on your domain that looks like your site
• Slot selection that pulls real-time availability from Acuity/Cliniko/Setmore/Cal.com API
• Intake form built to your spec (conditional logic, file uploads, signed agreements)
• Stripe checkout (with deposits or full payment) integrated into the flow
• Confirmation page on your site, then handoff to the SaaS for calendar sync and reminders
• Admin dashboard if you need one beyond the SaaS's own admin

What you don't get: anything beyond what the SaaS API exposes. If Acuity doesn't support a feature, your custom front-end can't either.

Typical timeline: 4-6 weeks.

Hosting after launch: AU$30-80/month, plus the SaaS subscription stays.

When it pays back: almost immediately, if the embedded widget is hurting your conversion rate. We see clients clear the build cost in 60-90 days from the conversion lift alone. (See our piece on why embedded booking widgets convert badly for the maths.)

The AU$25,000-45,000 tier: full custom build

This is where it gets more interesting. At this level, you're not paying for Acuity any more. You're paying us (or someone like us) once, then a few hundred a month for hosting and SMS.

What you get:

• Full database, hosted in an Australian region for data residency
• Custom calendar logic — multi-staff, multi-location, multi-service, complex availability rules
• Native Stripe integration with proper webhook handling, refunds, deposits, partial payments, packages
• SMS reminders via ClickSend or MessageMedia at AU 7-9 cents per message
• Email confirmations via Postmark or Resend
• Google Calendar and Outlook two-way sync for staff
• Custom admin dashboard with the reports you actually want
• Booking flow tuned for your specific business model

What you don't get: industry-specific features Cliniko or HotDoc would give you. If you need clinical notes and PBS integration, this tier isn't replacing your practice management system. It's only replacing the booking layer.

Typical timeline: 10-14 weeks.

Hosting after launch: AU$80-200/month depending on volume.

When it pays back: depends on what you're currently spending. The maths we run for clients looks like this. A 12-staff allied health clinic on Acuity Premium plus SMS pays roughly AU$150/month for Acuity, plus AU$250/month in SMS credits, plus they're paying USD pricing in a weak AUD. Call it AU$500/month all-in. Three years of that is AU$18,000.

Add the conversion-rate lift from a native flow (usually 25-35%) on top of whatever revenue the booking page is currently generating, and the payback period on a AU$35,000 build is usually 14-22 months. After that, the savings stack.

The AU$50,000-120,000 tier: multi-location platform

This is the tier where SaaS genuinely can't compete. Multi-location franchises, healthcare groups with 20+ practitioners, businesses where the booking system is a competitive advantage rather than a utility.

What you get:

• Everything from the previous tier
• Multi-location with location-specific pricing, services, staff, and availability rules
• Per-location admin access for managers, with HQ visibility across all locations
• Complex routing — "find me the next available therapist within 5km who handles [issue]"
• Custom intake flows that branch based on service, location, or customer history
• Integrations with accounting (Xero), CRM (HubSpot, Pipedrive), marketing automation, and customer support
• Customer accounts with booking history, package management, and self-service rescheduling
• White-labelled booking pages for partner organisations if you sell B2B

When it pays back: usually immediately, because the businesses spending this kind of money are either replacing a SaaS subscription that's costing them AU$2,000-4,000 a month, or they're capturing revenue the SaaS was forcing them to leave on the table.

What's actually in the build cost

When we quote a custom booking system, this is what the money goes to. Useful to understand because cheaper quotes are usually skipping one of these steps:

• Discovery and design: 15-20% of the build. Understanding your business model, mapping the booking flow, designing the UI. Skipping this is how you end up with a build that doesn't fit the business.
• Database and backend: 20-30%. Modelling appointments, staff, services, availability rules, payments, customers. This is where bad builds get bad.
• Front-end and booking flow: 20-30%. The actual UI customers interact with. This is the most visible part and usually what people assume the whole project is.
• Integrations: 10-15%. Stripe, Google Calendar, SMS provider, email provider, any CRM or accounting tool.
• Admin dashboard: 5-10%. The interface your staff use.
• Testing, deployment, training: 10-15%. The bit that always gets cut from cheap quotes and always causes problems later.

If a quote is significantly cheaper than the ranges above, the saving is coming from one of these areas. Usually discovery, testing, or the admin dashboard.

The ongoing cost that nobody quotes upfront

This is the part most agencies don't tell you about. After launch, a custom booking system has running costs:

• Hosting: AU$30-200/month depending on size. We use Vercel and Neon for most builds, which sit at the low end.
• SMS: AU$0.07-0.09 per message via ClickSend. A clinic sending 1,500 reminders a month spends about AU$110.
• Transactional email: AU$15-50/month via Postmark or Resend.
• Payment processing: Stripe takes 1.75% + AU$0.30 per domestic card transaction. Not specific to custom builds, but worth including in the maths.
• Maintenance: 0-15% of build cost per year, depending on how often you want features added or libraries updated.

For a typical AU$35,000 build, ongoing costs run AU$200-400/month all-in. Compared to AU$500-1,500/month for the equivalent SaaS subscription plus add-ons, the gap is real.

The break-even table

Rough numbers for when custom starts beating SaaS, assuming a AU$35,000 mid-tier build:

| Monthly bookings | SaaS monthly cost | Years to break even | |---|---|---| | 200 | AU$50 | Never | | 800 | AU$150 | 9+ years | | 1,500 | AU$300 | 5 years | | 3,000 | AU$600 | 2-3 years | | 6,000 | AU$1,200 | Under 2 years |

The break-even is sensitive to two things: how much SaaS you're paying now, and whether the custom build also increases your conversion rate. If both, the payback accelerates dramatically.

A real client number

A Melbourne allied health group came to us in early 2026. Twelve practitioners across three locations. They were on Cliniko (AU$295/month), Calendly for new-patient bookings (AU$200/month for the team plan), and their reception team was manually re-entering data into Xero.

We rebuilt the booking layer on top of Cliniko's API, killed the Calendly subscription, and added direct Xero integration. Build cost: AU$32,000.

Twelve months in, their numbers:

• AU$2,400/year saved on Calendly
• AU$8,000/year saved in reception time (one fewer shift per week handling data entry)
• New-patient conversion rate up 28% (AU$11,400/month in additional revenue, by their measure)
• Cliniko subscription unchanged (they still use it for clinical notes and PBS billing)

The build paid for itself in five months. Year two onwards, the system is essentially free to run.

When it doesn't pay back

To be honest with you, plenty of custom builds don't pay back. Cases we've seen go wrong:

• The business stopped growing after the build, so the volume that justified the maths never materialised.
• The custom build solved the wrong problem (it was a great booking system, but the conversion issue was actually the homepage).
• The business under-invested in maintenance and the system started feeling old after 18 months.
• The owner changed business models and the bespoke flow no longer fit.

The way to avoid this is to be honest about the volume and growth trajectory before you sign anything. A custom booking system at 200 bookings a month is a vanity project. At 2,000 bookings a month, it's infrastructure.

How to know if it's worth quoting

The questions we ask before we agree to quote a custom build:

1. How many bookings per month, current and projected for 12 months?
2. What are you currently paying for SaaS plus SMS plus admin time?
3. What's your current booking page conversion rate?
4. What can't you do with your current tool that's costing you money?
5. What's your three-year horizon — is this business going to be bigger or roughly the same?

If the answers don't justify the build, we say so before we send a quote. Best to know in 20 minutes rather than after we've spent two weeks scoping.

If you want us to run the maths on your specific business, book a free audit. We'll look at your current setup, your volume, and your conversion data, and tell you whether a custom build pays back or whether you should keep your SaaS subscription and spend the budget somewhere else.