Case Study
A barbershop with 317 reviews and no website
King’s Cut had the reputation and nowhere to send anyone. What we built, and why it has no build step at all.
Updated 5 min read
King’s Cut in Houston had done the hard part. A 5.0-star rating across 317 Google reviews is not something you can buy or rush. What they did not have was anywhere to send a person who heard the name and searched for it.
What was invisible
Eleven services and their prices were on a printed board behind the chair. The licence was framed on the wall. All of it was real, verifiable and completely unavailable to anyone not already standing in the shop. Someone searching for a barber in Houston found a Google listing and stopped there.
One page, no build step
The whole site is one HTML file, one stylesheet and a small script. No framework, no bundler, no dependencies. That is not minimalism for its own sake: the performance budget that mattered was a phone on shop wifi, held by someone in a barber chair deciding whether to book.
Nothing on the page was invented. Every price, every opening hour, every photo and every review quote came off their own Google Business Profile or the price board in their own listing photos, and the repository records where each one came from.
The booking form degrades to a phone call
A barbershop that loses a form submission has lost a customer. So the form is progressive: it posts if it can, and falls back to tap-to-call if it cannot. A phone number cannot fail to submit.
Being findable was the whole job
Full LocalBusiness structured data, a sitemap and a robots file, because the entire point was to rank on their own name instead of renting that space from a directory. The shop now has a page that says what it charges, when it opens and what the work looks like.