A small hair salon in Flemington came to me with a scheduling problem that's more common than it sounds: too many moving parts for a shared calendar, not enough volume to justify what the big booking platforms charge every month.
The gap between a calendar and a platform
The salon has more than one stylist working at a time, and each one needed her own view of her own clients — not one calendar everybody was squinting at and hoping nobody double-booked. A shared Google Calendar could sort of do this with enough workarounds, but "sort of" is exactly the kind of thing that turns into a mistake on a busy Saturday.
The obvious alternative — one of the well-known salon booking platforms — does handle that properly. It also comes with a monthly bill for as long as the salon exists, usually priced per stylist, for a set of features built for salons far bigger than this one. For a small, established local business, that's a lot of ongoing cost to take on for scheduling and checkout.
What actually got built
A desktop app, installed on a machine at the salon, with two kinds of accounts:
- The owner has an admin account. She creates a login for each stylist as they join, and can see the whole shop's schedule.
- Each stylist has her own account. She sees and manages her own clients and her own bookings — not everyone else's.
At checkout, the app takes the payment and pushes it through to a payment processor to actually move the money, rather than the salon handling that as a separate step by hand.
Why a desktop app instead of hosted software
This is the same tradeoff custom software versus off-the-shelf comes down to for a lot of small businesses, just with an extra option in the mix. A desktop app running on the salon's own machine meant:
One fee, not a monthly one. The salon paid once to have it built. No per-stylist subscription creeping up every time someone new joins the shop.
Nothing to host. The data lives on their own machine, not in my cloud bill or theirs. No hosting cost, no networking to configure beyond what a normal small business already has — the same reasoning behind a book-tracking app I built for a Princeton business, just synced through iCloud instead of living on one machine.
Sized to one salon, not a chain. The booking platforms this competes with are built to also handle multi-location chains with inventory, marketing tools, and reporting dashboards this shop will never use. This does the two things they actually needed — per-stylist scheduling and checkout — and nothing else.
The trade is the one you'd expect: it's this salon's software, not a product with a support line. In practice that's meant occasional visits to make sure backups are actually running, not a support ticket queue — which is the same arrangement I'd want if it were my own shop.
If the salon ever wants something the app doesn't do yet, that's a new, separate price when they ask for it — not a bigger subscription tier. The same is true for a Princeton business I built a book-tracking app for: pay once for what fits now, and pay again, on your terms, only when something actually changes.
If this sounds like your business
This is what a scheduling problem that's outgrown a shared calendar actually looks like solved — not a bigger subscription, just software sized to the business that has it. If you run a salon, a small service business, or anything with more than one person booking appointments around Flemington, Princeton, or Hopewell, get in touch and we'll go through what your schedule actually needs to handle. More on what I build.