Fade & Co. needed to feel like a neighborhood barbershop, not a SaaS dashboard. SupportAI and LeadFlow both live in the same dark-zinc-and-indigo world; giving Fade & Co. the same palette would have made three projects feel like one design with three names. So: cream storefront (Instrument Serif, warm ivory base, brass accent), matte black and gold for the dark interior sections (About, Reviews), and the admin on the same dark palette — so the shop and its back office feel like one building.
The typography pairing is Instrument Serif for display — headlines, section titles — and Inter for body, with Geist Mono for every number, price, time, and reference code. The serif carries the heritage; the mono carries the precision.
Structurally, three phases added an announcement bar with a session dismiss, a trust strip, real photography for the hero and the portraits, the printed-menu services layout, the dark About and Reviews chapters, a booking flow with slide transitions and a success screen, and a mobile sticky CTA. The whole build was three phases over eight days; the details are what make it feel like a real shop.
A booking flow has three states users actually care about: choosing a slot, seeing it confirmed, and not having to think about it again. Everything else is intermediate. The wizard has four steps — service, barber, slot, confirm — the steps slide horizontally between each other, and the progress indicator shows completed, current, and upcoming states in brass.
The success screen is a small thing that matters. A reference code in mono with a copy button, the full booking summary, and an .ics download so the appointment lands in the user's calendar without retyping the details. Building the calendar file surfaced a real bug: the timestamps were emitted without the Z designator, which makes an RFC 5545 date-time a floating local time. A 12:00 booking in Kuala Lumpur opened at 04:00. This is what separates a demo from a product — the small courtesies.
The concurrency test fires two POST /api/bookings calls in the same tick via Promise.all, then asserts exactly one 201 and one 409 and that the database contains exactly one row for the slot. It passes against the local server and against the deployed URL. The database doesn't care where the request came from — the constraint is the constraint.