Build
Pietro's Barbershop
The first shop trading on Chairhouse, a booking and loyalty product built to serve many barbershops rather than one. Customers book, come back, and pay the shop directly.
- Client
- Chairhouse
- Stack
- Next.js, Supabase, Stripe Connect, SMS
- Timeline
- First tenant live five weeks from an empty repository
A booking page for one barbershop is a weekend's work. One system serving a hundred shops, where no shop can ever see another's customers or takings, is a different problem, and it is the one worth solving because it is the one that scales. Each shop's data is separated in the database itself rather than by application code remembering to filter, because the day someone forgets is the day every shop sees every other shop. Money settles to each shop directly rather than passing through us, so nobody is waiting on somebody else's payout run to be paid for last week's haircuts.
What Was Delivered
The four areas this practice works in, and what this engagement covered in each. Three of the four were in scope here, and the rest are listed so the shape of the job is visible rather than implied.
- Offer and pricingNot in scope
- What the business sells, who to, at what price, and whether it is worth doing at all.
- Systems and software
- A booking and loyalty product built to serve many barbershops rather than one, with each shop's data separated in the database itself rather than by application code remembering to filter.
- Customers and demand
- Booking, reminders by text message and loyalty, so a first visit has a route back rather than depending on the customer remembering.
- Structure and compliance
- Money settles to each shop directly rather than passing through us, so nobody waits on somebody else's payout run, and tenant isolation sits in the database because the day someone forgets to filter is the day every shop sees every other shop.