Here is the honest answer to the question most multi-unit operators actually have: you cannot get a real system-wide view of leads, bookings, and revenue until each location is producing those numbers from a known seat with a known owner.
Most operators already know the output they want. They want a single number: system-wide booked appointments this week. System-wide lead volume. Revenue by unit, compared across units. They are not confused about what to ask for. What trips them is the structure that has to exist underneath the ask.
A roll-up of garbage is garbage. A roll-up of inconsistently defined metrics is noise. A portfolio view that aggregates "leads" from ten locations where each location defines "lead" differently gives you a number that feels decisive and is actually meaningless.
So before the portfolio view, there are five things that have to be true. This post goes through each of them.
1. Each location has to run its numbers from a seat, not a spreadsheet
The classic multi-unit setup is a spreadsheet that one person at each location fills out and emails to corporate on Friday. This produces a number. It does not produce visibility.
The spreadsheet has no owner in the way a seat has an owner. The person who fills it out changes. The fields get interpreted differently. Nobody is accountable when the number is wrong because "I just entered what the system showed me" is a complete and defensible answer.
A seat is different. A seat is a named role on a chart with a metric attached to it and a person or agent responsible for that metric every week. When the number drops, there is a conversation, and the conversation happens with the seat-owner.
At Sneeze It we have Arin as our call center manager seat. Arin reads the CCM-Stats data, tracks booking rate against a 30% target, and flags underperformance by agent before I ever look at a dashboard. Arin is a seat. There is no spreadsheet. The number comes from an owner. Tally, our scorecard seat, pushes that number onto the chart on a schedule, so it is never stale by the time anyone looks. Dash, our analytics seat, holds the cross-account view and surfaces the pattern when one location drifts from the rest.
For a franchise, this means each location needs at minimum a booking-rate seat, a speed-to-lead seat, and a revenue seat. They can be human seats or agent seats or a combination. The seat structure is what makes the number trustworthy enough to aggregate.
2. Each location has to track the same KPIs with the same definitions
This one sounds obvious. It is almost never done.
AUV (average unit volume) is the most widely cited franchise performance metric in the industry. Same-store sales is the standard measure of organic growth. Location-to-location benchmarking is explicitly named as a requirement by every franchise operations framework I have seen. And yet, the most common state I encounter is ten locations tracking twelve different variations of "new leads" in twelve different tools.
OTP handles this through presets. When a franchise runs on an OTP portfolio, the parent organization (the franchisor org in portfolio mode) sets the standard scorecard as a preset. Every location that joins as a member org inherits that preset. The franchisor can lock it. That lock means "this is what a lead is. This is what a booking is. This is how you count revenue. No local variation."
The preset is the franchise consistency problem applied to data. Most franchise brands spend significant energy enforcing operational standards (uniforms, SOPs, customer experience) and very little energy enforcing data standards. Data standards are what make a portfolio view worth having.
3. Each location has to have a speed-to-lead seat running before leads can be measured at the portfolio level
This one is specific to service-franchise operations, which includes gyms, med spas, wellness studios, and home services. And it is the most common gap I see when operators try to build a portfolio view.
Speed-to-lead is what determines whether a new inquiry becomes a booked appointment or goes quiet. If a location does not have a seat tracking that metric and responding to new leads in a structured way, the "leads" number at that location is measuring inquiries, not real pipeline activity.
At Sneeze It, Arin's seat watches speed-to-lead as a primary metric for the fitness and wellness clients we work with in our ad management business. The data shapes how we advise on staffing and call center setup. Across multi-location brands, speed-to-lead variance between locations is almost always one of the first explanations for why one unit outperforms another with comparable ad spend.
For portfolio-level leads numbers to mean anything, each location needs a seat that owns the response process. That seat can be human (a front-desk manager, a caller, a setter) or it can be an agent seat modeled on what Arin does at our level. Either way, it has to exist and it has to report before the roll-up is valid.
4. The franchisor has to decide what the super-metrics are before building the portfolio
A super-metric in OTP portfolio is a KPI at the portfolio level that is fed by one or more member-org KPIs rolled up into a single number. It is the mechanism that turns "each location's booking rate" into "system-wide booking rate."
The question the franchisor has to answer first is: what are the three to five numbers that, if you had them every Monday for every location, would actually change how you operate?
Not every metric a location tracks needs to roll up. Most of them should not. The value of the portfolio view is not comprehensiveness. It is the ability to look at system-wide lead volume, system-wide booking rate, and system-wide revenue in one place, rank every location against those numbers, and immediately see which units need attention.
If you define the super-metrics before building the portfolio, the portfolio is useful from day one. If you add metrics as you go, you end up with a portfolio view that is as hard to read as the spreadsheet you started with.
The verified franchise benchmarks give a clear starting point: AUV, same-store sales growth, booking rate as a percent of leads, and speed-to-lead response time. Those four numbers, aggregated across locations and ranked, will surface the underperforming units faster than any financial report that arrives after the month closes.
5. Visibility has to be continuous, not monthly
FranConnectGO put it plainly: "By the time financial results show a problem, it may be too late. Operators are always playing catch-up." That sentence describes the monthly financial report. It could also describe a weekly spreadsheet in slow markets.
The franchise concentration data from FRANdata and IFA tells you why this matters at scale: 19.3% of franchisees control 58.8% of all locations. The operators running that 58.8% cannot afford to be playing catch-up. They have too many locations. One underperforming unit that goes undetected for a quarter does not just cost that unit's revenue. It costs the time the operator spends diagnosing it after the fact, adjusting staffing, renegotiating local marketing, and retraining.
What OTP portfolio gives operators with that footprint is a continuous view. The member-org seats push numbers to the portfolio on the scorecard cadence. The super-metrics update as the member numbers update. The underperformer is visible in the current week, not next month.
That is the structural argument for a portfolio view. It is not a better report. It is a continuous view that replaces the report.
The OTP portfolio feature is available now in early access, for organizations on the enterprise tier. If you are building toward this and want to see how the seat structure and super-metric definitions work before you set them up for your own operations, the MCP is the fastest way in.
The five things above are the order of operations. Get the seats right at each location first. Lock the definitions with presets. Define the super-metrics before you wire them up. Then the portfolio view actually shows you something.
And when the system-wide booking number drops, you already know which seat owns the answer.
Let agents carry the operational work, so people are free for the work that matters.
See the live chart
The OTP MCP exposes portfolio structure and super-metric definitions, so you can query how a portfolio groups member orgs and what KPIs roll up to the top level.
In Claude Desktop or Cursor or any MCP client, add this block:
"otp": {
"command": "npx",
"args": ["-y", "@orgtp/mcp-server"]
}
Restart the client. Then ask: "Use OTP to show me how a portfolio org groups its member orgs and what super-metrics are defined at the portfolio level."
You will see the parent-org structure, the member relationships, and exactly which KPIs roll up, which gives you the template for how to design your own franchise portfolio before you build it.
Series: Franchise. Post 8 of an in-progress series.