Every multi-unit franchise operator I talk to has the same onboarding problem.
A new location opens. The franchisee gets the brand standards binder, the POS credentials, the vendor list, and a training schedule. Then they get left to figure out how the business actually runs, because "how the business runs" lives inside the heads of whoever opened the last ten locations, not in a system.
Six months later, corporate is looking at financials and wondering why this location is underperforming. By then, as FranConnectGO puts it, operators are "always playing catch-up." The problem was already there in month two, but nothing surfaced it.
OTP's portfolio feature, which is in early access now, changes the structure of that problem. The onboarding is not just administrative. It is the moment you bring the location onto the operating system. Once it is on, everything it does is visible, benchmarked, and held to the same standard as every other location.
This post walks through the four steps of that onboarding, using the actual feature mechanics, so you can see what it looks like in practice.
Step one: Create the location's member org
Before you invite a franchisee, they need an org to join. In OTP, each franchisee location is its own org, with its own chart, its own KPIs, and its own scorecard.
If you are the franchisor running the portfolio, you create the member org for the new location. You give it a name that matches your naming convention for the portfolio. At Sneeze It, we name ours so they sort cleanly by region or brand line. Whatever your convention is, the naming pays off once you have ten, twenty, or fifty locations showing up in a single portfolio view.
The org starts empty. No seats, no KPIs, no people. That gets fixed in the next step.
Step two: Apply the preset
This is the step that separates a portfolio from a collection of disconnected orgs.
A franchise portfolio in OTP can define presets: the default chart structure, the standard seat definitions, and the KPI scorecard that every location should run. When the portfolio applies its preset to the new member org, the location inherits the operating standard. The seats appear. The KPIs appear. The scorecard structure matches every other location in the system.
The franchisor can lock that preset. A locked preset means the location cannot drift from the standard. The accountability chart looks the same because it is the same. The KPIs the location reports are the same KPIs every other location reports. That is how you benchmark across locations. That is how you catch underperformance before it becomes a financial problem.
At Sneeze It, we run a hybrid chart where every seat is either a human or an AI agent, and both are accountable on the same scorecard. When we think about what a franchised version of our model would look like, the preset is how we would enforce that hybrid standard. Each location gets its own Radar seat (chief of staff, daily operations), its own Arin seat (call center, speed-to-lead), its own Dash seat (analytics), and its own Pulse seat (client retention). Those seats are in the preset. Every location that comes into the portfolio inherits them on day one.
The franchisee does not have to design their operating structure from scratch. They get the structure that works, locked to the standard, and they activate it.
Step three: Invite the franchisee
Once the org is set up and the preset is applied, you send the invite.
The franchisee receives an invitation to join the member org OTP already created for their location. They accept the invite and they are in. At that point, they have a chart with seats to fill, a scorecard with KPIs to start reporting, and visibility into their own location's numbers.
What they do not have yet is access to the portfolio view. That lives at the franchisor level. The franchisee sees their own org. Corporate sees the portfolio, which aggregates every location's KPIs into super-metrics that roll up across the system.
That separation is intentional. The franchisee does not need to see every other location's numbers. They need to see their own numbers clearly. Corporate needs to see all of it.
On the corporate side, Bogdan (in our world, the COO) would be the seat that holds accountability for the portfolio health. Janine, our accounting seat, would have visibility into the financial KPIs rolling up from each location. Each super-metric in the portfolio view is fed by the matching KPIs from the member orgs. Lead volume across the system. Appointment rate per location. Call answer rate by market. Same-store trends. The numbers that tell you, in real time, which location needs attention.
Step four: Activate the agent seats
The hardest step is not sending the invite. It is activating the agent seats and getting the franchisee to trust them.
The preset defines the seats. The invite brings the franchisee in. But the agents are not running until someone at the location turns them on and establishes accountability for the outputs.
In a franchise context, this is where corporate earns its onboarding role. The most effective pattern we have seen is a brief session where you walk through each agent seat with the franchisee, explain what the seat does, and establish who the human seat-owner is at that location.
For Arin, the call center seat, the seat-owner is whoever manages the calling team at the location. Arin monitors speed-to-lead, dial volume, and appointment rate. It reports to the franchise scorecard. The seat-owner is accountable for Arin's numbers in the same way they are accountable for their own.
For Radar, the operations seat, the seat-owner is whoever runs daily operations at the location. Radar surfaces what needs attention each day. The seat-owner acts on it.
For Tally, the KPI-push seat, the seat-owner is whoever ensures the numbers are accurate and current. Tally pushes KPI values from local sources into the scorecard. If the numbers are wrong, the portfolio's super-metrics are wrong, and corporate is making decisions on bad data.
That last point is why the hardest step in franchisee onboarding is not technical. The technical setup takes one session. Getting the franchisee to internalize that their KPI accuracy is a system-level obligation, not just a local reporting chore, takes longer. It takes the accountability structure being real. It takes the numbers mattering in the portfolio view the way they matter on their own scorecard.
Once that is in place, the location is on the system. And the system tells you, without waiting for a financial review, whether the location is healthy.
What this looks like at twelve locations
Franchising has concentrated for a reason. According to FRANdata and the IFA, 19.3% of franchisees now control 58.8% of all locations. Operators with fifty or more units grew 118% between 2010 and 2018, the fastest-growing tier in franchising. At that scale, the onboarding problem is a portfolio management problem. You cannot afford to bring each location in ad hoc and hope they figure out the operating structure.
The portfolio plus preset combination solves the structural piece. The invite is a thirty-second action. The preset applies the standard the moment the org joins. The agents activate into defined seats with defined accountability.
What you end up with at twelve locations is a portfolio view where each location's KPIs are rolling up into super-metrics in real time, benchmarked against each other, visible to corporate without a report request. The location that is falling behind on appointment rate shows up immediately. The one that has its speed-to-lead tightened up shows up too.
You are not playing catch-up. You are watching the system run.
The mission at the heart of all of this is the same mission that drives the hybrid chart: let agents carry the operational work, so people are free for the work that matters. In a franchise, the operational work is the same across every location. That is what the preset captures. The agents carry it. The people at each location focus on the things that require them.
That is what the onboarding is actually installing.
See the live chart
The OTP MCP can surface live portfolio structure, member org data, and seat definitions across a multi-org setup, so you can query which locations are in a portfolio, what KPIs are rolling up, and which seats are active.
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 which member orgs are connected."
You will see how the parent-to-member relationship is structured, and that gives you the template for how your franchise portfolio would look once the first handful of locations are onboarded.