> For the complete documentation index, see [llms.txt](https://guide.charityvest.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://guide.charityvest.org/about-our-venture/how-we-make-money.md). # How We Make Money How we serve donors with no-or-low-fee giving experiences and keep the lights on. The Charityvest venture makes money in three ways: 1. **Admin fees.** The main way Charityvest creates revenue is by charging an administrative fee for assets in its investment accounts, like other donor-advised funds. The difference is, we offer a modern experience, while being more affordable, thanks to technology. 2. **Workplace giving programs**. We operate workplace giving programs for companies and charge a software-as-service fee to them for this service. 3. **Community Funds.** Our Community Funds collaborative giving tool is a paid offering, either via an optional tip prompt for donors to Community Funds, or a quarterly fee based on total grant value. Some donors have asked if we can really create an attractive business with our model and fee levels. **The key to our business lies in our technology,** which creates significant efficiencies relative to other DAFs. We don't have the considerable costs that other DAFs do. Thus, we can be more competitive on fees. --- # 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 by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://guide.charityvest.org/about-our-venture/how-we-make-money.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. 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.