Why We Are Reconsidering GitHub Copilot Business After the New Usage Costs

[ahmed-oues]

🏷️ Discussion Type

Product Feedback

💬 Feature/Topic Area

Copilot in GitHub

Body

I have been using GitHub Copilot Business with a team plan, and honestly, the recent experience has been extremely disappointing.

Copilot used to feel like a useful productivity tool with predictable value. But now, with the new usage-based model and expensive premium requests, it feels completely different. One request alone burned around $19 and did not even finish the task properly.

That is not acceptable.

For a business plan, teams need predictable costs. We cannot work with a system where a single failed or incomplete request can consume a large amount of budget. If developers use Copilot daily, this kind of pricing can turn a monthly budget into something that disappears in a few days.

The worst part is that the value does not match the cost. If a request costs that much, it should at least complete the task correctly. Instead, we are paying more while getting less reliability.

Because of this, I am seriously considering cancelling GitHub Copilot Business. I also think other users and teams should carefully review their usage and costs before continuing, because this new model can become overwhelmingly expensive very quickly.

GitHub Support, please clarify:

Why can one request consume such a high amount?
Why are incomplete or failed requests still charged so heavily?
How is a small business supposed to predict monthly Copilot costs under this model?
Was this pricing change clearly communicated to Business users?

For now, this no longer feels like a fair or sustainable tool for small teams.

@githubsupport @GitHubCopilot

[github-actions[bot]]

💬 Your Product Feedback Has Been Submitted 🎉

Thank you for taking the time to share your insights with us! Your feedback is invaluable as we build a better GitHub experience for all our users.

Here's what you can expect moving forward ⏩

• Your input will be carefully reviewed and cataloged by members of our product teams. 
  • Due to the high volume of submissions, we may not always be able to provide individual responses.
  • Rest assured, your feedback will help chart our course for product improvements.
• Other users may engage with your post, sharing their own perspectives or experiences. 
• GitHub staff may reach out for further clarification or insight. 
  • We may 'Answer' your discussion if there is a current solution, workaround, or roadmap/changelog post related to the feedback.

Where to look to see what's shipping 👀

• Read the Changelog for real-time updates on the latest GitHub features, enhancements, and calls for feedback.
• Explore our Product Roadmap, which details upcoming major releases and initiatives.

What you can do in the meantime 💻

• Upvote and comment on other user feedback Discussions that resonate with you.
• Add more information at any point! Useful details include: use cases, relevant labels, desired outcomes, and any accompanying screenshots.

As a member of the GitHub community, your participation is essential. While we can't promise that every suggestion will be implemented, we want to emphasize that your feedback is instrumental in guiding our decisions and priorities.

Thank you once again for your contribution to making GitHub even better! We're grateful for your ongoing support and collaboration in shaping the future of our platform. ⭐

[jher7]

Predictable costs would be great. If your team is on VS code, this credit tracking extension I made with detailed analytics (daily/weekly spend, per-model, per-repo) might help them individually keep a better eye on spending

[suspex0]

Yes, unusable in the real world. Burned through the entire budget in 1 day, which usually is enough for at least 3 weeks.

[TroyCoderBoy]

They don't want your business or anyone else's. It was a money loser for them. But the way they have treated their customers will NEVER be forgotten.