Low-carb at a business dinner: what to order and what to skip

Why hidden carbs at a business dinner come from sauces, not steak

A low-carb business dinner is entirely manageable, the plate structure is simple: a plain protein, a non-starchy vegetable, and you're done. The steak, the grilled fish, the lamb chops? None of those are the problem. The problem is what's on top of them.

Sauces, marinades and dressings are where carbohydrates hide in plain sight at a corporate restaurant. A glaze is a sugar reduction. A "house sauce" is often a sweetened reduction built on a starch base. Teriyaki reads as a protein preparation; it eats like a dessert. The gap between what a menu describes and what's actually in the dish is widest precisely here, as guidance on hidden carbs in 15 Middle Eastern sauces, ranked makes clear, the variation across sauces is dramatic, and the labels give almost nothing away.

The other underappreciated risk is deciding under pressure. When a client is talking, the sommelier is waiting, and the table is ordering around you, the cognitive load of scanning a menu for carbohydrate risk is genuinely high. Arriving with a decision already made removes that pressure entirely and keeps your attention where it belongs: on the relationship, not the plate.

This article gives you three tools to do that. First, a five-minute pre-order routine. Second, a cuisine-by-cuisine reference table covering the most common business-dinner settings. Third, a vocabulary of red-flag menu words that lets you screen any menu silently, in seconds. Guidance on managing carb exposure when eating out professionally consistently points to the same conclusion: restaurant dining in a business context is navigable, with the right framework in place before you sit down.

How to build a five-minute pre-order plan before the meal

The routine takes one dedicated window before you leave, five minutes at your desk or in the car park is enough. Here's the sequence that works.

• Pull up the menu before you leave. Most corporate-dinner venues publish their menu online or via a QR code linked from their website. Find it, open it, and give yourself time to read it without a client across the table.
• Scan the menu with Eatova (formerly AlignEat). Eatova sorts each dish on a menu into Safe, Ask and Avoid for your dietary profile, enabling pre-arrival decision-making without analysis at the table. Upload a photo, paste the URL, or scan the QR code directly, the output is a colour-coded shortlist specific to your low-carb or keto parameters, not generic advice. You don't need to read the full menu at all; you read the Safe column.
• Lock in your protein anchor and vegetable side. Choose one grilled, roasted or pan-seared protein as your default, paired with a non-starchy vegetable, steamed greens, a dressed salad without croutons, roasted asparagus. That's your order. Done.
• Identify one Ask dish as a fallback. Pick a dish you'd genuinely enjoy if the sauce can come on the side or be swapped out. This gives you a confident alternative without having to think on the spot. If you're unsure whether the kitchen will actually accommodate the change, the article when to trust "we can accommodate" walks through exactly how to judge that call before you make it.

When you arrive with a decision already made, opening the menu is a formality. You order in ten seconds, close the menu, and return your full attention to the client. That's the whole point.

What to order at a business dinner, by cuisine

The protein-and-vegetable framework in the low-carb restaurant ordering principles from Atkins applies across cuisines, but the specific anchors and traps vary significantly by kitchen. Use this as your pre-arrival reference.

The Middle Eastern column deserves a closer look if this is a regular dining context for you. For a full breakdown of what to order and what to pass on, see our guide to low-carb at a Lebanese restaurant: what to order, what to skip.

Menu words that signal hidden carbohydrates

You don't need the ingredient list. You just need to know which words on a menu reliably signal a carbohydrate load, and the Eatova framework has identified the core set: glazed, teriyaki, crispy, battered, honey, molasses. These are the Red Flag Menu Words for hidden carbs, each one tells you something specific about what's in the dish before you order it.

• Glazed, a reduction almost always built on sugar, applied as a coating to proteins and vegetables alike. A glazed duck breast is a sweetened duck breast.
• Teriyaki, a specific form of sugar reduction combined with soy; the base protein is irrelevant once this word appears.
• Crispy, nearly always signals a flour or breadcrumb coating, not just a cooking technique. Crispy chicken, crispy tofu, crispy calamari: all battered.
• Battered, flour-based coating explicitly. No ambiguity here.
• Honey, a direct sugar addition in marinades, dressings and finishing sauces. Honey-roasted, honey-glazed, honey mustard: all carry meaningful carb loads.
• Molasses, common in BBQ rubs and slow-cooked preparations; a concentrated sugar source that doesn't announce itself loudly on the menu.

