Every few months an inquiry arrives from a franchisor. Sometimes it comes from a brand-standards group, sometimes from an operations office, sometimes from the private-equity ownership sitting above both. The ask is always some version of the same thing: come in, read the system, and give us something we can roll out across the network.
I decline those engagements. Not because franchising offends me, and not because the people who send those inquiries are acting in bad faith. I decline them because of where the buyer stands in the system. The party writing the check is not the party standing in the building, carrying the risk, or living with the result. In that configuration my work stops being an instrument of the operator’s own read and becomes an instrument of extraction pointed at operators who never chose it.
This is a scope refusal, not a flat no. The test is runnable, and I will hand it to you before this piece is over.
The Frame
The mechanism has a name in my framework: [Franchisor Arbitrage]. It names franchisor-side extraction of operating capacity from a captive operator network, running through three components installed in the agreement at signing — operating-manual authority, exit-blockage provisions, and mid-contract mandate installation capacity the operator has no authority to refuse.
The load-bearing property is where the money comes from. A franchisor’s revenue is collected from the network. Royalty on gross sales, mandated supply arrangements, technology fees, marketing fund contributions, system fees of every description — all of it lands on the franchisor’s ledger whether or not the individual unit’s operator compounded anything that period. The operator produces. The franchisor collects. When the franchisor is carrying debt service, return requirements, or capital calls it cannot absorb at its own balance sheet, the mandate authority activates and the operating cost of relieving that pressure runs against the operator’s building.
That is a different economic animal from an operation. An operation produces its result. A collection architecture receives its result. My entire body of work is built for the first one.
What Forty-Five Years Taught Me To Refuse
I have been in this industry since April 4, 1982. I am in my forty-fifth year. In that time I have watched the industry’s counsel infrastructure develop an extraordinary talent for selling operators the instrument that transfers their own accumulated position to somebody else, and an equally extraordinary talent for never naming it out loud. My framework calls that discipline of silence [Counsel Class Silence], and it is the reason the franchise version of the pattern has gone unnamed for four decades while unit operators absorbed the retrospective verdict for it.
The verdict arrives as [Case Study Reduction]. A system runs extraction against its network, units fail, and the industry writes it up as an operator-quality story. Bad operators. Under-capitalized operators. Operators who didn’t execute. The mandate architecture that produced the compression never appears in the write-up, because the parties who write the write-ups sit on the same side of the ledger as the party that installed the mandates.
I am not interested in adding my name to that side of the ledger. That is the whole of the credential I am claiming here.
This piece runs five arguments: where the economics come from, what a mandate does to the read, what it does to the Guest Experience, what it does to the performance work, and who the right buyer actually is. Then the tests.
Argument One — Extraction Is Not Production
Ask any franchisor’s operations office what its job is and you will hear a production answer: we make the system better, we lift the network, we protect the brand. Some of that is sincere. None of it changes the direction the cash flows.
The unit produces hospitality, executes service, and owns its admin. The unit’s operator signed a personal guarantee, hired the cast, and stands on the stage on a Friday night in February when the weather turned. The unit’s Profit is what remains after the collection architecture takes its cut off the top line, which means the operator’s Profit is a residual and the franchisor’s is a claim. Residuals bear risk. Claims do not.
Now put my work into that structure. A franchisor hires me to read the system and produce operating counsel for the network. Whatever I produce, if it lifts sales, lifts the franchisor’s royalty first and the operator’s Profit only after the operator has funded the labor, the inventory, and the capital the lift required. If it does not lift sales, the royalty is unchanged and the operator ate the cost alone. The engagement’s upside is shared; its downside is not. That asymmetry is the arbitrage, and it does not require anyone in the room to intend it.
The move that would work is not a better rollout. It is a different buyer — one whose Profit is the residual, so that the work and the risk sit on the same ledger.
Argument Two — A Mandate Strips The Read And The Authority
My engagements have two non-negotiable conditions. The operator owns the read. And the operator names who runs the change, with what authority, by when.
A franchisor mandate removes both by design. The read was performed above the building by people who will not staff the change. The operator receives a conclusion, not a diagnostic — and a conclusion without the read behind it is exactly what [Operator’s Read] exists to prevent, because the operator cannot tell whether the move is aimed at the right altitude in his building. He executes someone else’s architecture on faith. When it fails, it fails at his altitude and reads as his execution.
Then it compounds at the People ledger. The operator is held accountable for an outcome he had no authority to modify, and he passes the same structure down: the lead is accountable for coverage on hours he cannot change, the kitchen manager is accountable for food cost on a supply arrangement he cannot renegotiate. Accountability without Authority To Execute is The Scapegoat Model, and a mandate installs it across an entire network in a single manual revision. My work is built to close that gap. Mandated implementation is the machine that manufactures it.
The move that would work is the one my framework requires everywhere: the party who will carry the change does the read and names the owner. If that party is contractually barred from doing either, there is no engagement worth running.
Argument Three — Mandated Standardization Overwrites The Guest Contract
The Guest Experience is designed in a specific building, for a specific Guest cohort, in a specific market, by an operator who is present. That is not sentiment. It is the only mechanism by which a [Guest Contract] can be kept, because the contract is with people who walk through one door.
Network-wide mandates are written for the aggregate. Coverage mandates push the operator into channels whose transactional terms contradict the relational terms he holds inside the four walls, so the Guest meets two contradictory contracts under one name — one from each of [The Two Roads], running concurrently in the same building. Standardization mandates strip the operator’s authority to design against his own market. And because the mandate arrived without the read, the operator cannot even name which Fundamental is now running against his declared direction — the condition my framework calls [Cross-Road Arbitrage] when the operator does it to himself, arriving here as something done to him.
Left unrefused long enough, that is the road to [Coherence Collapse]: the Fundamentals stop cohering as one operating system, the building keeps running mechanically, and the P&L keeps reporting while the architecture is gone.
The move that would work is designing the Guest Experience at the altitude where the Guest actually appears. That altitude is the operator’s, and it is the only one I will work at.
Argument Four — Performance Work Under Mandate Cannot Terminate In A Move
Performance work is only worth what the operator can do with it. I run reads that end in executable moves — this metric, this cause, this move, this owner, this date.
Under mandate compliance, the chain breaks at the fourth link. Prime cost is out because mandated hours installed labor the daypart cannot carry, and the operator may not change the hours. Food cost is out because of a supply arrangement he may not renegotiate. A unit his own read says should close is held open by a committee process, so the royalty keeps flowing out of a building that is no longer economically alive. Every read is correct. Every prescribed move is contractually blocked. What I would be selling the franchisor is a diagnostic whose prescriptions the buyer intends to overrule wherever they touch the collection architecture.
That is [Hacksterism] wearing a system-wide brand: the appearance of architectural work without paying the architectural cost, which here means without surrendering any of the mandate authority producing the failure.
The move that would work is the one I am doing right now — refusing the engagement and naming the mandate architecture as the constraint, which is information the buyer can actually act on.
Where I Do Work Inside The Same Company
Here is where the refusal stops being a flat no, and the distinction is not a courtesy. It is the mechanism.
Company-owned divisions are in scope. A franchisor that also operates its own restaurants can hire me for that division. In that division the buyer bears the operating risk, holds the operating decisions, chose the engagement, and pays the implementation cost out of the same pocket that receives the result. The Profit is a residual again. Authority and accountability sit in the same hands. Every condition my work requires is satisfied — same corporate parent, entirely different position in the system. I am not testing the logo. I am testing the ledger.
Franchisees are among my best buyers. A franchisee is an operator carrying full risk, and typically carrying it while exposed to two sets of physics at once: the same environmental pressure every independent faces, plus contractual extraction the independent does not. That operator needs vocabulary for what is running against him more than almost anyone in this industry, because without it he will read extraction as his own execution failure and spend his remaining capital on operator-side moves that cannot restore what a mandate removed.
Franchisee associations are the highest-leverage version of that work. No individual operator out-negotiates a system alone; refusal at the extraction level requires network coordination. The industry has built extensive infrastructure for franchisor-side coordination and almost none for operator-side coordination. Building the operator side is real work and I will do it.
If you operate franchised units, start at For Franchise Operators — that page is written for you, and nothing in this piece is a refusal of your engagement. It is the opposite. It is why yours is the one I take.
The Deeper Argument
The reason this refusal is a positioning decision and not a moral posture is that my framework only functions when the person holding it can refuse things.
[By Design Or By Default] runs on every choice, and the lever only exists where the operator has the authority to pull it. Inside a captive network, that authority was contractually pre-removed at signing. Hand my vocabulary to the party holding the mandate authority and the vocabulary travels the network without any of the operating coherence behind it — my terms printed on a compliance deck, my diagnostic language attached to a mandate the receiving operator never read, my framework converted into the justification for the extraction it exists to name. The words arrive. The discipline does not. That is not adoption. It is my work turned into a brand-standards instrument, and every operator who then meets my framework meets it as something imposed rather than something he chose.
There is a version of my counsel that a franchisor can legitimately buy, and it has a narrow scope: the work of reading its own extraction infrastructure and dismantling it — mandate authority returned to negotiation, exit-blockage relaxed to real market terms, operators given standing to run their own reads and refuse conclusions they did not reach. That is a governance engagement, not a rollout engagement, and I have never once been asked for it.
The Scope Test
Four tests. Run them on any engagement, mine or anyone’s. They are the same four I run before I answer an inquiry.
Test One — Who bears the operating risk? Whose capital is at risk if the operation underperforms after the work is implemented? If the answer is a party who continues collecting regardless of the outcome, the work is being bought by the wrong side of the ledger. Yes for the operator, no for the collector.
Test Two — Who holds the operating decisions? Can the buyer actually change hours, staffing, pricing, supply, menu, and capital in the building the work concerns? If the buyer holds those decisions for buildings it does not operate, the engagement is a mandate in advance. Yes for the operator, no for the party writing the manual.
Test Three — Who chose the engagement? Did the party who will execute the change agree to have this work done in their operation? If the change arrives at the building as an obligation nobody in that building selected, no read was performed by the party who will carry it, and the work will fail as their execution failure.
Test Four — Who carries the implementation cost? Who funds the labor, the training, the inventory, the equipment, and the calendar time? If implementation cost lands on one ledger while the resulting revenue lands first on another, that gap is the arbitrage regardless of anyone’s intent.
The sort is simple. Four yeses pointing at the operator standing in the building — independent, chain division, company-owned, franchisee — and I can work. Any test pointing at a party collecting from that operator, and I cannot, and neither should the operator accept counsel produced under those conditions from anyone else.
What You Do Monday Morning
If you operate franchised units: take one hour with your franchise agreement and every operating-manual revision issued since your current ownership acquired the system. List each revision that materially changed your operating obligations, and for each one ask the single load-bearing question — does this produce revenue on the franchisor’s ledger at operating cost on mine? Write the answer down in your own words, and where the answer is yes, name the thing as extraction rather than as “the new hours requirement.” Vocabulary discipline at your own read is the first move, and it is the one that makes every refusal move afterward available.
If you sit on the franchisor side: run my four tests on the engagement you were about to commission. If Tests Two, Three, and Four point away from the operators who will execute, the engagement you actually need is the governance one — and that is a conversation I will have.
The Closer
I will not sell operating counsel to a party whose economics are collected from the operators who would have to execute it, because in that configuration my framework stops being the operator’s instrument and becomes the collector’s. The test is not the brand on the door, the size of the system, or anybody’s intentions. It is the ledger: who bears the risk, who holds the decisions, who chose the work, and who pays for the change. Point those four at the person standing in the building and I am in. Point them at the party collecting from that person and the answer is no, in my forty-fifth year the same as it was in my first.
Digging Deeper
Positions on the record
- For Franchise Operators — [URL TO CONFIRM]
- For Chain Operators — [URL TO CONFIRM]
- For Independent Operators — [URL TO CONFIRM]
- The Operator’s Contract — [URL TO CONFIRM]
- What Is “The Framework”? — [URL TO CONFIRM]
- Case Study Reduction — [URL TO CONFIRM]
- Diagnostics — [URL TO CONFIRM]
- Fractional Operations Leadership — [URL TO CONFIRM]
- Work With Me — [URL TO CONFIRM]
- Let’s Talk — [URL TO CONFIRM]
Term definitions from the Knowledge Base
- [Franchisor Arbitrage] — https://kb.jeffreysummers.com/docs/franchisor-arbitrage/
- [Operator’s Read] — https://kb.jeffreysummers.com/docs/operators-read/
- [The Two Roads] — https://kb.jeffreysummers.com/docs/the-two-roads/
- [By Design Or By Default] — https://kb.jeffreysummers.com/docs/by-design-or-by-default/
- [Case Study Reduction] — https://kb.jeffreysummers.com/docs/case-study-reduction/
- [Counsel Class Silence] — https://kb.jeffreysummers.com/docs/counsel-class-silence/
- [Coherence Collapse] — https://kb.jeffreysummers.com/docs/coherence-collapse/
- [Cross-Road Arbitrage] — https://kb.jeffreysummers.com/docs/cross-road-arbitrage/
- [Hacksterism] — https://kb.jeffreysummers.com/docs/hacksterism/
- [Guest Contract] — https://kb.jeffreysummers.com/docs/guest-contract/
- Authority To Execute — https://kb.jeffreysummers.com/docs/authority-to-execute/
- The Scapegoat Model — https://kb.jeffreysummers.com/docs/the-scapegoat-model/
