> For the complete documentation index, see [llms.txt](https://docs.paigo.tech/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.paigo.tech/saas-pricing/model-pricing-structure/subscription-tier.md).

# Subscription Tier

### Overview

Subscription tiers are very common among SaaS businesses. It's usually the go-to pricing strategy for new businesses. It's easier for both businesses and customers to understand, reasonable and predictable for paying customers. Commonly there are three tiers represent low/medium/high willingness to pay. Replit personal plan is a well-known example of implementing a fixed subscription tier. Its pricing can be found on [this page](https://replit.com/pricing). The core of this pricing plan is a fixed payment every month, and users are set for the usage limit on various things such as storage, transfer or the number of Repl instances. The billing schema behind is a fixed subscription payment with usage entitlement.

### Implement Replit Personal Plan

Replit personal plan can be implemented in Paigo with an offering called `Replit Personal Plan` with subscription price **$20**. This offering will be attached with 4 usage dimensions with configurations below.

<table><thead><tr><th width="246.33333333333331">Dimension Name</th><th width="188">Consumption Unit</th><th>Usage Entitlement</th></tr></thead><tbody><tr><td>Account Storage</td><td>Gigabyte</td><td>10</td></tr><tr><td>Outbound Data Transfer</td><td>Gigabyte</td><td>100</td></tr><tr><td>Always On Repl</td><td>Count-based</td><td>1</td></tr><tr><td>Boosted Repl</td><td>Count-based</td><td>1</td></tr></tbody></table>

###


---

# 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.paigo.tech/saas-pricing/model-pricing-structure/subscription-tier.md?ask=<question>&goal=<user_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.