case study

book2day

a multi-tenant booking and business management platform for service businesses in belize.

overview
~5providers taking real appointments
430+automated tests in CI
<50 mstypical page time, profiled locally
0possible double-bookings
my role
Product owner: product strategy, design decisions, testing and QA
built with
Claude (AI coding assistant), which wrote the implementation
core stack
Django · PostgreSQL · htmx · Celery · Render · Cloudflare
status
Live in production at book2day.bz
the problem

no front desk

Most service providers in Belize (barbers, nail techs, lash artists, therapists, dentists) own the practice and do the work. There's no receptionist. Bookings arrive by phone, DMs and walk-ins while they're with a client, so messages go unanswered and slots get double-booked.

Existing salon software is built for larger teams, priced in USD, and doesn't fit clients who live on WhatsApp.

how the product evolved

marketplace → tool

  • v1: booking marketplace. Customers browse local providers by category and town and book open times.
  • The insight. Providers' biggest pain wasn't finding customers. It was running the business while also being the staff. They needed a front desk.
  • v2: business management tool. Calendar, team, clients, services, classes, memberships, expenses and analytics for the provider. The marketplace became the discovery channel feeding each provider's calendar.
  • Scope decision. Automated reminders were cut. Clients get one WhatsApp confirmation when the booking is set, with a link to reschedule.
how it was built

product-led, ai-built

I owned the product end to end and built it with an AI coding assistant. I made the product, design and architecture decisions and set what "done" meant. Claude wrote the implementation.

  • Product: talked to providers, chose the pivot from marketplace to business tool, and set scope, including cutting reminders to ship a reliable confirmation flow.
  • Design decisions: UX and the design system, plus the technical direction: Django and htmx instead of a single-page app, correctness enforced by the database, tenant isolation and the security bar.
  • Testing: defined acceptance criteria and edge cases (concurrent holds, daylight-saving changes, cross-tenant access), tested every flow by hand on phone and desktop, and gated releases on the CI suite and layout checks.
  • Implementation: written by Claude from my specs, then reviewed and tested by me before merging to main.
architecture

One Django codebase deployed to Render as three services: the customer site and provider dashboard, a separate admin console with MFA, and a Celery worker. Every merge to main deploys automatically.

stack

the stack

BackendDjango 5.2 LTS (Python), Django REST Framework (REST API v1)
FrontendServer-rendered Django templates + htmx, no SPA. Custom CSS design system with colour and radius tokens. Responsive from 320 px up
DatabasePostgreSQL with range types, GiST exclusion constraints and btree_gist
Background jobsCelery workers and Celery beat on Redis
HostingRender: web, admin (separate host) and worker, all from one codebase. Auto-deploy on merge to main
Edge & storageCloudflare DNS; Cloudflare R2 (S3-compatible) via django-storages
MapsMapLibre GL, self-hosted, with OpenFreeMap tiles and a custom style
MessagingMeta WhatsApp Cloud API, called directly, with signed webhooks
IntegrationsGoogle Calendar (OAuth with PKCE, one-way sync), iCal feeds
CIGitHub Actions: 430+ tests plus headless Chrome layout checks at desktop and phone widths
engineering highlights

under the hood

  • 1

    The database makes double-booking impossible

    Each appointment stores a time range including the service's buffer minutes, and a PostgreSQL exclusion constraint stops two blocking appointments for the same staff member from overlapping. Checkout holds live in the same table, so one constraint covers holds, pending requests and confirmed bookings. Confirming updates the held row in place, leaving no window for a second customer. A test fires 20 concurrent holds at one slot and checks that exactly one succeeds.

  • 2

    One function controls every status change

    A single transition function handles held → pending approval → confirmed → completed or no-show, plus the cancel paths. Each change bumps a version number and sends events only after the database commit, so the API, webhooks, jobs and admin stay consistent, and stale jobs can't act on outdated data.

  • 3

    Availability is calculated live, never stored

    Weekly hours, minus bookings, time off and holidays, placed on a local-clock grid. Time-zone safe and tested across a daylight-saving change.

  • 4

    Group classes reuse the same engine

    Each seat is an appointment. Seats share an overlap key so they don't block each other, but the class still blocks the instructor's one-on-one time. Taking the last spot locks the class row.

  • 5

    Insights: analytics built from bookings

    Nightly jobs fill daily and hourly summary tables. Providers see income by month, weekday and hour, a busy-hours heat map, and which services earn the most per hour. Charts are SVG drawn on the server, with no JavaScript charting library.

  • 6

    Strict tenant isolation

    Every view checks business membership and capabilities, and querysets are scoped to the business. A test walks every URL and tries to reach another business's data.

  • 7

    Security in depth

    Same-origin-only Content Security Policy with no inline JavaScript. Photos re-encoded to WebP with EXIF and GPS removed. Sign-in codes HMAC-hashed and throttled. OAuth tokens encrypted. Webhook signatures verified. Append-only audit logs. Fresh sign-in required for sensitive actions.

  • 8

    Profiled under load

    Tested with 300+ businesses and a shop with 6,000+ bookings. Most pages run 3–29 queries in under about 50 ms locally, with no one-query-per-row problems. The ~1 MB map library loads only when a map scrolls into view.

product scope

what it does

Customers

  • Search and discovery
  • Business pages with galleries and maps
  • Live booking, guest or account
  • WhatsApp confirmation with reschedule link
  • Manage booking by link
  • Verified reviews
  • Spanish language

Providers

  • Day / week / month calendar
  • Approvals and walk-ins
  • Team and staff logins
  • Clients with private notes
  • Services and add-ons
  • Group classes and memberships
  • Expenses and Insights
  • Google Calendar and iCal sync

Platform admin

  • Business onboarding
  • Moderation, suspend or delete
  • Audit logs
  • Holiday and boost planning