Companies Are Throttling Employees’ AI Use Because It’s Too Expensive

The honeymoon is over. For months, companies handed out AI assistant seats like office supplies, betting on a productivity surge. Now, the bills are landing. A thread on Reddit’s r/technology that resonated with thousands of tech workers describes a new reality: IT and finance teams are quietly capping licenses, delaying renewals, or yanking access altogether.

The math is punishing. Microsoft Copilot costs $30 per user per month. OpenAI’s ChatGPT Enterprise is reportedly priced around $60 per user per month. For a mid-sized company with 5,000 seats, that’s a seven-figure annual line item - before any integration or training costs. That number gets attention in a budget review.

What we’re seeing is not a wholesale retreat. It’s an inflection point where AI tools move from experimental free-for-all to scrutinized investment. The same Reddit discussion describes measures like "throttling" - limiting the number of queries per employee or restricting access to certain departments. This is anecdotal, but the pattern is clear: the era of unlimited AI is ending.

This shift forces a decision that most leadership teams have avoided: is AI a utility or a strategic asset? When cost was invisible (or absorbed by pilot budgets), the answer didn’t matter. Now, per-seat pricing turns every license into a mini-business case.

The risk is binary. Under-throttle, and AI spending balloons without proof of value - a CFO’s nightmare. Over-throttle, and you strangle the experimentation that could uncover a competitive breakthrough. A large bank that limits Copilot to general counsel but blocks it from capital markets may save a few hundred thousand dollars while missing a document-analysis tool that reshapes deal flow.

The more strategic danger is that employees, facing restrictions, will route around IT. They’ll paste sensitive data into free consumer AI tools, creating compliance nightmares. So throttling doesn’t just manage cost - it shifts risk to the edges of the organization.

Start with an audit. Know exactly which departments and functions are using what tools, and at what cost. If you can’t map a license to a measurable output - time saved on a recurring report, faster contract review, fewer support tickets - it’s a target for removal.

Design a tiered access model. Power users (developers, researchers, analysts) get full seats. Role-limited users (frontline staff who need occasional summarization) get metered access or shared accounts. This isn’t just cost control; it’s about matching capability to need so that AI doesn’t become a distraction.

Set a quarterly AI spend review, not just an annual one. Require team leads to justify renewals with a simple ROI story: “X tool reduced weekly reporting time by three hours across 10 staff” is enough. Establish a central AI budget category separate from general IT, so spending is visible at the executive level.

Critically, forbid shadow AI. Make the approved tools the path of least resistance, and monitor for unsanctioned use. The goal is not prohibition - it’s to ensure that when an employee decides to use a free alternative, it’s a conscious policy violation, not an innocent workaround.

Over-throttling is the obvious trap. Cutting access to meet a budget number without understanding use cases kills the very experimentation that reveals high-value applications. If a competitor keeps the taps open on a critical process, the cost of playing catch-up dwarfs the saved license fees.

There’s also a cultural risk. Employees who have grown accustomed to AI assistance will see revocation as a loss of trust and a step backward. That can fuel turnover in talent markets where AI proficiency is a retention factor.

Then there’s vendor lock-in. As AI features become embedded in enterprise suites - Microsoft bundling Copilot into E5 licensing, for instance - the per-seat cost may appear to vanish, but the overall contract rises. Budget holders lose line-of-sight, and the ability to switch vendors shrinks. The CIO should treat every AI feature as a separate negotiation, not a free add-on.

Finally, treat the Reddit signal for what it is: a leading indicator, not a confirmed trend. The companies doing the throttling are not publishing press releases. If your own org hasn’t felt the squeeze yet, use this as a prompt to get ahead of the budgeting conversation, not a reason to panic.