Most chefs don't struggle with cooking—they struggle with explaining what they're charging for. A household asks "what do you charge?" and the honest answer depends on how you structure the work: your labor, the groceries, travel, planning time, and how much risk you take when the menu changes.

There isn't one "right" model. There are common models, each with tradeoffs. The goal is to pick one that matches how you actually work, quote it in plain language, and stick to it long enough to know whether you're profitable.

The Two Buckets Clients Need to Understand

Almost every sustainable quote separates:

  • Your service (labor + expertise). Menu planning, shopping, cooking, cleanup, communication, and the judgment that keeps a household fed without drama.
  • Food (ingredients). What you buy at the store or through suppliers—often passed through at cost, sometimes marked up modestly for sourcing and handling.

When those are bundled into one opaque number, clients assume you're overcharging on groceries. When they're split clearly, trust goes up—even if the total is the same.

Clients don't mind paying for good work. They mind not knowing what they're paying for.

Model 1: Service Fee + Food (Pass-Through or Receipt)

This is the backbone of most weekly recurring personal chef work—and it's worth understanding why so many experienced chefs default to it.

Two separate things on purpose

Under this model, you're not selling "dinner for $800." You're selling your service for a fixed fee, and the client is buying their own groceries that you shop for and cook. The food is theirs—conceptually and on the receipt. You're the agent in the store, not the grocer marking up inventory.

That separation matters:

  • Your wage doesn't swing with the protein. Lobster week and chicken week are the same cook day for you. Same planning load, same kitchen time, same cleanup—so your service fee stays the same. If they want halibut instead of cod, that's a grocery line item, not a negotiation over whether you "deserve" more for a harder protein.
  • Your income is predictable. You can block the calendar, know what you'll earn from labor each month, and build a business around that number—not around whether organic berries were on sale.
  • Their food cost is predictable in a different way. They see what meals actually cost at the store. Some weeks are $280, some are $420—and they can see why, because the receipts match the menu.

When service and food are bundled, every menu choice feels like it's hitting your fee. When they're split, you stop being punished for shopping well for someone who likes nice ingredients.

How it works in practice

  • Service fee: Fixed per cook day or per week—covers menu planning, shopping as work, cooking, cleanup, labeling, and the weekly check-in. Quote this number confidently; it's your business.
  • Food: Billed at cost with receipts (or a defined reimbursement rule). You buy it; they pay for it. No mystery markup unless you've disclosed one upfront.
  • Shopping time is almost always inside the service fee. The client isn't paying hourly for you to walk aisles—they're paying for the outcome. The groceries themselves are separate dollars.

Food budgets: two kinds of clients

You'll meet both, and the model still works—you just adjust the conversation.

Budget-conscious clients often want a weekly cap on top of pass-through: "Keep groceries around $350 this week" or "We're trying to stay under $400 until the trip." That's healthy. You plan the menu to the cap, flag anything that would push over (special occasion, out-of-season produce), and get a quick yes before you buy. Your service fee doesn't change when you hit the target—you're managing their ingredient spend, not discounting your labor.

Hands-off clients may barely look at line items. They trust you to buy what the menu needs and review the total when the card hits. That's fine too—but still send receipts or a short summary ("groceries $412 this week—higher because of the ribeye and the dinner for six on Thursday"). Transparency prevents quiet sticker shock six months in.

Neither type is better. Budget clients need you to be a good steward; hands-off clients need you to be a good communicator. In both cases, expensive ingredients are their choice, not your raise request.

Why chefs like it

  • Margin isn't hostage to salmon prices, organic everything, or "just this once" wagyu.
  • You can say yes to quality ingredients without feeling like you're donating the difference.
  • Scope fights shrink: "We didn't agree to $600 of groceries on a $400 pattern" is a data conversation, not a fight about your worth.

Why clients like it

  • They see the real cost of eating the way they want—not a blended number that makes them wonder if you're padding food.
  • They can dial food spend up or down without asking you to re-quote your life.
  • It feels fair: they own the cart, you own the kitchen.

Watch-outs

  • Who approves going over budget? Text before you buy the $45/pound fish if they're on a cap.
  • Reimbursement timing. Weekly invoice, same-day Venmo, monthly statement—pick one and stick to it.
  • Sales tax and tips on delivery apps—pass through or spell out what's included in "cost."
  • Don't let "just cover it this week" become a habit. Small grocery favors add up; if it's recurring, it's food cost, not a favor.

