Private chef booking website: an enquiry built around menus
Short answer: A private chef's website should sell the food first and take the booking second. Show sample menus that set expectations on style and format, then use an inquiry form that captures exactly what you need to quote: date, guest count, menu direction, dietary restrictions and allergies, and the kitchen you'll be working in. Reply with a proposal that the client can accept and pay a deposit on in one step, and keep their details so the next dinner takes two messages, not twenty.
Most chef websites end in a generic "Contact me" form. The result is an email thread that starts with "How much for a dinner party?" and takes a week to reach a firm booking. The journey below fixes that one stage at a time.
Stage 1: Menus that answer questions before they're asked
Visitors want to know what kind of chef you are. Sample menus show that faster than any About page.
- Three to five example menus, each a different format: plated multi-course dinner, family-style, brunch, a cooking class, weekly meal prep if you offer it.
- Label them as samples. Say clearly that menus are built around the season and the client.
- Format notes, not prices, if you prefer. Explain what is included: shopping, cooking on site, service, cleanup. If you show prices, use "from" figures and say what changes them.
- Photos of real dishes you made, not stock images.
Each menu gets a button: "Start an inquiry with this menu." That button should pass the menu name into the form, so the client doesn't have to describe it.
Stage 2: An inquiry form that gives you enough to quote
The goal is one form submission that holds everything you need for a proposal. Group the questions so it doesn't feel endless.
The event
- Date and start time (plus "my date is flexible" option)
- Occasion: birthday, anniversary, corporate dinner, family visit
- Number of guests, adults and children
- Format: plated, family-style, buffet, class, meal prep
- Menu direction: the sample menu they clicked, or cuisines and favorite dishes in their own words
Dietary needs
- A checklist of common restrictions (vegetarian, vegan, no pork, kosher-style, halal, gluten-free)
- A separate, required field: "Any food allergies among your guests? Please list each one."
- A free-text box for preferences and dislikes
Keep allergy capture factual. Ask, record and confirm in writing; don't make promises on the site about what you can guarantee in someone else's kitchen. Confirm each allergy again in the proposal so nothing is lost.
The kitchen
This is the question most forms skip and every chef needs:
- Number of burners and ovens, and whether there's a grill
- Counter space and seating for the number of guests
- Equipment you shouldn't assume (a stand mixer, enough plates)
- Parking and access, especially for apartments
- Photos of the kitchen (an upload field)
Budget and contact
- A budget range or "please suggest"
- Name, phone, email, and how they heard about you
Tools can handle this without custom code. HoneyBook, as one example, describes lead forms that create a project automatically when submitted, don't require the client to have an account, can include service selection and accept image uploads (as of November 2026, JPG, PNG and GIF, not PDFs). Its form builder guide notes forms can be shared by link or embedded on your website.
Stage 3: Checking availability without double booking
Private chefs often do one event a day, sometimes two. Don't show a public calendar of open evenings if you need to vet each request; instead:
- Block dates you are already booked in your calendar so the form can warn "This date is unavailable"
- Treat every other date as "request," confirmed only when the deposit is paid
- Hold a date for a set number of days after sending a proposal, then release it
Write the hold period into your proposal so clients understand why prompt acceptance matters.
Stage 4: A proposal the client can accept in one go
Your proposal should read like a confirmation, not a price list:
- The menu, course by course, adjusted for the dietary needs given
- Allergies restated, with a line asking them to confirm the list is complete
- Guest count, date, arrival time and what you'll need from them (oven free from 4pm, table set or not)
- What is included and what isn't (groceries billed at cost, rentals, service staff)
- Your cancellation and change terms
- The total and the deposit due now
Software that combines the proposal, agreement and payment saves an email round. HoneyBook's form builder mentions invoice, contract and scheduler actions; check which block types its current forms support, as its guide notes some are limited to certain form types.
Stage 5: Deposit and balance
Take a deposit to secure the date. If you invoice through Square, its deposits and payment schedules help page describes requesting a deposit as a percentage or a fixed amount, with a due date and reminders, and splitting the balance into milestones on some plans. A typical setup:
- Deposit due on acceptance, which confirms the date
- Grocery estimate either included in the deposit or billed separately
- Balance due a set number of days before the event, or on the day
Send the reminder automatically. Chasing a balance in person, mid-service, is nobody's idea of a good evening.
Stage 6: The week of the event
A short automated sequence keeps everyone aligned:
- Seven days before: final guest count and any new allergies
- Three days before: arrival time and parking reminder
- The day after: thank-you message, and a request for a review or photos if they're happy
Stage 7: Repeat clients
Private chef work runs on repeat bookings and referrals. Keep a client record with:
- Allergies and dislikes for each household member
- Menus served, so you never repeat a dish unless asked
- Kitchen notes (the oven runs hot, the corkscrew lives in the second drawer)
- Important dates they've mentioned
When they return, send a pre-filled link: their details are already in, they choose a date and a direction, and you send a proposal that night.
FAQ
Should I put prices on my website?
Optional. Many chefs show "from" pricing per format to filter out inquiries that won't fit, then quote properly in the proposal.
Do I need an online booking calendar?
Usually not for dinners. An inquiry form with date checking works better, because every event needs a menu conversation first. Instant booking can work for fixed-format services like cooking classes.
How do I handle last-minute allergy changes?
Ask for a final confirmation a week out and again on the day, and record any change in the client's file and your prep notes.
Can one tool handle forms, proposals and payments?
Several client management tools do; HoneyBook is one example. Compare them on how well they fit your inquiry questions, not just their feature lists.
Turning your sample menus into an inquiry that hands you everything needed for a proposal is a small build with a big payoff, and we'd enjoy helping you design your chef booking flow.