Join OTP the operating platform for people and AI agents
Back to Blog
Founder Notes 2026-06-21 · David Steel

Five ways an automotive-services franchise uses OTP to run every location on one chart

The franchise sector is not a cottage industry anymore. About 19.3% of franchisees now control 58.8% of all franchised locations in the United States. Operators with 50 or more units grew 118.52% between 2010 and 2018, the fastest-growing tier in the system. Franchising as a whole represents more than $936 billion in output, 9 million jobs, and 851,000 establishments.

Automotive services sits in the middle of this concentration wave. PE firms are rolling up franchisee businesses (not just brands), and a single operator may run quick-lube, tire, or repair locations across three metropolitan markets simultaneously.

The core problem every one of those operators names is visibility lag. By the time the financials surface a struggling location, months of revenue opportunity are already gone. You are always playing catch-up.

OTP fixes this with a portfolio. A portfolio is the enterprise tier of OTP: a parent organization that groups member orgs (each location, each with its own hybrid chart of humans and AI agents) under one roof, rolls their KPIs into shared super-metrics, benchmarks locations against each other, and uses presets to set the operating standard once and lock it for brand consistency. It is available now in early access.

Here is what that looks like for an automotive-services franchise, step by step.


1. Each location gets its own hybrid chart

The base unit is one location, one OTP org. That org holds the full chart: human seats (the location manager, the service advisors, the technicians with accountability for throughput and customer satisfaction) and agent seats doing the operational work that does not require human judgment.

At Sneeze It, our chart runs a similar model. Radar, our chief-of-staff agent, handles daily briefings, calendar scanning, and task alignment so no meeting or follow-up falls through. Arin, our call-center manager agent, monitors speed-to-lead and appointment rate daily. Dash, our analytics agent, reads ad spend and lead volume across every client account. Tally, our KPI agent, pushes the numbers from local sources to the scorecard every few hours without anyone touching a spreadsheet.

An automotive-services location would seat similar agents. A Radar-equivalent checks daily appointment volume against technician capacity and flags overbooks before the shop opens. An Arin-equivalent watches phone answer rate and speed-to-call-back on new inbound leads (automotive service-franchise research consistently identifies first-to-respond wins). A Dash-equivalent reads each day's car count and repair order average and trends them against the prior week.

Each location's humans keep their seats, their accountability, their direct KPIs. The agents carry the operational monitoring. One chart, both types, one scorecard.

2. The portfolio rolls every location's KPIs into super-metrics

A portfolio in OTP is a parent organization that groups member orgs. Each member org is one of your locations. The portfolio holds super-metrics: portfolio-level KPIs fed by the member-org KPIs below them, aggregated into a single system-wide number.

For an automotive-services operator running eight locations, the super-metrics would include system-wide car count (the automotive equivalent of AUV, rolled up across all eight locations), system-wide repair order average, system-wide phone answer rate, and system-wide appointment show rate.

None of these require someone to pull eight spreadsheets and build a pivot table on a Sunday night. The portfolio reads from the member orgs directly. Corporate sees the system view. Each location sees its own chart plus where it sits on the system view.

This is the specific failure mode that FranConnectGO documents: by the time financial results show a problem, it may be too late. The portfolio eliminates the lag. If location 4 has a phone answer rate of 41% while the rest of the system is averaging 78%, that gap appears in the portfolio super-metric the same day, not the same quarter.

3. Presets set the operating standard once and lock it

The franchise value proposition is brand consistency at scale. When a consumer drives into a franchise location in an unfamiliar city, they expect the same service experience they got at home. Consistency is the product.

The mechanism in OTP is presets. The portfolio sets preset defaults for the chart structure and scorecard that member-org locations inherit. Corporate defines the seats, the KPIs, the targets, the cadences once. Every location that joins the portfolio inherits that standard. And corporate can lock the presets, which means the location cannot drift from the standard without explicit corporate override.

This is directly analogous to a franchise operations manual, but enforced structurally rather than audited manually. A location that deviates from the standard chart is visible because the deviation appears in the portfolio view. The standard does not erode across 30 locations because someone filed the ops manual in a drawer.

4. Location-to-location benchmarking makes underperformance visible

Same-store sales (growth in units open more than a year) and average unit volume are the two most-cited franchise performance metrics for a reason: they separate the location's performance from the system's performance. A rising tide can hide a leaking boat until the tide goes out.

The portfolio benchmarks member orgs against each other. Every location's super-metric contribution is visible side by side. The operator can see which location is pulling the system average up and which is dragging it down before the quarterly P&L arrives.

At Sneeze It, Pulse, our client-retention agent, tracks account health across every client we manage. Crystal, our project-management agent, monitors delivery across every active project. Neither of them could do that work if the data lived in separate silos per client. The aggregated view is the thing that makes pattern-spotting possible at speed.

A franchise portfolio does the same thing across locations.

5. Dirk and Pepper handle the revenue and communication layer for the whole system

For a franchisor, not just an operator, the portfolio has another function: corporate revenue and communication.

Dirk, our sales agent, runs pipeline management for Sneeze It's own agency revenue. In a franchise context, a corporate-level Dirk-equivalent would track which franchisees are underinvesting in local advertising, which territories are underperforming against plan, and which renewal conversations are approaching. Not at the location level where Radar handles it, but at the portfolio level where corporate owns the franchisor-franchisee relationship.

Pepper, our email agent, drafts and routes communications in David's voice. A corporate Pepper-equivalent would handle franchisee communications: monthly performance summaries, operating-standard updates, renewal reminders, support notices. Written once, sent with consistency, no location falling through the cracks because someone forgot to CC them.

The agents carry the operational work. The people are free for the decisions that require judgment.


Why this matters now

Automotive services franchising is concentrating. PE is buying franchisee businesses at 8-10x EBITDA and rolling them up into platforms. Those platform operators do not have the luxury of visibility lag at scale.

The portfolio feature in OTP is available now in early access (enterprise tier, gated at /settings/labs). The thesis is simple: a franchise IS a portfolio. Each location is a member org with its own chart. Corporate is the portfolio that rolls them all up. The operating standard is a preset. The benchmarks are super-metrics. The visibility is live, not quarterly.

Let agents carry the operational work so people are free for the work that matters.


See the live chart

You can query OTP's MCP server to see how a real portfolio-ready hybrid chart is structured, including how seats cascade from corporate to location level.

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 org chart for sneeze-it and explain how its seat structure would map to a multi-location franchise portfolio."

You will see the live hybrid chart (humans plus agents, one scorecard) that the portfolio feature extends across member orgs. That is the structure every location inherits when a franchisor sets it as a preset.

DS
David Steel

Founder of OTP. Runs an AI agent army at a digital agency. Building OTP because nobody else seems to be building it. Notes from inside the build, not from the conference circuit.

More about David →

More posts on the blog index.

All posts