> For the complete documentation index, see [llms.txt](https://docs.bunny.com/guide/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.bunny.com/guide/tour/product-catalog/whats-a-product.md).
# What's a product?
The diagram below shows the relationship between products, plans, price lists, charges and charge tiers. In the example, we have two different products, Group and Business, each with monthly and annual pricing.
Most SaaS companies launch with a single product, typically named after the company. The company *is* the product. As their revenues grow, some SaaS companies will try to launch additional products to sell to their existing customers in an attempt to increase revenue and stickiness.
The product is the product brand your company is marketing. The plans are the various combinations of features you are offering and the price lists hold the actual charges that will go on the customer's invoice.
The typical SaaS company has three different plans: small, medium and large, which each has different sets of features. Typically, different pricing is offered based on how long you are willing to commit for. In the example above, you save $20 a year on the Group plan if you are willing to pay for the entire year up front.
---
# 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.bunny.com/guide/tour/product-catalog/whats-a-product.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.