It depends on the kind of work you do.

I'm in the academia, and Claude's performance in my field could be described as a very fast junior grad student. When I use Claude Code, I typically spend a few hours figuring out what needs to be done exactly, and describing it in sufficient detail. Then Claude does it in 30 minutes, while an actual student would need days. And then I spend anything from minutes to days evaluating the results, depending on if it needs to be tested with real data and how much weirdness those tests uncover.

But I also have other work to do beyond guiding the automated grad student. Which means my Claude Code usage rarely exceeds 1–2 hours/week.

I use Pro professionally and didn't hit limits most of the time. I believe I used up 5hr quota once or twice. We switched to Team sub and I'm on Standard(which is Pro x1.25 I believe). I don't vibecode entire applications, I ask it to make boilerplate, smaller, well scoped features or fix some errors. I don't let it go off with a prompt "make another netflix clone" cause I just don't see any real value in that

Just the Pro Plan Claude Code on its own? Maybe you could last a full day on just using Sonnet. Maybe one Opus dab in the morning to plan your Haiku/Sonnet day?

I have Pro Claude, Plus GPT and Pro Gemini. When one runs out I switch to another project on the next LLM. If I really need a task finished I'll restart it on another LLM, but I'm loathe to do that as it eats tokens just getting back up to speed.

I think it's more about how they approach their users in general that is the problem here.