Label111
FindBrows and BrowBars: we built them, we still run them
Not client work: how we built a beauty marketplace with bookings: and still run it, on one codebase for FindBrows and BrowBars.nl.
Client: Label111
FindBrows and BrowBars are not client work. We came up with them, built them, and we still run them. That means we pay the bill when a booking flow does not convert: and this case tells you what we learned from that.
Problem
A salon typically juggles separate tools: a calendar app, Instagram, WhatsApp for appointments, a till and a spreadsheet. None of them talk to each other. A no-show costs money and nobody can see where it came from. On the other side is the customer, who simply wants to know who is nearby, what it costs and whether there is a slot on Thursday evening. No standalone calendar app answers that question.
Approach
One codebase for FindBrows and BrowBars.nl, booking without a forced account, city-plus-treatment landing pages, and a salon dashboard that makes sense in minutes.
What we built
What this proves for you Marketplaces are hard because you serve two sides who want opposite things. The supplier wants as little admin as possible, the customer wants as few steps as possible, and those two collide precisely at booking and payment. We did not solve that once for a client and walk away. We still run into it every day. If you are considering a marketplace or booking platform, that is the difference between someone who has built one and someone who knows what breaks later. Technology Laravel, Filament and React. Multi-tenant and multi-domain: FindBrows.com and BrowBars.nl share the same foundation, with language and domain set per market.
Technology: laravel, filament, react
Sector: Salons