Client build · 2026
Safety, Sparkle & Green
A booking site for a Scarborough cleaning company: priced services, a two-minute request form, and an admin dashboard that runs the week — with bookings in MongoDB and email confirmations that stay optional.
- Role
- Design, front-end and back-end
- Stack
- Next.js 15TypeScriptTailwind CSS 4MongoDBResendZod
- Live
- ssghouseservices.ca
The repository is private — happy to walk through the code on request.

01What the build involved
01
One page that does three jobs
The landing page has to sell the service, list it with prices and take the booking, without turning into three sites. Prices come from a single service catalogue with a base price, per-bedroom and per-bathroom rates and a duration; the estimate the customer sees is calculated from those numbers, so a quote can never drift from the menu above it.
02
The reference is the primary key
Each booking’s document id doubles as the customer-facing reference (SS-7K4QDA), so there is one identifier everywhere instead of a database id plus a reference that can fall out of step. MongoDB guarantees uniqueness, a duplicate-key retry covers the rare collision, and indexes on the date and status fields are created on first connect rather than in a migration nobody runs.
03
A dashboard that runs the week
The team signs in to a bookings list with status filters and a week-by-week schedule. Moving a booking between pending, scheduled, completed, declined and cancelled emails the customer the new date and arrival window, keeps a reschedule history capped at the last twenty changes, and locks the date once a job is closed — enforced in the form and again on the server.
04
No user table
There is one admin account and an optional read-only member, both configured by environment variables: scrypt password hashes, a signed session cookie, and roles decided by which variable an address lives in. Revoking someone is an edit in Vercel, not a database migration, and every request re-checks the session instead of trusting a long-lived token.
05
Proof it works after deploy
A health endpoint pings the database, validates the mail key and says exactly what is missing; a preflight script checks the environment before you deploy; a smoke test books a job against the live site, confirms it reaches the dashboard and deletes it again. Turnstile is wired so a missing key can never block a real booking.
02What it left behind
Outcome
Live for the client at ssghouseservices.ca and taking real bookings: an estimate from the service catalogue, a confirmation email with an arrival window, and a dashboard that moves a job through its statuses. One identifier — the document id — covers both the database and the customer’s reference.
Another pass
One admin account held in environment variables suited the size of the job, but it turns adding a second staff member into a redeploy instead of a click. I would put the team in a collection now, keeping the same signed-cookie session. The mail templates also deserve a preview screen, because the confirmation email is the only part of the site a customer keeps.
03Inside the product
Click any screenshot to view it full size