View Categories

5.X The Price You Set Is Not Always the Price You Realize

6 min read

5.X — The Price You Set Is Not Always the Price You Realize #

Every operator sets prices deliberately.

Food cost analysis. Competitive benchmarking. Positioning decisions. The menu goes through multiple rounds of review before it prints. Every price reflects a decision about value, cost, and what the experience is worth.

And then service starts.

And the cast member who is challenged by a Guest on the price, or who senses dissatisfaction and decides a comp will fix it, or who is worn down by a persistent complaint and gives a discount to make the table stop talking — that cast member has just widened the gap between the price the operator set and the price the operation realized.

In B2B sales, this gap is called the pricing capability gap. The recommended price is the value-based price — what the offering is actually worth to the customer. The realized price is what gets charged after the sales rep finishes negotiating. The gap between them is the measure of how well the organization can defend the price it deserves.

Restaurants have the same gap. Most operators have never measured it.

The Founder Problem #

The operator who built the menu and knows why every item is priced the way it is — who understands the cost structure, believes in the value delivered, and can explain in thirty seconds why the $48 entrée is worth $48 — can defend that price in any Guest conversation.

The cast member who took the order and delivered the plate has none of that conviction and none of that knowledge. They know the price. They don’t know the argument for it. When a Guest challenges the value, or expresses dissatisfaction, or simply stares at the check with visible discomfort — the cast member has no defense. The path of least resistance is a comp, a discount, or an apology that implies the price wasn’t justified.

This is the operator’s pricing capability problem: the conviction and knowledge that justify the price live in the operator. They don’t travel automatically to the cast.

The menu’s prices are defensible. The organization’s ability to defend them is not built by default.

Where the Gap Appears #

The pricing capability gap in a restaurant shows up in three places.

The comp. The dish that gets sent back and comes off the check without a conversation about what specifically went wrong, what the recovery should look like, and whether the comp is the right response or a reflexive one. Every unjustified comp is a pricing capability failure — the cast member chose the easy resolution over the right one, and the operator absorbed the cost without understanding what produced it.

The discount. The table that pushed back on the check and got 20% off because the cast member didn’t know what else to do. Or the manager who was called over and gave something away to make the conversation end. These are not service recoveries. They are pricing failures in service recovery clothing.

The no-show cost. The reservation that didn’t show and cost the operation a covered table on a full night. The Guest who ordered delivery, paid the platform commission, and never built a direct relationship. The regular who hasn’t been back in six weeks and nobody knows why. These are all realized price failures — the operation didn’t capture the value it created because the Guest relationship wasn’t managed toward retention.

Building the Pricing Capability #

Three things close the gap between the price set and the price realized.

Price conviction in the cast. The cast member who knows why the price is what it is can defend it. Not with a scripted answer — with genuine belief in the value being delivered. This is a training and development decision. The operator who never explains the pricing rationale to the cast has guaranteed a pricing capability gap at every service interaction where a Guest challenges the value.

The menu tasting that includes the cost conversation. The pre-shift that connects the price point to the experience standard it represents. The development conversation that gives the cast member the language to say “the ingredients in this dish are sourced specifically because they deliver a quality you can taste — and that’s what’s reflected in the price.” These aren’t sales scripts. They’re the knowledge transfer that makes the cast member a pricing defender rather than a pricing liability.

Comp and discount authority. The cast member who can comp anything, anytime, without a conversation is operating without pricing governance. The operator who has never defined what a comp is for — what it should accomplish, when it’s warranted, and what it costs — has given away pricing authority without knowing it.

Road 2 comp policy is simple: a comp is a recovery tool, not a conflict resolution tool. It repairs a genuine service failure. It does not make an uncomfortable conversation end faster. The cast member who understands the difference between those two things — who has been developed to use the comp deliberately rather than defensively — is the one whose pricing decisions compound the Guest relationship rather than spending it.

Price realization tracking. The operator who never asks “what percentage of our menu price did we actually realize last period?” doesn’t know the size of their pricing capability gap. The comp total as a percentage of revenue. The discount frequency. The average check versus the theoretical check on fully-priced covers. These are the numbers that reveal whether the pricing decisions are being executed or eroded in the field.

The gap between what you charge and what you receive isn’t always a pricing problem. Often it’s an execution problem — the organization’s capability to realize the price it set. And like every operational problem, it doesn’t get managed until it gets measured.

Set the price deliberately. Build the capability to defend it. Measure the gap between the two.

The difference between a business that prices well and one that captures that pricing is the work that happens after the menu prints.

→ See also: Fundamental 3: People — 3.X Leading People vs. Using Them The cast member’s ability to defend the price is a development outcome. The operator who trains the cast on the menu but never develops their understanding of why the price reflects the value being delivered has built a pricing liability into every service interaction. Development — not just training — closes the pricing capability gap at the cast level.

→ See also: Fundamental 5: Profit — 5.X What You Say When You Raise the Price The pricing capability gap and the price communication gap are two sides of the same problem. The operator who can’t explain why the price is justified internally — to the cast — will struggle to communicate it externally to the Guest. Both require the same foundation: genuine conviction in the value being delivered.

Leave a Comment

This site uses Akismet to reduce spam. Learn how your comment data is processed.