Utpal, good piece. Two notes from the restaurant lane where I've been working this ground for a while.
First, what you're calling "reverse coupon" is a mechanism I've taught operators for years as Reverse Discounting. Same structure — the offer self-selects the customer who costs you the most and rewards the behavior you're trying to reduce. I've mostly applied it to straight discounts and loyalty programs. You've extended it to unlimited offers and the fit is clean.
Second, the pattern where the operator introduces targeted restrictions after the vulnerability lands — smaller plates, throttling, cancellation friction, weekly caps — has a name too. I call it Consent Erosion. The terms the customer thought they bought get quietly rewritten under them. Every example you cite ends with the customer feeling like the terms changed on them, because they did. It manages the exposure but degrades the relationship in the process.
Where I'd push: I don't read the vulnerability as a property of the pricing structure. I read it as a property of the operator building a relational-sounding promise ("come, be welcomed, eat freely") on top of transactional unit economics ("every plate costs me money"). The heavy user isn't exploiting the structure. They're running arbitrage on the gap between what the operator signaled and what the operator was actually running underneath. ClassPass's Payal Kadakia named it exactly: "What kind of business would we be if we wanted our members to work out less to reduce costs?" That's not a pricing failure. That's a business-model failure that pricing was asked to cover for.
Thank you, Jeffrey. This is very insightful, and I especially like your terms Reverse Discounting and Consent Erosion. In my experience, at least, the restaurant industry is far more sophisticated and nimble in considering and trying to solve these issues. I do quite a bit of work in the B2B space, and we often find that we are a bit behind some consumer industries in thinking through these things, and can learn from them.
My earlier comment named the drift — smaller plates, throttling, cancellation friction, weekly caps — as Consent Erosion. That was half the mechanism.
The other half is what Lesson 3 actually prescribes: the operator banking the gap.
I call that Consent Arbitrage.
Erosion is passive. Something happening to the Guest as the operation drifts. Arbitrage is active. The operator (or the vendor, or the system) deliberately monetizing the space between the consent that was given and the consent that currently exists.
The two coexist. Erosion opens the gap. Arbitrage exploits it.
Lesson 3 doesn't defend the offer. It teaches the arbitrage — how to keep the signaling of an unlimited relationship while quietly harvesting the margin created by degrading it. That's not a pricing fix. It's a positioning failure being monetized rather than corrected.
Utpal, good piece. Two notes from the restaurant lane where I've been working this ground for a while.
First, what you're calling "reverse coupon" is a mechanism I've taught operators for years as Reverse Discounting. Same structure — the offer self-selects the customer who costs you the most and rewards the behavior you're trying to reduce. I've mostly applied it to straight discounts and loyalty programs. You've extended it to unlimited offers and the fit is clean.
Second, the pattern where the operator introduces targeted restrictions after the vulnerability lands — smaller plates, throttling, cancellation friction, weekly caps — has a name too. I call it Consent Erosion. The terms the customer thought they bought get quietly rewritten under them. Every example you cite ends with the customer feeling like the terms changed on them, because they did. It manages the exposure but degrades the relationship in the process.
Where I'd push: I don't read the vulnerability as a property of the pricing structure. I read it as a property of the operator building a relational-sounding promise ("come, be welcomed, eat freely") on top of transactional unit economics ("every plate costs me money"). The heavy user isn't exploiting the structure. They're running arbitrage on the gap between what the operator signaled and what the operator was actually running underneath. ClassPass's Payal Kadakia named it exactly: "What kind of business would we be if we wanted our members to work out less to reduce costs?" That's not a pricing failure. That's a business-model failure that pricing was asked to cover for.
— Jeffrey
Thank you, Jeffrey. This is very insightful, and I especially like your terms Reverse Discounting and Consent Erosion. In my experience, at least, the restaurant industry is far more sophisticated and nimble in considering and trying to solve these issues. I do quite a bit of work in the B2B space, and we often find that we are a bit behind some consumer industries in thinking through these things, and can learn from them.
My earlier comment named the drift — smaller plates, throttling, cancellation friction, weekly caps — as Consent Erosion. That was half the mechanism.
The other half is what Lesson 3 actually prescribes: the operator banking the gap.
I call that Consent Arbitrage.
Erosion is passive. Something happening to the Guest as the operation drifts. Arbitrage is active. The operator (or the vendor, or the system) deliberately monetizing the space between the consent that was given and the consent that currently exists.
The two coexist. Erosion opens the gap. Arbitrage exploits it.
Lesson 3 doesn't defend the offer. It teaches the arbitrage — how to keep the signaling of an unlimited relationship while quietly harvesting the margin created by degrading it. That's not a pricing fix. It's a positioning failure being monetized rather than corrected.