Product design · full-stack build
An operating system for barbershops — booking, point of sale, queue, commissions, CRM, payroll, inventory, storefront and analytics in one product.
01 / 15 01 — The challenge
A barbershop owner runs the business across a booking app, a payment app, a commissions spreadsheet and a notebook for stock. Nothing talks to anything else, so the same information is entered three times and the owner still can't answer the simplest question: which barber actually made money this week? Meanwhile walk-ins are managed by shouting across the room, and no-shows cost a chair for an hour.
02 / 15 02 — The objective
Replace the patchwork with one system a shop can run its whole day on — bookings, walk-ins, payments, commissions and stock — while making every shop easier to find and easier to book online than the one down the street.
03 / 15 03 — The approach
04 / 15 04 — The solution · 01
The dashboard opens on what's happening right now — today's bookings, the live queue, who's on shift and what the shop has taken — so the owner starts from a single source of truth instead of four apps.
05 / 15 04 — The solution · 02
Customers book themselves from a public storefront that shows genuine availability, and deposits reduce the no-shows that used to cost an empty chair.
06 / 15 04 — The solution · 03
Commissions and per-barber performance are calculated from the work that actually happened, so payday stops being a spreadsheet argument.
07 / 15 05 — Key decision 01
Most competitors model appointments only. Real shops live on walk-ins, so the queue sits beside the calendar rather than behind it — that single difference decides whether the software gets used after week one.
08 / 15 05 — Key decision 02
Fade type, guard numbers and reference photos are stored per client, so a repeat customer gets the same cut from a different barber. Retention is the metric that matters in this business, and consistency is what drives it.
09 / 15 05 — Key decision 03
Each shop's public page carries its own structure, portfolio and reviews so it can rank on its own — the product markets the customer's business, not just ours.
10 / 15 05 — Key decision 04
Owners ask questions in plain language instead of hunting through reports. The value isn't the AI; it's that a busy owner gets an answer between two clients.
11 / 15 06 — The outcome
Clippr OS is live, in use by real shops, with public storefronts and paid subscription tiers running on production infrastructure. It is the clearest demonstration of what BLNKD can build: not a marketing site, but a working multi-tenant product with payments, scheduling and reporting.
12 / 15 07 — Proof
13 / 15 08 — Capabilities
Built with Next.js · Supabase · Vercel · GCash payments · Multi-tenant data model
In one line
A shop that ran on four disconnected tools and a notebook now runs on one system — and every shop on it is easier to find and easier to book than it was before.
End of the story
Want one like it? Tell us what it has to do.
(Next step)
Kendrick Samonte — Founder, BLNKD Studio