Extend that core list with secondary watch-words: house sauce, sweet chili, plum sauce, BBQ, candied, crusted. These appear frequently on corporate restaurant menus and carry the same risk. Crucially, these words apply to sides and accompaniments just as much as the main protein, glazed carrots, honey-roasted parsnips, and candied beetroot are easy to overlook when you're focused on the protein column.

One objection comes up regularly: asking about sauces feels awkward at a client dinner. It draws attention to a dietary choice you'd rather keep private. The answer is that knowing this vocabulary means you often don't need to ask at all. You scan the menu, identify the safe preparations, and order confidently without a single question about ingredients. When a swap is genuinely needed, the request is brief and unremarkable: "Could the sauce come on the side, please?" That's a one-sentence ask that any front-of-house team handles without a second thought.

Eatova sorts a restaurant menu into Safe, Ask and Avoid for a low-carb profile.

How to scan the whole menu quietly before anyone notices

Everything covered so far assumes you have time to think. Eatova is the tool that compresses that thinking into a few minutes before you walk in the door.

It works from whatever format the restaurant uses: a photo of the printed menu, a QR code, a PDF, or a direct URL. That means the scan can happen in the car park, at your desk, or during the commute, not at the table. By the time you sit down, the analysis is done. You already know which dishes are Safe, which are Ask, and which to avoid, all mapped against your specific low-carb or keto profile rather than a generic nutritional template.

Accuracy matters when the stakes involve a client relationship. Eatova's menu-decoding accuracy improved from 79% to approximately 93%, measured across a simultaneous test of 300 restaurant menus covering handwritten, chalkboard and QR formats, against roughly 500 allergens (Eatova internal accuracy testing, 300 menus, 2026). That's the number that makes the output trustworthy enough to act on without a second opinion from the waiter.

The discretion dimension is what makes this genuinely useful in a professional setting. There's no menu interrogation, no visible app use during the meal, no server conversation about macros or intolerances. The tool works in advance, and its output stays on your phone. You order the way everyone else at the table orders, directly and without explanation. If you want to understand more about how the scanning and matching process works, how Eatova reads a menu walks through the logic in detail.

Eatova dish detail flagging dishes to ask about to the server, as the app is not sure.

Staying social while you stay on track

The purpose of a business dinner is the relationship. Everything else, the menu, the wine list, the dessert trolley, is set dressing. Low-carb choices work best when they sit quietly in the background rather than becoming the topic of conversation, and with a decision already made before you arrive, they almost always do.

Declining bread or a shared starter is a moment that lasts about two seconds when handled correctly. A calm "I'm fine, thank you" moves the conversation on. So does a light redirect: "Let's order another round of the lamb" shifts attention to the table rather than to your plate. No explanation needed, no dietary autobiography required.

When the table is sharing and the spread is carb-heavy, protein-forward dishes and undressed salads can usually be navigated without drawing attention. The strategy is the same as for any shared-table format: take what works from the spread, eat it without comment, and stay engaged in the conversation. The same principles apply in higher-stakes group dining settings, if you regularly face similar social pressure around shared menus, our Friday brunch on a low-carb plan: the Dubai survival guide covers those scenarios in depth.

The single most effective habit, across all of these situations, is the pre-order mindset. When you've already decided what to eat, the dinner is just a dinner. The food becomes incidental to the conversation it's meant to support, which is exactly where your focus should be.

Frequently Asked Questions

What should I order at a business dinner on keto?

Anchor on a plain grilled, roasted or pan-seared protein with a non-starchy vegetable side, and request sauces on the side. Steakhouse ribeye, Japanese sashimi, tandoori lamb, and grilled fish at a French brasserie all work well, the protein is safe; the preparation is what to watch.

How do I avoid carbs in sauces I cannot see?

Scan for red-flag words before you order: glazed, teriyaki, honey, molasses, crispy, battered, BBQ and sweet chili all reliably indicate a carbohydrate load, even when the base protein looks safe. If the menu uses any of these terms, ask for the sauce on the side or choose a different preparation.

Can I ask about ingredients without making it awkward?

Yes, and often you won't need to ask at all. Knowing the red-flag vocabulary lets you screen the menu silently and choose a safe dish without raising the topic. When a swap is needed, "could the sauce come on the side, please?" is brief, specific, and handled routinely by any front-of-house team.

What if the table is sharing dishes?

Focus on protein-forward shared plates and take salads or vegetable sides without dressing. Avoid reaching for the bread, rice or sweetened dips and let the conversation carry the moment. A quiet "I'm fine with what's here" is enough, no explanation needed and no disruption to the table.