> For the complete documentation index, see [llms.txt](https://kizunai.gitbook.io/kizuna-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://kizunai.gitbook.io/kizuna-docs/13.-revenue-model.md). # 13. Revenue Model ## Revenue Model ### Product-First Monetization KIZUNA follows a simple product-first revenue model. Projects will be able to start with a Free plan to experience KIZUNA... and connect their project knowledge to an AI community agent. As a project grows and requires more knowledge, higher usage, and greater control, it can upgrade to a Paid subscription. The core idea is: START FREE → GROW WITH KIZUNA → UPGRADE WHEN NEEDED After TGE, paid subscriptions are intended to use $KZN as the payment \ token for the KIZUNA ecosystem. ### Why Would a Project Subscribe? A project may start with the Free plan when it only needs basic community support. As the project grows, its information and community requirements also grow. A larger project may need: * More knowledge sources * Higher AI usage * More project context * More frequent knowledge updates * Greater agent configuration * Higher knowledge capacity * Priority processing The Paid subscription unlocks these additional capabilities. The purpose is simple: Projects pay when they need more from KIZUNA. ## Free Plan The Free plan allows projects to experience the core KIZUNA product before subscribing. #### Free Includes **1 KIZUNA AI Agent** Projects can create one KIZUNA AI agent for their project. **3 Knowledge Sources** Projects can connect up to 3 trusted knowledge sources, such as: * Website * GitBook * Documentation * FAQ * Other supported project resources **1 Telegram Community** The KIZUNA agent can be connected to one Telegram community. **Limited AI Usage** The Free plan includes limited AI usage so projects can test the product and understand how KIZUNA works with their community. **Basic Project Context** Projects can provide their basic identity and context to the KIZUNA agent. **Basic Knowledge Management** Projects can manage their connected knowledge sources within the available Free plan limits. ## Paid Subscription The Paid subscription is designed for projects that need more capacity and control from KIZUNA. #### Paid Includes **1 Dedicated KIZUNA AI Agent** Projects receive a dedicated KIZUNA agent configured around their project. **Up to 6 Knowledge Sources** Paid projects can connect up to 6 knowledge sources, giving the agent access to a larger amount of project information. For example: Website + GitBook + Documentation + FAQ + Blog + Additional Official Resource **Higher AI Usage** Paid subscriptions provide higher AI usage limits compared with the Free plan. This allows larger communities to use KIZUNA more frequently. **Advanced Project Context** Paid projects can provide more detailed project information and context to their KIZUNA agent. **More Frequent Knowledge Updates** Paid subscriptions provide greater flexibility for maintaining and updating connected project knowledge. **Advanced Agent Configuration** Projects receive additional configuration capabilities to make their KIZUNA agent better aligned with their project and community. **Higher Knowledge Capacity** Paid subscriptions allow projects to maintain a larger knowledge base compared with the Free plan. **Priority Processing** Paid projects receive priority processing for supported KIZUNA operations. ## Free vs Paid | Feature | Free | Paid | | ------------------- | ------: | ------------: | | KIZUNA AI Agent | 1 | 1 | | Knowledge Sources | 3 | 6 | | Telegram Community | 1 | 1 | | AI Usage | Limited | Higher | | Project Context | Basic | Advanced | | Knowledge Updates | Basic | More Frequent | | Agent Configuration | Basic | Advanced | | Knowledge Capacity | Limited | Higher | | Priority Processing | No | Yes | The exact usage limits and subscription pricing may be adjusted as KIZUNA moves from development into production. ## The Upgrade Path KIZUNA is designed so that projects do not need to pay before they understand the product. The intended user journey is: FREE ↓ Create KIZUNA Agent ↓ Connect 3 Knowledge Sources ↓ Deploy to Telegram ↓ Experience KIZUNA ↓ Project Grows ↓ Need More Capacity ↓ PAID SUBSCRIPTION ↓ Connect up to 6 Sources + Higher Usage + Advanced Features This creates a natural upgrade path based on actual product usage. ## $KZN and Subscriptions $KZN is designed to serve as the payment token for KIZUNA subscriptions. The intended payment flow is: PROJECT ↓ SELECT PAID SUBSCRIPTION ↓ PAY WITH $KZN ↓ KIZUNA SUBSCRIPTION ACTIVATED ↓ ACCESS PAID CAPABILITIES This creates a direct relationship between the KIZUNA product and the utility of $KZN. ## Revenue Generation KIZUNA is currently in the pre-revenue stage. The product is being developed and prepared for future commercial use. Revenue begins when paid KIZUNA subscriptions are activated. The primary initial revenue source is: KIZUNA PAID SUBSCRIPTIONS The model is intentionally simple. KIZUNA does not need to introduce multiple complicated revenue mechanisms at the beginning. The product provides the value. The subscription captures that value. $KZN provides the payment layer. ## Simple Revenue Model The KIZUNA economic model can be represented as: PROJECT NEEDS AI COMMUNITY SUPPORT ↓ KIZUNA PROVIDES THE PRODUCT ↓ FREE PLAN ALLOWS PROJECT TO START ↓ PROJECT REQUIRES MORE CAPACITY ↓ PROJECT UPGRADES ↓ $KZN PAYMENT ↓ KIZUNA REVENUE This keeps the relationship between product usage, subscription demand, and revenue straightforward. ## Product-Driven Growth KIZUNA's revenue potential is directly connected to the number of projects using the platform and the number of projects that upgrade from Free to Paid. As more projects adopt KIZUNA: MORE PROJECTS ↓ MORE AGENTS ↓ MORE COMMUNITIES ↓ MORE PAID USERS ↓ MORE SUBSCRIPTION REVENUE The objective is to grow revenue through genuine product adoption rather than unnecessary token mechanics. ## Current Status **Product:** KIZUNA AI Community Manager **Stage:** Pre-Revenue **Free Access:** Available as the entry experience **Paid Access:** Subscription-based **Payment Token:** $KZN **Primary Revenue Source:** KIZUNA Subscriptions **Free Knowledge Sources:** 3 **Paid Knowledge Sources:** 6 **Primary Community Platform:** Telegram ## Summary KIZUNA uses a simple Free-to-Paid subscription model. The Free plan allows projects to experience KIZUNA with basic capabilities. As projects grow and require more knowledge, higher AI usage, and greater control, they can upgrade to a Paid subscription. The Paid plan provides additional capacity and capabilities, including up to 6 knowledge sources, higher AI usage, advanced project context, advanced agent configuration, greater knowledge capacity, and priority processing. $KZN is designed to provide the payment layer for these subscriptions. FREE → EXPERIENCE PAID → SCALE $KZN → PAYMENT SUBSCRIPTIONS → REVENUE --- # 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://kizunai.gitbook.io/kizuna-docs/13.-revenue-model.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.