Web Mister AI · Product family

The chair,and who is in it.

A salon is a diary, a team and a shelf — not a general ledger. Its colour, its logo and its client page are yours to set. This pack runs the day the way the floor runs it, and deliberately leaves the accounting turned off unless you ask for it.

See the intelligence Open the book

The Open Shear — the Web Salon & Spa product mark

/app/salonLive salon dashboard · real product

The Web Salon & Spa dashboard — sales, margin, inventory value, and operational alerts for expiry and shortages

0
screens in the pack
0
deterministic engines
0
journal entries required

What is actually in the box

A working salon, not a price list.

Sixteen screens — bookings and the day's schedule, clients and their history, services and looks, retail and its suppliers, the team and what they have earned.

The day

Salon dashboard
Bookings
Schedule & availability
WhatsApp assistant

Clients & services

Clients
Services
Lookbook

Retail

Products
Product orders
Suppliers
Purchases

Team & admin

Staff
Commissions
Expenses
Reports
Settings

The identity

The Open Shear

One continuous line runs through both finger rings, up to the pivot, out along the blades, and ends in a single point of light where they open — the moment before the cut, which is the moment the appointment exists for.

01
The Rings
Two hands, two people. The booking is made.
02
The Pivot
The chair is assigned, the hour is held.
03
The Blades
The service runs, and the commission accrues to it.
04
The Open Point
It is done, and she is booked again before she leaves.

Platform

The accounting is off. On purpose.

Every other pack in this family exists to put a transaction into a ledger. This one does not, and that is a decision in the source rather than a gap in the build: both salon engines carry «the salon does not touch accounting» as a binding constraint in their own headers, and the product registry marks accounting optional and disabled by default. A salon owner does not want a chart of accounts. She wants to know who is in the chair, who has stopped coming, and what her stylists have earned — and to hand a client a page that looks like her salon rather than like software. That is the whole of what this pack does, and the restraint is why it stays usable.

Operational, not financial
Bookings, schedules, clients, services, retail and commissions. No journal entries, no period close, no trial balance — unless you switch accounting on, which is a choice rather than a condition of using it.
The identity is yours, not ours
Settings carries a salon logo upload and a theme colour that applies to the admin screens and the public client page together — two presets (pink and dark gold), eight preset swatches, or any hex you type. The text colour above it is chosen automatically from the colour's perceived brightness, so a light accent gets dark text and a dark one gets white.
The diary is the system
The day's schedule is the primary screen: who is working, which chairs are free, what is confirmed, what is at risk of not showing. Everything else hangs off it.
Commission that is earned, not assumed
Each service carries its own commission, accruing when the service is completed and collected — not applied as a flat percentage of a monthly total.
A page your clients actually open
Each salon gets a short public link — services, work, and a “book by WhatsApp” route — carrying the same theme colour and logo as the admin screens. It appears only while its status is set to active, so an unfinished page is never live by accident.
Retail without a warehouse
Products, orders, suppliers and purchases at the scale a salon actually needs — a shelf behind the chair, not a distribution centre.

Bookings & schedule

The day, before it happens.

The dashboard opens on today: bookings, who is available now, what is upcoming, what needs confirming, and how much of the chair time is actually sold.

Utilisation is measured, not guessed
The dashboard shows occupancy against the minutes that were actually staffed — so a quiet day reads as a quiet day rather than as an absence of data.
Confirmation and no-show, separated
Awaiting confirmation, late, and did-not-attend are distinct states with their own counts, because they call for different actions.
Booking by WhatsApp
A salon number can take bookings and questions through an assistant, with a simulator to test the conversation before it faces a client.

/app/salon/bookings

How a booking arrives

Two doors, one diary.

A salon does not get its bookings from one place. Some clients open the page you sent them; most send a message at an hour when nobody is at the desk. Both doors lead to the same diary, and neither needs someone to retype anything.

The page you hand a client
Every salon gets a short public link carrying your services, your work and your identity colour. A client opens it, sees what you actually offer, and books — or takes the “book by WhatsApp” route from the same page. It goes live only while its status is set to active.
WhatsApp, answered by the assistant
Link the salon's number and the assistant takes bookings and questions on it directly. This is the model-backed tool of the pack, not one of the two deterministic engines — it reads what was written and drafts the reply, rather than matching a keyword.
It lands in the book, not in an inbox
A booking made on either channel becomes an appointment against a real chair and a real stylist, subject to the same availability and speciality rules the diary already enforces. There is no separate list of “requests” for someone to transcribe on Saturday morning.
Rehearse it before a client sees it
A simulator lets you run the conversation yourself and read what the assistant would say, so the first person to test it is you and not a customer.

/app/salon/whatsapp

Clients

Her rhythm, not her average.

A client register that carries visit history, so the system can learn how often each person actually comes — which is the only basis on which an absence means anything.

History per client
Visits, services taken and the stylist who did them, held against the person rather than the appointment.
Rhythm over frequency
Someone who comes every four weeks and someone who comes every twelve are both regular. A single threshold would call one of them lost.
Personal data held apart
Sensitive identity fields live in their own table behind stricter permissions than the record referencing them.

/app/salon/clients

The team

Who is on, and who is free.

Stylists with their specialities and their availability, so a booking can only be made against someone who is working and can actually do the service.

Specialities are real constraints
Colour, make-up, skin, nails and styling are attached to the person, so the diary cannot book a service to someone who does not do it.
Availability drives the diary
Shifts define which minutes exist to be sold; the schedule cannot offer an hour nobody is working.
Attendance without a payroll engine
Working hours are tracked here for the floor. Payroll itself stays at establishment level rather than being forked into the salon.

