There is a specific commercial pattern running against restaurant operators right now at industry scale. It is not new. The class ran it against American electric utility distribution between 1885 and 1920 and captured a century of margin. It ran it against restaurant sales infrastructure between 2015 and 2025 and captured 20-30 percent of every off-premise transaction, permanently.
It is now running against sixteen separate operating surfaces inside the restaurant simultaneously. Labor. Guest data. Transactions. Reservations. Off-premise fulfillment. Kitchen operations. Marketing. Scheduling. Inventory. Real estate. Payment processing. Franchise development. First-party ordering. Insurance. Menu engineering. Concept development.
The class rotates the surface. The play stays the same.
My framework has a name for it. [Edison Trust Arbitrage].
This piece names the pattern, teaches its six-beat structure, walks every surface it is currently running against, gives the operator the three tests that catch it inside any vendor pitch, and closes with the design principle that separates every commercial offer designed for operator ownership from every commercial offer designed for operator capture.
The Tool Is Not The Arbitrage
The piece has to say this first because the argument fails if this is not clear.
Automation equipment is real. Delivery is a real off-premise channel. POS software is real infrastructure. CRM captures real Guest data. Reservations platforms handle real coordination. Menu-engineering disciplines produce real check lifts. Payment processing is a real service. Every one of the sixteen surfaces I am about to prosecute has a real tool sitting inside it.
The tool is not the arbitrage. The arbitrage is the class-organized capture of the operating surface through five specific structural moves layered on top of the tool.
-
Ownership refusal. The tool is only available on subscription, lease, SaaS, or Robot-as-a-Service terms. Never on capital-purchase terms. The operator can never own the thing the operation is being built on.
-
Data extraction. The vendor retains rights to the operational data the tool generates. Aggregation rights, benchmarking rights, product-development rights, resale rights. The vendor’s data business is a second, hidden margin stream stacked on top of the tool business.
-
Infrastructure reframe. The tool is repositioned in trade press, vendor content, and counsel-class writing as “modern operational necessity,” “food-service infrastructure,” “the future of the category,” or “industry-wide requirement.” Refusal is made to feel unreasonable.
-
Dependency escalation. The vendor’s economics improve as the operator’s exit cost rises. The operation is redesigned around the vendor’s product. The staff who could run the pre-vendor version of the operation are gone. The operator has no clean exit path.
-
Class coordination. Vendors, financiers, counsel class, trade press, and industry association calendars coordinate to make the arbitrage feel like inevitable modernization rather than a specific commercial capture. The class does not need to force adoption. The class only needs to make refusal feel unreasonable.
An operator who buys an automation robot outright, on capital terms, with title in their name, owning the operational data — that is not [Edison Trust Arbitrage]. Same equipment. Different structure.
An operator who signs a Robot-as-a-Service subscription with the vendor holding title, the vendor holding data rights, a three-year auto-renew clause, and price-escalation language — that IS [Edison Trust Arbitrage]. Same equipment. Different structure.
The prosecution across the next sixteen surfaces is not a prosecution of the tools. It is a prosecution of the class structure the tools are wrapped in.
The Six-Beat Pattern
The Edison Trust was the name for the industrial consolidation that happened in American electric power distribution between roughly 1885 and 1920. Electric distribution was a genuinely new technology. Every municipality, every industrial operator, every commercial building could have owned and operated its own generation and distribution — the equipment existed, the expertise was learnable, the capital requirements were within reach for cooperatives and civic ownership.
That is not what happened. A small class of financiers, engineers, and legal professionals organized around the technology and reframed it as inevitable infrastructure requiring scale that individual operators could not achieve. Operators — municipalities, factories, commercial buildings — were convinced to lease access to the infrastructure instead of owning it. The holding companies captured the margin between what the infrastructure cost to provide and what operators paid to access it. They captured it forever.
That is the arbitrage. Six beats.
-
New technology arrives that operators could own. The tool is real. The equipment exists. The capital is reachable.
-
A class organizes around the technology. Vendors, financiers, integration consultants, counsel class, trade press.
-
The class reframes the technology as inevitable infrastructure. “Modern operational necessity.” “The future of the category.” “Industry-wide requirement.”
-
Operators are pitched leased access instead of ownership. Subscription, SaaS, Robot-as-a-Service, managed contract, integrated platform.
-
The class captures the margin between cost and price permanently. Ongoing recurring revenue indexed to operator dependency.
-
Operator dependency locks in — no exit. The operation is redesigned around the vendor. Going back is not a switch flip.
Six beats. Executed against utilities in 1900. Executed against restaurant sales infrastructure between 2015 and 2025. Now executing against sixteen operating surfaces inside the restaurant simultaneously.
The Sixteen Operating Surfaces Under Active [Edison Trust Arbitrage] Prosecution
Each of the sixteen surfaces below has an active class-organized [Edison Trust Arbitrage] execution running against it right now. The vendors vary. The pitch language varies. The industry verticals inside the food-service category vary. The play is identical.
Sales infrastructure — third-party delivery. The completed play, ten years in. Class captured 20-30 percent of every off-premise transaction, ownership of the Guest data generated through the transaction, and the operator’s off-premise operational data. Operator became a tenant in their own sales channel. Exit cost now approaches infinite for the operator whose off-premise volume was built on marketplace access. This is the reference case the framework prosecutes when it prosecutes the next fifteen.
Labor line — automation-as-a-Service. The active play. Vendors sell subscription access to automated fry stations, service robots, order-taking, prep, dishwashing, and delivery equipment. Ownership refusal is the structural tell — the vendor will not sell the equipment outright on capital terms. Data extraction is stacked underneath. Industry commentary reframes automation as “food-service infrastructure” and “bigger than a hiring issue.” The operator who signs replaces variable labor cost with fixed technology-and-services cost on vendor-set terms, gives up operational data, and cannot go back to human staffing without redesigning the operation. The commentary asset that surfaces this move is one of the class’s content instruments.
Guest intelligence — CRM and loyalty SaaS. The active play. Vendors sell subscription access to Guest data collection, segmentation, and loyalty program management. The Guest relationship the operator produced through hospitality is captured by the vendor. The Guest data the operator’s operation generates is aggregated, benchmarked, and often resold. The operator who leaves the platform loses access to the Guest history their own operation created. Ownership refusal — no meaningful path to owning the Guest database outright. Data extraction — vendor rights over aggregation, benchmarking, and platform-level analytics. Infrastructure reframe — “modern Guest engagement infrastructure.” Dependency escalation — every additional year deepens the switching cost.
Transactions — POS SaaS. The active play. Vendors sell subscription access to point-of-sale software with per-terminal monthly fees, transaction fees, and upgrade cycles. The operator does not own the POS. The operator rents the POS. The operator’s entire transaction history — every check, every void, every discount, every menu item’s performance — sits on the vendor’s terms. Ownership refusal is total in the modern POS market. Data extraction is universal. Infrastructure reframe — “modern restaurant operations require modern POS infrastructure.” Dependency escalation — hardware locked to software, software locked to subscription, subscription locked to vendor terms.
Reservations — booking platform arbitrage. The active play, in its second decade. Vendors sell subscription access to reservations infrastructure, per-cover fees, and marketplace listings. The operator’s Guest booking data is captured, aggregated, and used for the vendor’s marketplace product. Ownership refusal — no operator ownership of the booking platform. Data extraction — Guest booking history, preference data, cancellation patterns all held by vendor. Infrastructure reframe — “operators need to be discoverable where Guests search.” Dependency escalation — Guests trained to book on the platform, operator dependency locked in.
Off-premise fulfillment — ghost kitchens and virtual brands. The active play. Vendors sell subscription access to kitchen infrastructure, virtual brand rights, and marketplace-only concepts. The operator does not own the kitchen. The operator does not own the brand IP. The operator does not own the Guest relationship — the marketplace does. Ownership refusal is total. Data extraction is total. Infrastructure reframe — “digital-native food-service infrastructure.” Dependency escalation — operator has no physical brand, no direct Guest relationship, no exit product.
Kitchen operations — KDS and kitchen-management SaaS. The active play. Vendors sell subscription access to kitchen display systems, prep-management software, and back-of-house workflow tools. The operator’s kitchen operational data — ticket times, prep timing, station performance, cast productivity by station — is captured by the vendor. Ownership refusal — subscription-only. Data extraction — kitchen operational data as a second margin stream. Infrastructure reframe — “modern back-of-house infrastructure.” Dependency escalation — kitchen workflow now depends on vendor platform.
Marketing — platform-controlled analytics and advertising SaaS. The active play. Vendors sell subscription access to marketing analytics, campaign management, and audience-targeting tools built on top of platform data the operator does not own. The operator’s marketing spend generates data that feeds the platform’s product. Ownership refusal — no operator ownership of audience data. Data extraction — every campaign feeds vendor’s aggregation model. Infrastructure reframe — “modern restaurant marketing infrastructure.” Dependency escalation — audience data non-portable.
Workforce — scheduling and labor-management SaaS. The active play. Vendors sell subscription access to scheduling software, labor forecasting, and shift management. The operator’s cast operational data — shift patterns, hourly productivity, turnover metrics — is captured by the vendor. Ownership refusal — subscription-only. Data extraction — cast performance data aggregated across operators. Infrastructure reframe — “modern workforce infrastructure.” Dependency escalation — scheduling workflow now dependent on vendor.
Inventory — cost-management and inventory SaaS. The active play. Vendors sell subscription access to inventory tracking, food cost management, and vendor management. The operator’s purchasing data, waste data, and cost-of-goods data is captured. Ownership refusal — subscription-only. Data extraction — vendor sees every operator’s cost structure. Infrastructure reframe — “modern inventory and cost-management infrastructure.” Dependency escalation — inventory workflow dependent on vendor.
Real estate — brokerage and site-selection platform arbitrage. The active play. Vendors sell subscription access to site-selection data, competitive-set intelligence, and real estate analytics. The operator’s location performance data, expansion research, and real estate strategy is captured. Ownership refusal — subscription-only. Data extraction — location intelligence aggregated across operators. Infrastructure reframe — “modern real estate intelligence infrastructure.” Dependency escalation — real estate strategy dependent on vendor data.
Payment processing — processor and payments SaaS arbitrage. The active play. Vendors sell subscription access to payment processing, per-transaction fees, and integrated payments infrastructure. The operator’s transaction data — full processing history, refund patterns, chargeback data — is held by processor. Ownership refusal — no operator ownership of processing infrastructure. Data extraction — processing data aggregated. Infrastructure reframe — “modern payments infrastructure.” Dependency escalation — processor lock-in through integration.
Franchise development — franchise development consulting class. The active play. A specific counsel-class formation that sells subscription access to franchise development strategy, franchisee recruitment, and franchise system design. The operator’s franchise growth strategy is captured, aggregated, and often resold under adjacent brand names. Ownership refusal — the operator does not own the franchise system design methodology, they rent it. Data extraction — franchise system data used to build competitor systems. Infrastructure reframe — “modern franchise development infrastructure.” Dependency escalation — franchise growth locked to the consulting relationship.
First-party ordering — first-party ordering platform arbitrage. The active play. Vendors sell subscription access to first-party ordering infrastructure with per-order fees. The operator’s direct-order Guest data is captured. Ownership refusal — subscription-only. Data extraction — direct-order Guest data aggregated. Infrastructure reframe — “modern first-party ordering infrastructure.” Dependency escalation — first-party channel dependent on vendor.
Insurance and risk — insurance and risk-management SaaS arbitrage. The active play. Vendors sell subscription access to risk management, compliance tracking, and insurance platform tools. The operator’s operational risk data is captured. Ownership refusal — subscription-only. Data extraction — operational risk data aggregated across operators. Infrastructure reframe — “modern risk-management infrastructure.” Dependency escalation — risk-management workflow dependent on vendor.
Menu engineering — menu-optimization SaaS and menu-consulting arbitrage. The active play. Vendors sell subscription access to menu-engineering analytics, menu-testing platforms, and dynamic menu-management tools. The operator’s menu performance data is captured. Ownership refusal — subscription-only, no operator ownership of the menu-optimization methodology or the platform. Data extraction — menu performance data across operators aggregated. Infrastructure reframe — “modern menu-engineering infrastructure” and the specific rhetorical move that reduces the menu from operating-consequence-of-Product-architecture to standalone-optimization-document. Dependency escalation — menu now depends on vendor platform to be optimized. This is the surface a recent piece of industry commentary was executing against — reducing the menu to “the single highest-leverage document in the building” and quoting isolated statistical lifts to justify the subscription pitch. The menu is not a document. The menu is the operating consequence of Product architecture. Reducing it to a document is the reframe move that lets the arbitrage execute.
Concept development — concept development and brand-strategy SaaS arbitrage. The active play, less mature than the others. Vendors sell subscription access to concept development frameworks, brand-strategy tools, and concept-testing platforms. Ownership refusal — the operator does not own the concept framework, they rent it. Data extraction — concept development data aggregated. Infrastructure reframe — “modern concept development infrastructure.” Dependency escalation — concept strategy now dependent on vendor.
Sixteen surfaces. One pattern. Same class structure across every execution. Financiers organizing capital. Counsel producing legitimizing content. Vendors selling subscription access to physical or informational infrastructure. Trade press amplifying the “inevitable modernization” frame. Operators being convinced that ownership is either not possible, not their concern, or not worth the effort.
The industry’s operators have been the losing party in [Edison Trust Arbitrage] twice already at industry scale — utilities in 1900, delivery between 2015 and 2025. They are being asked to be the losing party across sixteen surfaces simultaneously right now.
[Stacked Arbitrage] — The Second Layer
And it is worse than sixteen surfaces. It is sixteen surfaces with additional arbitrage layers running on top of the surfaces the class has already captured. My framework has a name for this second-layer mechanic. [Stacked Arbitrage].
Once the class has captured an operating surface through [Edison Trust Arbitrage], the captured position becomes a new operating surface. Vendors organize around the new surface. A second layer of subscription products, consulting services, and analytics platforms is sold to operators to help them operate more efficiently inside the arbitrage they are already trapped in. Same six beats. New layer. The operator pays two rents where they used to pay one, then three, then four.
The delivery stack. Third-party delivery captured the sales channel first. Then delivery-menu-engineering SaaS stacked on top — subscription tools to optimize the delivery menu that only exists because the operator is trapped in delivery. Then third-party analytics platforms stacked on that — subscription access to analysis of the delivery performance the operator cannot escape. Then aggregator-management software stacked on that — subscription access to a tool that manages the aggregators the operator was captured by. Then delivery-optimization consulting stacked on that — subscription access to advisors who help operators run their delivery arbitrage more efficiently. Five rent streams on what was originally one operating surface the operator could have owned.
The POS stack. POS SaaS captured the transaction infrastructure first. Then payment processing SaaS stacked on top — the processor’s subscription fees plus per-transaction fees running on the POS the operator is already renting. Then reporting SaaS stacked on that — subscription access to reports on the transaction data the operator does not own. Then POS-optimization consulting stacked on that — subscription access to advisors who help operators use their POS SaaS more efficiently. Four rent streams on what was originally one purchased cash register.
The loyalty stack. Loyalty SaaS captured the Guest relationship first. Then customer-data-platform SaaS stacked on top — subscription access to a tool that unifies the fragmented Guest data across all the loyalty tools the operator is already renting. Then loyalty-program-optimization consulting stacked on that — subscription access to advisors who help operators design better loyalty programs inside the loyalty platform the operator is already captured by. Then loyalty analytics SaaS stacked on that — subscription access to analysis of the loyalty program the operator does not own.
The framework arbitrage stack. [Framework Arbitrage] captured operator-side operating discipline first by extracting artifacts (playbooks, systems, frameworks) from their operating coherence and selling them as standalone products. Then playbook-implementation consulting stacked on top — subscription access to advisors who help operators implement the extracted playbooks. Then playbook-certification credentialing stacked on that — subscription access to credentials that verify the operator has learned to run the extracted playbook. Then “community” and “peer network” subscriptions stacked on that — subscription access to conversations with other operators who are running the same extracted playbooks.
The counsel-class content stack. [Editorial Capture] captured industry commentary first. Then “industry analyst” subscription services stacked on top — subscription access to analysis of the industry the operator is inside. Then “market intelligence” platforms stacked on that. Then “advisory councils” and “operator peer networks” stacked on that — subscription access to peer conversations mediated by the same counsel class that captured the commentary.
The tell for [Stacked Arbitrage] in the operator’s own P&L. When the operator’s monthly software-and-services line item begins to approach or exceed their labor line item, or exceeds their food cost line item, they are almost certainly deep inside stacked arbitrage on multiple surfaces. The line items to inventory: aggregator fees, delivery-optimization tools, POS SaaS, payment processing, CRM/loyalty SaaS, reservations SaaS, KDS SaaS, kitchen-management SaaS, marketing-analytics SaaS, scheduling SaaS, inventory SaaS, menu-engineering SaaS, real-estate-intelligence SaaS, insurance/risk SaaS, consulting relationships tied to any of the above. Add them up. The number surprises most operators. The number is the class’s product.
[Stacked Arbitrage] is why the operator who has already been captured on five to eight surfaces cannot easily unwind the position with one decision. Each layer holds the layer beneath in place. Exiting the loyalty platform means exiting the customer-data-platform SaaS that unified the loyalty data. Exiting the POS means exiting the payment processor integrated into the POS. Exiting the aggregator means losing the delivery-optimization consulting that priced the menu for aggregator margin. The class engineered the interlock. Naming the interlock is the first move to unwinding it.
Where This Sits In The Framework
[Edison Trust Arbitrage] is a specific execution within the [Transactional Arbitrage] family — the Road 1 mechanism the class runs to capture margin between the operator and their operating surface at industry scale. Same family as [Third-Party Arbitrage] against the sales channel, [Framework Arbitrage] against operator-side operating coherence, and [Operator Arbitrage] against individual operator information asymmetry. Each captures a specific surface.
[Edison Trust Arbitrage] names the class-organized capture of an operating surface across a category of operators, permanently.
The framework’s [Counsel Class Silence] entry names the specific class dynamic that makes the arbitrage work. A class of counsel and advisors who cannot defend what they sell to operators because they know it does not survive the diagnostic. Every one of the sixteen surfaces above has its counsel class. Every counsel class produces content assets that execute one or more of the six beats. Every content asset that opens with anonymous industry statistics (“42% of restaurants unprofitable,” “89% of operators expect labor costs to rise,” “63% of workers stressed about money”) is running the class positioning move that lets the pitch that follows land as diagnosis rather than sales.
The framework’s [Hacksterism] entry names the specific behavioral pattern the arbitrage exploits. The operator posture that seeks operational outcomes without paying the architectural cost. The class packages hacks as products. The products get subscription pricing. The operator pays rent to run hacks against their own operation.
The Three Tests To Run On Any Vendor Pitch
Any vendor proposal on any of the sixteen surfaces above can be diagnosed for [Edison Trust Arbitrage] structure in three questions.
Test one — ownership versus subscription. Does the vendor propose the operator own the product outright, on standard capital or purchase terms, with the operator holding title, IP rights, or the equivalent? Or does the vendor propose a subscription, lease, SaaS, or Robot-as-a-Service arrangement where the vendor retains title and ongoing recurring revenue?
Yes to ownership, no to subscription = the vendor is selling a tool. No [Edison Trust Arbitrage] structure present. Evaluate on standard capital investment terms.
Yes to subscription, no to ownership = the vendor is running [Edison Trust Arbitrage]. Ownership refusal is the structural tell.
Test two — data ownership. Does the operator own, in writing, every piece of operational data the product generates? Or does the vendor retain rights to that data for aggregation, benchmarking, product development, or resale?
Yes to operator data ownership, no to vendor rights = clean arrangement. Operator’s operation, operator’s data.
Yes to vendor rights, or ambiguous “shared” data language = [Edison Trust Arbitrage] structure present. The data extraction is a second, hidden margin stream stacked on top of the primary pricing.
Test three — dependency economics. Does the vendor’s business model improve when the operator’s dependency on the vendor increases? Does the operator’s exit cost rise every year the operation is redesigned around the vendor?
No to both = independent economic actors in a normal capital or purchase relationship.
Yes to either = [Edison Trust Arbitrage] in motion. Operator dependency is the vendor’s product.
Two positive tests out of three means the operator walks. Not renegotiates. Walks.
Operating Consequence — What The Operator Does Instead
Refuse the subscription structure where a purchase alternative exists. For any product the operator determines is genuinely useful in their operation, the operator first asks whether the product can be purchased outright, on capital or one-time-purchase terms. If yes, buy. If no — if the vendor’s only offering is subscription, SaaS, or as-a-Service — recognize the vendor’s business model depends on operator dependency and walk. There are vendors on most of the sixteen surfaces who will sell products outright. Find them. Their pricing will look higher on day one and lower over the operation’s life.
Own the data on every contract, without exception. Every vendor contract the operator signs specifies in writing that all operational data generated through the vendor’s product is the operator’s property. The operator grants no license to the vendor for aggregation, benchmarking, product development, or resale. If the vendor will not sign the data terms, the vendor is running the second-layer arbitrage. Walk.
Refuse the infrastructure framing. When any vendor, consultant, or content asset reframes a commercial product as “modern operational necessity,” “industry-wide requirement,” “food-service infrastructure,” or “the future of the category,” recognize the reframe as [Edison Trust Arbitrage] in motion. The class does not need to force adoption. The class only needs to make refusal feel unreasonable. Refusal is the operator’s discipline. Refusal is what keeps the operator in ownership position across every one of the sixteen surfaces.
Read every content asset for its inoculation move. When commentary opens with anonymous industry statistics, follows with a “two-sided victim” frame that positions both operators and workers/Guests as struggling, then executes a product recommendation as neutral diagnosis, recognize the pattern. The statistics are inoculation. The two-sided frame is positioning. The recommendation is the pitch. Read the shape.
Read the surfaces you have already given up. Most operators have already signed into [Edison Trust Arbitrage] on five to eight of the sixteen surfaces above without recognizing the structure, and most are also inside [Stacked Arbitrage] on two or three of them. That is not moral failure. That is the class doing its job. The move is to inventory what has been given up, catalog the exit costs on each, catalog the stacked layers riding on top of each captured surface, and route new commitments only through the ownership tests. The surfaces the operator has already captured cannot always be unwound today. The next commitment can be refused today.
The Operator’s Alternative — Design Everything For Ownership
The class runs [Edison Trust Arbitrage] because operator dependency is the class’s product. The operator’s move is to design every commitment around the opposite structure. Operator ownership of the operating surface, the discipline, the data, the framework, the Guest relationship, and the operation itself.
The framework’s commercial architecture demonstrates this. The books are free. Every fundamental — Perspective, Product, People, Performance, Profit — the operator can read, own, and run against their operation without paying rent to me for the framework itself. The Dictionary at kb.jeffreysummers.com is free and open. Every locked IP term is operator property from the moment it publishes. The blog is free. Every position on the record at jeffreysummers.com is operator property. The industry-prosecution corpus at hacksterism.com is free. Every arc is operator property.
The commercial offers exist for operators who want the framework EXECUTED against their specific operation. Coaching. The Diagnostic. PeriodReview. OnsiteReview. OffsiteReview. One-On-One. Each of them is defined-scope, defined-price, defined-exit. None of them locks the operator into subscription capture. None of them extracts operational data as a second margin stream. None of them makes the operator’s exit cost rise the longer the engagement runs. None of them holds framework fluency hostage.
That is the design principle. Ownership-first. Everything the operator can own, the operator owns. Everything the operator engages with the framework for is a scoped engagement with a clean exit. The operator ends every engagement more capable, not more dependent.
The operator’s move on their own commercial architecture is to run the same discipline. Every vendor they contract with is asked: does this arrangement route me toward owning something, or does it route me toward renting something forever? Every service they buy is asked: do I end this engagement more capable, or do I end it more dependent? Every tool they adopt is asked: do I own the operational data this tool generates?
The operator who runs those questions across every commitment does not participate in [Edison Trust Arbitrage] against their operation. The operator who does not run those questions is the class’s product across all sixteen surfaces simultaneously.
Monday Morning
Do this tomorrow. Pull every subscription, SaaS, service, and vendor contract currently active in the operation. Every one. Delivery. POS. CRM. Reservations. Marketing platform. Scheduling. Inventory. Payment processor. Menu-engineering platform. Kitchen-management. Marketing analytics. Franchise consulting relationship. Real estate platform. Insurance/risk platform. Concept consulting. Every commitment the operation is paying monthly rent against.
Run the three-test diagnostic against each.
For every commitment where two or more tests come back positive for [Edison Trust Arbitrage] structure, put the commitment on the exit-planning list. Some of those commitments cannot be exited tomorrow — the exit cost is real, the operational dependency is real, the redesign work is real. That is the point. The class engineered those exit costs. Recognizing the engineering is the first move to unwinding it.
For every commitment where the tests come back clean — outright purchase, operator data ownership, no dependency escalation — leave in place and treat as a normal capital or purchase relationship.
Then take the next commitment the operation is about to make — any new vendor pitch, any new subscription renewal, any new SaaS trial — and run the tests before signing. Refuse anything that fails two or more.
Then read every service page on jeffreysummers.com. Every commercial offer I run passes the three tests. Ownership. Data. No dependency escalation. Every engagement scoped, priced, and exited. Every operator ends more capable than they started. That is not accident. That is design.
The operator who runs this diagnostic in 2026 does not become a tenant across sixteen operating surfaces. The operator who does not run it will be a tenant across sixteen operating surfaces for the rest of the operation’s life.
Closer
The Edison Trust took a century to unwind and never fully unwound. Delivery arbitrage is ten years in and still eating the industry. Automation arbitrage is happening in real time. Menu-engineering arbitrage is running content assets this week. Every other surface has a vendor class organizing right now.
The class runs the same arbitrage across generations because it works. It works because operators do not name it while it is running. It works because the counsel class produces content that positions the arbitrage as neutral diagnosis. It works because the reframe of subscription as “modern infrastructure” makes refusal feel unreasonable.
Name it while it is running. Refuse subscription where purchase exists. Own the data on every contract. Design every operator commitment for ownership, not for capture.
The framework’s commercial architecture routes the operator to ownership. Everything else routes the operator to rent.
The operator picks the road every time they sign a contract.
Digging Deeper
Positions on the record:
-
Why Do Restaurants Fail? — https://jeffreysummers.com/why-do-restaurants-fail/
-
The Insanity of Losses — https://jeffreysummers.com/the-insanity-of-losses/
-
Your Current Business Design Will Eventually Fail — https://jeffreysummers.com/your-current-business-design-will-eventually-fail/
-
QFO: Big Menu Or Small Menu? — https://jeffreysummers.com/qfo-big-menu-or-small-menu/
-
Great Hospitality Can Overcome Bad Food — https://jeffreysummers.com/great-hospitality-can-overcome-bad-food/
-
What Warren Buffett Taught Me About How to Run a Better Restaurant — https://jeffreysummers.com/what-warren-buffett-taught-me-about-how-to-run-a-better-restaurant/
-
The Hack Roster — The Repair Market Itself — https://hacksterism.jeffreysummers.com/hack-roster-repair-market/
-
The Tool Stack Is Not A Framework — https://hacksterism.jeffreysummers.com/the-tool-stack-is-not-a-framework/
-
The Chipotle Of X Is Framework Arbitrage — https://hacksterism.jeffreysummers.com/chipotle-of-x-framework-arbitrage/
-
Every Loyalty Program Redesign In QSR Is A Guest Contract Violation — https://hacksterism.jeffreysummers.com/loyalty-program-guest-contract-violation/
-
The Industry’s Editorial Class Just Endorsed A Case Study Reduction Of The Year — https://hacksterism.jeffreysummers.com/editorial-class-case-study-reduction/
-
Administered Pricing Without A Pricing Department — https://jeffreysummers.com/administered-pricing-without-a-pricing-department/
-
Shrinkflation Is A Guest Contract Violation — https://hacksterism.jeffreysummers.com/shrinkflation-guest-contract-violation/
-
The Class That Cannot Defend What It Sells — https://jeffreysummers.com/the-class-that-cannot-defend-what-it-sells/
Term definitions from the Knowledge Base:
-
[Edison Trust Arbitrage] — https://kb.jeffreysummers.com/dictionary/edison-trust-arbitrage/
-
[Stacked Arbitrage] — https://kb.jeffreysummers.com/dictionary/stacked-arbitrage/
-
[Transactional Arbitrage] — https://kb.jeffreysummers.com/dictionary/transactional-arbitrage/
-
[Third-Party Arbitrage] — https://kb.jeffreysummers.com/dictionary/third-party-arbitrage/
-
[Framework Arbitrage] — https://kb.jeffreysummers.com/dictionary/framework-arbitrage/
-
[Operator Arbitrage] — https://kb.jeffreysummers.com/dictionary/operator-arbitrage/
-
[Counsel Class Silence] — https://kb.jeffreysummers.com/dictionary/counsel-class-silence/
-
[Hacksterism] — https://kb.jeffreysummers.com/dictionary/hacksterism/
-
[The Hack Roster] — https://kb.jeffreysummers.com/dictionary/the-hack-roster/
-
[Case Study Reduction] — https://kb.jeffreysummers.com/dictionary/case-study-reduction/
-
[Editorial Capture] — https://kb.jeffreysummers.com/dictionary/editorial-capture/
-
[Symbolic Price Equity] — https://kb.jeffreysummers.com/dictionary/symbolic-price-equity/
-
[Two Roads] — https://kb.jeffreysummers.com/dictionary/two-roads/
Sources
-
LinkedIn commentary on food-service automation, industry class content asset. 08.17.2026.
-
LinkedIn commentary on restaurant menu engineering, industry class content asset. 08.17.2026.
