Too Expensive Is A Verdict, Not A Price

Somebody told you your restaurant is too expensive. Maybe it came in a review, maybe from a Guest at the door, maybe from a regular who has quietly gone from weekly to monthly, maybe from your own lead who hears it at the table and finally repeated it to you.

You did what the industry trained you to do. You looked at the price. You compared yourself down the street, you reconsidered the entrée range, you talked about a value item, you thought about a happy hour, you asked whether the portion could carry a lower number. Every one of those responses treats the sentence as a report about a number.

It is not a report. It is a verdict. The Guest performed a calculation between what they paid and what they got, and the calculation came out negative. The number was an input to that calculation and it was almost never the deciding one, which is why operations at the same price point in the same market get opposite verdicts from the same Guests.

Which means the sentence tells you the result and hides the cause, and there are four different causes that produce identical wording. Cutting the price answers one of them. It makes two of them measurably worse. And the fourth one it cannot touch at all.

Why That Is Not Just Semantics

The word-game objection here is stronger than usual, because price is a real number and a Guest who says too expensive did in fact look at your menu. So test the reframe the way you would test any other claim: does it send you somewhere different to work.

If too expensive is a price report, the work is on the menu, in the costing, in the range, against the competition. That work is all downstream of the plate.

If too expensive is a value verdict, the work is on everything the Guest weighed on the other side of the scale — what the room was like, whether the pacing was right, whether the cast could explain anything, whether the promise the operation made at the door matched what showed up, whether anybody noticed when something went wrong. The price is one term in that equation and the only one you can change without changing anything real.

Same complaint, two entirely different addresses for the work, and only one of them can produce a Guest who stops making the calculation at all.

That is why I will not open a pricing conversation with the menu, and why the first thing I want is not your price list but the last twenty things a Guest said about your operation.

The First Cause Is Illegibility

The most common version of too expensive is not a complaint about the amount. It is a complaint that the Guest could not see what they were paying for.

Value has to be legible or it does not count. A Guest cannot audit your food cost, cannot see the cost of the produce, does not know what you pay your kitchen manager, and has no idea what the rent is. What they can read is everything the operation put in front of them, and that read happens whether you designed it or not. The condition of the room. Whether the table was ready. How long the gap between courses ran. Whether the person taking the order knew anything about the food. Whether the plate looked like the money. Whether anyone acknowledged them by anything other than a table number.

When those reads come back thin, the check reads as expensive at any number, because there is nothing on the other side of the scale. And when they come back rich, the same check reads as fair or even generous. This is why an operator can charge more than the place down the street, for demonstrably similar food, and never once hear the complaint.

Illegibility is the cheapest of the four causes to fix and the one operators skip, because fixing it is unglamorous and does not show up as a strategy. It is pacing. It is the cast knowing the menu well enough to make a real recommendation. It is the room being in the condition you would want it in if the owner were coming. None of that requires capital and all of it moves the verdict.

That is why the first thing I test is legibility, not elasticity, and why I will spend a full period on what the Guest can actually perceive before I let anybody model a price change.

The Second Cause Is A Promise That Does Not Match

The second version is a positioning mismatch, and it usually arrives from Guests who came once.

Every operation makes a promise before anybody sits down. The exterior makes it. The name makes it. The website makes it. The photographs make it. The neighborhood makes it. The price band makes it. By the time a Guest walks in, they have already formed an expectation of what class of experience this is, and they will grade what happens against that expectation rather than against anything absolute.

Price a Guest into one register and deliver another and you get too expensive with total reliability, even when the delivery was competent. A fifteen-dollar plate delivered as a fifteen-dollar plate is fine. A fifteen-dollar plate delivered where the promise implied a twenty-eight-dollar experience is a bargain and gets talked about. A twenty-eight-dollar plate delivered where the promise implied fifteen is an insult, and the Guest expresses that as the price because the price is the only part they can name.

The mismatch also runs the other direction, which nobody complains about and which costs you just as much. An operation delivering well above its promise gets a Guest who is pleased and a check that never reflects what was actually produced. You are underpaid for real work, permanently, and the market reads your quality from your number rather than from your operation.

So the question is not whether your price is high. It is whether your price, your promise, and your delivery are pointed at the same register. Any two of those in agreement and the third out of line produces the complaint.

That is why I read your promise and your delivery as one system before I will discuss what the number should be, and why I have told operators to raise a price rather than cut it more often than they expect.

The Third Cause Is That The Guest Is Right

