The conventional wisdom in multi-unit franchising is that you need a field team.
Someone who drives between locations. Checks compliance. Sits in on the morning huddle. Pulls reports from three different systems, consolidates them into a spreadsheet, and delivers a summary every two weeks. The field ops coordinator, the regional director, the area developer's operations manager. Call them whatever you want. The job is the same: be the eyes the franchisor cannot have because the franchisor is not in the building.
This model worked when you had three locations. It starts straining around ten. FranConnectGO puts it plainly: "By the time financial results show a problem, it may be too late... operators are always playing catch-up." The field rep is the lag. By the time the lag resolves, the missed opportunity is already baked into the quarter.
The counter to that model is not a faster field rep. It is removing the lag entirely.
Why the lag exists
The lag exists because the unit is opaque until someone reports out of it.
A single location operates its own schedule, serves its own customers, manages its own staff, and produces its own numbers. If that location has a bad week on lead conversions, the signal lives inside the location's systems until someone extracts it. If the regional director checks in every two weeks, the bad week might be two weeks old before it surfaces. If the field rep handles twelve locations, the bad week at location seven might be three weeks old.
This is not a management failure. It is an architectural failure. The information produced inside the unit has no path out of the unit except through a human who physically collects it.
Franchising has concentrated hard because platforms at scale beat isolated operators. The 19.3% of franchisees who now control 58.8% of all locations (FRANdata/IFA 2026) are not better at running individual units. They are better at running a portfolio. The visibility problem is the central capability gap between a single-unit owner and a platform operator. Fix visibility and you close the gap.
What agents do to the opacity
When a location runs AI agents, the opacity disappears.
An agent is not a tool that sits idle until called. An agent occupies a seat on the location's org chart, owns specific work, and publishes its numbers on a schedule. The location does not need to wait for someone to extract data. The agents are the extraction.
At Sneeze It, we run a hybrid team: humans and agents on the same scorecard, one seat, one owner. Bogdan holds the COO seat. Janine holds accounting. Kristen holds creative direction. Alongside them: Radar in the chief-of-staff seat, running daily briefings and flagging calendar conflicts. Dash in the analytics seat, pulling ad performance across every account and surfacing outliers. Arin in the call center manager seat, tracking speed-to-lead and appointment conversion daily. Pepper in the email seat, triaging client comms and drafting responses. Tally in the KPI-push seat, writing scorecard numbers back to the chart every few hours without anyone asking. Dirk in the sales seat, scanning pipeline and flagging stale deals. Nick in the prospecting seat, drafting cold outreach. Pulse in the retention seat, watching for churn signals before they surface in revenue.
Now apply that to a franchise.
Each location gets its own Radar, tracking daily ops and flagging when something is off. Its own Arin, watching every lead that comes in and measuring how fast the staff responds. Its own Dash, reading ad performance for that location and comparing it to yesterday, last week, last month. Its own Pulse, watching client retention and flagging accounts that have gone quiet.
The agents do not wait for a field rep to ask. They publish. Every day. On schedule.
The location is no longer opaque. It is live.
What the portfolio adds
A live location is useful. Twelve live locations reporting into the same view is a different thing entirely.
OTP's portfolio feature is available now in early access. A portfolio is a parent org that groups member orgs under one roof. Each member org keeps its own full chart. The portfolio holds super-metrics that aggregate KPIs across every member. When location seven's Arin logs appointment conversion at 22%, that number flows into the portfolio's system-wide conversion super-metric alongside the same number from every other location.
The franchisor does not need to ask how location seven is doing. Location seven is on the dashboard. So is location three, which is running 31%. So is location eleven, which just dropped from 29% to 19% in four days.
That drop at location eleven is the visibility event the field rep would have caught in two weeks. The portfolio catches it on day five.
Presets are the other half of this. A portfolio can set standard defaults for every member org and lock them. For a franchise, this is the consistency mechanism. Corporate defines the operating standard: which agents run, what seats they fill, which KPIs they track, what the targets are. Every new location that joins the portfolio inherits that standard. Corporate can lock it. The location cannot deviate from the chart structure without corporate releasing the lock.
This is brand consistency expressed as a structural constraint rather than a policy memo.
The counter-position to the field-rep model
The field rep model assumes that local intelligence requires local presence. Someone has to be there to know what is happening.
The portfolio model with per-location agents assumes the opposite. Local intelligence is produced by the agents inside the unit. The portfolio aggregates it. The humans at corporate interpret it and decide. The field rep, when they exist, is freed from extraction work and can focus on what humans actually do better than agents: relationships, judgment calls, escalations that require authority.
The franchisor with 50 locations and no portfolio is running 50 separate reporting cycles, each with its own lag, each dependent on the quality of the data the location bothers to produce. The platform operator with 50 locations, per-location agent teams, and a portfolio is running one dashboard that reflects what all 50 locations produced in the last 24 hours.
Operators with 50 or more units grew 118.52% between 2010 and 2018, the fastest-growing tier in franchising according to FRANdata. That concentration continues. The platform operators are winning because they can see what is happening before it is too late to act on it.
Agents and a portfolio is the mechanism. It is not the only mechanism. But it is the one that removes the architectural failure without adding headcount.
What the OTP chart for a franchise location actually looks like
One location's OTP org has a small set of seats. A general manager human seat. A front desk or scheduling human seat. Then agents filling the work that produces no revenue when done by a human: daily briefing, KPI tracking, lead response monitoring, ad performance review, retention signals.
The GM reviews the agent-produced briefing each morning instead of compiling it. The agents surface what changed overnight. The GM decides what to do about it. The agents carry the operational load. The GM carries the judgment.
This is the mission at the center of why we built it: let agents carry the operational work, so people are free for the work that matters.
At the portfolio level, the franchisor reviews a briefing that covers every location. The super-metrics show where the system is healthy and where it is not. The presets ensure every location's agents are tracking the same things in the same way. The benchmark is automatic. Location three is not running 31% appointment conversion because a field rep noticed. Location three is running 31% because the agents measured it, the portfolio aggregated it, and the comparison to the system average was built into the view.
The field rep can now spend time at location eleven, where the drop from 29% to 19% in four days is worth a conversation, not a spreadsheet.
The early access caveat
The OTP portfolio feature is enterprise tier and available now in early access at /settings/labs. It is not default-on for everyone and it is not yet fully documented. If you run multiple locations and want to see what rolling your KPIs into a portfolio super-metric view looks like before committing, that is exactly the right time to explore it. The architecture is live. The features that sit on top of it are still being built.
What exists now is the core: member orgs, portfolio super-metrics that aggregate member KPIs, presets that member orgs inherit, and the ability to lock those presets from corporate. That is enough to build a real cross-location view.
See the live chart
You can query the current OTP portfolio structure and see how super-metrics are configured across member orgs, including which KPIs feed the roll-up.
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 the portfolio feature works and what super-metrics a franchise with five locations could track."
What comes back is a live description of the data model, not a marketing page. That is the difference between reading about a feature and seeing how it is actually structured.
Series: Franchise. Post 49.