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

# Plans

> Compare Project plans and understand how allowances affect your work.

A Project's Plan determines its feature access and allowances. Basic, Pro, and Max are available in self-serve checkout. Enterprise terms are agreed with Videntic. Your plan selection screen shows the price and billing interval that apply to your Workspace; review that total before confirming checkout.

## Compare the standard plans

| Allowance | Basic | Pro | Max |
| - | -: | -: | -: |
| Active Prompts per Project | 50 | 200 | 300 |
| Tracked Competitors per Project | 3 | 5 | 10 |
| Pages per Technical Audit | 500 | 5,000 | 10,000 |
| Technical Audit runs per month | 5 | 20 | 50 |
| Report recipient allowance | 1 | Unlimited | Unlimited |
| Scheduled Analysis | Monday and Thursday | Daily | Daily |

These are the standard Plan allowances. A contracted Project can have different entitlements; check **Settings → Billing** for its effective Plan. The current **Project Reports** screen accepts up to five email addresses even where the Plan allowance is unlimited; ask support if you need more. The monthly Technical Audit allowance applies to manual Audit Runs. Scheduled Audits and Analyses are separate activities.

Basic includes Sira chat, Content Studio, and supported CMS publishing, subject to their own allowances. Pro and Max add larger allowances and more Sira task capacity. Compare the feature list in the app before changing Plans; it reflects the current offering for your Workspace.

## Choose a Plan for your work

1. Estimate how many customer questions you need to measure. Count the Prompts you will keep active, rather than every idea you might collect.
2. Choose the Competitors you genuinely sell against. Share of Voice uses your tracked Competitor set, so adding unrelated brands changes the comparison.
3. Set a Technical Audit scope that covers the pages you intend to improve. Check the page and monthly Audit Run allowances if you expect to recheck fixes often.
4. Review the Plan price, interval, trial eligibility, and payment details on the checkout screen before confirming.

<Info>
  A Trial is offered only when the Project is eligible. The current self-serve Trial lasts three days and is shown during checkout; it is not a separate free Plan. Do not assume a new Project or returning Workspace receives another Trial.
</Info>

## How Prompt allowances work

Your Prompt Library can retain inactive Prompts. The active Prompt count is what uses the Project's allowance. If you reach the limit, review and archive low-priority Prompts before activating more. Keep a stable core of Prompts so changes in your metrics remain comparable across Analyses.

Agency Workspaces use a different purchasing shape: each Project has a feature level, while a Workspace Prompt Pack supplies a shared Prompt pool. The allocation shown in Workspace billing determines how many Prompts each Project can use. A standard Plan's included Prompt count does not apply to an agency Project in that shape.

## Change a Plan

Open **Settings → Billing** for the relevant Project. Review the effective date and lower allowances in the confirmation before proceeding. Existing Prompts and Competitors remain configured after a self-serve Plan downgrade, but a lower limit can prevent you from adding more. If you use an agency Workspace, its shared Prompt Pack is managed separately in Workspace settings; reducing a pack or allocation can deactivate excess Prompts after the lower capacity takes effect. See [Managing your subscription](/billing/managing-your-subscription).

## Related

<CardGroup cols={2}>
  <Card title="Quickstart" icon="rocket" href="/getting-started/quickstart">
    Set up a Project and review its first results.
  </Card>

  <Card title="Managing your subscription" icon="wallet" href="/billing/managing-your-subscription">
    Change a Plan or manage payment details.
  </Card>
</CardGroup>


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.