What Showed Up This Week

A revenue-management piece landed in the feed making a serious argument about AI. Not the hype version. The technical version. The piece named something real: agentic systems — AI that acts on its own, not just recommends — are moving from analytical tools into coordinating tools. Instead of telling the operator what to do, the system does it. Adjusts pricing. Restricts inventory. Reallocates marketing spend. Modifies staffing. Adjusts fulfillment zones. Continuously. Faster than any operator can convene a decision.

The piece pointed out that hotels have a centralized revenue function to redesign for this. Restaurants don’t. Restaurants never developed one. Pricing, promotions, menu design, delivery visibility, labor scheduling — all distributed across operators, POS systems, and increasingly, the delivery platforms themselves.

The piece framed the challenge as governance. Who defines the objective function. Who has authority when the system acts faster than the humans. Where the levers sit.

The framing was clean. It was also the wrong layer.

The Move Being Made

Every time an operator accepts the framing “how do I retain authority over the platform’s decisions,” the operator has already lost. Governance moves happen inside a system someone else designed. The operator negotiating governance rights over a platform’s coordination logic is running Road 2 concern through Road 1 physics — the same conundrum this newsletter named last week in a different vocabulary.

The load-bearing question is not “how much of the objective function do I still control on this platform.” The load-bearing question is “what is the objective function of my own operating architecture, and which vendors serve it or don’t serve it.”

Different question. Different physics. Different answer.

The operator running the first question is inside a dependency they didn’t design. The operator running the second question is running their own operation and reading whether the platform serves it.

What The Platform Actually Is

A delivery platform is a vendor. So is a POS system. So is a reservation platform. So is a review aggregator. So is the payment processor. So is the food distributor. The vendor’s job is to serve the operator’s operating architecture, not to run it.

That framing is not marketing. It is operating architecture. When the operator forgets it, the vendors become the operating architecture and the operator becomes a supplier to the vendors. Which is exactly what has happened to a large percentage of independent operators over the past decade. The delivery platforms did not seize control. The operators handed it over — one platform integration at a time, one algorithm-driven visibility optimization at a time, one commission tier at a time.

None of the individual moves looked like ceding control. Every individual move looked like “gaining a channel.” The cumulative move was ceding the coordination layer of the operation to vendors whose objective function is not the operator’s.

Agentic AI does not create this problem. It accelerates it. When the platform’s coordination happens continuously and autonomously — pricing, visibility, promotional surfacing, zone allocation, all adjusted in real time by a system running on the platform’s objective function — the operator who did not name their own operating architecture is now running a business coordinated by a vendor whose primary interest is fulfillment efficiency and take rate.

The Objective Function Is Not A Governance Question

The objective function is a design artifact. Every operation has one, whether the operator designed it or defaulted it. The operator who designed it can name it in one sentence — the operation exists to produce X for Y Guests through Z operating architecture, at a margin structure that funds W. The operator who defaulted it cannot name it, because the objective function is being defined by whoever is loudest in the coordination layer — the delivery platform, the reservation system, the review aggregator, the third-party marketer.

The Guest reads the objective function. The cast reads the objective function. The vendors read the objective function. The operator who has not named it is the only party in the arrangement who cannot see it.

This is where the framework runs upstream of the revenue-management conversation. Governance is a question you can only ask if you have already answered the design question. If the operator has designed their objective function and their operating architecture, then platform coordination is either serving the architecture or not, and the operator has actual decisions to make — accept the vendor, replace the vendor, remove the vendor, negotiate with the vendor. If the operator has not designed it, “governance” becomes a euphemism for negotiating the terms of surrender.

Three Tells You Have Already Ceded The Coordination Layer

Tell one: You cannot name your operation’s objective function in one clean sentence. Not the mission statement. Not the values poster. The actual thing the operation is designed to produce, for whom, through what architecture, at what margin. If the sentence doesn’t exist yet, the objective function is being written by someone else and the operator is executing against it without seeing it.

