Hospitality & Tourism

The Company Brain that runs
a 400k-visitor heritage attraction

The knowledge that makes a complex heritage operation run doesn't live in a handbook. It lives in the heads of the people who've been there longest: the estate manager who knows why the west wing closes in February, the visitor experience lead who remembers what happened when they tried that event format three years ago, the conservation officer who can tell you exactly why that one room is managed differently from every other.

That knowledge is invisible until the person who holds it leaves, or is unavailable, or is pulled in seventeen directions during peak season. Then you feel it.

The problem that brought us in

St. Aubyn Estates in Cornwall manages one of the UK's most complex heritage visitor experiences. Multiple teams. Layered history. Operations spanning hospitality, conservation, events, retail, and estate management. The kind of organisation where institutional knowledge is both its most valuable asset and its biggest vulnerability.

The teams were working hard. The systems weren't helping. Information lived in different places for every team. Reports got compiled manually from the same sources every week. New staff took months to reach full effectiveness, not because they weren't capable, but because there was no reliable way to absorb what the organisation knew.

That's the shape of the problem. The specific form it takes is different in every organisation. But across every business we work with, in every industry, the shape is the same.

What we built

The foundation: the Company Brain. We started by making the organisation's knowledge searchable. Processes. Conservation guidelines. Event protocols. Guest experience standards. Operational history. The decisions that shaped how things run today. All of it captured, structured, and made available to the whole team in plain English.

This is a system that understands questions and gives real, useful answers and guidance. It's not just a document library. A staff member can ask "what's the procedure for a venue hire enquiry over £5,000?" and get an answer from the organisation's own records, not a generic response from the internet.

The first intelligent workflow. We built the first workflow together: a visitor-facing system that handles enquiries. The brief was simple: visitors needed a better way to plan their trip and know what to expect in their journey. From ticket types, to whether they'll walk or take a boat, the visitor experience is enhanced and staff spends less time answering the same questions over and over.

That proved the platform worked. More importantly, it proved to the team what was possible. They know the operation better than we do. That's where the next ideas came from.

What the full operating system looks like

As we partner with clients like the Mount, OS Expansion allows the system to compound. Monthly workshops with the senior team. New Intelligent Workflows going live, one after another, as the team identifies the next problem worth solving and creating value for their visitors.

The operating system grows with the organisation. Every new process added means every future workflow is smarter. The connections mean the team works from one place instead of ten. And because the system is built on the estate's own context (its specific knowledge, its specific history) it does things that generic AI tools simply can't.

What this means for hospitality and tourism businesses

The specifics of a heritage attraction are particular. But the underlying challenge (scattered institutional knowledge, disconnected systems, time lost to work that shouldn't require human attention) shows up in every hospitality and tourism context we've worked in.

Hotels, visitor attractions, tourism operators, experience businesses: the operating model is different but the knowledge problem is identical. The team that knows how things work is the bottleneck. The AI operating system is what changes that.

If you're running a hospitality or tourism business and this sounds familiar, a discovery call is the right place to start. We'll listen to what's actually happening and tell you honestly whether we can help.

Start with a Foundation Assessment See the case study →

Frequently asked questions

What is an AI operating system for a hospitality business?
An AI operating system for hospitality has three layers: Context (your institutional knowledge captured and made searchable), Connections (a unified platform across email, booking systems, CRM, and documents), and Workflows (intelligent automation that handles routine tasks like enquiry triage, report generation, and meeting follow-up without manual effort).
How does the Context Layer work for a heritage attraction or hotel?
The Context Layer captures the institutional knowledge that normally lives in long-tenured staff's heads: conservation guidelines, event protocols, guest experience standards, operational procedures, estate history. This knowledge is made searchable so any team member can ask questions in plain English and get answers from your own records, dramatically speeding up onboarding and ensuring knowledge isn't lost when people leave.
What AI workflows work best for hospitality and tourism operations?
The highest-impact intelligent workflows for hospitality include: visitor enquiry triage that routes and drafts responses before staff read them, automated weekly operational reports compiled from booking and visitor data, meeting notes and task extraction, and knowledge-retrieval systems for front-line staff. The right workflow depends on where your team loses the most time.
How long does it take to install an AI operating system in a hospitality business?
The Foundation Install (Context, Connections, and Workflows configured in your business) typically takes 2 to 4 weeks. The first intelligent workflow goes live in the same period and proves the system works. The full operating system builds over time as the team identifies new problems worth solving.
What is the difference between AI tools and an AI operating system for hospitality?
AI tools solve one specific problem but don't connect to your broader operation. An AI operating system is built on your specific business context: your records, your processes, your history. This makes every workflow more accurate and relevant than anything built on generic training data. The operating system compounds over time; point tools stay static.
More from the blog

How a marketing agency stopped losing time to work it had already done

Read more →

When your whole business is knowledge, and it's not organised

Read more →