Booking app for a salon or clinic: the features you need and what it costs

A booking app is a set of calendar rules

The screens are the easy part. A customer picks a service, picks a person, picks a time and confirms. Every booking app looks roughly like that, and it is why owners expect them all to cost the same.

The price sits underneath. Who can be booked for what, how long each service takes, what happens between appointments, who may cancel and when. Those rules live in a backend, or in booking software you already pay for. Before I price anything, I ask one question: where does your calendar live today? The answer often decides the package on its own.

Salon and clinic booking features, mapped to Launch, Growth and Scale

This is the map I use when scoping one. Launch connects to APIs you already have, so on Launch the rules come from your existing booking system. Growth and Scale run their own Node.js backend and PostgreSQL database, so the rules are built for you.

Slot rules and buffers decide most of the backend

Owners describe their calendar in a sentence. Writing it down usually takes a page. A colour takes longer than a cut. One therapist cannot do lasers. The room needs ten minutes of cleaning after each treatment. Write these down before you ask anyone for a quote, mine included:

• Every service, its duration, and whether it needs a specific person, room or machine.
• Buffers: setup or cleaning time before and after each service.
• Opening hours, breaks, holidays and each staff member's own days off.
• Lead time: how close to the slot a customer can still book.
• Cancellation and rescheduling: up to when, and by whom.
• Can one booking hold several services in a row, or several people?
• Walk-ins and phone bookings: who enters them, so the app never double-books.

Reminders, deposits and the no-show problem

Reminders are the cheapest fix for no-shows, and push is the obvious channel. It is less automatic than people think. On Android 13 and later, notifications for a newly installed app are off by default until the user grants permission, and Google recommends asking in context rather than on first launch. I ask straight after the first booking is confirmed, when a reminder clearly helps the customer. Apple's App Review Guidelines also say push notifications must not be required for an app to function, so the booking list inside the app has to be enough on its own.

Deposits and no-show fees are a payment flow. A salon visit or a consultation is a service used outside the app, and Apple's guideline 3.1.3(e) says those payments must use methods other than in-app purchase, such as Apple Pay or card entry. My post on taking payments in a UAE app covers gateways and refunds in detail. For scoping, decide three things: deposit or full payment, whether a late cancellation keeps the deposit, and who issues refunds. A single gateway with a simple flow can fit a package. Anything more complex is quoted separately.

What a clinic needs that a salon does not

A salon booking holds a name, a phone number and a service. A clinic booking can reveal why someone is seeing a doctor. That changes how I build it.

I keep the booking app thin. It stores the appointment, not the medical history. Reason-for-visit fields stay short and optional. Reminders say "Your appointment tomorrow at 10:00" and never the specialty or treatment, which matches Apple's guidance that push notifications should not carry sensitive personal information. Staff see only the bookings their role needs. Clinics in the UAE may also have health data rules to meet, and I am not giving legal advice here: check your obligations with your licensing authority. Specialised compliance work is quoted separately from the packages.

Once a clinic wants consultation notes, prescriptions, lab results, billing or insurance in the same system, it has outgrown a booking app. That is hospital and clinic management software, a fixed-quote build, and my hospital management system page describes it.

Pricing a sample salon app and a sample clinic app

Two hypothetical scopes, not past projects. A two-chair salon already uses booking software with an API. Customers need welcome, sign up, login, services, choose a stylist, choose a time, confirm, my bookings, booking details and profile. That is ten screens on an existing API, so it fits Launch at $999.

A clinic group has three branches, no existing system, and wants doctors to see their own day while a receptionist manages everyone's. That needs its own backend, separate staff logins, branches and reminders, which is Scale at $2,500 for up to 50 screens with a full admin dashboard. A single-branch salon with no booking software sits between them, on Growth at $1,699.

Third-party fees such as payment gateway charges, hosting and maintenance are not included. The exact scope is agreed in writing before work starts.