Typical framing: "My service is $X per cook day—that's the same whether we're doing chicken or lobster. Groceries are yours, billed at cost with receipts. For a household your size I usually see $Y–$Z a week; if you want a firm cap, tell me the number and I'll plan to it."

Model 2: Flat All-In Per Cook Day (or Per Week)

One number covers labor and food up to an agreed scope.

  • How it works. " $1,200 per week includes up to 12 entrée portions and sides for four people, standard proteins, one fish night." Food and labor are bundled.
  • When it fits. Clients who want simplicity and chefs who have enough history to estimate food cost accurately for that household.
  • Pros. Easy to say yes to. Predictable invoice. Less receipt admin.
  • Cons. You absorb food inflation and scope creep unless boundaries are explicit. A "simple" week with wagyu and truffles is not the same job as chicken-and-rice week—write what "standard" means.

If you use all-in pricing, build in a menu band (standard vs premium) or a cap on specialty ingredients. Otherwise your flat rate becomes a gamble every week.

Model 3: Hourly (Labor Only)

You charge by the hour for time on site (and sometimes for off-site planning/shopping).

  • How it works. "$85/hour, four-hour minimum on cook day. Groceries separate." Some chefs bill planning and shopping hourly; others fold planning into a higher on-site rate.
  • When it fits. Irregular work, new clients you're scoping, consulting-style engagements, or kitchens where the job length varies wildly.
  • Pros. You're paid when the job runs long. Fair when the work is genuinely unpredictable.
  • Cons. Clients hear "hourly" and picture a clock-watching transaction. You must track time carefully. Recurring weekly work often feels expensive on paper compared to a clean per-day package—even when the total is similar.

Hourly is a tool for uncertainty—not a default for every cook day. If you know the rhythm after week three, a day rate is usually clearer for everyone.

Model 4: Per Person (Events and Dinner Parties)

Events are priced differently from weekly prep. Clients rarely want a grocery receipt for a birthday dinner—they want one number per guest that means "handled." So per-person pricing is the usual language for one-off entertaining: "$95 per guest, 12-guest minimum."

Food is usually bundled—and the math is different

Unlike Model 1, event quotes are almost always all-in per head: food, your labor, basic disposables, and the logistics of that specific party live in one rate. You're not passing through cart totals at the end; you're estimating what the night costs you and marking it up to a clean per-guest figure.

A rule of thumb many chefs and caterers use:

For events, food cost is often about one-third of what the client pays per person. Estimate your real food cost per guest, multiply by three, and you're in the zone for covering ingredients plus most of the overhead of doing the party—your prep day, travel, shopping, cooking, cleanup, and the "invisible" hours before anyone arrives.

Example: if you know dinner will run roughly $28 of food per plate (protein, sides, apps amortized across the room, a little waste), charging $84–$90 per guest is a sane starting point—not a final contract, but a back-of-napkin that doesn't leave you subsidizing the party. If the menu is lobster and passed seafood towers, your food third might be $45 and the quote drifts toward $135+ per head before rentals even enter the chat.

Clients can use the same math when they're budgeting: "What would this cost if I bought the ingredients for one plate at retail?" Triple it. That's roughly what they're paying for a professional to design, source, execute, and clean up—not because you're marking up groceries 200%, but because two-thirds of the ticket isn't the fish; it's everything wrapped around the fish.

