Copy Examples

FAQ page examples for chefs

An FAQ page is where the objections go that the rest of the site is too polished to name. Answer the money question first or the visitor leaves to find it.

Ten of them follow, written for chefs rather than filled in from a template. Your customer is someone booking dinner for people they want to impress, in their own home, and what they are weighing up before they get in touch is paying a lot for dinner in their own home and having it feel like a catering job.


What does it cost?

**What does it cost?** [your honest starting figure], and you get a sample menu before anything is agreed. What moves the number is [the two or three things that actually change the price] — so the quote comes after I have seen the dinner, not before.

Always answer this. The visitor who leaves to find it does not come back.

How soon can you come?

**How soon can you start?** Usually within [timeframe]. If I am booked further out than that, I say so rather than holding your date loosely.

Use this where availability is the deciding factor.

The objection, named

**[the question they are too polite to ask]** The honest answer is that paying a lot for dinner in their own home and having it feel like a catering job is a real risk in this trade. What I do about it: name the kitchens I trained and worked in, and describe the actual food, not a philosophy.

Use this for the worry people have but do not ask about.

Are you licensed and insured?

**Are you a trained chef?** Yes. Professionally trained, with the kitchens worked in named and food-safety certification current. Ask and I will send the documents before I start.

Use this wherever a credential is checked before anything else.

What happens when I get in touch?

**What happens after I contact you?** Tell me the date, the number and any allergies, and I will send a sample menu. I agree the scope and the price in writing before anything begins, and nothing starts until you say so.

Use this to take the friction out of the first contact.

What if something goes wrong?

**What if something goes wrong?** I put it right at my cost. [your guarantee, in one sentence]. I would rather fix it than argue about it, and that is easier to promise on a page than to do — so ask me for a reference from someone it happened to.

Use this where the risk is what stops people booking.

Do you do [adjacent thing]?

**Do you also do [the adjacent service people ask about]?** [Yes, and here is how] — or: no, I do not, and [who you would call instead] is who I would ring. Saying so up front saves us both a phone call.

Use this to catch the enquiries you want and deflect the ones you do not.

How do I prepare?

**Is there anything I should do beforehand?** [the one or two things that genuinely help]. Beyond that, nothing — I bring what I need.

Use this where a little preparation makes the job cheaper or faster.

How do I pay?

**How and when do I pay?** [your terms: deposit, on completion, invoice]. I do not ask for payment for work I have not done.

Use this where payment terms are a real question and silence reads badly.

Why are you more expensive?

**Why are you more expensive than the cheapest quote?** Usually because the cheap quote leaves something out. I name the kitchens I trained and worked in — that is in my price. Describing the food instead of a philosophy about food is the part you cannot see on a quote sheet and the part you notice a year later.

Use this only if you are, and only if you can answer it well.

Writing for chefs: what actually matters

What should a chef’s website say that a generic one does not?

Three things, in this order. That you are trained and certified. That you understand the thing people are actually worried about, which for chefs is paying a lot for dinner in their own home and having it feel like a catering job. And what happens next: tell me the date, the number and any allergies, and I will send a sample menu. Everything else on the page is decoration by comparison.

What does someone booking dinner for people they want to impress, in their own home check first?

The credential, then the proof. For chefs it sounds like this. I name the kitchens I trained and worked in. I describe the actual food, not a philosophy. I hold current food-safety certification. Put at least one of those above the fold rather than on a separate page nobody opens.

What is the most common mistake on a chef’s website?

Writing about the business instead of the customer. "We have been established since 1998" answers a question nobody asked. "Tell me the date, the number and any allergies, and I will send a sample menu" answers the one they are actually holding. If you only fix one thing, fix that.

How long should the copy be?

Shorter than you think, except where trust is being built. An About page of 120 well-chosen words beats 500 vague ones. The exception is anything explaining paying a lot for dinner in their own home and having it feel like a catering job — there, specifics earn their length.