Per-Seat vs. Per-Location: What Franchise Software Pricing Models Do to Your Network

Franchise software pricing models do more than set a price: they decide who in your network is allowed to use the product. Seat-based pricing rations access away from the frontline users who make a network tool worth having, while per-location pricing matches the unit franchise brands already budget and bill in.

Most evaluations treat the pricing page as the last conversation. It is closer to a design decision, and you inherit it.

The model is a rationing decision before it is a price

A pricing model does two jobs: it sets what you pay, which everybody negotiates, and it sets what you must ration, which nobody discusses.

Charge by the seat and the buyer's next question is how few seats they can get away with. That is not stinginess; it is the arithmetic the model asks for, and it gets asked twice — at headquarters, funding licences, and at every location, deciding which of its people is worth one.

Charge by the location and the question changes shape. Nobody asks how few staff should be allowed in; they ask whether the location is worth connecting at all — a bigger, slower, healthier question, because a location either belongs in the system or it does not.

Be fair to the seat model before taking it apart. It is honest where value accrues to an individual — a recruiter with a pipeline, a salesperson with a territory — and it is easier to start small, a real virtue in a category where implementations go wrong.

Seat pricing is not greedy; it simply meets a franchise network at its weakest point, where the marginal user matters most and counts for least on a rate card.

What a seat model does inside a network

Watch where the cut falls.

Take an illustrative brand of 40 locations where each store has 14 people who could plausibly use the product. That is 40 of one unit and 560 of the other, same brand, same software — and no franchisee is buying 14 seats for a store.

So the owner buys one. Sometimes two. Who gets left out:

• The assistant manager, running the building on the four days a week the owner is not there.
• The opening and closing shift leads, the only people present when most standards are actually executed.
• The new general manager at the location that opened in March, who needs the manual more than anyone and has been in the job for six weeks.
• The multi-unit operator's district manager, the real reader of anything comparative.

That last exclusion is expensive out of proportion. Multi-unit operators are a minority of franchisees — 19.3% as of 2025 — running most of the estate, with 58.8% of US franchised locations in their hands, on FRANdata's outlook research. A model that makes an operator choose between their district manager and their store managers has picked the wrong fight with the wrong people.

Then the workaround arrives, worse than the exclusion. One login gets shared around a location, the audit trail becomes fiction, and the departing manager still has the password. Every network tool I have seen rationed by seat ends up with a shared credential in it, and nobody ever tells the vendor.

Franchise software pricing models against the unit brands already bill in

Franchising has a house unit, and it is the location. Royalties are charged on it, marketing contributions are charged on it, and every pro forma a candidate is shown counts in it. Item 6 of the disclosure document is where technology gets priced, and 61.9% of franchisors put a fee there, on IFA's FDD analysis.

That matters for practical reasons rather than aesthetic ones.

It is passable through. A cost expressed per location can be recovered in a unit-based fee franchisees already understand. A per-seat cost has to be converted into one at headquarters, on a staffing assumption that is wrong at your smallest store and wrong again at your largest.

It is predictable. A franchisee can model it before signing and budget it in January. A bill that moves when they promote someone teaches them not to promote someone into it.

It moves with the base your royalties move with. Open twelve locations and both change together. When network headcount changes — a good year, a catering push, a second shift — only the seat bill does.

None of this makes per-location pricing generous. It makes it legible, which is a more durable property.

Where per-location pricing is genuinely worse

The case against it, put fairly.

It overcharges the small location. A flat unit price lands identically on a kiosk turning over a fraction of your flagship's volume, and the operator who resents it has the least room to absorb it.

It undercharges intensity, so vendors recover it elsewhere. A store with thirty users costs more to serve than one with four. Where the model cannot see that, the difference reappears as feature tiers, storage limits or a platform fee, and you are back to reading a matrix.

Revenue-banded versions look like a second royalty. Tie the per-location price to sales and you have built something that behaves like a percentage charge — exactly what franchisee advisory councils are most alert to.

It hides a definitional fight. What counts as a location? A store that closed in March, a seasonal site, a unit inside a stadium, one under transfer. Every per-location contract has this argument eventually, and it is cheaper before signing.

Usage pricing is the same problem in newer clothes

The model spreading fastest is consumption: a charge per query, per document processed, per generated answer. Its real virtue is that a network paying only for what it uses cannot be sold shelfware.

It also reintroduces rationing at the worst moment. A franchisee who knows each question costs something asks fewer of them, and the ones they stop asking are the cheap ones — the small standards question on a Saturday night that would have prevented a complaint. The expensive queries are not what gets cut. Curiosity is.

The tell is easy to check: ask what happens to next year's invoice if adoption doubles. If the answer is that the bill doubles, you have bought a product whose success carries a price, and somebody in finance will eventually be asked to slow that success down.

Whatever shape you land on, franchise software pricing models belong in the evaluation rather than the redline. It sets the ceiling on adoption before anyone logs in, which earns it a line in any franchise software pilot program — and a look at whether the rest of your technology stack is already rationed the same way.

A brand does not get the network effect it paid for by buying features. It gets it by having enough of the right people inside the system that the thing has something to see — and no feature list ever survived a pricing model that argued against that.

Have this conversation in the meeting itself: what to ask in the demo.