BeautyOS
What was scheduled is not what happened.
BeautyOS captures the visit — what actually happened on the floor, what your team needs now, and what should be remembered for next time.
Signature
CAPTURE THE VISIT
The calendar knows the appointment.
BeautyOS knows the visit.
The appointment stays the plan. The visit accumulates what actually happened — arrival, service, memory, checkout, and what comes next.
Illustrative capture for VISIT 024, Client S.M.. Appointment plan: Balayage, 10:00–13:00, 180 minutes, Provider A.. Visit actuals: arrived 10:07, started 10:16, providers Provider A. + Assistant M., services Balayage + Toner, duration 204 minutes. ServiceRecord captures formula and products. Checkout observed, visit closed 13:24. Rebook window late June or early July based on seven week color cadence.
- Plan: Visit not opened
- Arrive: Arrived 10:07 · EXPECTED → ARRIVED
- Wait: WAITING · Assigned Provider A.
- Start: IN SERVICE 10:16
- Diverge: +14 min elapsed · Balayage + Toner added · Planned 180 min · actual tracking 194 min
- Handoff: Toner: Assistant M. · Handoff note recorded
- Capture: ServiceRecord captured · Formula · products · actual duration
- Complete: SERVICE COMPLETE · Documentation attached to visit
- Checkout: CHECKOUT PENDING · Payment observed · Visit closed 13:24
- Continue: Color cadence ~7 weeks · Operational rebook window: late June / early July
Plan · Appointment
VISIT 024
Balayage
- Client
- Client S.M.
- Window
- 10:00–13:00
- Provider
- Provider A.
- Duration
- 180 min
Planned intent stays visible. It does not become the visit.
Actual · Visit
Arrive
ARRIVED
- Arrived 10:07
- EXPECTED → ARRIVED
Wait
WAITING
- WAITING
- Assigned Provider A.
Start
IN SERVICE
- IN SERVICE 10:16
Diverge
IN SERVICE
- +14 min elapsed
- Balayage + Toner added
- Planned 180 min · actual tracking 194 min
The appointment still says 180 minutes.
The visit knows 204.
Handoff
IN SERVICE
- Toner: Assistant M.
- Handoff note recorded
Capture
SERVICE COMPLETE
- ServiceRecord captured
- Formula · products · actual duration
ServiceRecord — VISIT 024
- Formula
- 7/71 · 20vol · mids→ends
- Products
- Lightener, toner 9/03
- Duration
- 204 min (planned 180)
- Provider
- A. · toner by M.
- Preference
- Sensitive scalp — low heat
- Handoff
- Toner application delegated
Complete
SERVICE COMPLETE
- SERVICE COMPLETE
- Documentation attached to visit
Checkout
CLOSED
- CHECKOUT PENDING
- Payment observed
- Visit closed 13:24
Continue
CLOSED
- Color cadence ~7 weeks
- Operational rebook window: late June / early July
ServiceRecord — VISIT 024
- Formula
- 7/71 · 20vol · mids→ends
- Products
- Lightener, toner 9/03
- Duration
- 204 min (planned 180)
- Provider
- A. · toner by M.
- Preference
- Sensitive scalp — low heat
- Handoff
- Toner application delegated
The appointment still says 180 minutes.
The visit knows 204.
Illustrative product experience
Attend
Service Day
A live visit-state board — who is expected, who is waiting, what needs attention — derived from visit truth, not a week calendar.
Live visit state
Tue 14 May
EXPECTED
VISIT 025 · Client K.R.
14:00
IN SERVICE
VISIT 023 · Client L.P.
Provider C.
WAITING
VISIT 024 · Client S.M.
Provider A.
Attention
CHECKOUT
VISIT 021 · Client N.T.
Checkout pending
Illustrative product experience
Attention signal
WAITING TOO LONG
VISIT 024 · Client S.M.
- Arrival
- 10:07
- Now
- 10:21
- Visit not started
- —
Deterministic signal from visit state — not a calendar reminder.
Remember
The provider changed. The context didn't.
Service memory continues across visits, providers, and handoffs — so the business keeps operational context when someone else serves the client.
VISIT 024
Provider A.
- Formula captured
- Toner by Assistant M.
- Actual duration 204 min
- Relevant service context retained
NEXT VISIT
Provider B.
- Prior ServiceRecord available as operational context
Illustrative product experience
System
Plan, operate, remember, attend, continue.
BeautyOS separates planned intent from operational truth — then projects what the floor needs now and what the next visit should inherit.
01 · Plan
Appointment
What you scheduled
02 · Operate
Visit
What happened on the floor
03 · Remember
ServiceRecord
What the business keeps
04 · Attend
Service Day
What needs attention now
05 · Continue
Next Visit
What tomorrow's provider can use
Design partners
Built with salons, not assumed for them.
BeautyOS is being developed with a limited group of design partners focused on real service-floor complexity — employee-based salons and studios where visit truth and service memory should belong to the business.
Capture visit truth on your service floor.
BeautyOS is being developed with design partners who operate employee-based salons and studios — where visit truth and service memory should belong to the business.