Calendly vs Acuity vs Setmore vs a Custom Booking System: What 30 Staff Across 8 Locations Pay in 2026

A multi-location service business with 8 sites and 30 bookable staff pays about $3,600 a year for Calendly Standard at its published $10 per seat per month, about $1,800 for Setmore Pro at $5 per user per month on annual billing, and between $660 and $828 for Acuity Premium at $55 to $69 a month, which covers up to 36 calendars (all prices read 19 October 2026). Nobody should build a booking system to save on those subscriptions; they are too cheap to beat. The custom question is narrower: a booking rule the products cannot express, such as a room, a machine and a practitioner that must all be free at once, built for $15,000 to $50,000 and tied to your own customer records.

Key facts (prices read 19 October 2026)

• Calendly Standard $10 and Teams $16 per seat per month (billing term not stated on the page); round robin and routing start on Teams
• Acuity Scheduling Starter $16 to $20, Standard $27 to $34, Premium $55 to $69 a month (the page shows two prices per plan, the lower tied to its 20 percent annual saving); packages and memberships start on Standard, custom API on Premium
• Setmore Pro $5 per user per month on annual billing, unlimited users, API included; Free is capped at 4 users
• Card fees are the same on every route: Stripe's published 2.9% plus 30 cents per successful US card payment, which is a bigger line than any booking subscription
• A custom booking layer: $15,000 to $50,000 for one scheduling workflow with your own rules; $50,000 to $100,000 with a customer portal and several systems; ongoing engineering $5,000 to $10,000 per month if you have no engineers

Who this comparison is for

A company with 10 to 100 staff and 4 to 12 locations: clinics, studios, salons, tutoring centres, installation crews. The pain is not the price of the tool, it is what happens when the tool cannot hold your rules: a double-booked treatment room, a package credit used at the wrong location, a deposit refunded by hand.

What the booking tools cost at 30 staff and 8 locations

Want to know what this would take for your own process? Send the workflow: the platform you already pay for, the one workflow it cannot run, and roughly how many people or customers touch it. A senior engineer sends back a one-page scope within two working days: what the platform does, where it stops, what we would build, and the range. If the honest answer is "configure, do not build", you get that too. No call needed. Or get a first range in a minute from the AI development cost calculator.

How to read these numbers. Subscription prices are the vendors' published list prices on the date shown, before taxes, overages, add-ons and seat growth. The custom-build figures are KUMO's published bands for the build only: hosting, model usage, third-party fees and ongoing engineering ($5,000 to $10,000 a month if you have no engineers) sit on top, and we say so wherever a total is compared. A standard tool is the right answer when your workflow fits it; configuration is enough when the gap is small; a custom build is justified only by a specific complexity named on this page, not by preference.

Calendly bills per seat and Setmore per user, so those lines grow with headcount; Acuity prices by plan and calendar count, so it stays flat until the 36-calendar ceiling. Calendly's page does not say whether its $10 and $16 are monthly or yearly rates, and Acuity does not label which of its two prices is annual, so treat each range as a floor and confirm at checkout. Prices are for the booking software only. Payment processing is on top of all of them: 4,000 bookings a month at an average $85 is $340,000 in card payments, about $11,060 a month in Stripe fees at 2.9% plus 30 cents ($132,720 a year), which is the same on every route and larger than every plan above.

The rule that decides it: how many things must be free at once

A booking tool models one resource per appointment: a person's calendar. A standard haircut or a consultation fits that. A treatment that needs a practitioner, a room and a machine, a class that needs a studio and an instructor, or an installation that needs a crew and a van does not, and no plan above changes that, because none of them lists multi-resource scheduling. The same is true of rules that span locations: a package of ten sessions bought at one site and used at another, a deposit held until the practitioner confirms, a no-show fee applied by customer history. Acuity's packages and memberships cover single-location versions of these; past that, staff work around the tool and the cost shows up as mistakes.

Break-even on the mistakes, not the subscription

