CG Common Ground | A five-star barbershop and barber school (Southwest, 2026)
What we did and what it producedActive

The work, decision by decision

The build, in the order it went

  1. Take the shop's number off his cell. Known: every call rang his pocket. The question was where a call should land when the person who runs the shop is the person cutting hair, and the answer was a line that belongs to the shop. That was the first thing built, because nothing on the site mattered if the phone kept pulling him off the chair.
  2. Quote the price of everything. Known: the old page said nothing about what the shop did or charged. I asked what a customer needs to see before they will book without talking to anyone, and the answer was the service, the price and the time. The site quotes pricing on the nine services the shop offers, each one, plainly. A customer who can see the price does not need to call to ask it.
  3. Book straight into Square. Known: the calendar already lived in Square. The question was whether to integrate or replace, and integrating was the whole decision. A customer picks a service and a time on the site and the booking lands in the shop's calendar, the same one the barbers already work from. Nobody re-keys anything.
  4. Put the brand on top. Known: the shop's reputation was better than its face. Our brand team did the brand work, and it went on after the systems worked, which is the order I wanted.
  5. Catch the drift. Known: we run the site end to end, so we see it every week. That is how we caught a five-month stretch where what was live in the code and what customers actually saw on several surfaces had come apart. A gap like that looks small from the inside and quietly costs a shop bookings, because the customer sees the stale version. We fixed it and we check for it.

Then a feasibility case for the owner's barber school, built on the state's own records.

What it produced

A shop a customer can book without calling, on the calendar the shop already ran. A phone that reaches the business. A brand that looks like the reputation. A feasibility case for the barber school, built on the state's own records, with its deal-killers named and the one that binds first said out loud.

I do not put a return on the shop work here; the shop's revenue is his, and the before-number never existed, as he told me himself. What changed is plain. The way into the shop used to run through his pocket. It now runs through a calendar that does not care whether he is holding clippers.

What we kept, replaced and installed

We kept Square. It held the services, the prices and the schedule, the barbers already worked from it, and a booking product that made them work from two calendars would have been a step backward with a nicer face. Building into it is why the site could go live without retraining anyone.

We replaced the routing of the shop's number to his cell. He had put that in himself, because that is how a shop starts: the person who cuts is the person who answers, and one phone is simpler than two. The fault in the logic was the assumption underneath it, that the person answering the phone would be free to answer it. In a barbershop he never is; the phone competes with the paying customer in front of him and loses, every time, as it should. So the design guaranteed that the busier the shop got, the more calls it dropped. It had to change when it did because the reputation now brought more callers than one man could answer, and because the tool that made the call unnecessary was already in the back office, unused by the one page customers could find.

We installed the site with booking built in, the phone line of the shop's own, and the brand on top, and we run the site end to end rather than handing it over, which is how the drift got caught.

What it cost to hold the line, and what I would watch

Running the site end to end costs us attention every week, and that is the price of catching drift instead of hearing about it from a customer. Building into Square instead of a booking product we control cost us some flexibility, and it was worth it, because the shop never had to learn a new tool.

What I would watch, on any service business that lives on the phone, and on any school built around a person:

The result, in short

The shop now books itself on the calendar it already ran, with a brand on top of it and a phone line of its own instead of the owner's cell. The school feasibility case survived its own red team and named the constraint that binds first.

A slice of the project list

A few related projects.