What that one-third covers (and what it doesn't)

Tripling food cost is a shorthand for solo or small-team chefs doing intimate dinners: you shop, cook, plate, and reset the kitchen. It absorbs menu development, procurement, prep and cook time on site, packaging or plating, and the fact that one event can burn a full day even when service is only four hours.

It does not automatically cover every upscale variable. Once you add paid servers, a bartender, rental china and glassware, venue fees, outsourced bread, or a commissary kitchen, you're in a different spreadsheet—labor lines, rental markups, vendor invoices, insurance minimums. That's still per-person pricing from the client's view, but your internal build is closer to catering P&L than "food × 3." For the full worksheet, see Event Pricing: From Food Cost to Final Quote.

Quote what "per person" actually includes

Per-guest pricing only works when the scope is explicit. Two chefs can both say "$110 per person" and mean different nights.

  • Menu: Passed apps, courses, dessert, coffee? Family-style or plated?
  • Beverage: Often excluded or a separate per-guest beverage fee—say so.
  • Staff: Just you, or you plus a server? Is gratuity for hired help included or on top?
  • Rentals & disposables: Your plates and linens, or theirs? Rental fees passed through or baked in?
  • Cleanup: Through dish wash and trash out, or "kitchen broom clean" by midnight?
  • Travel & load-in: Especially for estates or venues—built into the head count or a flat logistics fee.

Write the inclusion list into the proposal. Guests count; ambiguity counts against you when someone expected a fourth course.

Minimums protect the day

A 10-person dinner that quotes at 12-guest minimum means you're paid for twelve whether ten show up or not. Same logic as weekly service minimums: prep doesn't shrink linearly when two seats are empty. You still develop the menu, shop, and block the calendar.

Common patterns:

  • Guest minimum (12 guests minimum at $95 = $1,140 floor)
  • Revenue minimum ("$2,400 minimum event fee" for small parties)
  • Deposits & headcount deadline—final count five days out; last-minute +2 guests at full rate, -2 guests may not reduce the minimum

When per-person beats Model 1

Weekly prep: client owns the food, your fee is stable. Events: client wants one invoice, one decision. Per-person is how you sell that without absorbing unknown grocery totals. Use the food-cost-third as your internal check; quote per guest externally; keep rentals and extra labor as separate lines when the night outgrows a simple triple.

Typical framing: "$110 per guest, 12-guest minimum, includes three courses and service through cleanup. Beverages and rentals quoted separately. Based on the menu we discussed, ingredient cost runs about $35 a plate—your all-in rate reflects prep, cooking, and the full day, not just the grocery bill."

Model 5: Monthly Retainer or Package

"Four cook days per month for $3,800, groceries not included" or "includes up to $600 groceries."

  • Why use it. Cash-flow predictability for you; convenience for the client. Great when trust is established.
  • Structure clearly. Unused days—roll or forfeit? Extra days—rate? Guest nights—surcharge? Food over cap—billed how?
  • Risk. Retainers without written scope become unlimited concierge. Tie the package to number of portions, people, or hours—not just "meals."

Food Markup: When and How Much

Some chefs bill groceries at cost; others add 10–20% for sourcing, credit card fees, cooler bags, and the liability of buying on the client's behalf. Both are normal—pick one and say it upfront.

If you markup, clients still deserve itemization (category totals or receipts). Markup on mystery totals erodes trust faster than a disclosed handling fee.

Choosing a Model (Quick Guide)

  • Weekly household prep, ongoing. Service fee + food (receipts) or a tight all-in weekly rate with a written menu band.
  • New client, unclear scope. Hourly with a minimum, or a paid trial cook day before committing to a package.
  • Dinner party / event. Per person with minimum guest count; use the event pricing worksheet when staff or rentals are involved.
  • Busy professional who wants "handled." Monthly package with explicit caps—days, portions, food budget, guest surcharges.

Quote Language That Prevents Friction

Whatever model you use, say these out loud (and put them in your agreement):

  • What's included in your fee vs food
  • Travel charges outside your radius
  • Planning and shopping time—bundled or billed separately
  • How menu changes after approval are handled
  • Payment timing: deposit for events, weekly invoice for recurring

You're not being corporate—you're preventing the awkward conversation where they thought "per week" included unlimited wine reductions and daily breakfast.

Common Mistakes

  • Quoting labor without estimating food. You win the job, then the grocery line shocks them. Give a realistic range early.
  • Switching models mid-relationship. Fine if you communicate and transition fairly—not fine as a surprise on invoice six.
  • Underpricing planning. The cook day is visible; the menu email thread isn't. Your service fee must cover off-site work.
  • Competing on food cost. You're not a grocery store. Compete on reliability, diet safety, and the experience of the week—not who can buy chicken cheapest.

If you remember one thing: separate your expertise from the groceries, name the model you're using, and write down what "included" means. Clarity closes clients; confusion churns them—even when the food is excellent.