Bond Street Barbery

Outcome

The problem

What the client was up against

Bond Street Barbery was losing bookings to ambiguity rather than to competitors. A barbershop's two hardest questions are "what will this cost me" and "who is actually cutting my hair". Most shop sites answer neither. They open with a gallery, bury a phone number, and leave the price list to a chalkboard nobody can see from the street. The customer's alternative is to walk in and ask — which is exactly the friction that sends them to whoever answered the question online first. The brief was not "make us a website". It was: stop people bouncing before they book.

The approach

How we decided to build it

We decided to publish the full price list on the homepage, above the fold, including the awkward numbers. That was the contentious call. The conventional advice is to hide pricing so you can have the conversation in person, and the owner was understandably nervous about leading with $150 for the full hour. We argued the opposite: a published price is a filter, not a deterrent. The customer who leaves because of the number was never going to book, and the one who stays has already accepted it — which makes the chair time more profitable, not less. We also published the cash discount honestly ($10 less in cash, shown against every service) rather than treating it as something you discover at the counter, and wrote "from" prices with an explicit promise that the barber tells you the final number before they start, not after. The rest of the build followed from that decision: if the site's job is to answer questions, then booking has to be the shortest path on the page, and everything decorative has to earn its place.

Booking a person, not a shop

Each barber has their own profile and their own availability. The booking flow starts from the barber, not from a generic service dropdown, because repeat customers do not want "a haircut" — they want the person who already knows their head. That is a small modelling decision with a large retention effect. It also gave the shop somewhere to put the thing that actually differentiates a good barber from a cheap haircut: the last ten minutes of the cut, the blend, and knowing when to stop.

Structured data that describes a barbershop

The site publishes a complete schema.org graph for a local service business: BarberShop with geo-coordinates and opening hours, an OfferCatalog with a PriceSpecification per service, ReserveAction for the booking entry point, plus FAQPage and Review nodes. This is the part most small-business sites skip, and it is why they never appear as anything richer than a blue link. Publishing the price list as real structured data — not just as text in a div — is what lets a search engine or an assistant answer "how much is a skin fade in Surrey Hills" with this shop's actual number.

Photography without the penalty

The site carries full-bleed photography of the shop and the work, which is non-negotiable for a barbershop and is also the single biggest threat to load time. We treated that as an engineering constraint rather than a reason to use fewer pictures. Images are served in modern formats at the size they are actually displayed, the hero is prioritised and everything below it defers. On a throttled mobile connection the main image lands in just over three seconds and the page responds to touch well before a visitor has finished reading the first line.