QZee

The brief

Service businesses live and die by the calendar. QZee is the booking layer underneath: a customer finds a business, books a slot, and pays; an owner runs the diary and gets paid. The pricing posture is transaction-led — no per-seat tax, no setup fee — because the whole pitch is that a small business shouldn't need a procurement department to take a booking.

The hard part

One product, multiple surfaces. A marketing site, a customer app, an owners' app, and a mobile surface all have to look and behave like the same QZee — so the design system is the spine of the whole thing, vendored across every surface rather than re-built from scratch each time. Underneath, availability has to collapse correctly when a venue auto-schedules, and money has to reconcile through Stripe without the booking losing its thread. None of it is glamorous. All of it has to be exact.

What we built

A shared design system, vendored so every surface is the same product. A GraphQL customer API, a Stripe integration for payments, a Go notification worker, and AWS infrastructure written as Terraform. The marketing site is Next.js 14 on the App Router; the apps are React and TypeScript; the accent is a single lime (#7DEA01) on near-monochrome, because a booking tool should feel calm, not loud. Cameron owns the system and the surfaces; Joel owns the API, the payments, and the infrastructure.

The rule we held

Nothing fake ships. The proof on the marketing site — testimonials, partner logos, user counts — stays hidden until it's real, rather than padding the page with numbers we can't stand behind. It's the same rule we run the whole studio on, and it's easier to hold when you own the product.