Custom booking systems for businesses too complex for off-the-shelf scheduling.

Custom booking platforms in production for franchise sports, multi-site beauty, equipment rental, and specialist service businesses. Stripe Connect, complex availability, full operational integration.

The case for a custom booking system

Most service businesses can run their booking on a SaaS scheduler. The market is mature: Calendly for one-on-one, Acuity for small service businesses, Mindbody and Zenoti for multi-location wellness, SimplyBook for general purpose. Each does its category well. For 80% of service businesses, picking the right SaaS and using it well is the right answer.

The point at which custom becomes the right answer is when your booking model has structural complexity the SaaS schedulers cannot model. The trigger is rarely a single missing feature; it is the accumulation of small misalignments that have each become a workaround.

Common patterns that break SaaS scheduling:

• Multi-resource bookings. A booking that requires a room, a staff member, and a piece of equipment all available at the same time. Most schedulers handle one or two of these, not all three. The staff schedule says yes, but the equipment is already booked, and nobody finds out until the customer arrives.
• Variable duration based on selections. A booking duration that depends on which add-ons the customer selects, calculated dynamically. A 60-minute base service becomes 95 minutes if the customer chooses two add-ons; the scheduler needs to find a slot that fits the final duration.
• Buffered or staggered bookings. A 60-minute service followed by 15 minutes setup before the next slot. Different buffer rules per service type. The buffer for a haircut is not the buffer for a chemical peel; the scheduler needs to know which buffer to apply.
• Group bookings and capacity. Classes, workshops, or events where multiple customers book into the same slot with capacity limits. Waitlist behaviour, partial cancellations, and minimum-attendee thresholds all change the booking logic.
• Franchise or multi-tenant. Each location, franchisee, or business unit operates independently but shares infrastructure and reporting. The customer sees one brand; the back office routes the booking to the right franchisee with the right commission structure.
• Operational integration. Bookings trigger more than calendar entries. They might trigger inventory allocation, staff scheduling, customer communications, payment splits, or government reporting. The booking is the start of a workflow, not the end of one.

The honest moment most agencies skip: most service businesses should not commission a custom booking platform. If Mindbody, Zenoti, or Acuity covers your model, the build cost of custom rarely justifies itself. About one in three booking discoveries we run ends with our recommendation to fix the SaaS configuration (or to switch SaaS) rather than build custom. The discovery cost is the audit deliverable. Custom becomes the right answer when the workarounds have started costing more than the licence, when integration is the constraint, or when your business model is genuinely outside the SaaS templates.

If your booking workflow has been forced into a SaaS that almost-but-not-quite fits, call 0431 000 062.

Symptoms to look for

You probably need a custom booking system when one or more of the following are true.

• Your SaaS scheduler does almost what you need, but staff work around its limitations. Manual notes, double-bookings managed manually, or external spreadsheets fill the gap. The scheduler is the system of record on paper; the spreadsheet is the system of record in practice.
• You have rules the scheduler cannot express. “If the customer books service A and service B, the duration is X. If they book A and C, the duration is Y.” These configuration cliffs are where SaaS schedulers stop working. The platform’s flexible-pricing module covers 90% of cases and leaves the other 10% to manual intervention.
• Multiple resources per booking. Room + staff + equipment + customer, all needing to align. The SaaS scheduler handles staff well, room sort-of, and equipment not at all.
• Multi-location or franchise. Each location has its own staff, services, prices, and availability, but you need cross-location reporting and central administration. The current setup is one SaaS account per location, with a manual data export job to consolidate them weekly.
• Payment complexity. Deposits, partial payments, refunds with cancellation fees, package payments, gift card redemption, member discounts. The scheduler does some of these; the rest are handled in Stripe directly, with reconciliation handled manually.
• Integration into a wider operational stack. Inventory, accounting, CRM, marketing, and reporting all need to receive booking data in real time. The current integrations rely on third-party connectors that break once a quarter.
• The customer experience is a problem. Customer feedback consistently mentions the booking flow as confusing or slow. The SaaS branding and design feel generic next to the rest of your customer experience. Drop-off in the booking funnel has plateaued and cannot be improved without controlling the front end.

DIAGNOSTIC

If three or more describe your situation, custom booking is probably the right answer. The question is whether to build a full platform or to layer custom logic on top of an existing scheduler.

The architecture we deploy

Every custom booking system follows the same architectural pattern. The components are deliberately boring. Boring is the point.

Resource and availability model

A flexible resource model: staff, rooms, equipment, capacity slots, or any other bookable entity. Availability is calculated from a combination of base schedules, exceptions, holidays, and live bookings. The availability calculation is performed once, on the source data, and cached at the right granularity for fast booking-flow rendering. No “let me check and get back to you” delays for the customer.

Service and pricing model

Services defined with duration, resource requirements, pricing rules, prerequisites, and add-ons. Variable duration and pricing supported. Package and bundle support built-in. The pricing rules live in code and are version-controlled, so the “why did this booking cost what it did” question always has a traceable answer.

Booking engine

The core engine: given a service, a customer, and a preferred time, find the next available slot that satisfies every resource constraint. Handles concurrent booking attempts safely. No double-bookings. The engine uses database-level locking to prevent the race-condition double-bookings that plague SaaS schedulers under high load. Two customers clicking “book now” on the same slot at the same time: one wins, one is offered the next available slot.

