Booking software or a custom booking system? How to choose

Start with established booking software. For most small businesses, that is the right answer: the calendar works, reminders go out, payments reconcile and somebody else handles the unglamorous edge cases around time zones, rescheduling and double-booking.

Move toward a custom booking system only when a business rule or integration creates a real ceiling. “We dislike the booking page” is usually a configuration or design problem. “A booking must reserve a qualified staff member, one of three rooms, a scarce piece of equipment and the matching inventory in another system—atomically” may be a software problem.

That distinction is narrower than the broader choice between a template and a custom website. A booking flow is not just a page. It changes calendars, takes money, creates obligations and becomes part of the working day. The question is not whether custom feels more premium. It is whether standard software can reliably express how the business actually sells time and capacity.

Four ways to put booking on a website

“Online booking” can describe four very different arrangements. Choosing the smallest one that satisfies the real requirements usually produces the best result.

Approach	What it is	Best fit	Main tradeoff	What you own
Embedded scheduler	A button, inline widget or hosted booking page from a general scheduling product	Consultants, solo providers and straightforward appointments	Fastest and least expensive, but the vendor controls most of the flow and data model	Your website and configuration; not the scheduling engine
Industry platform	Booking plus the operational tools common to one sector: POS, memberships, classes, tables, waitlists, CRM or marketing	Salons, studios, gyms, restaurants and multi-location service businesses	More capability, setup and recurring cost; changing platforms can become a business migration	Your business data subject to the contract and export tools; not the platform
Composable/API integration	A custom website experience using an established platform for availability, bookings or payments	Businesses that need a distinctive journey or a connection to existing systems without rebuilding scheduling itself	Better fit at the front end, but dependent on the vendor’s API, plan, limits and changes	Your interface and integration code; the vendor still owns the scheduling service
Fully custom system	Purpose-built availability, rules, admin tools, customer flow and integrations	Operations with unusual constraints that standard platforms cannot model	Maximum control and maximum responsibility for reliability, security, support and change	The code and data architecture, assuming the contract says so

One useful hybrid keeps an industry platform as the system of record while building a better public journey around it. That is custom development, but not a new scheduling engine.

What current booking software already covers

General schedulers are no longer just calendar links. As of August 27, 2026, Calendly lists a free plan, Standard at $10 per seat per month when billed yearly ($12 monthly), and Teams at $16 per seat per month yearly ($20 monthly); Standard can connect up to six calendars, while Teams adds team scheduling and routing capabilities (Calendly pricing). That is a sensible shape for calls, consultations and meetings where the scarce resource is primarily a person’s time.

Acuity is oriented more directly toward paid services. Its current US list prices are $16/$20 per month for Starter, $27/$34 for Standard and $49/$61 for Premium, with the lower figure in each pair requiring annual billing. Standard supports up to six calendars plus memberships, packages and text reminders; Premium supports up to 36 calendars, custom API and CSS access, and the option to enter a business associate agreement (Acuity pricing).

Square combines appointments with payments and POS. Its current US tiers are Free at $0, Plus at $49 and Premium at $149 per location per month. Published card rates vary by tier and channel: for example, online card payments are 3.3% + 30¢ on Free and 2.9% + 30¢ on Plus or Premium; the page also lists unlimited calendars and compares waitlists, reminders and staff controls across tiers (Square Appointments pricing). For a salon already running Square at the counter, that shared customer, payment and checkout context may matter more than a prettier standalone scheduler.

Vertical platforms go further. Mindbody’s US Starter plan currently begins at $79 per location per month and includes scheduling, online booking, payments, staff management, a website widget, basic reporting and discovery through the Mindbody app; higher plans are quote-based, and Accelerate adds room and resource management (Mindbody pricing). For fitness, wellness and beauty businesses, configuring that existing operating model is often more rational than commissioning it again.

Restaurants have different inventory: tables, party sizes, turn times, combinations, pacing and walk-ins. OpenTable currently lists Basic at $149, Core at $299 and Pro at $499 per month in the US. Core adds floor and table management, advanced inventory controls, waitlists and POS integration; network cover fees and a 2% fee for prepaid experiences can also apply, while the standard contract is one year and auto-renews unless notice is given (OpenTable plans and pricing). Those details belong in the buying decision because a restaurant is choosing distribution and operations, not merely a calendar.

The point is that a capable market already exists. Before building, test the business against it honestly.

Requirements worksheet: write the rules before comparing tools

