Limiting usage is a bad feature

Feature request for product/service

– Other –

Describe the request

I pay for a monthly subscription, and I’m hitting usage limits mid-session. That’s not a feature, that’s a regression. Three things break when you do this.

1: the user loses control. I planned my work around having this tool available for the month I paid for. A hard cutoff mid-flow means I’m negotiating with a meter instead of building.

2: creativity gets killed. The best sessions are the ones where you stay in the zone. When you know a limit is coming, you start rationing your prompts, second-guessing whether to ask, and the whole thing becomes about managing scarcity instead of solving the problem.

3: it’s a weird deal. I paid for a full month of value. Being told I can only use it in time-sliced chunks means I’m not getting what I paid for. If the limit exists for infrastructure reasons, fine, be transparent about it. But don’t frame it as if I’m the problem for using the product.Give me the month I paid for. Full access, full value. Fix this.

Operating System (if it applies)

Windows 10/11

2 Likes

3 posts were merged into an existing topic: Introducing The X Subscription