> For the complete documentation index, see [llms.txt](https://docs.themspkb.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.themspkb.com/msp-foundations/msp-business-models-and-revenue-generation/revenue-streams.md). # Revenue Streams A successful MSP business leverages a mix of recurring, one-time, and complementary revenue streams to ensure financial stability and growth. By diversifying their income sources, they can adapt to market changes and capitalize on new opportunities. This section outlines various revenue streams that MSPs incorporate into their business models. For most MSPs, the recurring revenue is their preferred model. **Recurring Revenue** * Monthly or annual fees from clients for ongoing IT services, such as network management, security management, and IT support. * Subscription-based pricing for cloud services, software, and infrastructure management * Service level agreements (SLAs) that outline the scope of services and associated fees **One-time Revenue** * Fees for one-time projects, such as system installations, migrations, or custom software development * Revenue from consulting services, including IT assessments, strategy development, and technology roadmaps. * Commissions or referral fees from hardware and software vendors when selling products to clients **Complementary Revenue Streams** * Value-added reselling (VAR) opportunities, where MSPs bundle their services with third-party products to offer clients a more comprehensive solution. * Professional services, such as IT strategy consulting, project management, or business continuity planning * Managed security services, including vulnerability assessments, penetration testing, and incident response. * Training and educational services, such as workshops, webinars, or certification courses for clients’ staff --- # 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://docs.themspkb.com/msp-foundations/msp-business-models-and-revenue-generation/revenue-streams.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.