A premium barbershop with online booking and its own CRM: schedule, clients, cash and barber payouts in one panel.
The case at a glance
14
sections in one panel, from the schedule to the payouts
- The problem
- Bring a barbershop's bookings, clients, cash and payouts into one system, without an external CRM.
- What it does today
- A 6-step booking and its own panel with schedule, clients, cash, stock and payouts.
- Where a person decides
- A person takes payment at the counter: cash, card, transfer or Mercado Pago.
Try it
- Try the 6-step booking Demo(opens another site in a new tab)
- Open the CRM Demo(opens another site in a new tab)
Use the demo access button; it includes the assistant with its knowledge base.
How I solved it

Bookings, payments and clients were handled through loose messages: schedule, cash and clients lived apart.
Gallery · live site captures
The same site, on every screen.



For those who want the detail
How it's built
System architecture
Under the hood.
The system's real parts and how they talk: pick a path or open a component.
The whole system
12 components, 14 connections and 3 guided paths.
Open a component to see what it receives, where it sends and which paths include it.
Components
- Clients and team — Web and mobile
- 6-step booking — /reservar · wizard (Next.js 16)
- Admin panel — 14 sections
- Barber portal — /barbero/mi-agenda
- Roles and permissions — has_permission() · 4 roles
- Row Level Security — 26 tables with RLS
- book_appointment — No double booking
- close_cash_day — POS and cash close
- close_barber_settlement — Payouts
- Supabase Postgres — 26 tables · history
- Reactivation — send-reminders
- AI assistant — Gemini → OpenAI → rules
Connections
- Clients and team → 6-step booking: HTTPS
- Clients and team → Admin panel
- 6-step booking → Roles and permissions: Session
- Admin panel → Row Level Security: Permissions
- Barber portal → Row Level Security
- Roles and permissions → Row Level Security
- Roles and permissions → book_appointment: RPC
- Row Level Security → close_cash_day
- Row Level Security → close_barber_settlement
- book_appointment → Supabase Postgres: Row lock
- close_cash_day → Supabase Postgres
- close_barber_settlement → Supabase Postgres
- Supabase Postgres → AI assistant
- Supabase Postgres → Reactivation: Inactive
Guided paths
- Booking without double booking
- Clients book in six steps and the book_appointment function checks the slot with a row lock before confirming it.
- Cash and payouts
- The counter charges, closes the day's cash and settles what each barber is owed, all with role-based permissions.
- Clients and reactivation
- Each client record keeps their history; an edge function flags inactive clients and the team reaches out on WhatsApp.
Read the case as text
01 · The challenge
Bring a barbershop's bookings, clients, cash and payouts into one system, without depending on an external CRM.
02 · Constraints
- Quick decisions on mobile.
- Four roles with different permissions: client, barber, manager and admin.
03 · Decisions
- 01Six-step booking, one decision per step.
- 02Its own CRM on Supabase instead of an external one.
- 03Business rules live in the database: no double booking, cash close and barber payouts.
04 · Outcome
Booking becomes self-service and the business runs from its own panel: schedule, clients, cash, stock and payouts.






