Skip to main content

Template

Hair salon software specification: the filled-in template

Appointments, client records, services, loyalty: the one page that fully describes a salon application. Copy it, put in your actual services, and it becomes your specification — or directly your Blueprint Maker description.

This template applies the four-block method — THE THINGS, THE LINKS, THE STATES, THE NUMBERS — to the hair salon. It's filled in for a three-chair salon: the example shows how to describe the daily routine, from appointment to technical record, without ever describing a screen.

The trade's treasure is the client record: the colour formula that worked, the processing time, the scalp sensitivity. That's what the appointment book never keeps — and what the THINGS block structures first.

Filled with your vocabulary, this text briefs a developer — or is submitted as-is to Blueprint Maker, which turns it into an application plan you validate, then a generated application: database, screens, dashboard and demo data.

The template to copy

My business: hair salon, three chairs,
two stylists plus me, strong colour activity.

THINGS tracked:
- Clients (name, phone, first visit date)
- Technical records (client, date, colour formula, processing time,
  notes — sensitivity, preferences)
- Services (name, duration, price — cut, colour, highlights, blow-dry, treatment)
- Appointments (date, time, client, services, stylist)
- Payments (appointment, amount, payment method)

LINKS:
- An appointment concerns a client and a stylist.
- An appointment carries one or more services.
- A technical record attaches to a client.
- A payment settles an appointment.

STATES of an appointment: booked, confirmed, honoured, no-show, cancelled.

NUMBERS to see every morning:
- Today's appointments per stylist
- No-shows this month
- Revenue per service this month
- Clients with no visit for over 3 months

Adapting this template to your salon

  • The technical record: it's what sets you apart from a diary. Note YOUR real fields (formula numbers, developer, timings) — the next visit starts by rereading the last one.
  • No-shows: distinguishing "no-show" from "cancelled" makes the phenomenon measurable — and the list of repeat offenders becomes factual, not felt.
  • The "no visit for 3 months" number is your win-back: export the list and offer a slot — zero-cost loyalty work.
  • Product sales: if you sell shampoos and treatments, add a "Product" entity with light stock — otherwise leave it out, a simple model that lives beats a complete one that sleeps.
  • This register is your internal tool: online client self-booking is another project — the code being exportable, a developer can add it if the need firms up.

The matching use case

The hair salon, without the generic booking calendar

Salon described? See the application it produces