A private chef sells events. A four-course anniversary for six, a corporate offsite for sixteen, a Hanukkah dinner for a family of eight. Every event is a curated menu and a fixed headcount, and every event has a website page or a booking record that holds the menu, the date, the venue, and the price. The work of typing the menu has been done.

What hasn't been done is the social card. Most private chefs either skip the menu graphic and post a hero photo with text overlay, or rebuild the graphic in Canva for each booking. Both paths produce a feed that looks scattered, which matters because a private chef's grid is the portfolio.

SleekPixel renders the menu card on save. The course list, the headcount, the date, the venue, the price (or a discreet "price on inquiry") compose into the 1080x1080 grid card. The OG image for the event URL matches. The chef's portfolio reads as one chef across a year of bookings.

Private chef bookings come from word of mouth and from a portfolio that looks expensive enough to justify the price. The food photos do half of that work, the menu cards do the other half. A grid of nine menu cards that share one type system reads as a chef with a real practice.

A grid of nine menu cards built in different Canva sessions reads as a hobbyist. The chefs at the top of the field already understand this, the chefs growing into it usually don't have a designer on retainer. The fix is to type each event's menu into the booking post and let one template carry the visual identity across every event.

The price on the card matches the proposal. The venue on the card matches the contract. The portfolio reads as one chef across cities and seasons, which is the surface where the next high-value booking lands.