Complete this with the people who take, deliver, change and reconcile bookings. Mark each item required now, likely within 18 months, or not needed, then state the rule. A feature name alone is not a requirement.

Requirement	Questions to answer	Priority / rule
Staff calendars	Can any qualified person take the booking, or must the customer choose? Can staff work across locations?
Rooms and resources	Must a room, chair, vehicle, table or device be reserved with the staff member? Can resources be substituted?
Services and duration	Are duration and price fixed, staff-dependent or selected through add-ons?
Buffers and travel	Is cleanup, preparation or travel time required before or after? Does it vary by service or location?
Deposits and cancellation	Full payment, deposit, card hold or pay later? What are the cutoff, refund, no-show and exception rules?
Memberships and packages	Do credits expire, roll over, transfer or apply only to certain services?
Classes and recurring appointments	One-to-one, group, series or recurring? Can one occurrence be changed without breaking the series?
Waitlists	Is it first come, first served, staff-approved or ranked by customer status? How long does an offer remain open?
Inventory and capacity	Does a booking consume stock, seats, beds, tables or another finite unit in real time?
Payments, CRM and POS	Which system is authoritative for customers, taxes, tips, refunds, gift cards and revenue reporting?
Permissions	What can owners, managers, front desk staff, providers and contractors see or change?
Reporting	Which daily decisions and financial reconciliations must the data support?
Accessibility	Can a keyboard-only user complete the flow? Are errors, labels, focus and status messages understandable?
Privacy and regulation	What personal or sensitive data is collected, why is it needed, where does it go and how long is it retained?
Export and exit	Can customers, future bookings, history, notes, forms, credits and payment references be exported in usable form?

Build five tests from real work: a normal booking, last-minute cancellation, reschedule across staff, payment failure and the ugliest recent front-desk exception. Run all five in each shortlisted product.

Configuration inconvenience is not a custom-software requirement

Standard software may add a step, use different terminology or impose a slightly different cancellation process. Those compromises have a cost, but so does replacing tested machinery.

Try these remedies first:

Change the service model, availability, buffers, forms and notifications.
Test the appropriate plan and an industry platform whose model already includes your problem.
Improve the website around the flow with clearer service selection, expectations, pricing and a well-placed embed.
Use a supported integration—or a focused API layer—while leaving bookings in the established system.

A restaurant site such as Luna Rosso can make reservations obvious without pretending to be operations software. Gloss Society reduces a request to the fields it needs. Forge Athletic Club shows programmes, membership and schedule before someone commits. The website should remove uncertainty; it need not replace the operating platform.

Warning signs that standard software has become the constraint

Consider composable or fully custom software when several of these are true and documented with real examples:

Staff repeatedly override the system or maintain a second spreadsheet.
Availability depends on multiple resources that must be reserved together, and partial success would create an invalid booking.
Pricing, eligibility or duration depends on customer history, inventory, contract terms or another live system.
The booking must trigger a bidirectional operational workflow, not just a notification.
Membership, credit, cancellation or waitlist rules are central to the business and cannot be represented without manual exceptions.
Reporting cannot reconcile bookings, fulfillment and payments at the transaction level.
Permissions are too broad for the roles or sensitivity of the data.
Testing shows the platform itself—not unclear services or weak demand—is losing bookings.
The vendor’s API omits an operation the business must perform reliably.

That last point deserves a prototype, not an assumption. Square’s Bookings API, for example, can search availability and create, update and cancel bookings, but seller-level write operations require a paid Appointments plan; it cannot create a booking with a non-zero cancellation fee, and bookable staff configuration still happens outside the Bookings API (Square Bookings API concepts). An API can expose a great deal without exposing everything.

Custom does not mean better; it means you now own the problem too.

With full custom software, support means diagnosing why two people saw the last slot at once. Maintenance means adapting when a provider changes an API. Build only when the advantage is worth carrying those duties for years.

Three worked scenarios

1. A solo consultant selling calls

The consultant offers 30- and 60-minute sessions, needs a buffer, collects payment and wants intake answers. There is no shared resource or complicated entitlement.

Likely answer: established software. Calendly Standard is currently $10 per seat per month on annual billing and supports multiple connected calendars; Acuity Starter is $16 per month annually and includes payment integrations, email reminders and custom forms (Calendly pricing; Acuity pricing). Choose by testing the booking and payment workflows.

A styled handoff may improve the website. A custom engine would reproduce solved work and create a new system to maintain.

