When franchise operators first see OTP's portfolio feature, they make a reasonable mistake. They assume the corporate organization and the portfolio are interchangeable, that one is just a fancier name for the other, and that the difference is cosmetic.
It is not cosmetic. It is structural. And getting this wrong means the whole architecture falls apart before you ever get a useful number out of it.
Here is the distinction, stated plainly: the corporate org is a seat. The portfolio is a container. They do different jobs.
What the corporate org actually is
Every entity in OTP is an org. Corporate headquarters is an org. Each franchise location is an org. Your personal coaching practice, if you ran one, would be an org. An org is where the work happens. It has a chart, seats, KPIs, and a scorecard. People sit in seats. Agents sit in seats. The scorecard tracks performance against targets.
At Sneeze It, our org has a COO seat (Bogdan), an accounting seat (Janine), a chief-of-staff agent seat (Radar), a sales agent seat (Dirk), a retention agent seat (Pulse), an analytics agent seat (Dash), a call center agent seat (Arin), a prospecting agent seat (Nick), an email agent seat (Pepper), a project manager agent seat (Crystal), and a KPI agent seat (Tally). One seat, one owner. The scorecard runs every week.
A franchise's corporate org would look similar. There is a VP of Operations in a seat. There is a field support director in a seat. An agent like Radar runs the morning briefing across corporate channels. An agent like Dash watches system-wide KPIs. The corporate org is where the franchisor's own team operates. It is its own accountability structure.
This is important: the corporate org is not elevated above the location orgs. It is not their parent. In OTP's data model, an org is an org. Corporate does not own the locations. The portfolio does.
What the portfolio actually is
The portfolio is a parent structure that groups member orgs and rolls their KPIs up into shared super-metrics. It is available now in early access through OTP's Labs tier.
A portfolio is not a place where people work. No one sits in a seat inside the portfolio. It has no chair to fill. It is a viewing and standardization layer that sits above the member orgs it contains.
What a portfolio does:
First, it aggregates. Each location org has its own KPIs on its own scorecard. The portfolio takes one or more of those KPIs from across member locations and aggregates them into a portfolio-level super-metric. Instead of asking "what is the appointment rate at the Phoenix location?", you can ask "what is the appointment rate across all thirty locations?" That is a super-metric. The franchisor sees it in one place.
Second, it benchmarks. Because the portfolio is pulling from every member org's scorecard, you can rank locations against each other. The Phoenix location versus the Tampa location versus the Denver location, all on the same metric, in real time. This is location-to-location benchmarking. FRANdata names it as an explicit requirement for multi-unit operators. It is what the portfolio makes structurally possible.
Third, it standardizes. The portfolio sets presets, including defaults for how member orgs are configured, and it can lock them. This is the franchise consistency mechanism. Corporate defines the operating standard once. Every location inherits it. If the standard is that speed-to-lead gets measured by Arin at every location, that is the preset. No location can opt out of the locked version. Brand compliance is not a policy memo. It is structural inheritance.
Why the two objects must be separate
Here is the failure mode I want to head off.
If you try to run the corporate org as the portfolio, you collapse two separate jobs into one object and neither job gets done well. The corporate org would need to track both the work its own team is doing (Bogdan's OKRs, Janine's accounts receivable, the pipeline Dirk is working) and the performance of forty locations it does not directly operate. Those are incompatible on one scorecard. The signal gets buried.
More practically: the corporate org team has accountability for its own metrics. When Dirk's cold email count drops, the conversation at the Monday meeting is about Dirk and Sneeze It's pipeline. That is the right level of detail for that scorecard. The moment you ask that same scorecard to tell you what happened to the Phoenix location's show rate last Tuesday, you are mixing operational altitude in a way that makes both conversations worse.
The portfolio separates the altitude. Corporate runs its own org. The portfolio watches the locations. The franchisor team uses both, but they are looking at different objects for different reasons.
Where the corporate org and the portfolio connect
They connect through the people, not through the data model.
A corporate executive who is a member of the corporate org can also be granted access to the portfolio. From there, they see the rolled-up super-metrics, the location benchmarks, and the preset configuration. They are not working inside any location's org. They are looking at the portfolio layer that sits above all of them.
This is the right architecture for how franchise corporate teams actually function. The VP of Operations does not clock in at the Phoenix location. They watch the Phoenix location from corporate. The portfolio is the mechanism for that watching. The corporate org is where the VP's own accountability lives.
What this means for how you build it
If you are a franchise operator thinking about how OTP would work for your network, the sequence is:
Each location gets its own org. Location staff and location-level agents (an Arin for call center, a Dash for ad performance, a Pulse for retention signals) sit in location seats. The location scorecard is the location's truth.
Corporate gets its own org with its own seats and its own scorecard. The strategic and operational work of running the brand from headquarters lives here.
Then the portfolio is created and member orgs are invited in. The portfolio inherits or rolls up the KPIs that matter at the system level: AUV trends, same-store performance, lead volume by market, show rate across locations. Corporate executives who need the system-wide view get access to the portfolio layer.
The three layers (location, corporate, portfolio) are distinct objects doing distinct jobs. Collapsing any two of them is the mistake.
The visibility problem this solves
FranConnectGO's ops teams have described franchise portfolio management as "always playing catch-up" because by the time financials surface a problem, months of revenue opportunity have already been lost.
The portfolio architecture attacks that lag directly. When every location runs Arin measuring speed-to-lead, and Dash watching ad performance, and those KPIs feed into portfolio super-metrics, the franchisor is not waiting for monthly reporting. The super-metric moves when the location moves. The benchmarking shows which location diverged, and when. The preset locks ensure the metric was even being tracked at the location level in the first place.
The mission that drives Sneeze It's agent architecture is: let agents carry the operational work, so people are free for the work that matters. For a franchise system, the work that matters is strategy, expansion, and brand. The portfolio layer, fed by location-level agents, is what makes that possible at scale.
See the live chart
The OTP MCP exposes portfolio structure, super-metrics, and member org relationships as queryable data, so you can inspect how the corporate org and portfolio layers are differentiated in a live system.
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 sneeze-it org and explain how it relates to any portfolio it belongs to or manages."
What comes back is the live structural relationship between an operating org and the portfolio layer above it, which is the distinction this post is about in concrete queryable form.
Series: Franchise. Post 25 of an in-progress series.