> For the complete documentation index, see [llms.txt](https://docs.nalpeiron.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.nalpeiron.com/zentitle2-docs/get-started/pricing-and-packaging-with-zentitle.md). # Pricing & Packaging with Zentitle Design good-better-best pricing tiers in Zentitle by mapping offerings to a feature matrix, then let your application check feature entitlements through a full abstraction API instead of hardcoding pl {% embed url="" %} One of the key tasks for a product manager is determining how to price and package your software. This means deciding what plans to market, their price points, and what features to include in each plan. Our plan abstraction approach provides an easy way to manage this at exactly that level. You can maintain your full list of offerings (often called SKUs or stock keeping units) and either manage them within Zentitle or import them from another system. Once you have this product catalog, you can plan how to market these different SKUs and their capabilities. Typically, there's a progression from good to better to best. The entry-level plan starts with basic capabilities at a lower price point. The mid-tier plan, usually the most popular, offers additional capabilities at a higher price point. The top-tier plan may include enterprise or custom offerings. As you define these, you can map them to the classic product feature matrix, specifying which features are included in each offering and making sure they're meaningful to the end customer. Our offering management lets you easily define which features should be enabled for each tier. You can enable or disable individual features and specify custom parameters. For example, you might limit monthly reports or the total number of widgets customers can manage, with different values for each tier. When a customer purchases a license for one of these editions, it generates a specific entitlement with enabled rights and specified parameters, which you can always override if needed. From an application standpoint, instead of checking whether a customer is on "good" or "better" tier, we provide a full abstraction API. Your applications can query whether specific features should be enabled for a customer. This means applications don't need to know about different plans—they only need to focus on enforcing license rights at the feature or parameter level. This separation of business model from code means you won't need to re-architect or re-implement logic when rolling out new plans. The result? More agility and flexibility as you experiment with new offerings and bring them to market. --- # 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.nalpeiron.com/zentitle2-docs/get-started/pricing-and-packaging-with-zentitle.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.