Sell a Franchise Business at a Premium: Valuation Follows Documentation

Sell franchise business premium valuation outcomes are decided by documentation more often than by unit count. Two brands with identical royalties can price turns apart because one runs on written process a stranger can follow and the other runs on the founder's memory, which a buyer prices as a hiring risk.

Two brands in the same category go to market the same year. Similar unit counts, the same royalty rate, unit volumes within a few points of each other. One clears at a materially better number, and neither founder can explain the gap.

It is almost never a secret. One of those systems could be handed to a stranger on a Monday. The other one could not, and the buyer worked that out in week three.

Same tier, different price

The bands published by advisers who actually run franchise sale processes step up with system size: mid-single digits of royalty EBITDA at the emerging end, the low-to-high teens once a system is scaled. Founders fixate on the step-up, because it looks like a growth problem with a growth answer. Open more units, move up a band.

The mid-market band alone, which advisers put at roughly 8–14x of royalty EBITDA, is wide enough to hold two systems priced a fortune apart.

The spread inside a band is the part nobody plans for. Two brands sitting in the same tier are not offered the same multiple, and the difference cannot be unit count, because unit count is what put them in the tier in the first place. I have set out the full ladder and the other levers under what sets the multiple; documentation is one of five, and it gets its own treatment here because it is the lever founders most confidently believe they have already pulled.

Here is what the buyer is actually pricing. If the operating model cannot be separated from the person who built it, what the acquirer is really buying is an employment relationship they cannot enforce, from someone who has just been paid. Every structure that follows — the retention package, the earn-out, the entry multiple — is that sentence expressed in money.

So the question worth asking is not whether the brand is documented — everyone says yes — but what a stranger would find on testing the claim.

What "documented" means when a stranger tests it

A three-ring binder is not the standard. Four properties are, and a manual can satisfy the first while failing the other three.

• Decision rules, not descriptions. "Maintain adequate staffing" describes an ambition. "Two closers on any night forecast above the volume threshold, approved by the general manager, exception logged" is a rule somebody who has never met you can follow.
• Dated and versioned. A document with no version history cannot be shown to have governed anything. It can only be shown to exist now.
• Evidence it was used. Acknowledgements, training records, field notes that cite a section number. This is what separates a system from a writing project.
• Retrievable at the moment of need. A procedure nobody can find during a shift is an archive rather than a control, and buyers have met plenty of archives.

Read that list as an operator and one thing stands out: three of the four are records, not documents. The writing is the cheap half.

Where a sell franchise business premium valuation is actually decided

Nobody reads your manual in diligence. There is no time, and it would not answer the question anyway.

What a good associate does instead is pick three decisions and trace each one from the rule to a real instance. How a candidate gets approved, and who has ever been declined against those criteria. How a supplier gets removed. What happened the third time a top-quartile operator missed a standard.

That third trace is the one that finds things, because it is where the exception lives. Plenty of brands have a written escalation ladder and an unwritten rule that the ladder does not apply to the operator holding eleven units. Both facts are discoverable. The written rule with a quiet override is worse than no written rule, because it tells a buyer the documentation describes a system that is not the one being run.

Then they call your operators, and mood is not the thing being tested. Contentment is this industry's normal state: across 330 brands surveyed by Franchise Business Review, 82% of owners say they enjoy running the business and 86% would recommend their brand. A buyer is listening for something narrower. Ask an owner how a pricing exception gets approved and you get one of two answers. A process, or a name. Preparing for validation calls is mostly about which of those two your network will say without thinking about it.

The five decisions almost nobody has written down

Founders under-document in a consistent pattern. What goes unwritten is judgement, never the opening checklist or the food-safety log:

1. Who grants exceptions, and against what test. Every system has exceptions. Few have a rule about them.
2. Discount and pricing approvals above the level a general manager holds.
3. Site approval — the reasons a location was declined, which live entirely in the founder's read of a trade area.
4. The escalation ladder past the field coach, including the part where an operator calls you directly and you answer.
5. Why candidates get declined. The most valuable underwriting in the business, and usually the least written.

There is a paper trail that exposes the gap without anyone admitting to it. When practice changes and the disclosure document does not, the operated system and the documented system have drifted apart, and the FDD amendment process is where that shows up in a form a buyer's counsel already knows how to read.

The part that cannot be backdated

Here is the timing problem, and it is why the sell franchise business premium valuation conversation goes badly for founders who start preparing when the banker is hired.

You can write a manual in a quarter. Good ones have been written in less. What you cannot produce in a quarter is the evidence that the manual governed anything: versions with dates, acknowledgements collected as versions changed, field notes citing sections, a log of exceptions granted and refused. That record is made continuously by unremarkable people doing administrative work, or it does not exist.

A buyer knows the difference on sight. A policy library issued three months before a process, with no usage behind it, reads as preparation. The same library with two years of traffic behind it reads as how the company works.

So what you are selling is not the document but the property that your network keeps answering the same question the same way on a week when nobody can reach you — and the only proof of that anyone will ever accept is a record you made before you needed proof.

Drift between the operated system and the disclosed one shows up in one place first: FDD amendment process.