Clipbook
From "I hate this system" to "Can we show it to other salons?"
- Role
- Senior product designer
- Timeline
- 9 months
- Team
- 5 engineers, 2 PMs, me
- Platform
- Web and tablet

A system people put up with
Clipbook runs appointments, stock and payments for independent salons. When I joined, the people who used it every day described it as something they put up with. Owners kept paper diaries as a backup. Stylists built private spreadsheets for the things the software could not do.
That is a strong signal. When a product forces people to build their own workarounds, the design has already failed, however polished the screens look.
Learning how a salon actually works
I spent my first six weeks in salons, in Leeds, Sheffield and York, watching a Saturday from the front desk. A booking is rarely one thing. It is a colour consultation, a patch test two days before, a double slot because someone's hair is long, and a late change because a child is ill.
I mapped those moments and noticed that stylists have very firm opinions about scheduling screens, which I respect. They know in one glance whether a diary looks right.

Rebuilding from the diary outwards
We rebuilt the product starting with the diary, because it is the screen everything else hangs from. The new diary shows a whole team on one screen, lets you drag a booking and see immediately what it collides with, and treats multi step appointments as one block with visible gaps.
Stock, payments and client notes were rebuilt to match how salons talk about them, not how the old database stored them. We shipped in slices, one salon at a time, so each change could be tested with the people who would use it.
The result
Within a quarter, the salons in our pilot had stopped keeping paper backups. Owners started asking whether they could show the product to the salon down the road, which is the best review a design team can get. Churn in the pilot group fell to nearly nothing.

