Skip navigation
A RESTAURANT DOESN'T HAVE A LABOR COST PROBLEM. IT HAS A JULY PROBLEM.
0:00 / 0:10

A RESTAURANT DOESN'T HAVE A LABOR COST PROBLEM. IT HAS A JULY PROBLEM.

tenzo

@0xTenzo3.6K followers

Visit on X

33,749 views

A RESTAURANT DOESN'T HAVE A LABOR COST PROBLEM. IT HAS A JULY PROBLEM. On paper this makes no sense to me. Waiting tables is the cheapest labor in the building, and half of it gets paid in tips the owner never touches. You don't spend real money to replace the smallest line on your payroll. So if I were buying one, it wouldn't be about the wage at all. What actually breaks a restaurant is that somebody quits in July, the schedule falls apart, and the owner spends his week interviewing instead of running the place. Front of house turnover is relentless and it never lets up. That's the thing a machine fixes. Not cost, continuity. Where I think it falls down is the room. Half the reason people go out is someone noticing an empty glass before they do, reading the table, deciding you're ready for the check. That's the service. A tray on wheels does none of it, and no amount of iteration gets it there soon. So my honest read is these live in food courts, chains, and high volume rooms where nobody expected service in the first place. In a place you'd actually book, it makes the experience worse. Anyway, what do you reckon, real or AI? I think it's AI. Nobody at those tables reacts to the thing, and in a real room every phone would be up. The article below breaks down what these machines actually cost today and where the money in this is really moving.

Comments

Comments from the original post on X (Twitter)

No comments yet