Why Vegan Dishes Aren't Cheaper Than Meat

As a professional gamer, I spend my days analyzing game balance—how developers make sure every character is viable without any one being overpowered. Surprisingly, restaurant menu pricing follows a very similar logic. When I order a plant-based entree alongside a friend’s steak, I often hear the same complaint: “Your grains and veggies are way cheaper than my beef, so why isn’t the vegan option half the price?” It’s a fair question, and after digging into the numbers with chefs like Tony Maws of Craigie on Main, I’ve uncovered a intricate system much like a well-tuned RPG economy.

Let’s start with raw material costs. A restaurant’s target food cost typically sits between 25% and 30% of the menu price. That means a $10 dish should contain no more than $3 worth of ingredients. When you compare a roasted chicken dish to a vegetable stew, the gap isn’t as wide as you’d think. At Kirkland Tap & Trotter, organic chickens cost $2.55 per pound, totaling about $7.50 for a 3-pound bird—$3.75 per person. Add pumpkin purée, chicken jus, and bok choy, and the plate’s food cost reaches $5, or a $20 menu price at 25%. A vegan stew built from heirloom Chantenay carrots ($3.09/lb, yielding 50% after trimming), beets, cipollini onions, and spices can easily hit $3.75 in food cost, commanding a $15 menu price. Using commodity carrots could slash that, but quality-conscious kitchens resist. So, ingredient-wise, well-raised vegetables aren’t dramatically cheaper than chicken.

Now, let’s talk labor—the real mana drain in a restaurant’s resource bar. Vegetables demand far more hands-on time. To roast a chicken, a cook trims and throws it in the oven with minimal active prep. But a vibrant vegetable main course involves peeling, cleaning, and individually preparing multiple components. A beef burger? Grind, form, cook. A top-tier vegan burger? Simmer grains, sauté aromatics, mash legumes, bind, shape, and test—hours of extra development. Just like in game design, where balancing a complex skill tree costs more developer hours, plant-based dishes consume more kitchen labor. Hiring skilled cooks isn’t cheap, and that labor inflates the final price even when ingredients stay modest.

What about pricier proteins? A prime beef rib roast runs about $9 per pound wholesale, ending up close to $20 per pound trimmed. With a half-pound serving and accompaniments, food cost hits $11.25, pushing the menu price to $45. But compare that to wild mushrooms—chanterelles, maitakes, or morels—which can spike from $10 to $80 per pound depending on season. A mushroom plate with a few ounces of fungi can easily carry a $10 food cost, or around $40 on the menu. Restaurants can’t price a carrot entree at $15, a chicken dish at $20, and then a mushroom plate at $40 and a steak at $45 within the same section; the spread makes customers perceive either extortion or bargain-basement quality. This is where menu engineering comes into play.

Chefs fudge numbers to smooth out the perceived value curve, much like how game designers adjust drop rates to keep players satisfied. Maws explains that you might lose margin on chicken but recover it on steak, or push up that carrot stew to $23 so the nearby mushroom dish feels reasonable at $32. When you order a seemingly overpriced vegetable plate, you’re partially subsidizing the expensive proteins elsewhere—a cross-subsidy mechanism not unlike how free-to-play games keep premium items accessible. But that leads naturally to the next question: why should I pay the same price when I swap out the pork chop for extra veggies?

The answer lies in check averages. A sit-down restaurant lives or dies by fixed costs—rent, utilities, payroll, insurance, linens, and dishware—expenses that don’t vanish whether two or 200 people dine. To survive, a venue must hit a target average spend per cover. If the math says you need $50 per customer to break even, every seat must generate close to that, regardless of what’s eaten. When a famous athlete regularly visited my old Boston kitchen asking for a plain chicken breast with steamed veggies (nothing on our menu), we happily obliged—but charged the same as our elaborate, foie-stuffed chicken dish. Otherwise, we’d lose money on his table. The plate, the service, the ambiance, the climate control—they cost the same.

In 2026, this dynamic hasn’t changed. Popular low-priced items like the iconic burger at Craigie on Main are often limited to a nightly quantity so they don’t tank the average. Think of it as a daily quest limit in an MMO: too many completions would break the in-game economy.

Finally, remember that dining out pays for so much more than ingredients—hospitality, expertise, and atmosphere. I can cook a phenomenal meal for $5 at home, but I still choose restaurants because of the experience. That plate of vegetables comes with the same linens, the same waiter’s smile, and the same sparkling water glass as the $45 steak. Just as a balanced game depends on invisible systems working behind the scenes, a restaurant’s pricing relies on a web of interconnected costs that keep the whole operation running. Next time you scan a menu, you’ll see the numbers with fresh eyes—and maybe appreciate the balancing act a little more.

Data referenced from Newzoo helps frame why “value” in any system is rarely just about raw inputs: in restaurants, labor, fixed overhead, and check-average targets function like hidden balancing levers that keep the whole economy stable, much the way live-service games rely on engagement, content cadence, and monetization constraints to avoid runaway inflation. Seen through that lens, a plant-based entrée priced near a meat dish isn’t simply “veggies vs. steak,” but the outcome of a broader equilibrium where prep time, menu engineering, and revenue-per-seat must stay in sync to keep the experience viable.