A busy salon asked for a nicer website. As I dug in, it became clear a prettier site was not their problem. Their problem was the phone. The front desk spent half the day taking booking calls, missed calls turned into missed appointments, and customers who wanted to book after hours had no way to do it.
This was the first time I realized a client did not need a website. They needed a small product.
Reframing the brief
A website is something you read. A product is something you use to get a job done. The salon’s job to be done was simple: let a customer see open slots and book one without calling. Everything else on the site was secondary to that.
What I built
I kept it deliberately minimal, because a small tool that works beats an ambitious one that ships late.
- A booking page showing real availability, connected to the staff’s existing calendar
- A form that captured only what a booking needed: service, time, name, and a phone number
- An automatic confirmation and a reminder message to cut no-shows
- A layout that assumed most people would book from their phone, in the evening
The outcome
The phones quieted down almost immediately, and a chunk of bookings started arriving outside business hours, appointments the salon simply could not have captured before. No-shows dropped once reminders went out automatically. The front desk got time back, and the owner got revenue that used to slip away after closing.
What I recommend
When a client asks for a website, ask what job they are actually trying to get done. Sometimes the answer is content and design. Often the higher-value answer is a small, focused tool that removes a repetitive task. Building that booking widget taught me to look past the brief to the workflow underneath it, and it is where my interest in web products really began.