> 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/common-business-models.md). # Common Business Models MSPs typically adopt one or more of the following business models * **Break/Fix Model:** MSPs provide IT services on an as-needed basis, charging clients for individual services or incidents. This model is less predictable and offers limited recurring revenue. While companies who are living exclusively in this model wouldn’t be classified as a “Managed” Service Provider, many MSPs do still have an element of Break/Fix incorporated into their offering, especially if they are of a lower maturity * **Subscription Model:** MSPs offer a range of IT services for a fixed monthly fee. This model provides a predictable revenue stream and encourages long-term client relationships. * **Tiered Service Model:** MSPs offer different levels of service (e.g., basic, premium, enterprise) at varying price points. Clients can choose the level that best meets their needs and budget. * **Value-based Model:** MSPs charge clients based on the value delivered or the outcomes achieved, rather than the specific services provided. This model aligns the MSP's interests with the client's and encourages long-term collaboration. --- # 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/common-business-models.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.