Claim and evidence
Our recent pricing changes for individual plans were not communicated clearly, and we take full responsibility.Cursor · cursor.com · 2025-07-04
Primary
The company or founder describes the tactic and its result themselves: own blog, talk, filing.
Working · 2025-07 Cursor did this June 2025 and apologised July 4, 2025 for unclear communication.
What the numbers show
monthly usage pool on Cursor Pro after it dropped request-based limits (plan design)
cursor.comWhy it works
Request counts hide that harder tasks burn far more compute; a usage pool reflects cost but needs clear communication.
How to run it
- Define included usage
- Set auto/unlimited exceptions
- Show usage in dashboard
- Give advance notice
- Plan refunds for surprises
Before / after
Generalised wireframe of the pattern, not a copy of any company's screen.
Ways to run it
Design options to test, not promised results.
- Option AUsage pool with exceptions
Replace request counts with an included usage amount and keep some modes unlimited.
- Option BNotice and refunds
Announce ahead and refund unexpected charges after the switch, as Cursor did.
- Option CDashboard before switch
Show usage in the dashboard before the new limits apply so users can see their pattern.
Dated examples
- 2025
Cursor
Moved Pro from request limits to $20 included usage; apologised and refunded surprise charges.
“Our recent pricing changes for individual plans were not communicated clearly, and we take full responsibility.”
✓ quote checked word-for-word on the pagecursor.com · 2025-07-04
Does it still work?
Cursor did this June 2025 and apologised July 4, 2025 for unclear communication. source
Risks
- Backlash and refunds if comms are unclear
Sources
- cursor.com
“We moved from request-based pricing to $20 of included usage on Pro.”
✓ quote checked word-for-word on the page - cursor.com
“we will refund any unexpected charges you may have incurred for usage over the past 3 weeks.”
✓ quote checked word-for-word on the page
Change log
- 2026-11-20 — harvest v0.1 (revenue-expansion)