> For the complete documentation index, see [llms.txt](https://naplozz.gitbook.io/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://naplozz.gitbook.io/docs/the-roadmap/future-prospects-what-does-the-future-hold-for-nap.md). # Future Prospects: What Does the Future Hold for NAP? Before we look at the future prospects of Naplozz, here is its current usage status. * We delivered our MVP at the end of the summer of 2022. * Around 40 active users constantly using and testing the app. * We have gained valuable team members and partnerships who help us achieve our goals faster and more efficiently. * We are just about to launch our NAP token to revolutionize the project and quality management industry. ### The Future prospects * We plan to allow users to use our educational system to get specific certificates * Our Document Wizard to create different assessment documents will be launched soon so clients can easily order professional and mandatory assessments. * Our Audit system is soon to be beta launched. * We have a great plan to execute our roadmap and build up our community and so as our user base. * For the NAP token, we will implement all the planned utilities while the ecosystem manifesting, also, constantly figuring out new use cases for better work quality. --- # 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://naplozz.gitbook.io/docs/the-roadmap/future-prospects-what-does-the-future-hold-for-nap.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.