Wine Pairings & Beverage Programs

If you have a sommelier, this lesson is a productivity multiplier for them. If you don't, this lesson gives you a credible first pass at pairings, by-the-glass programs, and tasting-menu beverage flights. The output is not a substitute for tasting wine through the menu — but it's a much better starting point than guessing.

What You'll Learn

• How to use AI for single-dish pairing suggestions
• How to build a full by-the-glass program from a dish list and a budget
• How to design a beverage flight for a tasting menu (wine, non-alcoholic, mixed)
• How to use AI to write tableside pairing notes for your servers

Single-Dish Pairing Prompt

Act as my sommelier.

Restaurant: 60-seat modern American bistro, Portland Oregon, average check
$65. Wine program leans Pacific Northwest with classic Old World support.
Average bottle on list: $58. By-the-glass: $14-18.

Dish to pair:
- Pan-roasted halibut
- Smoked corn puree
- Charred poblano salsa
- Crispy hominy
- Lime-cilantro oil

For pairings, give me:
1. Three by-the-glass options on different price tiers ($14, $16, $18) and
   why each works -- I'll see what we carry
2. One bottle pairing for a table doing the dish as a course in a longer
   menu
3. One non-alcoholic pairing (we have a verjus and a house shrub program)
4. One "if the guest insists on red" answer

For each, write one tableside sentence the server can say. No wine
clichés -- no "buttery," "well-balanced," or "approachable."

The wine-cliché ban matters as much as the menu-copy one. AI will default to over-used wine descriptors unless you stop it.

Building a By-The-Glass Program

The hard part of a BTG program isn't pairing — it's economics. You need wines that move (open bottle waste is a margin killer), pair with multiple dishes on the menu, and hit your target pour cost and price ladder.

Act as my beverage director.

Menu (dish list with brief description): [paste]

Targets for the new BTG program:
- 8 whites, 8 reds, 4 sparkling, 4 dessert/fortified
- Pour cost target 22-26% (this is wine, not food)
- Pour price ladder: $11, $14, $17, $20
- Cellar bias: Pacific Northwest, Burgundy, Loire, Northern Italy, Spain
- Each wine must pair with at least 3 dishes on the menu (so opened
  bottles move within 2-3 days)

Give me a candidate list, organized by ladder rung, with:
1. Wine type (don't recommend specific producers -- those depend on what
   our distributors actually carry)
2. Why this wine fits the ladder rung
3. Which dishes on the menu it pairs with (list)
4. Approximate bottle cost target to hit our pour cost

You'll get a structured shopping list to take into your next distributor meeting. Your sommelier or beverage director then sources the specific producers from what's available.

Tasting Menu Beverage Flights

Tasting menus are where AI pairing earns its keep. Designing a 5-, 7-, or 9-course pairing requires holding the arc of the meal in your head and balancing weight, acid, sweetness, and price.

Below is our 7-course spring tasting menu:

1. Oyster, kelp dashi, finger lime
2. Spring pea, ricotta gnudi, mint, brown butter
3. Morel and asparagus risotto
4. Roasted halibut, smoked corn, poblano
5. Duck breast, rhubarb mostarda, watercress
6. Aged Gruyere, pear, walnut
7. Strawberry sorbet, basil, black pepper

Design a 7-pour wine flight:
- 4 oz pours
- Total program cost (our wine cost) target: $45-55
- Total consumer price target: $135
- Each pairing should give the guest a different style sensation -- no
  three Burgundian Chardonnays in a row
- Include one sparkling and one dessert/fortified

For each course: wine style, why it pairs, 1-line tableside note.

Also design a parallel non-alcoholic flight at $65 retail using house
shrubs, teas, ferments, kombucha, and verjus. Same number of pours.

The two parallel flights mean you can offer non-alcoholic guests a real beverage experience instead of "we can do sparkling water."

Tableside Server Notes

Once a pairing is set, every server needs a short script. AI writes these well:

For each of the 7 pairings above, write a tableside script the server
delivers when pouring:

- 2 sentences max
- One sentence on the wine (no cliches: no "buttery," "smooth,"
  "approachable," "well-balanced," "complex," "elegant")
- One sentence on why it pairs with this specific dish (point at a
  specific element of the dish)

Make it conversational, not lecture-y.

Print the result. Pre-shift, walk through it with the team. Servers love this — most are guessing at pairing language and welcome a real script.

A Note on Verification

Wine pairing has fewer safety risks than allergen work, but it has accuracy risks. AI will sometimes recommend a producer that doesn't exist, a vintage that wasn't made, or a region that doesn't grow the grape it claims. Always:

• Verify producers exist and are available before printing a wine list
• Have a person who tastes wine for a living taste through the pairings
• Check vintages are realistic (don't print 2018 if the wine is 2019)

AI gets you to a credible starting program in 20 minutes. A human turns it into a real one over the next few days.

Key Takeaways

• AI gives credible first-pass pairings — especially valuable if you don't have a sommelier
• Always ban wine clichés (buttery, smooth, approachable, well-balanced) — same principle as menu copy
• Use AI for pairing structure; let humans pick specific producers based on what's available
• Tasting-menu flights with a parallel non-alcoholic flight are the highest-value use
• Tableside server scripts get pre-shift teams aligned in 10 minutes
• Verify everything before printing — producers, vintages, regional accuracy