A legitimate tool amplifies a specific human capability the operation has already built. It takes something the operation does well and makes it bigger, faster, more consistent, more reachable. It does not create the capability. It does not substitute for it. It does not camouflage its absence. It multiplies what is already there.
Amplification passes. Substitution fails.
The LTO makes the case cleanly. A limited-time offer used as a menu device amplifies — it showcases a capability the operation has already built. A chef’s range. A kitchen’s technique. A sourcing relationship the operation has cultivated. The LTO is the amplifier; the capability is what it amplifies. The Guest sees the operation displaying what it can do. Nothing is taken away; something is put on the table that wasn’t there before.
A discount dressed as an LTO is a different object. The capability being amplified is nonexistent. The tool is carrying a traffic need, not a capability. Same surface, opposite deployment, opposite math.
The rising-cost argument collapses against the same logic. Operators under cost pressure reach for gimmickry and call it survival. Run the subtraction. Rising costs already compress margin. The gimmick then subtracts Guest expectation, connection, trust, and the standard itself — stacked on top of the margin already under pressure. Two minuses do not make a plus. They compound.
The honest move under cost pressure is the opposite one. Every dollar of cost pressure is a reason to make the operation more undeniably worth the price, not less. Gimmickry says the Guest won’t pay what this now costs, so pretend it costs less. The standard says the Guest will pay what this costs because what we deliver is worth it. Same pressure. Opposite response.
Run the two operators forward five years. The gimmick operator has trained the Guest to expect discounts and now delivers a compressed product at a rented price — smaller margins, smaller standards, a Guest base that leaves the moment the next operator offers a steeper discount. The standard operator has trained the Guest to expect excellence and delivers it at a price the Guest pays without flinching — holding margin through the squeeze, holding the Guest through the squeeze, more defensible at the end of it than at the beginning.
Cost pressure did not pick which operator survived. Response to cost pressure did.
Build the capability. Name it — in one sentence, without hiding behind the tools. Then ask what tool would let more of that capability reach more Guests. Install the tool as the amplifier of the capability you can already name. If you cannot name the capability, the tool is standing in for something you have not built. And the operation is being run by the tool instead of running it.
Build first. Amplify second. Subtract nothing.