Build cost divided by the monthly cost of the problem gives the payback. An illustration with assumed numbers, to be replaced with yours: if 2 percent of 4,000 monthly bookings go wrong because of a resource conflict or a package error (80 bookings), and each one costs $60 in refund, rebooking and front-desk time, that is $4,800 a month, or $57,600 a year. A $30,000 build pays back in about 6 to 7 months before hosting. If the same 2 percent costs $10 each, the payback is about 3 years and configuration is the better answer. Count your own errors for a month first.

Three routes, one honest recommendation

Configuration is enough. One site, one resource per appointment, a few packages: Acuity Standard or Setmore Pro with Stripe handles it for under $1,000 a year. Stop there.

Configure plus connect. If the gap is a hand-off, for example a booking that should create a customer record or trigger an invoice, an automation tool on the booking product's webhooks or API closes it for a few hundred dollars a month. The n8n vs Make vs Zapier comparison prices that route.

Custom booking layer. Justified by a specific complexity: multi-resource availability, credits and deposits that work across locations, rules driven by customer history, or booking that has to write into the system your team already runs the business in. KUMO builds that as a small application: an availability engine with your constraints, a customer booking view and a staff view, payment handling through Stripe, and write-back to your customer record. $15,000 to $50,000 for one scheduling workflow; $50,000 to $100,000 when it includes a customer portal and several systems. The Softr vs Bubble client portal comparison covers the portal half; the field-service app comparison covers crew dispatch.

What the build includes and what it does not

Included: discovery against real bookings, the availability engine, customer and staff views, Stripe integration, tests against a month of bookings, handover. On top: payment processing fees, hosting (a few hundred dollars a month), SMS and email sending costs, and ongoing engineering at $5,000 to $10,000 per month if you have no engineers. Run your own numbers in the AI development cost calculator, or send a short brief and get a scoped estimate in two working days.

Proof, labelled

KUMO has not published a booking-system case study, so the proof here is adjacent. Equipp is a rental operations platform KUMO built for a B2B equipment rental business, with item-level orders and asset identity, which is the closest shape to bookings that depend on a specific room or machine being free. FLIN is a production customer-facing portal build from scoped brief to launch. KUMO's founders built Volopay's first production version as its founding engineers, a finance product where every payment and approval had to be traceable, which is the discipline deposits and package credits need. KUMO is a software engineering studio that builds custom AI agents, workflow apps and portals for 10 to 100 person companies.

Questions multi-location service businesses ask

Is Calendly, Acuity or Setmore better for a 30-person multi-location business? Acuity Premium is the closest fit on price and structure: up to 36 calendars for $55 to $69 a month, with packages, memberships and an API. Calendly is built for meetings between people, not for rooms and services, and Setmore Pro is the cheapest at $5 per user per month on annual billing.

How much does a custom booking system cost compared with Acuity? Acuity Premium is about $660 to $828 a year; a custom booking layer is $15,000 to $50,000 once, plus hosting. It only pays back if booking errors cost you more than the build within a year or two.

Can Acuity handle bookings that need a room and a practitioner together? Its pricing page (read 19 October 2026) lists calendars, packages and memberships, not combined room and practitioner availability. If both must be free at once, test that case in the free trial before you commit.

What do I pay on top of the booking software? Card fees: Stripe's published rate is 2.9% plus 30 cents per successful US card payment (read 19 October 2026), and it is the same whichever booking route you choose.

How long does a custom booking layer take? 8 to 12 weeks for one scheduling workflow with Stripe and one customer-record integration, longer if your data needs cleaning first.

See AI workflow automation for how KUMO scopes a workflow layer, or book a 30-minute call with the two booking rules that cause the most mistakes.

The numbers in one file. The Build vs Buy Price Book, October 2026 has the published prices of 40 business tools read in October 2026, what they cost a 40-person company, and the four tests that say whether a custom build is worth it. Download the PDF (8 pages, free, no form).