/app/salon/staff

Retail

The shelf behind the chair.

Products sold alongside the service, with the orders, suppliers and purchases that keep them there — at salon scale, without pretending to be a warehouse system.

Products and orders
What is stocked, what has been ordered, and what is due — enough to keep the shelf full without inventory ceremony.
Suppliers and purchases
Buying from suppliers increases stock. The chain is short on purpose.
Expenses recorded simply
A plain expense log, with no journal entries behind it — consistent with the pack's decision not to be an accounting system.

/app/salon/products

Identity

Pink, or gold, or anything you type.

The salon's colour and logo are settings, not a decision we made for you. The theme applies to the admin screens and the public client page together, so the salon a customer sees and the salon you work in match without being configured twice.

Two presets, eight swatches, any hex
Pink and dark gold are one click. Eight more colours are one click each. Beyond that, type a hex — it is validated before it is saved.
Text contrast is chosen for you
The colour above the accent is computed from its perceived brightness, so a light accent gets dark text and a dark one gets white. There is no way to save a combination that cannot be read.
Nothing about the pack is gendered
Services, stylists, bookings, retail and commissions carry no assumption about who the salon serves. The identity is the part that says who it is for, and that part is yours.

/app/salon/settings

Commissions

Earned on completion. Paid on collection.

Commission is attached to the service, not to a monthly percentage — it accrues when the work is completed and the money is collected, which is the only version of the number a stylist and an owner can both agree on.

Per service, not per month
Each service carries its own rate, so a mix of high and low margin work does not average into something nobody recognises.
Two conditions, both required
Completion alone does not earn it, and collection alone does not either.
Visible to the person who earned it
The number is on a screen rather than in a spreadsheet that arrives at the end of the month.

/app/salon/commissions

Salon intelligence

Two engines and an assistant. Each shows its limits.

No chat box bolted onto a database. Two deterministic engines run where a salon quietly loses money — clients who stop coming without saying so, and chair time that is technically booked but effectively wasted. Neither needs an AI provider or an API key, and neither writes an accounting entry, because this pack does not have one.

She leaves without saying goodbye

The engine learns each client's own visit rhythm and raises her only when her absence exceeds it. Someone who comes every four weeks and has been gone nine is a signal; someone who comes every twelve and has been gone nine is not.

Winning a new client costs several times what keeping one does, and leaving is silent — nothing in a diary announces that a regular has stopped appearing.

A client with fewer than the minimum number of visits gets no rhythm and no churn claim at all — she is classified as “no rhythm” and their number is declared. Two visits is one gap, and one gap is not a rhythm. The rhythm uses the median rather than the mean, so a single unusual absence — a trip, an illness — does not poison it.

The empty chair nobody can see

Measures real utilisation, finds the dead gaps, and proposes moving specific appointments to close them — without creating a conflict or breaking a speciality requirement.

A day that looks busy can hide two hours broken into fragments too short for the shortest service on the menu. That time appears on no screen, and is invisible precisely because the diary looks full.

Conflicts are detected against the running maximum end time, not just the neighbouring appointment: a 9:00–12:00 booking clashes with a 9:30 one and a 10:00 one, not only the nearest. And where not a single staffed minute was measured, utilisation is returned as null rather than zero — an absence of data is not an absence of work.

The assistant that answers at midnight

A salon number can take bookings and questions through an assistant, with a simulator that lets you rehearse the conversation before it ever faces a client.

Most booking requests arrive when nobody is at the desk. An unanswered message is a booking that goes to whoever replies first.

This one is not deterministic — unlike the two engines above it, it calls a language model, and its usage is metered under its own tool key. It drafts and answers; it does not confirm a booking without the rules the diary already enforces.

The two engines are deterministic and produce candidates for the owner to review — never an automatic reschedule. The assistant is model-backed and drafts replies; neither sends anything to a client on its own.

/app/salon/reports

Architecture

Simple on purpose, separated by construction.

The restraint is enforced in the source, not left to configuration.

Accounting is off by default
The pack is described in the product registry as operational, with accounting optional and disabled unless enabled. Both salon engines state the no-accounting constraint in their own headers.
Its own permission set
Salon resources are a separate namespace, so access to one product grants nothing in another.
Guarded twice
A server-side guard runs before any data loads, mirroring a database guard on every write. Hiding a button is not isolation — a direct call still lands.
Personal data separated
Identity fields sit in their own table under stricter permissions than the client record that references them.

Described from the product's own implementation. No compliance certification is claimed.

Part of the Web Mister AI family

One family. Not one shape.

Web Salon & Spa shares a platform with packs that are deeply accounting-driven — a restaurant closing its day into the ledger, a pharmacy dispensing against batches, an ERP core carrying all of them. It shares none of that weight, and that is the point: the same platform can be a full double-entry system or a diary with a shelf, depending on what the trade actually needs.

Web Salon & SpaAccounting (ERP)Restaurant & CaféClinicPharmacyHotel & ApartmentsSchool & KGTraining CentreFuel StationsCar RentalHR & Payroll

Products listed are packs present in the platform's registry. Web Salon & Spa is the product described on this page.

Get started

See it run one day.

The fastest way to judge this is to watch a single day: the diary at open, the chairs as they fill, and the commission each stylist has earned by close.

Explore the platform

Request a demo

The chair,and who is in it.