Every multi-unit franchise operator I talk to has the same thing: a BI dashboard. Tableau, Looker, Power BI, a custom spreadsheet pipeline that took months to build. The data is good. The reporting is often beautiful. The visibility problem is still unsolved.
This is not a contradiction. The dashboard is working exactly as designed. The problem is that the problem was never about data.
The core failure in multi-unit franchising is accountability. According to FranConnectGO, by the time financial results reveal a problem, "it may be too late," and operators are "always playing catch-up." That phrase is not a data quality complaint. It is a governance complaint. The data arrived. Nobody with a clear seat and a defined response owned the number that moved.
OTP portfolio is not a better dashboard. It is a different class of tool. What follows is the decision tree I would give any franchise operator trying to figure out which one they need, or whether they need both.
Start here: what question are you actually trying to answer?
The first fork in the decision tree is simple.
If the question is "what happened at my locations last week?" you want a BI dashboard. That is the right tool for retrospective reporting, trend lines, variance charts, and board decks. BI tools excel at slicing historical data across dimensions. They are built for that work.
If the question is "who is accountable for the number that dropped, and what are they doing about it?" you want OTP portfolio. The portfolio shows you the scorecard for each location, the seat that owns each metric, and the rollup of every location's KPIs into a super-metric at the franchisor level. It answers the accountability question because the org chart and the scorecard are the same thing.
Most franchise operators need both, in that order. The BI dashboard generates the signal. OTP portfolio assigns the ownership.
The visibility lag problem is not a data problem
About 19.3% of franchisees control 58.8% of all franchise locations, according to FRANdata and the IFA. Operators with 50 or more units grew 118.52% from 2010 to 2018, the fastest-growing tier in franchising. If you are running 12, 30, or 80 locations, you have already discovered that the reporting stack does not scale the way the location count scales.
Here is why. A BI dashboard, however well built, is a display layer. It reports on what the data says. It does not tell you that Location 14's call center agent has no one reviewing her speed-to-lead numbers every Monday. It does not tell you that the ops director responsible for locations 12 through 18 does not have a defined KPI she is accountable for. It does not tell you that when AUV drops at three locations in the same territory, there is no seat on any chart that owns the question of why.
OTP portfolio addresses that structural gap. Each member org in a portfolio (each location) runs its own full hybrid chart: one scorecard, one seat per accountable role, one owner per metric. The franchisor's portfolio rolls those member-org KPIs up into super-metrics. The franchisor's view is not a report. It is a live cross-location accountability picture.
The second fork: humans only, or humans plus agents?
BI dashboards are built for human readers. The signal flows to a person, who makes a decision.
OTP portfolio is built for hybrid orgs, which is exactly what a well-run franchise location is, or should be.
At Sneeze It, our own chart has Bogdan (COO) and Janine (accounting) sitting on the same scorecard as Radar (chief of staff), Tally (scorecard and KPI tracking), Dash (analytics), Dirk (sales), Pulse (client retention), Pepper (email), Crystal (project management), Arin (call center and speed-to-lead), and Nick (prospecting). Each seat has one metric owner, one accountability row. The chart does not distinguish between humans and agents because the operating discipline is the same for both.
A franchise location running OTP can do the same thing. Arin, the call center agent, can own speed-to-lead at each location and push the metric to that location's scorecard daily. Dash can pull ad performance by location. Pulse can flag when a location's lead volume drops 20% before the monthly financial review would have caught it. Radar can compile the weekly briefing for the location manager so she arrives to her Monday with the numbers already organized.
The BI dashboard shows the location manager what Arin's speed-to-lead data says. OTP portfolio shows her that Arin owns that row, the number is below target, and the fix belongs to the location's call center seat.
The third fork: standardization
This is where OTP portfolio has no BI equivalent.
Franchising's core consistency problem is that, without a central system, each location starts operating like an independent business. Policies get interpreted differently. The operating standard drifts. Brand compliance erodes, as Trainual's research on SOP drift describes, "without corporate realizing it."
OTP portfolio solves this structurally through presets. The franchisor sets the default chart configuration and the standard scorecard once, at the portfolio level. Every member org (every location) inherits those presets. The franchisor can lock them. That means the operating standard is not a document the location manager may or may not have read. It is the architecture of their OTP org itself.
A BI dashboard can report on whether locations are hitting the standard. It cannot encode the standard into the structure the location operates from. That is not a criticism. It is a scope difference. The tools are designed for different layers.
The fourth fork: benchmarking
Location-to-location benchmarking is a named requirement in every serious multi-unit franchise operation. Who is the highest performer. What do they do differently. What does the bottom quartile have in common.
BI dashboards can produce benchmarking reports. You can filter by location, rank by AUV or conversion rate, and output a comparative table.
OTP portfolio surfaces benchmarking at the super-metric level. When the franchisor's portfolio rolls up a KPI like speed-to-lead from every member org, the portfolio view shows that KPI across all locations in one chart. The underperformer is visible. The seat that owns the metric at that location is visible. The conversation is not "run a new report to find out who's lagging." The conversation is "Location 22's Arin seat is below the system average. What changed?"
The difference in time to action is significant. Reporting lag, according to FranConnectGO, is what turns a recoverable problem into a revenue loss. The portfolio closes that lag because the accountability picture is always current, not queued for the next reporting cycle.
The decision tree, stated plainly
If your locations have no accountability structure below the financial statements: start with OTP before building more reporting. More data without clearer ownership compounds the lag.
If you have accountability structure but weak visibility: a BI dashboard closes the gap. Get the data in front of the people who already own the numbers.
If you have both and they are not connected: OTP portfolio is the integration layer. Each location's scorecard feeds the franchisor's super-metrics. The BI dashboard can pull from those same sources for historical analysis. They are not competitors. They sit at different altitudes.
If you are running 10 or more locations and want each one operating with the same chart structure, the same seat definitions, the same locked standards: OTP portfolio with presets is the structural answer. A BI tool cannot encode that. It can only report on whether it is happening.
What the portfolio is not
OTP portfolio is available now in early access, gated as a Labs feature at the enterprise tier. It is not a reporting suite. It does not replace a BI stack for historical trend analysis, statistical modeling, or board-level financial reporting. It is the accountability architecture under the reporting. The structure that ensures someone owns every number before the number becomes a problem.
The mission at Sneeze It is to let agents carry the operational work so people are free for the work that matters. At the franchise level, that means each location can run a hybrid chart where agents handle the daily monitoring, the speed-to-lead tracking, the briefing compilation, and the scorecard publishing, and the location manager's attention lands on decisions, not data collection.
The BI dashboard tells you the quarter ended down. OTP portfolio tells you the seat that was supposed to prevent that had no clear metric, no current owner, and no one looking at it on Monday morning.
See the live chart
The OTP MCP lets you query portfolio structure, member org KPIs, and super-metric rollups from any connected AI 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 what a portfolio org looks like and how super-metrics roll up from member orgs."
You will see the actual structure: parent org, member orgs, the KPI sources feeding each super-metric. That is the architecture a franchisor gets, one chart that shows what every location owns and whether they are hitting it.
Series: Franchise. Part 46. Next post: how presets encode the operating standard into each location's OTP chart before the franchise opens.