Cursor Pricing: Individual Seats, Team Pools and Model Usage

Different seats, different procurement channels

Cursor’s official billing documentation lists Pro at $20/month, Pro+ at $60 and Ultra at $200 for individuals; Teams Standard at $40 per member monthly and Premium at $120 per member monthly. It also describes a separate India-only Start tier and custom enterprise pricing. The public subscription fee is not a flat token price, and a Teams purchase is not an unrestricted personal-Pro pool. Actual checkout tax and territory eligibility require account-level verification.

What a model choice can do to the bill

Cursor describes Auto routing and third-party usage fees, including public model API prices and an additional Cursor Token Rate for applicable third-party model paths. That means a heavier or higher-priced routed model can alter spend without changing seat count. Repeated code generation and long-context repository work can increase usage faster than short chat requests. Preserve request logs and model routing if a team wants to explain why its bill differs from the subscription headline.

Team allocation and additional charges

The Teams documentation says seats have included usage pools and permits approved on-demand usage after those pools are consumed. Model family and seat category can have distinct allowances; some pools do not transfer freely among employees. A company should monitor active paid seats, account billing settings and agent cost alerts rather than assuming all included use is centrally shareable cash. Unpaid administrator access should not be confused with a developer seat.

An actionable three-scenario forecast

Consider five developers on Teams Standard: five × $40 gives $200 per month as the listed fixed-seat baseline before taxes. Then model a low, expected and stress case for paid on-demand model usage separately, using actual accounting telemetry rather than a guessed multiplier. An advanced procurement analysis also includes code-review labour, cloud test runs, security requirements and release quality. None of those productivity outcomes follows automatically from a higher advertised plan.

Before choosing a paid tier

Obtain the billing quote for the exact Cursor product, account geography, tier, model or subscription, currency and commitment length. If the provider offers several kinds of meters, forecast each independently rather than summing quantities in incompatible units. The relevant captured meters here include seat_month. Build a low, expected and high workload from your own request logs or editorial schedule; a pricing page is not a credible estimate of how many retries or approvals your team will need.

For governance, add an approval threshold for paid overages, reconcile invoices with metered activity, and schedule a quarterly or release-triggered source audit. The absence of an identified enterprise rate, promotional expiry or regional tax line is not evidence that the amount is zero. This guide does not represent a product trial, capability benchmark, procurement offer or warranty of uninterrupted access.

Historical availability and boundaries

Preserve the precise source version, checked date and any stated effective date before reusing these figures. A model launch announcement may confirm an introductory token rate without proving which private offers remain available; a mutable plan page can describe a later product state. If a source changes after this cutoff, publish a new snapshot instead of silently editing the historical record. Specialised product evaluations belong to the relevant AI 02–09 editorial teams, while this article documents the billing model and its limitations.