Cursor: the pricing arc
Cursor's arc is a seat becoming a meter between June 2025 and July 2026. The Pro plan moved from a count of requests to included compute at API prices with the price held, and within three weeks a public apology and usage refunds priced the transition. Teams agent usage then left fixed request costs for variable credits that rise with the work an agent does, and Auto stopped being unlimited for individuals. Bugbot moved from a per-seat subscription to usage billing. The Teams seat split into standard and Premium classes that differ on included volume, and a local-currency entry plan opened in India. Request, then compute, then seat classes shaped by usage, with one credit spanning every plan.
tracked and read.
first move to latest.
last re-checked.
Last tracked move:
Cursor pricing moves, newest first.
- Jun 16, 2025Licensing + Pricing · Unit swap
- Jul 04, 2025Pricing · Terms change
- Aug 12, 2025Licensing + Packaging · Unit swap
- May 11, 2026Licensing · Unit swap
- Jun 01, 2026Packaging + Pricing · Repackage
- Jul 28, 2026Licensing + Packaging + Pricing · Access change
The move
Cursor launched a new plan called Cursor Start priced at ₹649/month (approximately USD 6.80/month) for developers in India, with local INR billing and UPI payments.
The SPP read
Cursor introduced a new subscription tier aimed exclusively at developers in India, billing in local currency and accepting UPI payments. The move adds a geographic access boundary and a distinct price point below existing plans, expanding where on the arc the vendor prices its AI coding capability. This sits at the intersection of a new edition entering the market and a deliberate access segmentation by country.
The move
In June 2026 Cursor repriced its Teams offering, introducing a Premium seat at $120 per user per month alongside the standard Teams seat.
The SPP read
The seat split into classes, but the classes differ on volume alone: Premium is the standard seat with a larger allowance, the meter collapsed into the packaging. A volume limit is a licensing-model construct, so this edition split spends the packaging layer doing the licensing layer's work and leaves packaging's own levers unpriced: priority access, longer-running sessions, the capability boundaries a team would actually pay to cross. What Premium sells is more of the same unit; what it could sell is different capabilities.
The move
Cursor is switching Bugbot from a $40 per seat per month subscription to usage-based billing for Teams and Individual plans, effective after June 8th, 2026 for existing customers.
The SPP read
A seat became a meter: Bugbot moved from a flat per-seat subscription to usage-based billing for teams. The direction runs against the market's comfort story, since product lines inside one vendor can walk the arc both ways, and a bounded seat fee became an unbounded meter on exactly the workload that agents multiply, code review.
The move
On August 12, 2025, Cursor announced two billing changes taking effect at each customer's next renewal after September 15: Teams agent usage moves from fixed request costs to variable request costs that scale with the work the agent does, the credit system already used on individual plans, and Auto for individuals stops being unlimited and counts toward included monthly usage at token rates.
The SPP read
Two meters moved at once, and both on renewal rather than on the announcement. Teams agent usage left fixed per-request pricing for variable credits that rise with the work an agent does, the unit individual plans already carried, so one billing unit now spans every tier. Auto for individuals lost its unlimited status and started drawing on included monthly usage at token rates. An allowance that stops being unlimited is a bounded meter, and a bounded meter is a price.
Read revised Sep 06, 2026Reason: Tightened for reading; the dated terms are unchanged.
Cursor announced two billing changes taking effect at each customer's next renewal after the stated cutover date.
The move
On July 4, 2025 Cursor publicly apologized for the rollout of its June 16 Pro pricing change, acknowledging it failed to clearly communicate that unlimited usage applied only to Auto mode, and offered full usage refunds for unexpected charges incurred between June 16 and July 4, 2025.
The SPP read
Three weeks after the unit changed, the vendor paid for the transition itself: a public apology naming the failure precisely, unlimited had quietly meant only one mode, and full refunds for every unexpected charge in the window. Reaction events are part of the arc, and this one prices the cost of moving a meter faster than customers can re-learn it: the refund is the vendor buying back the variance it had shifted onto buyers without telling them.
The move
Cursor's Pro plan is moving from request limits to compute limits, with all users receiving at least $20 of model inference at API prices per month.
The SPP read
The unit dropped beneath the request: a countable monthly allowance of fast requests became a pool of included frontier usage metered on compute, and the plan price stayed put while the thing it bought changed shape. The same announcement added an Ultra rung well above Pro, carrying a multiple of the included usage. A request was a unit the buyer could count; included-usage dollars are a unit the buyer must trust the conversion on. The rollout drew a public apology and refunds within weeks.
Read revised Sep 15, 2026Reason: reads carry the shape; the price points stay in the move (Chris, 2026-09-15)
The unit dropped beneath the request: five hundred countable fast requests became a pool of included frontier usage metered on compute, and the plan price stayed put while the thing it bought changed shape.
Planning a move like one on this arc, or countering one Cursor just made? Talk to a pricing expert before it ships: describe the move, and a pricing architect reads it against your own licensing, packaging, and pricing.
What we have written about Cursor.
Channel, OEM, and White-Label Pricing: The Grant Decides Before the Discount Does
Reseller margins, OEM royalties, and white-label fees are licensing questions first. What the unit grants a partner decides what any discount schedule can do.
The Value Metric Decision: How to Choose What You Charge For
The value metric — what unit your price attaches to — is the decision that determines whether your pricing model works. Here is how to choose…
Other vendors on the log.
All tracked vendors on the AI Pricing Observatory
Get this week’s verified AI pricing moves in your inbox.
The moves, the week they’re verified. A dated headline and a one-line read for each new move, with a link back to the full page.
One issue a week, only when something’s actually moved. Unsubscribe anytime from the confirmation email.
Prefer Slack? Get the weekly digest in Slack.
Primary sources behind the Cursor arc, dated.
| Date | Source | Record |
|---|---|---|
| cursor.com | primary ↗ · archived | |
| cursor.com | primary ↗ · archived | |
| cursor.com | primary ↗ · archived | |
| 2025 | ||
| cursor.com | primary ↗ · archived | |
| cursor.com | primary ↗ · archived | |
| cursor.com | primary ↗ · archived | |
Chris Mele
Ranked #1 on OpenView’s list of B2B SaaS pricing experts. Every read on this page is written by a pricing architect, never drafted by a model, backed by a team that has held CFO, CPO, and CIO seats inside software companies.
The claims ledger and citability gate do the heavy lifting on sourcing. The expert makes the calls only humans can: what a move actually changes under its label, and what it signals for the vendors around it.
Read more about Chris →Want this arc read against your own pricing architecture?
Watching how Cursor moves is one input. Deciding how your own licensing, packaging, and pricing should respond is a different discipline, and it is not something a dashboard can do for you.