Customer experience

A clean booking interface. Mobile-optimised. Designed for your specific business, not a generic scheduler. Branded with your design. The booking flow is part of your brand, not an iframe with someone else’s logo. Page load times are tuned for mobile, where most bookings now happen.

Payment and deposits

Stripe or Stripe Connect integration for one-off payments, deposits, full payments, refunds, and cancellation fees. Membership and gift card redemption supported. The deposit logic handles the awkward cases (deposits applied to specific resources, deposits forfeited on no-show, deposits transferred to rescheduled bookings) without manual intervention.

Operational integration

Bookings flow through Nexus to every downstream system: accounting, inventory, staff scheduling, customer communications, reporting. Confirmations and reminders sent through email and SMS. The new-booking event fires once; everything downstream subscribes to it. Adding a new downstream system later is configuration, not re-development.

Admin and management

Staff and admin tools for viewing the schedule, managing bookings, handling exceptions, running reports, and configuring services. Built for the operational team, not just for IT. The admin interface is where the front-of-house team spends most of their day, so it gets the design care that public-facing pages usually receive.

Full audit trail

Every booking, every modification, every payment, every communication is logged. Disputes and customer support become a query. When a customer asks “I’m sure I booked the 3pm slot, not 4pm,” the answer is the audit log, including the exact selections the customer made at booking time.

Three engagement shapes

We structure custom booking engagements one of three ways. All three start with discovery.

• Focused booking platform. From $40,000. Single business, standard booking model with custom rules, payment integration. 10 to 14 weeks. Best when one specific booking model is the bottleneck and the rest of the operational stack already works.
• Multi-tenant or franchise platform. From $80,000. Multiple locations or franchisees, central administration, cross-location reporting. 16 to 24 weeks. Best for groups operating multiple sites or franchise networks.
• Run With Us retainer. From $6,500 per month. Post-launch development, continuous additions, security patching, quarterly review. Booking platforms evolve constantly as the business adds services and changes rules; the retainer is the most common path post-launch.

Call 0431 000 062 to talk through which fits.

Custom booking systems we have built

Three custom booking platforms. One named client, two confidential at client request. Reference calls available.

Motiv8sports franchise platform

• Problem: Sports franchise with weekly recurring programs across multiple locations and franchisees. Booking model required: multiple program types, capacity per program, recurring booking with prepayment, franchisee revenue splits, and integration into staff scheduling and physical kit fulfilment. Previous solution was a mix of three SaaS schedulers, one per region, with no central visibility.
• Built: Custom booking platform on Symfony with Stripe Connect. Customers book ongoing programs with weekly recurring payments. Franchisees receive automated payouts. Operations team has central visibility across all franchises. Customer-facing booking is fast and mobile-optimised. Built over 14 weeks across 100+ franchises Australia-wide.
• Result: Franchise expansion became operationally feasible. Manual booking work for franchisees significantly reduced. Cross-franchise reporting available for the first time. Head office support load on booking-related queries dropped to near zero.
• Stack: Symfony, PostgreSQL, Stripe Connect, Xero API (multi-tenant), AWS Sydney, Nexus middleware.

Multi-site service business booking

• Problem: Multi-site service business with three locations, complex availability rules (some services available only at specific locations, some staff trained on specific services), and a need for one customer record across all sites. The previous SaaS scheduler treated each location as a separate business, and the customer experience reflected it.
• Built: Custom booking layer over an existing operational platform, with Nexus orchestrating the data flow. Customer-facing booking shows real-time availability across all locations. Bookings flow to the right operational site automatically. The existing operational platform was preserved; only the booking layer was rebuilt. Built over 12 weeks.
• Result: Online booking adoption increased significantly. Phone bookings reduced. Customer experience consistent across locations. The “this should be one booking, not three” cross-site experience now actually works.
• Stack: Symfony booking layer, existing operational platform, Stripe API, Nexus middleware, PostgreSQL, AWS Sydney.

Equipment rental platform, name confidential

• Problem: Equipment rental business across two depots with 500+ unique pieces of equipment, multi-day rentals, equipment that required pairing (camera body and lens, trailer and hitch), and conditional pricing based on rental duration and customer type. The existing solution was a Google Sheet maintained by two staff members full-time.
• Built: Custom booking platform on Symfony with multi-resource booking as a first-class concept. Pairing rules built into the resource model. Customers browse availability across both depots, with pickup and return locations selectable independently. Stripe deposits and damage holds handled automatically. Built over 16 weeks.
• Result: Two FTE worth of admin work retired. Online bookings doubled in the first six months as customers stopped having to phone in to check availability. The Google Sheet retired. Damage holds (which were previously handled by manual credit card pre-authorisation calls) now happen automatically at booking time.
• Stack: Symfony, PostgreSQL, Stripe API, custom Vue.js booking interface, AWS Sydney, Nexus middleware.

Who you will work with

No account managers, no offshore teams, no juniors learning on your project. The two engineers below scope, build, and ship the work. Bring your operations lead and your front-of-house manager to discovery. Booking platforms live or die by the workflow understanding, and the workflow lives in the heads of the people who run it every day.

How we ship it

Custom booking system builds run in four named phases. Each phase is fixed scope and fixed price.

For most builds, total project time is 10 to 20 weeks. Multi-tenant, franchise, or equipment-rental builds with 500+ resources run longer.

Custom booking FAQs