Improving Kiro’s Pricing Tiers
### Feature Description Thank you for letting me try Kiro and for all the hard work you’ve poured into it so far, I really appreciate it, but I have to be honest: I was disappointed by the current pricing. Asking for more than 2.5x what Amazon Q charges makes me feel like you’re out of touch with the current competitive landscape. I think it’s worth taking a step back and considering whether the high demand you’re seeing is due to the product’s functionality, or simply because people get a free trial. I’m sorry to sound so critical, but I didn’t expect a company like yours to miss the mark so badly on pricing psychology. I’m just trying to share my honest frustration. 1. Giving your requests a cool name like "Vibe" won’t let you charge more for them. 2. A huge reason so many people are ditching Cursor is that they’ve lost transparency—and their prices are wildly out of line with competitors, with no enough value to show for it. 3. You’ve kept request limits flat at higher tiers when they should be increasing. Amazon Q’s $20 plan gives you 1,000 requests and their $40 plan gives you 3,000 requests, that’s an incentive. None of your upgrade options are enticing right now. 4. Making things more complicated than they need to be always backfires. Splitting requests into "Vibe" and "Spec" types interferes with how users budget their spending—and could easily backfire. If these request types really cost you differently, you need to handle that complexity on your end, not pass it
Posted by mustafa519 on Aug 1, 2025, 11:11 PM
Tags
Related issues
- Yeah, the plan is far too expensive for what it provides.
- Crashed demand after one of the big AI labs (probably Anthropic because they focus way too hard on expensive frontier models) become inso...
- /dev/random is much too expensive for this.
- Yeah, this always bugged me.
- A year ago, I had the opinion that it'd be too expensive for developers to support offline mode, peer to peer, or community servers after...
- The weird thing about this product is that its biggest competitor is "an old ipad." I feel like most of their target customer base alread...
Raise real-world problems, find people facing the same issue, and discuss solutions.2,000 issues0 comments
pricing (Other)
Yeah, the plan is far too expensive for what it provides.
NewCrashed demand after one of the big AI labs (probably Anthropic because they focus way too hard on expensive frontier models) become inso...
New/dev/random is much too expensive for this.
Yeah, this always bugged me.
A year ago, I had the opinion that it'd be too expensive for developers to support offline mode, peer to peer, or community servers after...
The weird thing about this product is that its biggest competitor is "an old ipad." I feel like most of their target customer base alread...
There's a talk from Travis Kalanick recently on a podcast about this.
>nobody ever bought German cars for their low prices, except the Beetle Huh?
Improving Kiro’s Pricing Tiers
### Feature Description Thank you for letting me try Kiro and for all the hard work you’ve poured into it so far, I really appreciate it, but I have to be honest: I was disappointed by the current pricing. Asking for more than 2.5x what Amazon Q charges makes me feel like you’re out of touch with the current competitive landscape. I think it’s worth taking a step back and considering whether the high demand you’re seeing is due to the product’s functionality, or simply because people get a free trial. I’m sorry to sound so critical, but I didn’t expect a company like yours to miss the mark so badly on pricing psychology. I’m just trying to share my honest frustration. 1. Giving your requests a cool name like "Vibe" won’t let you charge more for them. 2. A huge reason so many people are ditching Cursor is that they’ve lost transparency—and their prices are wildly out of line with competitors, with no enough value to show for it. 3. You’ve kept request limits flat at higher tiers when they should be increasing. Amazon Q’s $20 plan gives you 1,000 requests and their $40 plan gives you 3,000 requests, that’s an incentive. None of your upgrade options are enticing right now. 4. Making things more complicated than they need to be always backfires. Splitting requests into "Vibe" and "Spec" types interferes with how users budget their spending—and could easily backfire. If these request types really cost you differently, you need to handle that complexity on your end, not pass it
Comments (0)
No comments yet. Start the discussion.