# Booking SaaS for salons, barbershops, and spas — deploying the platform Booksy charges by the hire > When a salon adds a new stylist, Booksy's invoice goes up. Not because the software expands. Not because the salon moves to a richer feature tier. Because the pricing model is wired to the business's headcount — and headcount is exactly the number a growing service business is trying to increase. Source: https://saascode.ai/inside/booking-saas-for-salons-barbershops-and-spas-deploying-the · Published: 2026-08-09 · Section: use-case · Product: Reservo (https://saascode.ai/products/reservo) --- When a salon adds a new stylist, Booksy's invoice goes up. Not because the software expands. Not because the salon moves to a richer feature tier. Because the pricing model is wired to the business's headcount — and headcount is exactly the number a growing service business is trying to increase. Booksy charges $29.99 per month for the base plan, then $20 more per month for each additional staff member. At two staff: approximately $49.99. At five: approximately $109.99. At ten: approximately $209.99 (as of 2026-08-07, biz.booksy.com/pricing). The invoice grows with the team before the new hire has taken a single booking. That coupling — the meter tied to the customer's growth — is a design feature of the subscription, not an edge case. Every incumbent in this category has a version of it: Fresha meters on bookable team members, Acuity on calendar count, SimplyBook.me on both booking volume and provider cap. You, as the platform operator, do not have to pass that structure down to your tenants. When you deploy Reservo, you set the plan structure. Whether your customers pay per staff member is a pricing decision you make — not one inherited from a vendor's rate card. **Reservo is a multi-tenant booking and appointment-management SaaS sold once as source code.** You deploy it under your own brand and run it as the platform service businesses subscribe to — multi-staff calendar, deposit collection, automated email reminders, customer records — on infrastructure you control. This page covers what the appointment-services family specifically needs, which competitors belong in this comparison, and where Reservo's honest limits land for this market. --- ## What this family actually needs from a booking platform Multi-staff service businesses — salons, barbershops, spas, tattoo studios, nail techs, pet groomers — share one defining shape: a roster of practitioners who each take appointments, often offering overlapping services. A barbershop with four chairs runs four stylists who all cut hair. A spa runs aestheticians who all offer facials. A client books a service rather than a specific person, and the platform needs to route that booking to an available qualified staff member. That routing problem — one service, multiple qualified staff, real-time availability across the roster — is what separates this family from solo-operator calendar tools. A tool built around one person's schedule handles one-person shops. A staff-roster engine handles the rest. Beyond routing, this family shares several consistent needs. **A deposit mechanism.** No-shows carry real costs in this market — blocked chair time, product opened, staff paid for downtime. An upfront deposit collected at booking converts a tentative slot into a financial commitment. Configurable cancellation policies with deposit-forfeiture rules on late cancellations are an operational tool, not an amenity. **Customer records that stay with the operator.** A client who has visited the same salon for years has a history: services received, preferences, notes. On a third-party platform, those records live on the platform's infrastructure. The day a tenant considers leaving, they learn which records they can export and which the platform retains. On Reservo, that data is in the operator's database from the first booking. **A direct public booking page.** The brand experience this market expects is a direct link to the business — not "book through Booksy." Reservo generates a per-slug public booking page for each tenant, reachable directly, showing real-time staff availability with no third-party platform branding in the path. **Group-mode capacity for the right services.** Not every service is one-to-one. A nail salon might offer group pedicure sessions; a small studio might run a couples treatment with a capacity of two. Reservo's booking engine supports both individual slot mode and group class mode — multiple clients booking the same slot up to a configured capacity ceiling — enforced atomically at the reservation layer. Membership packs and recurring class series are not included in v1. --- ## The competitors your tenants are currently paying These four products dominate the appointment-services market. Each is a subscription sold to the service business. Together, they are evidence that what you are entering is a market that pays — and that the per-staff meter is its organizing economic principle. | Product | Pricing (as of 2026-08-07) | Metering axis | Confidence + source | |---|---|---|---| | **Booksy** | $29.99/mo base + $20/mo per additional user | Per staff member | HIGH — biz.booksy.com/pricing | | **Fresha** | Paid plans: Independent (flat), Team (per bookable team member), Enterprise (custom). No free plan since ~2025-08-01 | Per bookable team member on Team tier | HIGH on structure; USD figures UNVERIFIED (page geo-localises; USD amounts omitted) — fresha.com/pricing | | **Square Appointments** | Free (solo); Plus approximately $29–49/mo per location (figures conflict across sources) | Per location — distinct from per-staff | MEDIUM — two sources give different Plus figures; verify at squareup.com/us/en/appointments/pricing | | **Setmore** | Free: up to 4 users, 200 appointments/month; Pro approximately $5/user/month (annual) | Per user on paid tier | MEDIUM — aggregator-sourced; setmore.com | **The Setmore free tier is the honest concession for the small end of this market.** A two- or three-person shop running under 200 bookings a month has a real, functional, multi-user booking option at no cost. The per-staff argument applies cleanly once a business grows past that ceiling — which is precisely when Booksy's $20 per additional user and Fresha's per-member tier engage. None of these are available for you to purchase and operate as your own platform. They are subscriptions sold to the businesses that use them. The revenue they generate flows to Booksy, Fresha, Square, and Setmore respectively. Running Reservo means that revenue flows to you instead. --- ## What Reservo does not do for this family — stated plainly **Booksy's consumer marketplace genuinely brings new-client bookings, and switching booking software does not transfer that demand.** Booksy operates a consumer-facing discovery app. When a new client searches "barbershop near me" in the Booksy app, they may book a business they had never previously visited. That new-client flow is Booksy's product — as much as the scheduling calendar is — and it is not replicated by switching to any other booking system, including Reservo. For a salon that relies on Booksy's discovery directory for new-client acquisition, this is a real loss. Not a configuration gap. Not a feature on a roadmap. A scope difference that needs to be communicated clearly to any prospective tenant before they make the switch. Say so. **The staff-invite flow ships with the tenant-facing UI disabled in v1.** Reservo's multi-staff architecture is functional: the operator can add and configure staff members through the admin panel, set per-staff availability rules, and assign services. However, the self-service invite flow — where a tenant's admin opens their dashboard and invites a new colleague directly — ships with the invite buttons hardcoded to disabled. Three buttons on the staff management page carry an unconditional disabled state: the primary invite button, the resend button for pending invites, and the invite button in the empty-state panel. The underlying API and invitation logic exist in the codebase; the tenant-facing UI is not live. Adding staff to a tenant's roster in v1 requires the operator to act through the admin side rather than the tenant managing their own team. For a product whose defining use case is managing a multi-person roster, this is a day-one operational gap. Do not market self-service staff management to prospective tenants based on current v1 capability. **Email reminders only in v1.** The automated reminder pipeline sends at 24 hours and 1 hour before each appointment, with three-layer deduplication that prevents missed or duplicate sends. SMS reminders via Twilio are on the roadmap for v2. Phone numbers are already collected in the booking form. Do not present SMS as a v1 capability. **Calendar sync is read-only iCal in v1.** Staff members can connect any iCal-compatible external calendar — Google Calendar via its public feed, Apple Calendar, Outlook.com — and Reservo blocks those external busy slots from appearing as available to clients. Two-way sync and Google or Microsoft OAuth integration are roadmap. The connection is an overlay, not a write path back to the external calendar. **No consumer marketplace, no POS, no native mobile apps.** Booksy and Fresha each operate discovery marketplaces alongside their booking software. Both offer built-in payment processing, card readers, and retail inventory. Reservo covers booking, deposits, reminders, and customer records. A tenant running a product retail counter would need a separate POS alongside Reservo. A tenant hoping the platform brings walk-in traffic will not find it here. --- ## Why own it — for this scope and this market The argument for deploying Reservo to the appointment-services market is not a feature comparison with Booksy. It is a structural argument about who controls the terms. When a salon subscribes to Booksy, Booksy sets the rules: the per-seat rate, the processing fee, the terms of the marketplace listing, the privacy policy for client data. None of those are negotiable from the salon's side. The business is a customer of someone else's platform, operating under someone else's pricing schedule. When you deploy Reservo, you are running the platform. You set the subscription plan. You decide whether it meters on staff count, on booking volume, on some flat-rate structure, or on something else your market will accept. Your tenants' client records live in your database under your terms. A tenant who grows from two staff to eight does not trigger a pricing change on Booksy's schedule — it triggers a pricing change on yours, which you designed. The deposit mechanism is worth naming specifically for this market. No-show rates in salons, tattoo studios, and similar appointment-based businesses run high enough that deposits are an operational necessity, not an optional add-on. Reservo's deposit flow is configurable per service: fixed amount or percentage, with defined refund and forfeiture policies on cancellations inside the policy window. The funds settle via Stripe Connect Express — into each tenant's own Stripe account, not aggregated into a platform wallet that the operator then redistributes. The right scope statement for any conversation with a prospective tenant: Reservo is the booking and appointment-management layer for multi-staff service businesses that bring their own clients or acquire them outside the platform. It is not the consumer discovery platform that Booksy and Fresha also are. The businesses for whom Booksy's marketplace is the primary value — where the platform drives new-client acquisition — should stay on Booksy. The businesses that already have their clients and want a platform that keeps the data, the brand, and the billing relationship on their side of the ledger are the right fit. [See the live demo →](https://reservo.saascode.ai) · [Purchase Reservo for $249 →](https://saascode.ai/products/reservo) --- ## Common questions — appointment-services operators ### Can I operate Reservo as a booking platform for salons, barbershops, and spas under my own brand? Yes — that is the transaction this product is built for. You purchase the source code once at $249, deploy it under your own brand, and run it as the platform service businesses in your market subscribe to. Each tenant gets isolated staff, services, availability rules, deposit policies, and a public booking page. You set the plan structure. You keep what your tenants pay you. Reservo is sold to operators who want to run a booking SaaS for multi-staff service businesses — not to service businesses that want booking software for their own salon. ### What does Reservo not include that Booksy and Fresha do for salons and spas? Booksy and Fresha both operate consumer-facing discovery marketplaces that generate new-client bookings through their apps. Reservo has no marketplace. A tenant switching from Booksy or Fresha does not carry that new-client flow — the demand belonged to the platform, not the business. Both incumbents also ship native mobile apps for staff and clients, built-in payment processing and card readers, and retail POS with inventory. Reservo covers booking, deposits, automated email reminders (email-only in v1; SMS via Twilio is v2 roadmap), read-only iCal calendar overlay, and customer records. No marketplace. No POS. No native apps. ### Can the tenants I deploy Reservo for invite their own staff members through the dashboard in v1? No — not through the tenant dashboard in v1. The operator can add and configure staff members through the admin panel, set per-staff availability rules, and assign services. However, the tenant-facing self-invite flow ships with the invite buttons disabled — the underlying API and invitation logic are present, but the tenant UI is not live. Adding staff to a tenant's roster in v1 requires the operator to act through the admin side rather than the tenant managing their own team. This is a day-one operational gap for a multi-staff booking platform and should be communicated honestly to prospective tenants before they onboard. ### How does Reservo handle scheduling when multiple staff members at the same salon all offer the same service? Services are assigned to staff members in Reservo — a salon configures a service and assigns it to every practitioner who offers it. When a client books that service, the booking page shows available slots across all qualified staff and the client selects a time. Each practitioner has their own working hours, buffer rules between appointments, and external calendar overlay. The booking claims one practitioner's slot via an atomic database function that prevents double-bookings under concurrent requests. For group-mode services — where multiple clients book the same slot up to a configured capacity ceiling — the capacity is also enforced atomically at the reservation layer. ### Does the per-staff meter that my tenants currently pay to Booksy or Fresha apply to Reservo? No — the per-staff meter belongs to Booksy and Fresha, not to the codebase. Nothing in Reservo counts your tenants' staff members and reports a per-seat fee back to a vendor. The plan structure is yours to design: per staff member, per booking volume, flat monthly rate, or something else. Booksy's $20 per additional user is a fixed feature of Booksy's subscription. On Reservo, the equivalent line in your plan structure is a variable you set — and the growth your tenants achieve by hiring more staff does not automatically become a line item that increases what they owe you, unless you build that into your own pricing. ## Related reading - [Deploying Reservo for clinics and allied-health practices](https://saascode.ai/inside/deploying-reservo-for-clinics-and-allied-health-practices.md) - [Booking software for service businesses — a genuine buyer's guide (2026)](https://saascode.ai/inside/booking-software-for-service-businesses-a-genuine-buyer-s.md) - [Reservo vs Booksy, Cal.com, and the ways to acquire a booking platform](https://saascode.ai/inside/reservo-vs-booksy-cal-com-and-the-ways-to-acquire-a-booking.md)