The franchise industry has concentrated in a way that most people outside it have not noticed. About 19.3% of franchisees now control 58.8% of all franchised locations, according to FRANdata and the IFA. The operators at the top of that concentration are not running one brand. They are running two, three, sometimes five. Private equity has noticed. Blackstone holds a majority stake in Jersey Mike's. Bain Capital launched Prosper Growth Partners specifically to buy franchisee businesses. Operators with 50 or more units grew 118% between 2010 and 2018, the fastest-growing tier in the sector.
This is what the industry now calls the multi-brand platform operator. They did not get here by being good at one thing. They got here by building the operating architecture that lets them run more than one brand without the second brand destroying the first.
The core failure in platform operations is not strategy. It is visibility. By the time financial results reveal a problem at one location, FranConnectGO's research notes, "it may be too late." Operators describe their own situation as "always playing catch-up." They are not wrong. The delay is structural. Each brand has its own reporting rhythm. Each location surfaces its numbers on a different lag. The platform operator sits above all of it, watching a dashboard that shows yesterday's picture of a business that moved this morning.
This is the problem OTP portfolios were built to solve.
What a platform operator's org chart actually looks like
Before the portfolio question, there is a simpler question worth answering: what does a multi-brand platform operator's accountability structure look like when it is built correctly?
Each location is its own org. It has its own humans and its own agents. At Sneeze It, our marketing agency, we run a hybrid chart where every seat carries a specific function. Radar is our chief of staff, running the daily briefing and flagging calendar issues. Arin manages the call center team and coaches speed-to-lead. Dash reads the advertising numbers across every account, flags outliers, and publishes the daily analysis. Pulse monitors client retention and spots churn risk before it lands. Dirk manages the sales pipeline. Crystal tracks project delivery. Each of those seats has one job. One owner. The scorecard measures each one.
Now multiply that by five locations. Each location should run this same architecture, adapted for its brand standards. Each location has a Radar-type seat keeping the daily operations honest. Each location has an Arin-type seat watching speed-to-lead and booking rate. Each location has a Dash-type seat reading the numbers. The brands differ. The operating model does not.
The platform operator's problem is that without a portfolio layer, they are reading five separate scorecards to ask one question: which location needs attention today?
The lifecycle of a platform portfolio
The way a multi-brand platform operator grows into OTP portfolios follows a predictable sequence. Understanding the sequence is the fastest way to see where the portfolio adds value and where it does not.
Stage one: the first org. The operator runs a single brand, maybe two or three locations. They set up one OTP org. They put humans and agents on the same chart. Bogdan, the COO-type seat, has rows on the scorecard. Janine, the accounting seat, has rows. So does the agent running call center performance. The discipline is the same for everyone. This is the phase most operators are already in when they start asking about the portfolio.
Stage two: the second brand. The operator acquires or launches a second brand. They set up a second OTP org for it. The second brand has different KPIs, different staff, different operating rhythms. The operator is now reading two scorecards on two separate tabs and doing the cross-location comparison in their head. This is the phase where the visibility lag starts hurting. The operator cannot see both brands in one view. They are making decisions about brand two with brand one fresh in their mind, and vice versa. The comparison happens but the platform for making it is the gap.
Stage three: the portfolio. This is where OTP's portfolio feature becomes the right tool. A portfolio is a parent organization in OTP that groups member orgs under one roof and rolls their KPIs up into shared super-metrics. The second brand's OTP org joins the portfolio as a member. The first brand's OTP org joins as a member. The portfolio itself is not a brand. It is the corporate view above all the brands.
From the portfolio, the platform operator can see a super-metric like total leads across all brands, or total same-store booking rate, or aggregate call answer rate, aggregated from every member org's scorecard. They can benchmark location against location inside a brand and brand against brand across the platform. The comparison that was happening in their head is now happening on a chart.
Stage four: the lock. This is the part that differentiates a platform from a collection of independent orgs. The portfolio can set presets that member orgs inherit. The platform operator defines the operating standard once, the KPI definitions, the scorecard structure, the accountability model, and each member org inherits it. More than that, the platform operator can lock those presets.
For a franchise, this is the consistency problem solved structurally. Without a lock, each location drifts. The SOP gets interpreted differently. The KPI definitions diverge. What one location calls a "qualified lead" is not what the next one calls it, and the comparison breaks before it starts. With a locked preset, the definitions are set at the portfolio level. Every member org runs the same standard. The brand consistency that the franchise model promises is now enforced by the structure, not by the field rep making quarterly visits.
Stage five: the operating rhythm. The portfolio is now live. The platform operator's Monday review changes. Instead of opening five tabs and reading five scorecards, they open one portfolio view. The super-metrics are on top: platform-wide leads, platform-wide AUV trend, platform-wide booking rate. Below them are the member org scores. The underperformer is visible. The outlier location running above standard is visible. The conversation about what the underperformer can learn from the outlier is possible because the comparison is immediate.
The agents running inside each location continue doing their work. Arin at location three is still coaching the calling team and watching speed-to-lead. Dash at location five is still reading the advertising numbers. Those agents are not aware of the portfolio. They do not need to be. They publish their KPIs to their member org's scorecard, and the scorecard rolls up to the portfolio automatically. The platform operator sees the result. The local agents do the work.
What the portfolio is not
The portfolio does not eliminate the need for a strong org at each location. A portfolio of weak member orgs is a weak portfolio. The visibility improvement only helps when the underlying orgs have the discipline that makes their KPIs meaningful. If a location's Dash seat is not publishing accurate numbers, the portfolio super-metric built on that location's data is wrong. The platform operator gains visibility into a number that is not trustworthy.
This is why the lifecycle frame matters. The portfolio is stage three and four of a progression, not a replacement for stages one and two. The operator who sets up their first org, installs the operating discipline, and then expands is the operator the portfolio is built for. The operator who skips to the portfolio without the underlying org quality is just moving confusion up a level.
The portfolio also does not invent the operating model. It surfaces it. The presets are defaults the platform operator has to define. The super-metrics are aggregations the platform operator has to construct from the member-org KPIs that actually exist. The portfolio gives the platform operator a way to see and enforce an operating standard. It does not write the standard for them.
Where this sits on OTP today
The portfolio feature is available now in early access, gated in Labs. It is the enterprise tier. It is not default-on for every org. If you are running a single brand with a handful of locations, the standard org and scorecard cover most of what you need. The portfolio is the right layer when you are managing multiple orgs and the cross-org comparison is a daily operational need.
The agent team approach, letting agents carry the operational work at each location so the people in those seats are free for the work that matters, is available at every tier. The portfolio is the layer that makes that operational work visible to the operator above all the locations.
That is the thesis of this series, applied to the platform operator specifically. A franchise is a portfolio. Each location runs its own org. The platform operator runs the portfolio above them. The operating standard flows down. The KPIs roll up. The comparison that reveals the underperformer and the outlier happens on one chart, not across five tabs.
See the live chart
The OTP MCP exposes portfolio structure, member org KPIs, and super-metric definitions as queryable data, so you can ask about roll-up architecture directly from any MCP client.
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 super-metrics are defined in the sneeze-it portfolio and which member orgs feed into them."
The response shows you the actual portfolio structure, which member orgs are linked, and how the KPI rollup is configured. That is the architecture the platform operator uses to stop playing catch-up.