> 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/operational-maturity-levels-omls-in-msps/what-are-omls.md).
# What are OMLs?
The Service Leadership Operational Maturity Framework was designed to help MSPs evaluate and improve their operational efficiency, profitability, and client satisfaction. This framework consists of five levels of operational maturity, each tailored to the specific needs and challenges faced by MSPs at different stages of growth and development. By understanding and implementing the framework, MSPs can optimize their operations and achieve long-term success in the industry.
Level 1: Beginning
At Level 1, MSPs are characterized by low to negative financial performance and inconsistent service quality. Traits that support improvement at this level include:
* Implementing basic time tracking and project management systems
* Developing a basic understanding of pricing strategies and profit levers
* Establishing a foundational level of service delivery and customer support
* Creating a basic process for hiring, onboarding, and terminating employees
Level 2: Emerging
MSPs at Level 2 exhibit low to negative financial performance and inconsistent service quality but have started to understand the basics of profit levers. Traits that support improvement at this level include:
* Implementing basic controls and operational processes
* Improving pricing strategies and understanding their impact on profitability
* Establishing forward planning and budgeting processes
* Aligning incentive compensation with operational goals
Level 3: Scaling
Level 3 MSPs typically deliver median financial performance and service quality. Traits that support improvement at this level include:
* Implementing more advanced controls and operational processes
* Refining budget planning and attainment tracking processes
* Ensuring that incentive compensation is directly tied to operational goals
* Streamlining service delivery and enhancing customer support
Level 4: Optimizing
At Level 4, MSPs demonstrate high financial and service quality performance. Traits that support improvement at this level include:
* Focusing on continuous improvement of operational processes and controls
* Utilizing advanced budgeting and forecasting techniques
* Leveraging incentive compensation plans tied to budget attainment
* Implementing advanced service delivery methods and technologies
Level 5: Innovating
Level 5 MSPs are the highest performers in terms of financial performance and service quality. Traits that support improvement at this level include:
* Continuously innovating and expanding service offerings
* Developing strategic partnerships with vendors and other industry players
* Fostering a culture of innovation and growth within the organization
* Utilizing advanced data analytics and business intelligence to drive decision-making
---
# 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/operational-maturity-levels-omls-in-msps/what-are-omls.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.