The third version is the one this industry does not want on the page. Sometimes too expensive means the operation is extracting, the Guest can feel it, and the complaint is accurate reporting.

You know the moves because the trade has normalized every one of them. The portion that came down while the price held. The protein grade that quietly changed. The side that used to be included and is now an upcharge. The bread that became a line item. The fee added at the bottom of the check under a name that suggests it goes somewhere it does not. The menu price that no longer predicts the total. The reservation that requires a deposit that was never really about the reservation.

Each of those is defensible in isolation and each one is a small transfer from the Guest’s side of the exchange to yours, executed where they cannot audit it. The Guest cannot itemize what happened, which is exactly the point of the move. But they can feel the spread, and the sentence they have available for that feeling is too expensive.

This is where the discount response becomes actively destructive rather than merely useless. An operation that has been extracting and then answers the complaint with a promotion has added a second manipulation on top of the first. The Guest now gets a lower price on a diminished thing, learns the price was never real, and concludes correctly that the number was always negotiable. You have confirmed their suspicion and trained them to wait.

I will not help an operator make this class of complaint go away, because the complaint is doing its job. The work is to stop the extraction and restore what was quietly removed, which usually costs margin in the period it happens, and I will say so before we start rather than after.

The Fourth Cause Is That The Relationship Thinned

The fourth version comes from Guests who used to come and now come less, and the price on their check has often not moved at all.

Price is invisible inside a strong relationship. The Guest who comes twice a week is not running a value calculation on the way in, because the calculation was settled a long time ago and nothing has happened to reopen it. When frequency declines for any reason, the calculation reopens, and the moment a Guest is deliberating again, a number they never questioned starts to feel wrong. Nothing about the price changed. The thing on the other side of the scale got lighter.

Which means this version of the complaint is a lagging indicator of something that already happened. A cast member the Guest was attached to left. The pacing slipped on the nights they come. A recovery went badly and nobody addressed it. The room got tired. The regular who is now telling you that you are too expensive is reporting an event from three months ago, and the price is where the report finally surfaced.

I have written about the frequency mechanism elsewhere and will not re-run it here. What matters for the operator is the diagnostic order: when the complaint comes from a Guest with history, the price is the last place to look and the visit pattern is the first.

That is why I ask who said it before I ask what they said, and why a complaint with no cohort attached to it is not usable data.

The Complaint Is A Record, Not The Event

All four versions share one property that governs how you should treat any of them. The sentence arrives after the visit that produced it, which makes it a record rather than the work.

The verdict was formed during the visit, in a sequence of small reads the Guest performed without narrating any of them. By the time it reaches you as a sentence, the conditions that produced it are over, the Guest has already decided, and in most cases they have already adjusted their behavior. Which is why the operator who manages by complaint is always one period behind, and why the absence of complaints is not evidence of anything. Most Guests do not tell you. They simply stop, and stopping does not generate a sentence.

That has a direct consequence for where you look. Your reviews and your comment cards are the lagging record of a value read; your leading indicators are the things the Guest is reading in real time on your stage tonight. Pacing, table readiness, whether the cast can answer a question about the food, whether a failure got acknowledged. Those are visible on the shift and free to read.

That is why I do not build engagements around collecting more feedback, and why the read I install runs on the stage rather than in a survey.

Discounting Answers The Complaint By Confirming It

Whatever the cause, the industry’s reflex answer is the same, so it is worth naming precisely what that answer does.

A discount tells the Guest that the experience is transactional and that transactions should cost less. It does not dispute their calculation. It concedes it. You have agreed that the value did not justify the number and offered to fix the number, which teaches them the number was arbitrary and that patience is rewarded.

Then the mechanics take over. The discount that filled the room has to be repeated to fill it again, and repeated deeper once the pattern is learned, because a Guest who has been trained on a price cannot be untrained by removing it. That is accumulation, and accumulation needs a rising dose to hold ground it already has. Remove the discount and the volume goes back, minus the Guests who now read your full price as the inflated version.

There is a narrow legitimate use for a price move, and it is worth distinguishing. A deliberate, bounded, fully costed promotion with a specific hypothesis and a measurement attached is a tool. Structural discounting baked into how the operation fills its room is a dependency wearing the costume of a strategy. The test is simple: can you name the date it ends and what you expect to have learned.

That is why I will build you a price test with a hypothesis and a period attached, and why I will not build you a value menu.

Your Cast Cannot Defend A Price They Cannot Explain

