LetsBook

Online booking platform built on Laravel 12 + Inertia.js/React. Providers get a branded booking page, a scheduling calendar, and a customer-management dashboard; customers book services through a mobile-first public wizard with no account required.

Stack

• Backend: Laravel 12 (PHP 8.3), MySQL
• Frontend: Inertia.js + React 19 + TypeScript, Tailwind v4, Vite
• SSR: Inertia server-side rendering for the public-facing pages
• Auth: Laravel session auth for the provider dashboard, Sanctum tokens for the API surface used by external/future clients

Supported business types

LetsBook started as a home-cleaning-only booking engine. It now supports appointment-style businesses (barbers, dentists, and similar) as one app, not a fork — behavior is driven by three flags on Provider:

• business_type: regular (default) or appointment. Controls behavior only — specifically, whether the public wizard collects a customer address. regular means the provider travels to the customer (cleaning, or any other mobile service). appointment means the customer visits the provider (barber, dentist, etc.). It has no say in wording — that's business_niche's job, entirely.
• business_niche: freeform string, defaults to 'cleaning'. Controls wording only — completely independent of business_type. barber and dentist read very differently ("Select a treatment" vs. "Select a service"), and wording is resolved purely by niche, with no fallback to business_type-based copy. A niche without its own tailored entry falls back to generic, business-agnostic wording — so setting a brand-new niche never requires a migration, only an optional follow-up to give it dedicated copy.
• uses_staff_scheduling: boolean, false by default. Controls whether there's more than one interchangeable person doing the work. When on, a provider can add staff members, give each one their own hours and holidays, and customers get a "Who would you like?" picker in the wizard. Double-booking checks are scoped per staff member instead of the whole business. When off, there's a single shared calendar for the whole business, and none of the staff UI is reachable.

business_type × uses_staff_scheduling combine into four supported business shapes; business_niche independently tailors wording for any of them (most usefully for appointment providers):

business_type	uses_staff_scheduling	Shape	Example
regular	off	Single calendar, address required	A solo home-cleaning provider (today's default for every real customer)
regular	on	Multiple staff, address required	A cleaning company with several cleaners, each with their own calendar, still visiting customers' homes
appointment	off	Single calendar, no address	A solo appointment-based provider — one-person barber, dentist, etc.
appointment	on	Multiple staff, no address	A small shop with several staff to choose from — barbershop, small dental practice

Current status

• All three flags default to the values that match every existing customer's behavior today, are excluded from mass assignment ($fillable), and can only be set via forceFill() — there's no self-serve or admin-UI way to enable them yet. This is intentional: it keeps the three real cleaning customers on this platform completely unaffected while the other shapes are piloted by hand.
• The public wizard's main touchpoints (category step, services step, intro copy, calendar event title, confirmation receipt) are business_niche-aware; the address step is business_type-aware. The provider dashboard (services, orders, help) still says "Home Type" regardless of either flag — planned as its own separate release.
• No self-serve onboarding flow exists yet for the non-default shapes — enabling them for a new provider is a manual, hand-held step.

See appointment.md in the repo root (untracked, local working notes) for the detailed build history and open items on this effort.