The work
It answers the salon's customers while the salon is cutting hair.
Built for Studio Rooms in Batley. Live since August 2026, and still running this morning.
A salon's enquiries do not arrive during working hours.
They arrive at eleven at night, on a Sunday, while the chair is occupied. Most of them are the same handful of questions about price, availability and what a treatment involves. Every one of them still costs somebody the time it takes to stop and answer.
What it does, and what it refuses to do
The rules that matter run in code, before the model is asked.
A prompt can be talked around. A rule cannot. Every one of these is enforced before the model gets a look at the message.
Measured, not estimated
Counted from the live message log on the salon's own server.
Read from the production database on 15 October 2026, counted rather than projected.
What changed
Before August, the booking page was quiet.
One completed booking in the four months to July. Forty five in the ten weeks since, worth £1,675.
Completed bookings through Studio Rooms' own online booking page, read from their account on 17 October 2026. The assistant went live on 13 August. October is a part month.
Reporting that maintains itself.
Nobody rebuilds it on a Monday, because the systems that already hold the numbers write it overnight.
Built to show what the reporting looks like, on figures for a company that does not exist. Showing you a real client's numbers is not mine to do.
Start with the audit.
A structured look at where your week actually goes, and which of it is worth handing over. You leave knowing what is worth automating, what is not, and roughly what each one gives back.