BOA — Chef privé
Design and high-fidelity prototype of BOA, chef Max's private-chef and table-service brand in Montreal. Built from a client-filled PRD (Word document) and a competitive analysis (Take a Chef, The Culinistas, Cozymeal, Tock), the site sells an experience — "When the love for food meets unforgettable memories" — rather than plain catering: private dinners, weddings, birthdays and corporate events, cooked and served at your home. The mockup covers the whole journey: an editorial home (hero, "the art of hosting" pillars, trust strip, "what's included"), a culinary concierge that recommends a menu in 30 seconds (occasion, guests, budget, restrictions), the menus (fixed / event / call required), experiences, venues, a photo gallery, the chef's story and contact. At its core is a multi-step booking flow: menu → date (2-week minimum lead time, last-minute fees flagged, "notify me" waitlist) → format (table service / chef's table / event), guests (capped at 20, 20+ → mandatory call), address (Island of Montreal · distance-based fee) and allergies → summary (25% non-refundable deposit, balance per agreement, taxes not applied) → mocked payment (card / debit / Interac) → confirmation (deposit received, 48h reminder, notification to Max). It also ships a guided "BOA Concierge" chatbot, an FR/EN switcher, a burgundy & cream light/dark theme (Newsreader + Hanken Grotesk + Allura), premium animations honouring prefers-reduced-motion, and an admin mode with drag-and-drop photo slots to wire in real images. Everything is cleanly mocked — no real payment, no live AI — pending decisions on pricing, calendar (Calendly), payment processor (Stripe / Square) and legal copy (Loi 25) with the client.

The idea
Booking a private chef should be as simple as booking a table. BOA explores that flow: chef, menu, date, at-home service.
- ▸Two sides: the client who books, the chef who manages
- ▸Constraint: availability and menu change together
- ▸Honest status: product framing, no code yet
Why show it
An honest portfolio also shows what is being thought through — and what I would do before writing the first line.
- ▸Framing before code: the Cadence lesson, reapplied
- ▸Next step: prototype the booking flow