2. A multi-staff salon or gym

The business has two locations, varied providers, classes, rooms, memberships, packages, waitlists, POS checkout and management reporting. The public page is only one surface; front-desk tools matter too.

Likely answer: configure an industry platform first. Square Plus is currently $49 per location per month before processing and optional fees; Mindbody starts at $79 per location per month, with resource management on a higher quote-based tier (Square Appointments pricing; Mindbody pricing). Calculate real fees and include front-desk staff in the trial.

If operations fit but the public journey is weak, keep the platform as the source of truth and build a focused integration.

3. An inventory-constrained, operationally complex business

Imagine a mobile service that must assign a certified technician, suitable vehicle, route window and consumable stock. A booking must update dispatch, inventory and the customer record together.

Likely answer: prototype a composable system. An API-backed platform may supply calendars, customers or payments while custom logic validates the combined constraint. If no product can create one authoritative reservation across all resources, full custom may be justified.

The proof is not “our workflow is unique.” It is required transactions the shortlisted products cannot complete, the cost of failure and an operating plan for support. Then compare the build with changing the workflow.

Compare total cost of ownership, not the first invoice

Use a three-year view. Add:

Setup: discovery, configuration, migration, training, website work and acceptance testing.

Recurring software: subscriptions, add-ons, SMS, marketplace or cover fees, and taxes.

Payments: transaction fees, chargebacks, refunds and processor changes.

Operations: staff time correcting bookings, reconciling systems and maintaining workarounds.

Technical ownership: monitoring, security, hosting, backups, incident response, accessibility and API changes.

Switching: export, cleanup, mapping, customer communication, parallel running and migration risk.

Published prices are inputs, not totals. OpenTable Basic is $149 per month, but its US pricing also includes network cover fees and either $0.25 per cover or $49 monthly for website reservations; Core is $299 and includes website reservations while retaining network cover fees (OpenTable pricing). Custom software may lack seat licenses, but it still has a support bill.

CMT Web scopes systems individually because booking rules, integrations and migration change the work. The pricing page explains the cost drivers without inventing a number that would be wrong for most businesses.

Data ownership is not the same as a usable exit

A contract may say the business owns its data while the export omits relationships needed elsewhere. Inspect a sample. Can you recover customers, appointments, cancellations, notes, form answers, staff assignments, balances, memberships, consent records and stable IDs? Can a replacement import them?

Acuity documents CSV exports for appointments and clients, including contact details, appointment type, calendar, price, payment status and selected form answers (Acuity export documentation). Its imports cannot include packages, gift certificates or subscriptions—proof that “CSV available” is not a migration plan (Acuity import documentation).

Calendly offers REST, embed and webhook APIs, but access depends on subscription and role, and webhooks require a paid subscription (Calendly API documentation). Record dependencies, vendor IDs, failures and retry behavior. Decide what customers see during an outage. An API is a rented dependency, not an ownership strategy.

Name the export format, migration owner, notice period, retention and deletion rules, fallback method and acceptable downtime. Test the plan before renewal.

Sensitive data changes the decision, but custom is not a shortcut

Clinics and other regulated businesses should begin with their legal and security obligations, then evaluate products and contracts against them. Do not assume that a scheduler is appropriate because it has encryption, a privacy page or a healthcare customer logo.

For HIPAA-regulated use, the US Department of Health and Human Services says a covered entity or business associate using a cloud provider for electronic protected health information needs an appropriate business associate agreement and must otherwise comply with the HIPAA Rules (HHS cloud guidance). Acuity offers HIPAA enablement and a BAA on Premium, while assigning customers responsibilities for configuration and message content (Acuity HIPAA guidance). That does not prove a clinic’s full workflow is compliant.

Collect the minimum necessary data. Review subprocessors, access, audits, retention, breach terms, backups, messages and connected calendars. Have qualified counsel or a compliance professional verify obligations. Custom may give finer control, but it expands what the business must secure.

The practical decision

Choose an embedded scheduler when the scarce resource is mostly a person’s time. Choose an industry platform when booking is inseparable from the sector’s ordinary operations. Choose a composable integration when the public experience or a system connection is special but the scheduling core is not. Choose full custom only when required rules cannot be represented safely and reliably any other way.

Bring the worksheet, the five test cases and the systems you already use to a discovery call. Tell us what the booking process actually has to do. “Use an existing tool” is an entirely acceptable answer—and sometimes the most valuable one we can give.