Jimenez Julien, founder of PolishBook

Why I built a color history tool instead of another calendar

PolishBook started in a nail studio in Queens where the owner kept a shoebox of index cards behind the desk. Each card had a client name, a phone number and a column of shade codes in three different handwritings. She could tell me, from memory, which of her regulars needed a rubber base and which one swam four mornings a week. What she could not do was hand that memory to the technician covering her Thursday, or find the exact taupe a client had worn the previous October without twenty minutes of hunting.

I had spent the previous years building small operational tools for service businesses, and I kept meeting the same shape of problem: the most valuable record in the business lives in one person's head, and the software on the counter only cares about the appointment slot. Booking systems are good at filling a chair. They are almost useless at remembering what happened while somebody sat in it. In a nail studio that gap is expensive, because the work is repeat work, the quality is judged by how long a set survives real life, and the client rarely knows the name of what she loved.

So I picked one narrow job and refused to widen it: keep the service and color history per client, record how long each set actually held, track what came out of the bottle, and use that history to time the return message. Everything else in PolishBook exists to make those four things quick enough that a busy technician will actually do them between clients.

The first eighteen months were mostly listening. I sat in on Saturdays in studios in Queens, Tempe, Providence and Chattanooga, watched close outs, and timed how long it took to log a set. My first version needed ninety seconds and nobody used it. The version that stuck needs two taps and finishes before the client has her coat on. That was the whole lesson: in this trade, an extra fifteen seconds per client is not a small ask, it is the difference between a tool that works and a tool that sits unopened.

I also learned things about the trade that no product plan predicted. Booth renters are running their own business inside somebody else's room, and their client history is their asset, not the salon's, so portability had to be a rule rather than a feature. Lift and chipping are almost never random, but you cannot see the pattern without three or four data points per client, which means the wear question has to be one tap or it never gets answered. And owners do not want a dashboard, they want to know which two technicians need a conversation this month and which four shades are paying for the shelf.

How I work with the studios that use it

I run onboarding calls myself for Salon and Salon Group accounts, and I do the first data import by hand when a studio sends a spreadsheet, a booking export or photographs of a card box. Every quarter I call a rotating group of ten studios and ask what they stopped using and why. When two studios describe the same friction in the same week, it goes to the top of the list ahead of anything I personally find interesting.

What I am accountable for is narrow and specific: the product stays up, the data stays yours and exportable, the price on this site is the price on the invoice, and a support email gets a human reply within one business day. If PolishBook ever stops being worth $19, $49 or $99 a month to you, cancelling takes two clicks and I would rather you did that than stayed on a plan you resent.