One Call Beats Five Visits: Franchise Group Coaching, and When to Refuse It

Franchise group coaching is the practice of answering a repeated problem once, with the affected locations together, instead of five times in five separate conversations. It works when the locations share a cause and one of them already has a workaround. It fails badly when the problem is individual.

The waste is in answering five times without ever noticing you were repeating yourself.

Nobody hears their own repetition

Repetition is invisible from inside a week. The five calls came on Monday, Tuesday, Tuesday, Thursday and the following Monday, separated by two openings, a landlord dispute and a bad set of numbers at a store you like. Each arrived as somebody's problem, and you solved each one properly.

Caseload makes it worse rather than better. Average coverage per franchise business consultant reached 34 units in 2020, after a jump of more than 21% that FranConnect's operations index puts down partly to the pandemic. A coach at that width is a queue processor, and queue processors optimise for closing whatever is in front of them.

Three things follow, and they are all worth catching:

• The fifth conversation is worse than the first, compressed into something efficient, minus the part where you asked what they had already tried.
• The locations do not know about each other. Five owners each believe they have an unusual problem, which is a lonelier experience than the problem deserves.
• Somebody already solved it. In almost every batch I have watched, one location found a workaround in week one and told nobody, because there was no reason to think anyone else cared.

That last one is the whole return. You are not an expert being efficiently distributed; you are the only person positioned to notice that the answer already exists.

Franchise group coaching starts with a log, not a calendar

You cannot batch what you have not counted. The instrument is one line per inbound question — date, location, a phrase for the problem — kept anywhere you will actually keep it.

Read it weekly and sort by cause rather than symptom, which is the part that takes judgement. "Three locations asked about the new packaging" is a symptom. Three asked because the guide assumes a shelf depth half your stores do not have is a cause, and only one of those can be answered on a call.

A working threshold: three locations in a fortnight, same cause. Below that you are pattern-matching on noise.

Then two moves that are easy to skip:

1. Find the location that has not asked. They either solved it or have not noticed it yet, and both are worth a two-minute call. The solver becomes the reason the group call has content.
2. Check whether the theme shows up in numbers as well as questions. Some batches never reach your inbox — a supplier substitution, a labour line drifting the same way at four sites — and those surface only if the data is connected, a return on a franchise POS accounting integration that most brands never claim.

Most brands are small enough for this to be manageable by hand. On the most recent published brand-size distribution — FRANdata's 2017 data, covering roughly 3,800 US franchisors, reported by Franchise Performance Group — 82% of brands ran fewer than 100 units, and at that scale a coach's whole territory fits on one page.

Running the call so it does not become a webinar

The failure mode is a presentation with an audience, and it is decided in the first three minutes.

Keep it small. Five to eight locations, all of whom have the problem. Invite the whole network and you have made a broadcast, which nobody attends twice.

Open with the question, not the answer. "Five of you hit this in the last fortnight — Maria, what did you try first?" The workaround comes from an operator, and you are the convener rather than the source.

Name the person whose fix it is. They earn standing, and the network learns that solving something quietly is worth mentioning — worth more than the fix itself.

Half an hour, one problem. An agenda with three items is a regional call in disguise, and regional calls are where questions go to be deferred.

Send one artefact afterwards — the revised step, a photo of the workaround, two lines of guidance — to everyone, including the locations that did not attend. That is what makes the call worth having twice.

Do not record attendance as compliance. Once operators can be marked absent from a call, a good use of thirty minutes becomes an obligation, and obligations get delegated to whoever is least busy.

When batching is the wrong move

This is the part that decides whether the practice survives, and the failures are always judgement rather than logistics.

When the problem is individual. A franchisee with a cash-flow problem, a partner dispute, a manager they need to remove or a location genuinely behind does not need company. Put that person on a group call and they learn something worse than nothing: that the person paid to help them could not tell their problem from four others. It is reliably one of the franchisee satisfaction warning signs that surfaces in an exit interview two years later.

When the same symptom has five causes. Five stores over on labour is not a theme; it is a coincidence of arithmetic. Broadcast one fix to all of them and four locations implement something that does not apply.

When someone asked in confidence. Anything told to you privately is not raw material for an agenda, however useful it would be to the group.

When a location would be the case study. No operator wants their numbers to be the worked example, and one instance of that teaches an entire network to stop volunteering.

When the real answer is a decision headquarters has not made. Convening five franchisees to discuss a question you cannot answer does not distribute an answer. It organises a constituency, and you will meet it again at the advisory council.

The same test applies to goals: a location behind for its own reasons needs the conversation described in setting a location's own targets, not a cohort call about a shared tactic.

Batching works because it treats a repeated problem as a network problem, which is what it is. It fails the moment it treats a person as an instance of a category. The distinction is not subtle, and the only thing that reliably enforces it is a coach who checks — before sending the invitation — whether the five names on the list actually share anything beyond the shape of what went wrong. That check takes a minute, and it is the difference between the hours franchise business consultant span of control says you do not have and hours somebody would thank you for.

Batching exists because of a load nothing else relieves: why the week never contains the visits.