Speed-to-lead is the one metric that tells you, more than almost any other, whether a location is running the business or just holding it.
Every lead is a window. The window opens the moment someone fills out a form, calls the front desk, or texts in a question. The window stays open for a few minutes, maybe a few hours. Then it closes. The lead is either contacted or it is not, and the difference in outcome between those two states is enormous.
The problem for a multi-location operator is not knowing what that window looks like at each location. You know your overall booking rate. You know which locations are performing. What you often do not know, in real time, is which location had a lead sit for six hours yesterday before anyone touched it. You find out when the monthly numbers look soft. By then the lead is long gone.
This is the visibility lag problem that defines multi-unit franchising. FranConnectGO describes it plainly: "by the time financial results show a problem, it may be too late." Operators are "always playing catch-up." Speed-to-lead is where that lag hits hardest, because lead response is immediate-or-never in a way that most business outcomes are not.
What I see in the fitness and wellness accounts we work with
Sneeze It runs performance advertising for multi-location fitness and wellness brands. Workout Anytime, HiTone, and others like them. We are on the ad side, not the operations side, but you cannot manage lead generation without seeing lead response, because the two are inseparable.
What I see consistently is a split. Some locations treat every lead like a live opportunity. They respond within minutes, the call center is dialing, Arin (our call center agent) is tracking the speed-to-lead and the booking rate in the same view. Other locations in the same brand, sometimes just miles apart, are running on a process that has drifted. Forms are going to a shared inbox that nobody owns. Calls are coming in during hours when nobody picks up.
The brand is spending the same ad dollars in both locations. The leads are of similar quality. The outcomes are not close.
The reason you cannot see this from a portfolio level is that each location's data lives in its own silo. You might pull reports weekly. By the time the pattern is visible, you have already paid for a month of wasted leads.
The structure that fixes this
I run Sneeze It on an OTP chart. Every seat has one owner. Arin, our call center manager, has a row on the scorecard. Her row shows appointments booked, speed to lead by project, and show rate. Tally, our KPI agent, updates those numbers throughout the day. Dash, our analytics agent, flags when any account falls below its baseline.
The key is that the number is visible in the same place as every other number. Bogdan, our COO, can look at the same scorecard Janine looks at for accounts receivable. Speed-to-lead sits on that chart the same way cash collected sits on that chart. When it drops, it surfaces at the same meeting, in the same rhythm, with the same accountability conversation.
For a multi-location operator, the same structure applies at the portfolio level.
Each location is its own OTP org. It has its own chart, its own seats. The location's Arin-equivalent (a call center agent, a front desk seat, a human manager) owns speed-to-lead on that location's scorecard. The location's Radar-equivalent runs the daily briefing and flags when response times drift.
At the portfolio level, those location-level KPIs roll up into a single super-metric. Not a weekly report someone emails. A live number. The portfolio view shows speed-to-lead across all locations, not as a flat average that hides the outlier, but as a set of values you can compare location to location.
The location sitting at 18 minutes average response time shows up next to the location sitting at 4 minutes. You did not have to wait for the month-end report to see that.
Presets: set the standard once
The other thing speed-to-lead reveals is an operations consistency problem. The reason one location responds in 4 minutes and another in 18 minutes is usually not that one location has better leads. It is that one location has a cleaner process. A clearer handoff from lead-in to first contact. A team that knows what the standard is.
In a franchise, the standard is supposed to come from corporate. That is the whole structure of the model. But as Operandio and Trainual both document, without centralized enforcement systems, "each unit begins operating as an independent business," and SOPs drift. A multi-unit operator with 20 locations cannot manage SOPs by sending a monthly PDF.
OTP's portfolio feature addresses this structurally. The portfolio (the corporate layer) sets presets that member orgs inherit. Corporate defines what a location's scorecard looks like. What KPIs every location tracks. What the speed-to-lead target is. And critically, corporate can lock those presets. The location cannot remove the speed-to-lead row from its scorecard. The standard is enforced at the chart level, not the email level.
This is not a workaround. It is the franchise model mapped to software. Franchisor sets the standard. Franchisee executes against it. The difference is that the standard is now queryable in real time instead of interpretable by the franchisee at their own discretion.
A worked example: what this looks like in practice
Imagine a 12-location fitness brand. Each location has its own OTP org. At each location:
- The front desk or call center seat owns speed-to-lead and show rate.
- The location's Arin-equivalent updates those KPIs daily.
- The location's Radar-equivalent runs a morning briefing that flags if any lead from yesterday has not been contacted.
- Tally keeps the numbers current so nobody is relying on a manual push.
At the corporate level, the portfolio org rolls up speed-to-lead from all 12 member orgs into a super-metric. Corporate sets the target (say, under 5 minutes average). That target is locked via presets so every location scorecard shows the same target. When corporate looks at the portfolio view, they see all 12 locations, ranked by speed-to-lead, against the same target.
The location at 18 minutes is not hidden in a monthly spreadsheet. It is the red row at the bottom of the portfolio view, visible today, not next month.
The conversation that follows is a coaching conversation, not a forensics project. You know which location, you know the gap, and you know it while the pattern is still correctable.
Why this matters more as concentration increases
Franchising has concentrated sharply. About 19.3% of franchisees now control 58.8% of all locations, according to FRANdata and the IFA. Operators with 50 or more units grew 118.52% between 2010 and 2018, the fastest-growing tier in the industry.
That concentration means the people running the most locations are running portfolios in the true sense. They are not managing a business. They are managing a system of businesses. And a system of businesses needs system-level visibility, not location-level reports assembled by hand.
Speed-to-lead is a sharp example because it is immediate, measurable, and directly connected to revenue. But the same logic applies to show rate, appointment rate, same-store sales, labor percentage, and every other KPI that varies by location. Portfolio visibility is not a reporting convenience. It is the operational prerequisite for running at scale without always being behind.
The mission at Sneeze It, and the reason I built OTP, is to let agents carry the operational work so people are free for the work that matters. For a multi-unit operator, the work that matters is coaching the underperforming location, not building the spreadsheet that reveals it.
The portfolio feature in OTP, available now in early access, is the structure that closes the visibility lag. One chart per location. One portfolio view for the operator. The slow location shows up before the leads are gone.
See the live chart
You can ask the OTP MCP to show you what a speed-to-lead super-metric looks like at the portfolio level, including how member-org KPIs feed up into a portfolio-level 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 a portfolio super-metric is structured and what member-org KPIs feed into it."
What comes back is the actual data model for how location-level KPIs roll up into a corporate view. That is the architecture this entire post is describing, and seeing it live is worth more than the explanation.