The last mechanism runs on the People side and it decides whether any of the above holds up in the room.

Your cast hears too expensive before you do, and they have to respond to it in real time. What they say in that moment is not a training question, it is an architecture question. A cast member who understands what the operation is producing, who has been told why the price is what it is, and who has the authority to do something about a bad experience will defend the value without sounding defensive. A cast member with none of that will agree with the Guest, out loud or with their face, because agreeing is the only socially available move when you have no answer.

Watch what happens next, because this is the part that compounds. The cast member who agrees with the complaint learns that the price is indefensible. That belief shows up in how they describe the specials, whether they recommend the higher-margin item, whether they suggest a second round, and whether they stay. And the reward structure usually finishes the job: if they are paid and measured on throughput, they will resolve every value question in favor of speed, which produces exactly the thin experience that generated the complaint.

So the complaint at the table is a read on your reward structure and your information flow, not on your menu. That loop closes in both directions, and it is invisible if you only look at the menu.

That is why I read what your cast has been told and what they are paid for before I take a pricing question seriously.

The Diagnostic

Run these before you touch a number. Each has a specific move and a plain read.

Test one — the cohort test. For your last twenty instances of the complaint, sort them into three buckets: never been before, been a few times, has history with you. First-timers point at promise mismatch. Regulars point at relationship decline. A spread across all three points at illegibility, which is the only cause that hits every cohort at once.

Test two — the legibility test. Sit at your own table on a busy night, order like a Guest, and time it. Write down everything you could perceive without knowing anything about restaurants. If your list is short, the Guest’s list is shorter, and the check has nothing to weigh against.

Test three — the promise test. Look at your exterior, your name, your photographs, and your price band as a stranger would, and write the sentence they would form about what class of experience this is. Then compare it to what actually happens at the table. A gap in either direction is the complaint’s address.

Test four — the removal test. List everything that has quietly gotten smaller, cheaper, or newly chargeable in the last two years. Portions, grades, inclusions, fees. If the list is not empty, some portion of the complaint is accurate reporting and no messaging fixes it.

Test five — the total test. Order from your own menu as a Guest and compare what the menu implied to what the check said. Any gap the Guest cannot predict from reading the menu is a place where the exchange stopped being transparent.

Test six — the defense test. Ask three cast members separately why an item costs what it costs. If you get three different answers, or an apology, or a shrug, the price is undefended on the stage every shift.

Test seven — the reward test. Name what your cast is measured and paid for. If the answer is throughput, they are being paid to produce the thin experience that generates the complaint, and the pricing conversation is the wrong conversation entirely.

How the score sorts. Fail one or two and you have a specific repair with a clear address. Fail four or more and the complaint is not about any single thing, it is the accurate output of the architecture, and no price move will hold against it. Pass all seven and hear the complaint anyway, and you have a genuine positioning question about which market you are in, which is the rarest and most solvable version of all of this.

What You Do Monday Morning

Take your last twenty pieces of Guest feedback, from anywhere. Reviews, comment cards, what your lead has repeated to you, the direct messages, the conversation at the door.

Read each one and write down what the Guest was reading when they formed that opinion. Not what they said. What they were looking at. Pacing. A cast interaction. The condition of the room. The gap between the photograph and the plate. The fee at the bottom. The person who used to be there and was not.

Then count how many of the twenty are actually about the amount of money, in the sense that a different number would have changed the verdict.

For most operations that count comes out at three or fewer out of twenty. That is your answer, in your own Guests’ words, about whether you have a pricing problem. And the seventeen tell you where the work is, in order of how often they show up.

The Closer

The Guest was never running your numbers. They were weighing what happened against what it cost, reaching a verdict, and then handing you the only word the language gives them for a bad one.

Answer the word and you change a number. Answer the verdict and you change what goes on the other side of the scale, which is the only side that compounds and the only side that is actually yours.

Your price is a positioning statement. Make sure the operation is saying the same thing.

Digging Deeper

Every term used above is defined in my Knowledge Base: https://kb.jeffreysummers.com/

Terms used: Menu Arbitrage, Transactional Arbitrage, Transactional Cost-Plus, Guest Menu Read, Guest Contract, Two Roads, Reward Structure Architecture, Static Decline, Hacksterism, The Lost Opportunity Tax

The architecture taught in full, fundamental by fundamental: https://physics.jeffreysummers.com/

The Road 1 arbitrage prosecuted where it lives in the wild: https://hacksterism.jeffreysummers.com/