The ClubOS Brain: how a football club runs
The vision of ClubOS has always been to help clubs modernise how they make decisions, so that football's most complex decisions can be made on ClubOS. We knew that was a massive task, and it became even bigger once we realised we would also have to build the operating system behind the entire day-to-day running of a football club. Instead of just connecting a club's existing tools and data and building decision intelligence on top, we now had to build the tools and the data layer that feed that intelligence as well, while still building the intelligence itself.
The complexity was clear straight away. The sporting side lives in performance data, scouting targets and squad availability, among many other things. The commercial team is deep in ticketing, sponsorship and matchday revenue. The membership and fan side runs the CRM and manages every relationship the club has with the people who actually fund it. Finance and operations sit underneath all of it, making sure the numbers reconcile. And that only scratches the surface of the roles, tools, and activities ClubOS needs to support.
Over the years, each of these departments has built its own way of working: its own spreadsheets, its own systems, its own version of the truth and its own context. Those ways of working have got clubs this far, but if we were going to connect them, we needed to use modern technology to build a real understanding of how each department runs day to day, across many clubs. That is what led us to build the ClubOS Brain, and in this blog series we'll cover:
- What is the ClubOS Brain?
- How did we map out an entire football organisation?
- How do we build the software around it?
Building a platform that works like a club does
When people hear "operating system for a football club", they picture a FIFA-like dashboard: one screen, a few numbers pulled together, nice and clean. If that were the job, we'd have shipped it a year ago.
The real job isn't presenting data in a better way. It's capturing the context that would otherwise be lost, the context that explains what the data actually means, and making sure every department works from it. Clubs don't need more data; they need more context.
A football club works a bit like a brain: different roles process information and pass it around the club for other roles to act on, and everything is connected.
What this looks like inside a football club
A player's contract status changes. That single fact needs to land with finance as one thing, with commercial as another, with the sporting side as something else, and with the membership team as something different again, because none of them need the raw update. They need the consequence of it, in their language, for their job.
Capturing that one piece of information is only the start. It then needs to be analysed, interpreted, and sent to every role that depends on it, so each of them can act.
Two halves of the brain
The ClubOS Brain has two halves, built in sequence: one holds the context of a football club, and the other holds the logic ClubOS uses to act on that context.
The first half is understanding. Before we wrote a line of code, we went inside clubs and learned how they really run: every role, what each person needs to do their job, what that job involves day to day, and who depends on the work they produce. So far, that has meant mapping 61 roles, giving us a picture of how a club truly operates, role by role and dependency by dependency. This is what we call the context.
The second half is software. Once you know how the jobs connect and what context needs to be captured, building the product becomes a question of making the system match the real club, which is why we designed 13 platforms around how those roles actually work. This is what we call the logic.
So what have we built with ClubOS? A system that takes a single entry or update and turns it into the right signal for every part of the club that needs to know, in that department's language and in real time.
How has the brain helped us build this? For every activity at a football club, it describes the real workflow behind it, backed by hundreds of interviews about how different clubs actually do that work, and links it to exactly how ClubOS supports that workflow.
Why this is hard to copy
The easy answer to "why can't someone else just build this?" is that it's a lot of work. That's true, but it's the weak version.
The real answer is that you can't even start unless you have the access. You can only build this brain by sitting down with every role across many clubs and learning how the work really flows. We can do that because of the ve2ventures network and because, through Estrella Football Group, we have a direct connection to the clubs themselves. That's access almost nobody else has.
What's coming in this series
This is the first of three posts. In the next two, I'll go deeper into each half of the brain:
- Part two: how we learned the club. The interviews, the roles, and the dependency map underneath everything.
- Part three: how the brain works. The build, and how one update reaches every department that needs it.
We built the connective tissue that makes a club behave like the organism it is, rather than a set of silos. The next post is about what made it possible, and the half of the story that usually gets left out.