CASE 02 · INFRASTRUCTURE
The operating system behind a consolidation thesis
Restaurant consolidation has historically failed at scale because the operational complexity multiplies faster than the platform value. A six-layer technology stack changes that math. The Hospitality Intelligence is the infrastructure thesis that makes the Heritage Experience Platforms consolidation operationally tractable, and the reason 400 basis points of margin expansion is recoverable rather than aspirational.
- $1,829
Per location, per month
fully loaded TCO at platform scale
- 6 layers
From data ingestion to agent orchestration
each layer commercially available
- 400 bps
Margin expansion unlocked
vs. independent operator baseline
- Live
Agent orchestration deployed
Slack, Notion, research enrichment
Six layers, each commercially available, assembled into one operating system.
Layer one is data ingestion: POS, reservation, payroll, and supplier systems pulled into a single warehouse. Layer two is integration, the connective tissue that lets the data move. Layer three is the operating intelligence that runs pricing optimization, labor forecasting, and demand prediction. Layer four is the management surface, where dashboards and exception flags reach the operator on a Tuesday morning.
Layer five is the Deal Intelligence Engine. The same scoring infrastructure that screens acquisitions runs continuously against portfolio company performance, flagging operational drift before it becomes a quarterly miss. Above that, layer six. Agents handle the work that previously required a regional manager: research enrichment, briefing generation, exception escalation.
None of these layers is novel. The thesis is in the assembly. The fund that deploys all six wins margin expansion that no individual restaurant can justify investing in. The fund that deploys only the first three is running a 2018 playbook in a 2026 market.
$1,829 per location per month. The number is small enough that it disappears at platform scale.
Fully loaded TCO per location, including SaaS subscriptions, integration costs, agent inference, and amortized implementation, lands at approximately $1,829 per month at platform scale. For an independent restaurant generating $3M in revenue, that is 0.7% of top line. For the same restaurant inside a 15-location platform, the same stack drives 400 basis points of EBITDA expansion through dynamic pricing optimization, labor scheduling discipline, and supply chain visibility.
The asymmetry is the entire thesis. Independent operators cannot economically justify the stack. Platform operators cannot afford not to deploy it. That gap is the structural moat, and it widens every year as agent capabilities improve and stack complexity decreases.
The fund that treats this as an IT cost will underwrite to legacy multiples. The fund that treats it as the platform infrastructure will buy at seven and sell at twelve.
Agents are the operating layer the previous five were waiting for.
Two agents are currently deployed in production. A Comms Officer that monitors Slack and Notion across multiple workstreams and produces executive briefs each morning, replacing the work previously distributed across three operations managers. A Research Analyst that enriches a structured directory with web-sourced context, running unsupervised against a backlog of two hundred entities.
These agents operate as scoped autonomous workflows running against real data, with structured outputs and accountability. The architecture is open-source, Paperclip on Node and React, which means the same patterns extrapolate to portfolio companies without vendor lock-in. A 15-location restaurant platform deploying this layer offloads roughly 60% of the regional management overhead that historically capped consolidation economics.
WHAT STAYED WITH ME
Premium hospitality will never become a technology business. The next generation of premium hospitality platforms will be built by funds that treat technology infrastructure as the cost of entry rather than the cost of innovation. The operating system is the precondition for the product to scale without losing what made it premium in the first place.
REQUEST THE FULL CASE FILE
The full technical architecture document maps each of the six layers against vendor selection, integration sequence, deployment timeline, and total cost of ownership across portfolio sizes. Twelve pages, PDF, available on request.
Request access