A beard trim with thirty minutes and a fade with thirty minutes
When the shop opened, somebody set up the booking app in an evening. Every service got thirty minutes because it was a round number. A beard trim now blocks thirty minutes it does not need, so the barber stands around. A skin fade with a beard and a hot towel gets the same thirty minutes and always overruns. A kids' cut on a wriggly five-year-old is anybody's guess.
The apprentice is booked at the same length as the senior barber, even though he takes noticeably longer on a fade. The senior barber is booked at the same length even though she could fit more in.
Lengths set once, never checked
- The app asks for a duration per service, and nobody revisits it after setup.
- Very few shops set different lengths per barber, although most apps allow it.
- Add-ons like a hot towel, eyebrow tidy or hair design are added to the booking but not always to the time.
- Nobody has ever measured how long things actually take, so there is nothing to compare against.
- Customers book the cheapest-sounding service and turn up wanting more.
The underlying issue is that the diary is built on numbers nobody has tested. Every other scheduling problem in the shop sits on top of that.
Wasted gaps and constant overruns
Service lengths that are too long leave gaps too short to sell. Lengths that are too short cause overruns that ripple through the afternoon. Both are happening at once in most shops, which is why the day can feel busy and still have dead time in it. Apprentices are set up to fail when booked at a senior's pace, and seniors are held back when booked at an apprentice's.
Measuring real times and setting them properly
- We pull a few months of bookings and check-in or payment times from your booking app and till, through their APIs or exports. The time between check-in and payment is a usable proxy for time in the chair.
- Where that data is patchy, barbers tap start and finish on the tablet for a few weeks. It takes a second per customer.
- We work out typical times per service per barber, and how much they vary. A service that varies wildly is a sign it covers several different jobs.
- We show you a simple table of booked length against real length for every combination, and flag the biggest differences.
- Together we decide new lengths, including splitting vague services into clearer ones, and set them per barber in your booking app.
- A monthly check reruns the numbers, so when an apprentice speeds up, their lengths follow.
| Service | Booked for everyone | What we look at |
|---|---|---|
| Beard trim | Same slot as a cut | Real time per barber, often shorter |
| Skin fade | Same slot as a trim | Real time, often longer |
| Fade with beard and hot towel | Service plus add-ons, no extra time | Combined time for the add-ons |
| Kids' cut | Standard slot | Varies by age, may need two services |
| Apprentice fade | Senior's length | Their own real time |
This is analysis and configuration. Sometimes that is all you need, and if so we will say so rather than build anything else.
A diary that matches what happens in the chair
Bookings fit together because they are based on how long things actually take in your shop, not a round number from setup day. Barbers get fewer awkward ten-minute gaps and fewer overruns. Apprentices are booked at a pace they can manage, and that pace updates as they improve.
Signs your service lengths are wrong
- Most services in your app have the same length.
- Barbers regularly have short gaps nobody can book.
- The same services always overrun.
- Apprentices and seniors are booked at the same pace.
- Nobody can remember when the lengths were last changed.