Tell two: Your weekly reads live inside vendor dashboards. DoorDash rankings. Yelp scores. OpenTable conversion. Uber Eats visibility. If the operator’s primary weekly read is inside a platform’s interface, the platform’s objective function is running the read. The platform has designed the dashboard to surface what serves platform economics. What the operator’s own operating architecture requires may not appear on the dashboard at all.

Tell three: Your revenue mix is coordinated by whichever platform is running the promotional cycle that week. If the operator does not know, without checking a platform, what percentage of this week’s revenue is coming from which channel at what margin — the coordination is happening outside the operator. The platform is coordinating. The operator is reacting.

If any of the three lands, the platform is already coordinating the operation, and the operator has not yet designed the architecture the coordination is supposed to serve.

The Framework Layer That Matters Here

This is where the arbitrage family runs. [Third-Party Arbitrage] names the mechanism: the platform extracts value from the operator’s Guest relationship, positioning capital, and margin structure under the framing of a service. The extraction runs through pricing tier, commission structure, visibility algorithm, and demand allocation. What agentic AI adds is that the arbitrage is now happening in the coordination layer, not just the transaction. The platform is not just taking a cut. It is running the operator’s operating decisions on the platform’s objective function.

[The Summers Principle] runs the diagnostic. By design or by default — no third state. The operator who has designed their own objective function and operating architecture is running the operation by design, and platform relationships are vendor decisions inside that design. The operator who has not designed the objective function is running the operation by default, and the objective function is being written by whichever vendor has the loudest signal in the coordination layer.

[Positioning Capital] names what erodes. When the operator’s operation is being coordinated toward the platform’s objective function, the operator’s positioning — the specific coherence that earned the Guest, the specific standard the cast learned to produce, the specific margin structure that funded the operation — decays quietly. It doesn’t crash. It drifts. Guests who came for a specific operating experience start receiving a platform-optimized experience instead. They stop returning. The cast learns a platform-optimized rhythm. The margin structure gets shaped by promotional cycles the operator did not design. Positioning capital, drained.

The Restaurant Version Of The Problem Is Not “No Central Coordinator”

The revenue-management piece framed the restaurant problem as “restaurants never developed a centralized revenue management function.” That reads as a gap. The framework reads it differently.

Restaurants do not need a centralized revenue management function like hotels have. Restaurants need something upstream of that — an operating architecture the operator designed, with an objective function the operator can name, executed by an operator whose read discipline covers the leading indicators of the architecture running clean.

A restaurant with a designed operating architecture does not need “centralized revenue management.” It needs the operator running their operation from that architecture. Every pricing decision, promotional decision, platform-integration decision, and coordination decision runs from the architecture. The architecture is the coordinator. Not a system. Not a function. The design itself.

The reason so many restaurants look uncoordinated is not that they lack a central function. It is that they lack a designed operating architecture, and the vendors — POS, delivery platforms, review aggregators, reservation systems — have filled the vacuum with their own coordination logic. Building “centralized revenue management” on top of that vacuum still does not fix the underlying problem. It just moves the surrender to a different room.

What Changes Tomorrow

Take a piece of paper. Write one sentence. Do not spend more than five minutes on it. The sentence has this shape:

“This operation exists to produce [what] for [whom] through [operating architecture], at a margin structure that funds [what continuing work].”

If the sentence takes longer than five minutes, that is the diagnostic — the objective function has not been designed, and the platforms and vendors have been filling the vacuum without you seeing it. If the sentence comes out in three minutes and reads clean, run it against three specific vendor relationships you have right now. Does this vendor serve the objective function you just named. If yes, keep. If no, name what would have to change for it to serve — or name what removing the vendor would require the operating architecture to absorb.

Do that read for three vendors this week. One delivery platform. One review aggregator or reservation platform. One food distributor or supplier. Not to fire vendors. To run the read that reverses the direction of coordination — the operator’s operating architecture is what the vendors are being read against, not the other way around.

The read runs one vendor at a time. The direction changes one read at a time. You are not overhauling the operation. You are recovering the coordination authority the platforms have been running by default.

Agentic AI will accelerate whichever direction the operator is already running. If the operator has designed the objective function, agentic systems become powerful vendors serving the design. If the operator has not, agentic systems become the design.

You get to decide which one.