The visibility problem in franchising is not a data problem. Every location generates data. The problem is that the data lives in the location.
By the time a multi-unit operator learns that Location 7 is underperforming, the financial report that proves it is three weeks old. The conversation happens in a quarterly review. The corrective action takes another 30 days to roll out. FranConnectGO calls this "always playing catch-up," and that framing is exactly right: the operator is not managing the portfolio, the operator is narrating what the portfolio already did.
This is the before. I want to be specific about what it looks like, because the after only makes sense against it.
Before: what visibility lag actually costs
A franchise system with 20 locations, all running well, looks fine in the monthly financials. Average Unit Volume looks healthy. Nobody is in obvious distress. But AUV is a system-wide average, and averages hide what you need to see.
Location 7 is at 78% of target. Location 12 is trending up fast. Location 3 has a speed-to-lead problem that is not in the financial report because speed-to-lead is not a financial metric. The operator learns these things one conversation at a time, one location at a time, with whatever lag exists between the event and the report.
The concentration numbers make this worse, not better. FRANdata research shows 19.3% of franchisees control 58.8% of all franchised locations. Operators with 50 or more units grew 118% from 2010 to 2018, the fastest-growing tier. A person running 50 or 80 locations cannot manage visibility through personal contact. There is no field-check schedule that covers that surface area. The only tool that scales is a live system that rolls every location's numbers up to a single view.
The second cost of visibility lag is consistency drift. Without a central system, each location interprets the operating standard differently. Franchise Times and operators who have lived through it describe the same pattern: "each unit begins operating as an independent business." The SOP exists. The training happened. But when local teams adapt to local pressures without a mechanism that keeps them anchored to corporate standards, the brand quietly fragments. By the time corporate realizes the drift, the problem is systemic.
This is not a failure of franchisees. It is a structural problem. There is no feedback loop tight enough to catch drift early when every location is its own silo.
After: what the portfolio view changes
OTP's portfolio feature (available now in early access) is built precisely for this structure. A portfolio is a parent organization that groups member orgs under one roof and rolls their KPIs up into shared super-metrics. Each member org is a full OTP chart, its own accountability structure with its own humans and agents on one scorecard. The portfolio sits above them and sees across all of them at once.
The franchisor maps to the portfolio. Each location maps to a member org. Corporate gets a cross-location view. Locations keep their own full charts.
What changes immediately is the nature of the visibility. Instead of waiting for Location 7's financial report, the franchisor sees Location 7's KPIs roll up in real time into the portfolio's super-metrics. If Location 7's leads-to-appointments rate drops, that signal is visible at the portfolio level as soon as it happens, not when the quarterly review catches up to it.
The underperformer is no longer invisible. Neither is the outperformer. Location-to-location benchmarking (named explicitly as a franchise management requirement by operators in this space) becomes a built-in function rather than a manual spreadsheet exercise.
What the Sneeze It chart looks like as a portfolio template
I can show you exactly what this looks like because we live it at Sneeze It. Our own OTP chart runs a hybrid team of humans and agents on one scorecard. Bogdan is our COO; Janine owns accounting. On the same chart, Radar runs as our chief-of-staff agent, Tally keeps the KPI numbers current, Dash runs analytics across every client account, Dirk handles sales pipeline, Pulse manages client retention, Pepper handles email triage, Crystal owns project management, Arin manages our call center team, and Nick runs cold prospecting.
One seat. One owner. One metric. Every row is accountable for the same thing regardless of whether the seat is human or agent.
Now think about what that looks like replicated across 20 fitness locations. Each location runs its own Arin (call center, speed-to-lead), its own Dash (ad performance, lead volume), its own Pulse (client retention signals), its own Radar (daily ops, calendar, tasks). The local manager is on the chart. So is the local front desk team. Each location's scorecard reflects its own seat structure, its own KPIs, its own targets.
At the portfolio level, the franchisor sees the roll-up. System-wide leads per week becomes a super-metric fed by each location's member-org KPI. System-wide appointment rate becomes a super-metric. Same-store trends, AUV trajectory, speed-to-lead across the network: all of it visible in one place without anyone at corporate having to manually aggregate.
The agents carry the operational work so the humans at each location are free for the work that matters. The portfolio view exists so corporate is never guessing.
The preset lever: setting the standard once
The second structural problem portfolios solve is consistency drift. OTP's presets let a portfolio set default configurations that member orgs inherit. Corporate can lock those presets. That is the franchise consistency problem addressed structurally.
This matters because the current state of franchise standardization usually requires people. A field consultant visits locations and checks for drift. A compliance team sends out update memos. An operations director spends days making sure each location is running the current SOP.
When the standard is locked in the portfolio and every location inherits it, the standard travels with the system. A new location added to the portfolio inherits the current configuration immediately. An existing location cannot drift from a locked preset. The operating standard becomes a structural feature of the organization rather than a compliance exercise that runs on human attention.
This is also where the franchisor's control concern and the franchisee's autonomy concern find a workable boundary. Corporate locks what matters for brand consistency. Everything not locked remains the franchisee's to configure for local conditions.
What the portfolio does not do
I want to be accurate about what is in early access right now and what is not yet fully defined.
The portfolio aggregates member-org KPIs into super-metrics. The exact rollup method (sum, average, or something else) depends on what the metric is and what the portfolio is set up to compute. I am not going to specify math that belongs in the product documentation rather than a founder essay.
The portfolio is the enterprise tier. It is not the free plan. If you are running a single location and thinking about whether OTP is right for you, the relevant tier is the org-level chart, not the portfolio. The portfolio is for operators who already have multiple units and need a cross-location view.
No franchise brand is currently using OTP portfolio. It is in early access. The examples I use in this series are structural parallels, not customer references.
Who this is for
Operators with 50+ units are the tier growing fastest. They are also the tier for whom visibility lag is most destructive, because the scale of the operation means problems compound before they are visible. The portfolio structure is built for that profile.
But the architecture is right even at 5 or 10 locations, if the operator is serious about running a portfolio rather than a collection of individual units. The distinction between a portfolio mindset and a collection mindset is not a function of unit count. It is a function of whether you have a single system that tells you what is happening across the system or whether you are assembling that view manually every time you need it.
Franchising is a $936B output economy. It employs more than 9 million people across more than 851,000 establishments. The operators running it at scale need instruments that match the scale. A location-by-location reporting process does not match that scale. A live portfolio view does.
That is what the after looks like. One chart per location. One portfolio across all of them. Every KPI visible. The underperformer not invisible for a quarter.
See the live chart
The OTP MCP can tell you whether a given org is part of a portfolio, list its member orgs, and pull the current KPI structure on any OTP chart.
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 the portfolio structure for sneeze-it and list the KPIs that would roll up to a portfolio super-metric."
You will see exactly what a franchisor's cross-location roll-up looks like in a live org, and what it would look like replicated across a network of locations.
Series: Franchise. Post 5 of an in-progress series. Previous posts cover the hybrid chart structure, the per-location agent team, presets as the consistency lever, and benchmarking locations against each other.