Nia's Crown Salon: from a marketplace profile to a booking system she owns

Renting your own clients

A booking marketplace is a great way to get your first clients and a terrible place to keep them. Every appointment, every phone number, every no-show lives inside a platform that can change its fees, its ranking, or its rules whenever it wants. A stylist who books through a marketplace is building someone else's asset.

Nia Christian had eight years behind the chair and a loyal client base in Waldorf, Maryland. Her online presence was a StyleSeat profile. That meant no home for her portfolio, no page of her own for Google to rank, and no client list she could pick up and take anywhere.

Ship the front door first, then build the engine

I did not start with the booking system. I started with a site that could go live in days.

The Goddess template, one of my six service-business designs, gave Nia a complete site: home, services with real prices, a portfolio of her actual work, an about page with her portrait, location, and FAQ. For the first few weeks the booking button simply pointed at her StyleSeat page. That was the bridge. Her clients had a real destination to send friends to while the engine was being built behind it.

That order matters. A business owner should never have to wait on the ambitious version of a project to get the useful version.

A booking system she owns

Native booking replaced the StyleSeat link in late July 2026. The flow is four screens: pick a style, pick a day from the next 30 days of real availability, pick a time, enter your details. Stripe Checkout then takes a $25 deposit, and the appointment confirms only when the deposit clears. Her deposit policy went from a line in her bio to a rule enforced by code.

A few things were non-negotiable for a one-chair salon:

• One chair means one calendar. Any appointment blocks every service, and a long style cannot start in a slot it will not finish before closing.
• Times are salon-local and daylight-saving correct, so a booking made in July still lands at the right hour in November.
• Two people cannot take the same slot, even if they both hit confirm in the same second.

The part that compounds: a client list

Every booking creates or updates a client record, matched by email and then by phone. Nia's admin shows each client's visit count, total spent, no-show count, hair notes, tags, and full appointment history. Phone, DM, and walk-in clients get added through a manual booking so the list stays complete.

This is the asset a marketplace never hands over. It is the list she can reach when a Tuesday opens up, and it is hers whether or not any platform exists next year.

Built for a phone, run without a developer

Nia runs the business from her phone, so the admin was designed for a phone. A passcode instead of a username and password. A top bar instead of a sidebar. One-tap status changes: confirm, complete with the final price, no-show, cancel. Weekly hours plus vacation blackouts. Per-service duration, buffer, and deposit settings. A revenue view built from completed services and deposits.

Email runs itself through Resend. A confirmation goes to the client and to Nia on every booking, the client gets a reminder 24 hours out, and Nia gets a morning email with the day's schedule. Every message is logged so nothing sends twice.

What this became

The booking and CRM layer was extracted into a reusable template the day it shipped, so the next salon, barbershop, or studio gets the same engine as an install rather than a rebuild. Nia's site is the reference deployment. Improvements land in the template first and flow back to her.

The timeline, for anyone wondering how long this takes:

• March 2026. Template site stood up.
• June to July 2026. Real services, prices, portfolio, and portrait. StyleSeat bridge live.
• July 27, 2026. Native booking and CRM live on niascrownbraiding.com.
• September 17, 2026. Stripe deposits live.

The site and the booking engine were both built in Claude Code, the same workflow I set up for clients who want to own their systems instead of renting them.