> For the complete documentation index, see [llms.txt](https://docs.klai.studio/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.klai.studio/engineering-reference-docs/software-testing-overview/ux-ui-checklist/pages/pricing.md). # Pricing 💵 * [ ] Pricing options Subscriptions plans or one-off purchase * [ ] Pricing features What the user will get for purchasing the product * [ ] A free pathway to sign up A way for user to try your product before considering purchase ⭐️ Clearly state the length of the trial period before being charged * [ ] Refund or return policy A user may want to understand this further * [ ] Highlighted price as a recommendation Showcase a price that most users purchase, or they will get the best value from * [ ] Security logo for payment processing Show how you process purchases with a credible vendor for legibility * [ ] Frequency of payments (monthly vs yearly) You may offer an annual option for long term customers that are rewarded with a discount --- # 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://docs.klai.studio/engineering-reference-docs/software-testing-overview/ux-ui-checklist/pages/pricing.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.