RotaOwner1 / 5
Staff Management
The floor behind the diary: who is working, who is signed off for what, and what each chair actually earns. Kept in a system rather than in a WhatsApp group.
- From
- $699
- Function
- 22
- User types
- 2
- Platform
- iOS & Android
React Native · TypeScript · PostgreSQL · Expo
Inside the app
What it does out of the box
22 connected functions on one schema across 2 user types. Everything below is in the template before a line of customisation.
Rota
Built by week and published once, with unfilled hours visible before Saturday arrives rather than on the morning.
Skills
Who is signed off for what, and it drives the booking app. A skills matrix that does not stop a booking is decoration.
Holiday
Requests with cover shown at the moment of deciding, so an approval is made with the rota in view rather than from memory.
Commission
Calculated from takings on your rules. Commission worked out by hand at month end is the single most common source of salon arguments.
Chair economics
What a chair earns against what it costs. The number that decides whether to hire, and most salons cannot produce it.
Privacy between staff
A stylist sees their own numbers and nobody else’s. Enforced, not merely hidden in the interface.
User types
Two apps, one floor.
The owner sees the salon and a stylist sees themselves. That boundary matters more here than almost anywhere else, because the data includes what people earn.
Owner, the salon
Builds the rota, holds the skills matrix, approves holiday and sees what each chair earns against what it costs.
- Rota by week, published once
- Skills matrix that drives booking
- Holiday requests with cover visible
- Commission per stylist, calculated not argued
- Chair revenue against chair cost
Staff, the team
Sees their own rota, their own numbers and asks for time off, without seeing the whole salon’s finances.
- Your shifts, and swaps you agreed
- Your own takings and commission
- Request holiday and see the answer
- Your skills and what is being signed off
- No sight of other people’s pay
The limits
What this is not.
The same list we give for every app in the catalogue, because the fastest way to a bad project is a promise made in a meeting that nobody wrote down.
It is not payroll
It calculates commission and hours. Paying people, tax and statutory deductions run through your payroll provider, Payroll in the business catalogue is the internal counterpart.
It is not employment advice
Contracts, working time rules and holiday entitlement where you trade remain yours to satisfy. We build to the rules you confirm apply.
We do not process payments
Nothing here moves money.
It will not settle a commission dispute for you
It will show the numbers and how they were reached, which is usually enough, but the rules are yours to set and defend.
Questions
Questions, answered plainly.
If yours is not here, ask it on the call rather than guessing from a pricing page.
Does it do payroll?
No. It calculates commission and hours and hands them to your payroll provider. Building payroll properly means statutory deductions in every jurisdiction you operate in, and that is not a thing to bolt onto a salon app.
Can a stylist see what other stylists earn?
No, and it is enforced server-side rather than hidden in the interface. It is the single most sensitive thing in the system.
Does the skills matrix affect booking?
Yes, if you run Salon Appointment Booking alongside it. A stylist not signed off for colour cannot be booked for colour. A matrix that does not enforce anything is a spreadsheet.
How does holiday approval work?
A request shows the cover position for those dates at the moment you decide, so approval is not made from memory and then regretted on the Friday.
Do I get the source code?
Yes. Both apps, API, schema, migrations and deployment configuration transfer on delivery.
Related
More on-demand builds.
Click through it before you spend anything.
The preview is the real app with sample data. Open it and judge the software rather than the pitch.