Saloria
Resources Demo
AI for hairdressersInformational-commercial intentGuide 06

Hair simulation in the salon: why it isn't needed

Anyone looking for a hair simulation wants one thing: to understand how it will turn out before deciding. A generated image is not the only way to give that, and not the most reliable one.

Target keywordhair simulation salon
Page goalEducate, qualify, lead to the demo

The real question is not seeing, it's understanding

The question a client brings into the salon is not "how will I look", it is "what happens if I do this". How many sessions, what it costs over time, what changes in her routine, what is not achievable on her base. An image answers the first question and leaves all the others open.

There is also a reliability problem. A preview works on the photograph: it changes tone and brightness while keeping the existing shape, volume and movement. It does not know the real base, how many lightening sessions the hair has been through, or how a porous shaft will react. Presented as a result it becomes the final benchmark, and the comparison almost always goes against real hair, which has light and depth a screen cannot reproduce.

This is why the Saloria method does not go through a look plan. The consultation closes on a written look plan: cut schema, colour direction, number of sessions, total cost and maintenance. It is a document the client rereads at home and the team executes at the chair — something an image cannot do.

Important note: a preview handed to the client becomes the benchmark for the result, and the comparison almost always goes against the real hair.
What a preview request is really about

The questions behind "how will it look?"

The chart is qualitative and shows how much each question actually weighs in the client's decision.

How many sessions it takes89
What it costs over time87
What isn't achievable on my base85
How it will look in a photo44

Image and written plan

The table compares the two possible answers to the same client question.

AspectVisual previewWritten look plan
What it communicates A guess at appearance Journey, cost and limits
Feasibility on the real base Not considered Stated explicitly
What is left afterwards An image to compare against A document to follow
Use at the chair None It is the execution brief
Operational method

How to answer in consultation

01

Start from the real base

Technical history and current condition.

02

State the stages

What is achieved at the first session and what after.

03

Quantify maintenance

It makes the decision assessable.

04

Hand over the written plan

The document that remains and that the team executes.

At the chair

  • Answer "how will it look" with stages, cost and maintenance.
  • State straight away what takes more than one session.
  • Hand over a document, not an image.

A client who receives a written plan goes home with something that holds up on a second reading: she knows what happens at the first session, what at the second, and what maintenance will cost. An image, looked at again a few days later, does the opposite — expectation grows and the context in which it was discussed is lost.

The document also has a practical effect at the chair: whoever executes reads what was agreed instead of reconstructing it. That is the difference between a consultation that reaches the service and one that stops at the moment the client said yes.

Where Saloria fits in

From discourse to guided consultation

Saloria integrates the look plan inside a wider flow: it doesn't show an image, it connects preview, face analysis and technical protocol. It doesn't replace management software, doesn't promise realtime AR and doesn't turn look plan into certainty. It brings method to the moment when client and professional decide the look together.

Book a demo

Frequently asked questions

Does Saloria do hair simulation?

No. The method closes on a written look plan: cut schema, colour direction, stages, cost and maintenance.

Why not use a visual preview?

Because it works on the photo without knowing the real base, and once handed over it becomes the benchmark for the result.

How do you answer "how will it look?"

With the stages of the journey, what is achievable on the current base and what it costs to maintain: the information the client actually decides on.