> ## Documentation Index
> Fetch the complete documentation index at: https://docs.getenso.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Plan Types

> Enso supports multiple plan types to help you model your pricing and billing strategies. Understanding these plan types is essential for setting up your products and services correctly.

## Overview

Enso supports **four main plan types**:

* **One Time Fixed Fee**
* **Recurring Fixed Fee**
* **License Fee**
* **Usage Fee**

Below, you'll find a description of each plan type, when to use it, and practical examples.

***

## 1. One Time Fixed Fee

> **Use this plan type if there is a single, upfront fee to be paid.**

**Example:**\
A setup fee for onboarding a new customer.

```mermaid theme={null}
flowchart LR
    Customer-->|Pays once|Provider
```

**When to use:**

* Onboarding/setup fees
* One-time purchases
* Non-recurring services

***

## 2. Recurring Fixed Fee

> **Use this plan type for regular, fixed payments (e.g., monthly or yearly).**

**Example:**\
A monthly subscription for a SaaS product.

```mermaid theme={null}
timeline
    title Recurring Fixed Fee Example
    Monthly Payment : Payment occurs every month
```

**When to use:**

* Standard subscriptions
* Maintenance contracts
* Memberships

***

## 3. License Fee

> **Use this plan type for recurring fees based on the number of licenses, seats, or subscriptions.**

**Example:**\
A software product that charges per user per month.

```mermaid theme={null}
flowchart TD
    Customer-->|Pays for 10 users|Provider
    Customer-->|Pays for 20 users|Provider
```

**When to use:**

* User-based SaaS pricing
* Seat-based subscriptions
* Any plan where the fee scales with the number of licenses

***

## 4. Usage Fee

> **Use this plan type for charges based on consumption or usage of units.**

**Example:**\
Charging for the number of SMS messages sent or API calls made.

```mermaid theme={null}
flowchart LR
    Customer-->|Consumes 1000 SMS|Provider
    Customer-->|Consumes 5000 API calls|Provider
```

**When to use:**

* Pay-as-you-go models
* API usage
* Communication services (SMS, emails, etc.)

***

## Choosing the Right Plan Type

| Plan Type           | Best For                             | Example              |
| ------------------- | ------------------------------------ | -------------------- |
| One Time Fixed Fee  | Single, upfront payments             | Setup fee            |
| Recurring Fixed Fee | Regular, fixed interval payments     | Monthly subscription |
| License Fee         | Recurring, per-license/seat payments | \$10/user/month SaaS |
| Usage Fee           | Charges based on consumption/usage   | \$0.01 per SMS sent  |

***

> 💡 **Tip:**\
> You can combine multiple plan types for a single product (e.g., a setup fee + recurring subscription + usage charges).

***

## Plan Type Configuration Fields

| Field                  | One Time Fixed Fee | Recurring Fixed Fee | License Fee |  Usage Fee  |
| ---------------------- | :----------------: | :-----------------: | :---------: | :---------: |
| **Amount**             |         ✔️         |          ✔️         | In `prices` | In `prices` |
| **Billing Frequency**  |          -         |          ✔️         |      ✔️     |      ✔️     |
| **Anniversary Cycle**  |          -         |          ✔️         |      ✔️     |      ✔️     |
| **Proration**          |          -         |          ✔️         |      ✔️     |      -      |
| **Meter**              |          -         |          -          |      ✔️     |      ✔️     |
| **Pricing Model**      |          -         |          -          |      ✔️     |      ✔️     |
| **Prices**             |          -         |          -          |      ✔️     |      ✔️     |
| **Revenue Rule**       |         ✔️         |          ✔️         |      ✔️     |      ✔️     |
| **Block Size**         |          -         |          -          | In `prices` | In `prices` |
| **Day/Month of Cycle** |      ✔️ (Day)      |          ✔️         |      ✔️     |      ✔️     |

> ℹ️ **Note:**
>
> * "✔️" means the field is directly configurable for that plan type.
> * "In `prices`" means the field is part of the pricing tiers array.
> * "-" means not applicable.

For full details, see the [Plan Type Schemas](../../enso-models/src/config/planTypes/jsons/).

***

***

## Price Increments

Price increments allow you to automatically increase the price of a plan over time — for example, applying an annual 5% escalation to a recurring contract.

### Configuration Fields

| Field               | Description                                                                                                                                         |
| ------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Increment value** | The amount to increase by — either a percentage (e.g. `5%`) or an absolute value (e.g. `$500`).                                                     |
| **Every**           | How often the increment is applied (e.g. every 1 year, every 6 months). Maps to the billing cycle cadence.                                          |
| **Starting from**   | Which billing period the increment first kicks in. A value of `1` means the increment starts after the **1st period** (i.e. from period 2 onwards). |

### How it works

The **Starting from** value defines a delay — the number of complete billing periods that must pass before the first increment is applied.

| Starting from | Billing frequency | First increment applied |
| ------------- | ----------------- | ----------------------- |
| 1             | Yearly            | Year 2 onwards          |
| 1             | Monthly           | Month 2 onwards         |
| 2             | Yearly            | Year 3 onwards          |

> **Example:** A contract starts in April 2026 with a 5% yearly increment set to start after 1 year.
>
> * **Year 1** (Apr 2026 – Mar 2027): base price, no increment.
> * **Year 2** (Apr 2027 onwards): base price × 1.05.

The contract view shows the exact calendar date the increment kicks in — e.g. **"+5% every year starting from April 2027"** — so there is no ambiguity about when the escalation begins.

### Example

A 3-year contract at \$10,000/year with a 10% annual increment starting after year 1:

| Year   | Price    |
| ------ | -------- |
| Year 1 | \$10,000 |
| Year 2 | \$11,000 |
| Year 3 | \$12,100 |

***

For more details, check out the [Enso Pricing Guide](../pricing-guide).
