Multi-Unit Consolidated Operations & Reporting
One consolidated operating view across every unit and every concept, built alongside the franchisor systems rather than replacing them.
- Tier
- Flagship
- Build order
- 2nd of 3 on the operator track
- Shape of it
- 8 steps
- At launch
- Runs supervised, with you approving what goes out
The problem this solves
An operator with twelve units across two concepts has two franchisor reporting systems, two POS platforms, possibly two scheduling tools, one accountant and no single view.
So the basic questions of multi-unit operating are hard: which unit has the worst labour variance this week, which is drifting on food or product cost, which manager is developing and which is struggling, and where is the next problem forming.
Instead, problems surface monthly through the accountant, by which point they are a month old.
And brand compliance reporting duplicates data the operator already holds, consuming a day a week that produces nothing for the operator.
How it works, step by step
Every wait, threshold and branch below is a value we set with you during the build, against your stages and your language. None of it is a default we impose.
- What starts it
Step 1Trigger
Unit-level data is consolidated daily from the systems that already hold it: POS, scheduling, payroll, and the brand's reporting where accessible.
Step 2
One view across all units and all concepts, normalised so they can actually be compared, which brand systems never do.
Step 3
Exception thresholds are set per metric and per unit, because a new unit and a mature one have different normal.
Step 4
Daily variance alerts rather than monthly reports: labour percentage, product cost, void and discount patterns, sales against the same day last year.
Step 5
Manager-level views so each general manager sees their own unit and their own exceptions, which is what actually changes behaviour.
Step 6
Brand compliance reporting is assembled from the same data rather than re-keyed.
Step 7
Cash and working capital across units is visible, because an operator financing expansion is managing cash across the portfolio rather than per unit.
Step 8
Period-end reporting to the accountant is produced rather than assembled.
How it gets built
Built inside what you already run
- FranConnect
- ClientTether
- Naranga
- Salesforce
- HubSpot
- or whatever your office already runs on
Nothing to log into and nothing to license. If a system needs a record your platform does not hold, we add the field to your platform rather than starting a second one beside it.
This is the actual build order, in the phases its own steps fall into. It runs in supervised mode first, with you approving what goes out, until you are happy with the tone.
- 1
Build
Confirm the franchise agreement permits data extraction from brand systems. Some prohibit it and some brands technically block it.
Built inside the software you already run, against your stages and your language.
- 2
Map
Inventory the data sources per concept.
Nothing is designed until we have looked at what already exists, including the parts nobody officially owns.
- 3
Build
Build normalisation across concepts. This is the hard part and it is the value, because the concepts genuinely define metrics differently.
- 4
Agree
Set exception thresholds with the operator per unit maturity.
The thresholds, the wording and the names are yours. We write them down with you and get the consequential ones signed off.
- 5
Build
Build the manager-level views.
- 6
Build
Build compliance report assembly.
- 7
Build
Build the cash view.
- 8
Prove
Run one period end supervised.
It runs with a person approving what goes out until you are happy with the tone. Nothing sends unreviewed on day one.
What changes after it goes live
How it runs today
An operator with twelve units across two concepts has two franchisor reporting systems, two POS platforms, possibly two scheduling tools, one accountant and no single view.
After this one is live
The operator can compare their own units, daily, across concepts. Problems surface in days rather than at month end. Managers see their own numbers. Compliance reporting stops consuming a day a week. And the operator finally has a view their franchisors never gave them because it was never in the franchisor's interest to build it.
How to measure whether it worked
Your arithmeticRun with your numbers, not ours
Three numbers: labour and product variance identified within a week rather than a month, hours spent assembling brand compliance reporting, and hours spent at period end. The first is where the money is and the other two are where the time is.
We agree the baseline before anything is built, and we do not take credit for things that were going to happen anyway. There is no figure on this page claiming what we have produced for somebody else, because there is no verified figure to publish.
What we will not do
This is from the same delivery document as everything above it. It is on the page because a supplier who has not thought about it will not tell you, and you would find out later.
Earnings claims are the hardest line in this series and it is a legal one.
- Under the FTC Franchise Rule, any representation about actual or potential financial performance of a franchise is an item 19 financial performance representation, and a franchisor may not make one outside its FDD.
- No system, message, template, dashboard or automated communication may state, imply or infer what a unit earns, could earn, or typically earns. That includes automated content sent to candidates, and it includes anything a system might assemble from real unit data and surface to a prospect.
- System 6 handles real unit-level financial data for an operator. That data must never reach a candidate-facing system. The separation between the franchisor development systems and the operator reporting systems is a compliance boundary, not an architectural preference.
- Every candidate-facing template requires review by the brand's franchise counsel before it goes live. No exceptions.
FDD timing is a legal deadline. Delivery, receipt and the mandatory waiting period before signature are regulated. System 3 tracks them as a record, and that tracking must be built with counsel and must not be treated as legal advice or as a substitute for the brand's own compliance process.
State registration. Several states register franchise offerings and regulate franchise sales communications. What may be said, and by whom, differs by state. Automated candidate communication crosses state lines by default.
Franchise agreements bind the operator. Before any operator-side system is designed, confirm the agreement permits parallel systems and data extraction from brand platforms. Some prohibit both.
Messaging. TCPA and CAN-SPAM apply. Consent per number, quiet hours in local time, immediate opt-out across every system.
Nothing here is legal advice. Franchise law is federal and state, it changes, and the penalties for earnings-claim violations fall on the franchisor personally as well as corporately.
Nothing here is legal advice. Rules in this area have moved more than once recently, and every template that states a commercial term or a guarantee goes to your own counsel before it goes live.
Seven systems forfranchise development.
We build one at a time and prove it moved before starting the next. The tiers are the dependency order, not a price list.
Tier 1Foundational
Nothing arrives late or unowned. These come first because everything above them assumes they are true.
Tier 2Growth
The recoverable money. These work the pools the foundational systems have made visible for the first time.
Tier 3Flagship
One connected system end to end, plus what the owner reads on a Monday. Only once the pieces are proven individually.
- 5Multi-Unit Opening & Expansion Control
- 6Multi-Unit Consolidated Operations & Reportingyou are here
- 7The Morning Brief
The tiers are the dependency order for franchise development, not a price list. Most firms do not start at the first one, because the order is a default and the call is where it gets changed.
A note on sequencing this trade
Do not sell both to the same organisation at the same time. A franchisor also operating corporate units has both problems, and the temptation is to combine them. They are different teams, different systems and different timelines, and combining them is how an engagement stalls.
Sequencing note. For franchisors, Systems 1 and 2 together are the entire first pitch. Lead source truth plus a worked not-ready pipeline usually recovers more than the engagement costs, and both are visible within a quarter, whereas System 4's results arrive only when a unit opens.
Back to the franchise development overview for the stage map and where these fit.
Is this the oneyou need first?
Often it is not. On the call we look at what is actually costing you most right now, which is frequently a different system from the one that brought you to this page. If there is nothing worth building yet, we will say so.