> For the complete documentation index, see [llms.txt](https://docs.onefootballclub.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.onefootballclub.com/2-the-end-of-fragmented-fan-value/2.3-why-fans-create-value-but-capture-none.md).

# 2.3 Why fans create value but capture none

In both economies, fans create much of the value but capture little of the economic upside.  Their attention funds the media that surrounds the game. Their spending funds the clubs, platforms, and products. Their loyalty and presence give this entire economy its meaning.

Yet the fan is only visible at each point of contact: an impression here, a purchase there, a ticket scan elsewhere. Rarely are they recognized as the person who connects those actions. The reputation a fan builds over years of devotion remains fragmented across media platforms, clubs, and social networks. In pieces, that reputation is worth less to everyone. As a unified record, it could become a source of value and capital for the fan, club, and platform.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.onefootballclub.com/2-the-end-of-fragmented-fan-value/2.3-why-fans-create-value-but-capture-none.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.