> For the complete documentation index, see [llms.txt](https://wiki.beabee.io/community-journalismus/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://wiki.beabee.io/community-journalismus/english/pioneer-portraits/mecseki-muzli-hungary/revenue-streams-and-finance.md). # Revenue Streams & Finance Mecseki Müzli relies on multiple revenue streams to sustain its operations. Despite three years of existence, the platform is still striving to achieve self-sustainability. At present, grant funding, along with subscriptions, supports a team of three people and covers operational costs until September 2024. The revenue mix includes: * € 370/month from paid Newsletter subscriptions: Subscriptions are at the heart of its revenue structure, offering different tiers with varying levels of access and exclusivity. Presently, there are 685 newsletter subscribers, with 89 of them paying for the service. Furthermore, 33 individuals voluntarily contribute a little extra. * € 100/month from Sponsorships: A local NGO is sponsoring a section on local history in the newsletter, contributing $25 per newsletter. * € 30.000 in grants from IPI (20,000 for one year) and Internews (10,000 for 6 months) * Donations: So far, three individuals have made small donations. * Content partnership: A content-sharing arrangement with the media outlet Telex, where Ervin works. This partnership offers the opportunity to generate additional value through regular long-form pieces that can be incorporated into the Mecseki Müsli newsletter. Güth sees the greatest potential for revenue growth by expanding the Telex partnership to a higher level and increasing the number of subscribers. He is contemplating discontinuing the free version of the newsletter and transitioning to a model where everyone is required to pay, especially since the current conversion rate from free to paid subscribers already stands at 50%. Güth believes he could potentially reach a total of 3,000 people with his newsletter. --- # 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://wiki.beabee.io/community-journalismus/english/pioneer-portraits/mecseki-muzli-hungary/revenue-streams-and-finance.md?ask=&goal= ``` `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.