The call
Run the pilot on Teams seats, from US$30 a month on the new Premium plan, with a team-wide spend limit only admins can change.
Commit Project Rules before day one and put your largest repository in scope from week one. Judge it on spend per accepted change.
Cursor bills third-party models and usage past each seat's weekly pool from a prepaid team balance, and legacy Teams plans turn on-demand usage on by default, so an uncapped pilot can surprise finance in one weekend. Public accounts describe two more ways pilots go wrong: a repository too large for Cursor to load, and teams that end up paying for a second agent beside it. Decide the plan, the spending limit, shared rules, and which tool owns agent work before the first seat is assigned.
When you need this
- Engineers already use Cursor on personal plans, or pay for it themselves.
- You are choosing between Cursor and a terminal agent for the same team.
- A renewal is coming, seat counts will not justify it, and you need evidence of accepted output.
Worked example: what a 20-seat pilot costs and where it breaks
Seats
On Premium, each Teams seat costs US$30, so the pilot costs US$600 a month. Teams still on the legacy plans pay US$40 per Standard seat, or US$800 (GILD calculation from Cursor's pricing).
The spend ceiling
One team was hit with US$2,500 of unauthorized weekend usage, so the monthly team limit goes in before anyone gets a seat.
Seat hygiene
Another team found 66 of 86 seats on an annual plan still held by removed members, so the admin reads seat assignments monthly.
The large repository
Cursor could not load Salesforce's Core monolith of hundreds of thousands of files, and Salesforce scoped workspaces to team-owned modules, so the pilot opens its largest repository in week one.
Evaluation criteria
Plan and seat type
Which plan does the pilot need?
Look forSince announcing the X Subscription on Oct 12, 2026, Cursor sells new plans inside it. These are Plus US$8 (Grok models only), Premium US$30, Super US$100, and Ultra US$200 per month, and Teams seats from US$30 per user per month on Premium. Super seats cost US$100 and Ultra seats US$200. Teams created before the X Subscription keep legacy Standard seats at US$40 and Premium seats at US$120 until they switch, so confirm which plan your contract is on. Enterprise adds pooled usage, invoicing, SCIM, and group-level spend limits. Each paid seat includes a weekly pool for Cursor's own models, and third-party models bill from the first request at API list price plus US$0.25 per million tokens, so budget above the seat price.
Spend controls before day one
What stops one engineer's usage from surprising finance?
Look forOn current Teams plans, usage past the seat pools draws from a prepaid team balance. Set the monthly additional usage limit, a default per-member limit, and per-member overrides; only admins can change them. Legacy Teams seats have on-demand usage on by default, so cap them with the team-wide spend limit. Read per-user spend in the dashboard each week. A seat removed mid-cycle stays billed until the cycle ends if its member used credits.
Shared rules first
Will every pilot engineer start from the same conventions?
Look forCommit Project Rules or AGENTS.md before the pilot and set Team Rules in the dashboard. Mark Harrison's small team uses AGENTS.md to point to a devprompts directory and explain when each file applies.
Where agent work runs
Will the team use Cursor's agent, or keep Cursor as the editor beside another agent?
Look forPublic accounts split almost evenly, and several teams ended up paying for Cursor and a separate agent at once. Decide in the pilot which tool owns agent work for each workflow, and budget for that choice.
Large codebases
Can Cursor work in the repository the team uses most?
Look forHave the agent finish a real ticket in the largest repository the pilot team uses during week one. If Cursor cannot index it, scope workspaces to team-owned modules, as Salesforce did.
Spend-tracking worksheet
What will you compare when the pilot ends?
Look forCompare each engineer's weekly merged pull requests, review time, post-merge defects, and spend with the pre-pilot baseline. Separate included usage from additional usage and calculate spend per accepted change. Use team analytics for adoption, and the repository and tracker for accepted changes and defects.
Questions to ask vendors
- What is our projected monthly spend per seat at our model mix, including the Cursor Token Rate on third-party models?
- Which usage settings can only admins change, and what are their defaults for our team?
- On an annual plan, does a seat freed by a departing member return to the pool, or stay billed to the end of the term?
- If we hold a legacy request-based contract, what changes at renewal?
Red flags
- A pilot judged on prompts sent or lines suggested.
- Additional usage, or on-demand usage on a legacy plan, with no spending limit.
- Seats for every engineer before one team has proven the workflow on one repository.
- Renewal terms not checked against the pricing model the contract will move to.
Worth evaluating
Listed in no particular order.
Sources
- Official documentation
- 7
- Public source
- 6
- Cursor docs: Team Pricing
- Cursor docs: Models & Pricing
- Cursor docs: Team Dashboard
- Cursor docs: Usage Analytics
- Cursor docs: Rules
- Cursor pricing
- Cursor forum: Introducing The X Subscription, staff announcement (Oct 12, 2026)
- Salesforce Engineering: Cursor and the Core monolith (Sep 8, 2025)
- Salesforce Engineering: operationalizing AI productivity at scale (Jun 23, 2025)
- Cursor forum: a small team keeping agent rules in AGENTS.md (Feb 17, 2026)
- Alex Ghiculescu: notes on rolling out Cursor and Claude Code (Apr 29, 2025)
- Hacker News: US$2,500 of unauthorized weekend usage (Apr 3, 2026)
- Cursor forum: seat management on an annual Team plan (Feb 26, 2026)