# Jerry OS — The Agentic Operating System for Sports Business

> Knowledge, roles, processes and approvals in one system — for organisations in and around the sports business. Client-specific implementation by Jerry Digital.

Canonical URL: https://wearejerry.com/en/jerry-os/

## Frequently asked questions

### What is Jerry OS?

The agentic operating system for organisations across the sports business ecosystem: knowledge, roles, processes, tasks and approvals in one shared system. AI agents take on clearly defined tasks; people lead, decide and approve.

### Isn't this just another AI tool?

No. You open a tool when you need it. Jerry OS is built into how you work: it holds knowledge, roles and approvals together instead of scattering them across tools. It does not replace a decision, it makes sure the decision is taken on the basis of everything the organisation already knows.

### What does this have to do with sport?

Not the imagery, the principles. High-performing organisations in sport work with clear roles, shared processes, the right combination of capabilities for each task and systematic learning. That is exactly what Jerry OS transfers to the collaboration between people and AI agents.

### Is it available yet?

Jerry OS is available as a client-specific implementation. Standardised modules and reusable product components are being developed in parallel; the concrete scope is defined bindingly for each project.

### What happens to our data and approvals?

They stay with you. Approvals, decision authority and escalation are explicitly governed — that is the difference between agentic work and automation. What you can continue to approve, reject and stop, we name concretely in the project.

### We are not a sports company.

We developed it for the sports business because that is where we come from. It can be used anywhere work happens under high pressure, with distributed knowledge and changing teams.

### Do we get the same system you use internally?

No. Jerry OS is a productised operating model and an implementation framework — for every client a system of their own is created, based on their organisation, their knowledge and their governance.

### How is this different from "we'll build you an AI agent workflow"?

A workflow is a chain of steps — it does not know what your company is. Tools such as LangChain, Copilot Studio or UiPath orchestrate agents; none of them names and checks the properties of the organisation they work for. Jerry OS starts at the other end: it describes your organisation — roles, knowledge, processes, approvals — and the system follows from that. A workflow is finished when it runs. An operating system is the basis for the next case, the one nobody knows yet.

### Can the system change itself?

It learns — but it may not move the boundaries of its own learning. What gets checked, who approves and what is off limits, it does not change by itself. That boundary is part of the system, not a setting inside it. Measured in our own way of working: zero breaches across fourteen changes to the boundaries.

### Do we need our own AI subscriptions for this?

No. We take on running the AI: the services that power Jerry OS are procured and managed by Jerry — one price, your approvals. The providers are named in the data processing agreement, not on a slide. And you can leave at any time with your data and artefacts — held separately per client.

## Contact & organisation

- We are Jerry (We are Jerry GmbH) · Föhringer Allee 6 · 85774 Unterföhring · DE
- Karsten Streng — Founder & Managing Director
- Web: https://wearejerry.com/ · All pages as markdown twins: see https://wearejerry.com/llms.txt