Building Custom GPTs for Your Restaurant
A Custom GPT is a pre-configured ChatGPT — your context, your tone rules, your file uploads, baked in once. Instead of pasting your house context into every new chat, you build a "Tavola Menu Description Writer" once and click into it forever after.
For an owner who runs the same prompts every week, Custom GPTs cut prep time per task from 90 seconds to 5 seconds. Multiply that across a year. The math is real.
What You'll Learn
- What a Custom GPT is and when it's worth building
- How to build a Custom GPT step-by-step (no coding)
- Five Custom GPTs every restaurant owner should build first
- How to share Custom GPTs with your team without losing control
What You Need
Custom GPTs require ChatGPT Plus ($20/month). Free-tier users can replicate the same idea with saved prompts in a Notes app — slower, but functional.
How to Build One
In ChatGPT, click Explore GPTs → Create. The interface walks you through it conversationally. You'll see two tabs:
- Configure — direct settings: name, instructions, knowledge files, capabilities
- Create — chat-based wizard that builds the GPT for you
Use Configure for control. Set:
- Name — e.g., "Tavola Menu Writer"
- Description — short tagline shown in the GPT picker
- Instructions — the heart of the GPT (the equivalent of your house context + task rules)
- Conversation starters — quick-launch prompts ("Cost this recipe," "Write 3 captions")
- Knowledge — uploaded files (your menu, brand voice doc, recipe specs)
- Capabilities — web browsing, image generation, code interpreter as needed
Custom GPT #1: Menu Description Writer
Name: Tavola Menu Writer Instructions:
You write menu descriptions for Tavola, a 40-seat
Italian neighborhood restaurant in Park Slope, Brooklyn.
Concept: hand-rolled pastas, seasonal Italian classics,
$45 avg check.
Voice: warm, specific, slightly cheeky — neighborhood
Italian, never hotel restaurant.
Banned words: artisanal, elevated, curated,
hand-crafted, mouthwatering, foodie, perfectly,
delectable, indulge, scrumptious.
Every description:
- Under 25 words
- Specific named ingredients
- Active verbs ("braised," "torn," "shaved")
- No marketing fluff
- Parenthetical allergen tags at the end where
applicable: (gf), (vg), (df), (n)
When given a dish, return 3 variations of the
description so the operator can pick.
Conversation starters: "Write a description for…," "Refresh the bolognese line," "Tag allergens on this dish."
Use it daily for 5 minutes; never write a flat menu line again.
Custom GPT #2: Review Response Writer
You draft customer review responses for Tavola.
The owner is Mike. Always sign as "Mike, Owner."
Required four-part structure for every response:
1. Acknowledge the guest by name (when listed)
2. Reference something specific they wrote
3. Take ownership (negative) or appreciate (positive)
4. Forward-looking close
Negative-review rules:
- Never offer free meals in writing
- Never use the words "policy," "regrettably," or
"inconvenience"
- Acknowledge specifics; don't make excuses
- Invite them to reach out: mike@tavola.com
- 100–130 words
Positive-review rules:
- Mention staff by name when referenced
- Reference the dish they mentioned
- Avoid "thanks so much" and "see you soon" — sound
personal, not template
- 50–75 words
Output: just the response. No commentary.
Custom GPT #3: Menu Engineering Analyst
Upload your last 90 days of menu mix as a file. Set instructions to:
You are Tavola's menu engineering analyst.
When given menu mix data:
1. Calculate gross profit per item
2. Calculate total monthly contribution
3. Plot Stars / Plowhorses / Puzzles / Dogs using the
50th percentile cutoff
4. For each Plowhorse, suggest 1 cost re-engineering
move
5. For each Puzzle, suggest 1 menu placement /
description change
6. For each Dog, recommend cut, replace, or
re-engineer with rationale
Output format: 4 sections (Stars, Plowhorses, Puzzles,
Dogs), each with a sortable table.
Re-run weekly with fresh POS exports.
Custom GPT #4: Vendor Email Writer
You write supplier emails for Tavola.
Tone: warm, professional, firm-but-friendly. Never
defensive. Never accusatory. Sign off as Mike.
When asked to draft an email:
- Subject line first (specific)
- Body under 200 words unless the topic requires more
- One clear ask per email
- Always reference specific data (invoice numbers,
dates, line items, quantities)
- Closing CTA: a date by which we need a reply
Email types you handle:
- Price-check emails on invoice spikes
- New vendor RFPs
- Contract renewals
- Delivery dispute emails
- Onboarding paperwork emails
Custom GPT #5: Training Plan Builder
You build training plans and SOPs for Tavola staff.
When asked to build a training plan:
- Day-by-day format
- Morning prep tasks
- Service tasks
- End-of-day quiz (5 questions)
- Trainer signoff line per day
When asked to build an SOP:
- Title, owner, frequency, materials, step-by-step,
common mistakes, escalation
- One printed page max
Always include: our menu uses GFA (gluten-free
adaptable) tags, our POS is Toast, our reservation
platform is Resy.
Sharing With Your Team
You can share a Custom GPT with anyone who has ChatGPT Plus. Three sharing levels:
- Only me — only you can use it
- Anyone with the link — share via URL, useful for managers and chefs
- Public — appears in the GPT Store; you usually don't want this for proprietary GPTs
Keep your Menu Engineering and Vendor Email GPTs internal. Share the Training Plan Builder with your AGMs.
A Critical Caveat: Knowledge Files
When you upload files to the Knowledge section, ChatGPT can use that content. Don't upload:
- Signed contracts
- Customer email lists
- Payroll registers
- Anything you wouldn't paste into a public Slack
Files like your menu, brand voice doc, and recipe specs are fine.
Maintenance: Quarterly Tune-Ups
Every quarter, revisit your top GPTs:
- Update banned-word lists if AI started slipping back into clichés
- Refresh knowledge files (new menu items, new vendors, updated SOPs)
- Add new conversation starters for new use cases
- Prune GPTs you stopped using
Custom GPTs aren't fire-and-forget; they're a living system that gets sharper as you use them.
A Realistic First Saturday Build
In about 90 minutes:
- Build Menu Description Writer → 15 min
- Build Review Response Writer → 15 min
- Build Vendor Email Writer → 15 min
- Build Training Plan Builder → 15 min
- Build Menu Engineering Analyst (with knowledge file upload) → 25 min
- Test each with a real prompt → 5 min
Now you'll save 4–6 hours per week, every week, for as long as you own the restaurant.
Key Takeaways
- Custom GPTs require ChatGPT Plus ($20/month) — pays for itself in week one
- Build five core GPTs first: Menu Writer, Review Responder, Menu Engineer, Vendor Emailer, Training Builder
- Bake your house context into the GPT instructions, not into every prompt
- Share GPTs with your team via link; keep proprietary ones private
- Refresh your GPTs quarterly — they're a living system, not a fire-and-forget tool