Cursor restructures Teams pricing: $32 Standard vs $96 Premium per seat

Cursor split its Teams plan into Standard ($32/seat/month annual) and Premium ($96/seat/month annual) tiers from July 1, 2026, separating heavy agent users from typical usage. Procurement teams comparing AI coding tool costs now need to budget per-seat rather than per-tool.

Cursor — one of the two most-adopted AI coding tools alongside Claude Code — has restructured its Teams plan pricing, effective for new customers immediately and for renewing customers on billing cycles starting 1 July 2026.

What changed

Teams seats now split into two tiers. Standard costs $32 per seat per month on an annual plan ($40 monthly), with usage split across two pools: one for Cursor’s own models plus Auto, and one for third-party API usage. Premium costs $96 per seat per month annual ($120 monthly) and includes five times the usage of Standard for three times the cost — aimed at the heaviest agent users, the ones currently driving unpredictable overage spend.

Cursor’s stated reasoning is that its in-house Composer 2.5 model is now cheap enough to run that it could expand the Standard pool without raising the price. Admin dashboards also gained spend forecasting and per-seat usage visibility.

Why this matters for budgets

AI coding tool spend has stopped being a rounding error on engineering budgets and started being a line item procurement teams actively manage. The shift from flat-rate to tiered, usage-aware pricing — already underway with GitHub Copilot’s move to token billing — means the real cost of an AI-assisted development team now depends heavily on how agentically your engineers work, not just headcount.

For founders and product leads commissioning a build, the practical takeaway isn’t which tool your agency uses — it’s whether they’re tracking and controlling this spend deliberately, or treating it as a fixed cost that quietly creeps. We factor AI tooling costs into project scoping as standard. More on how we work on the AI-assisted development page, or get in touch to talk through a project.

← All research

More research.

GitHub's Copilot metrics now flag developers whose usage data is missing

GitHub's 5 November 2026 changelog adds fields to the Copilot usage metrics API showing which users send no telemetry or run outdated editors. AI coding tool reporting now admits its own blind spots.

Read ›

Claude Code 2.1.323 adds experimental Code Mode and plugin version ranges

Claude Code 2.1.323 adds an opt-in Code Mode where Claude writes JavaScript to call its tools, and lets plugins declare which Claude Code versions they support. Claude Code teams get more control over extensions.

Read ›

GitHub Apps can now manage enterprise Copilot seats through the API

GitHub's 10 November 2026 changelog lets enterprise GitHub Apps assign and remove Copilot seats through a new permission. Seat management for AI coding tools can now be automated.

Read ›

GitHub will switch off Dependabot alerts on year-old inactive repositories from 8 December

From 8 December 2026, GitHub will turn off Dependabot alerts on most repositories with no activity in the past year. If you own software that is stable but unmaintained, your security alerts go quiet.

Read ›

Gemini 4 Carbon arrives in GitHub Copilot, and it can switch itself on for your whole organisation

GitHub made Gemini 4 Carbon generally available in Copilot on 10 November 2026 across ten clients. Under default model enablement, Business and Enterprise organisations get new models automatically unless an admin opts out.

Read ›

Claude Code 2.1.322 adds fast mode on Google Vertex, with a quiet fallback to standard speed

Claude Code 2.1.322, released 10 November 2026, adds fast mode on Vertex in the global, US and EU regions. If Vertex refuses it, Claude Code falls back to standard speed.

Read ›

Start a project

Building with AI? Let's talk.

Tell us what you are building. We'll give you an honest view of the right approach.

Start a projectSee our work